Re: [amqp] new addressing draft for monday

[Ted Ross <tross@redhat.com>]

Thanks for the Update.

I have a high-level question:  What is the intended scope of this 
specification?

I think that the purpose of the addressing specification should be to 
define the format of addresses and their semantics as they appear in the 
various protocol fields ('to'/'reply-to' on message delivery; 
'source'/'target' on link-attach).  I believe that this specification 
should not dictate how networks propagate route information (section 
4.7).  I expect that three or four such mechanisms may evolve over time, 
hopefully each served well by this addressing specification.

Also, the issues I raised last week apply to this version as well.

Regards,

-Ted

On 09/14/2013 07:04 AM, Rafael Schloming wrote:
> I've uploaded a new addressing draft for the Monday TC meeting:
>
> https://www.oasis-open.org/apps/org/workgroup/amqp/download.php/50701/amqp-addressing-v1.0-wd01.pdf
>
> Changes from the previous draft address (most of) the notes from the
> last addressing meeting. I've copied the meeting notes here so people
> have an idea where to look for the changes:
>
>   Section 3:
>     - add examples of service records including non tcp
>     - define what happens for multiple service records, is there a
>       preference order?
>     - link out to a registry for the protocol fields
>
>   Section 4.1:
>     - Second sentance: that should be rewritten to speak of equivalence
>       between to matching target and to being null
>
>   Section 4.2:
>     - define relay node first and seperately
>     - add examples with patterns
>     - make anonymous terminus section be solely the definition of the
>       capability that indicates the null address refers to a relay node
>     - what happens when a message can't be relayed?
>
>   Move Patterns -> Routing
>
>   Section 4.5:
>     - add node property to advertise this capability (if you advertize
>       to me I am capable of routing back to you)
>     - do relay nodes support this property?
>     - call out use in request/response with some sort of examples
>
>   Update all the meta sections
>
> --Rafael
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php