[OASIS Issue Tracker] (AMQP-134) Undefined use of "network"

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Clemens Vasters created AMQP-134:
------------------------------------

             Summary: Undefined use of "network"
                 Key: AMQP-134
                 URL: https://issues.oasis-open.org/browse/AMQP-134
             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
          Issue Type: Bug
          Components: Response Routing 
            Reporter: Clemens Vasters


This spec, just as the base AMQP 1.0 spec, uses a notion of "AMQP network" and also "sub-network" that has no formal definition in the AMQP specification set. This spec also does not refer to the "intermediary" term that is mentioned several times in the AMQP 1.0 spec, and it must be assumed that the "gateway" nodes that are discussed here are acting as such intermediaries.

For readers not deeply unfamiliar with the idea that AMQP has its own idea of "network", there is also substantial confusion risk with the common concept of "network" (and "sub-network"), which usually refers to the Internet Protocol Stack notion.

The terms "address domain" and "address" are also used without definition. The closest to a definition of "address" is in AMQP 1.0 Sec 3.5 where the term "address" is defined, with a note in parens, as to be resolved to a "node within that container". An address domain as illustrated here appears to span containers, which raises the question of how containers are being addressed on the AMQP network (vs. the underlying IP network)  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)