-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: WD03
-
Fix Version/s: WD04
-
Component/s: Global Addressing
-
Labels:None
Would it make more sense for the text
it is also
necessary to define a standard pattern notation to identify address spaces as opposed to individual addresses,
e.g. to differentiate between the region of addresses prefixed with "/domain" vs the specific address "/domain".
To that end, this section also defines an address pattern syntax for use in identifying regions of the global AMQP
address space. Note that this is analogous to the role that CIDR notation defined in IETF RFC 4632 [RFC4632]
plays in IP routing. There is defined notation for both specific network endpoints such as "18.239.0.1" as well as
notation for identifying an entire region of the address space, e.g. "18.239.0.0/16".
To be moved into section 4.2 Address Patterns. I assume that text (currently in the intro for Chapter 4) is the justification for the patterns, but it is not entirely evident that that is what that paragraph is saying, nor is there then any into within 4.2 itself.
Also I wonder if address patterns might be moved to later in the chapter... they seem somewhat of a jump from routable messages