draft-ietf-sigtran-v5ua-04.txt

[Randy Bush <randy@psg.com>]

summary:

sigtran in general, and this document in particular, is about using
ip to transport commands to sushi delivery trucks.

---

darn hard to find IP in draft-ietf-sigtran-v5ua-04.txt.  it is an
extension of RFC , which seems to be an example of nothing to do
with the internet except it uses it as a signaling transport.  in
particular, this document seems to have only the following
references to anything internet

    1.5.  Client/Server Model

    The SCTP (and UDP/TCP) registered User Port Number Assignment
    for V5UA is 5675.

and

    3.  SCTP Stream Management

    A single SCTP stream SHOULD be used for grouping all of the
    following protocols together: BCC, Link Control, Control and
    PSTN protocol on a specific C-channel.  A separate SCTP stream
    SHOULD be used for the Protection protocol on a specific
    C-channel. One SCTP stream SHOULD be used for all ISDN user
    ports on a specific C-channel. One single stream SHOULD NOT be
    used to carry data of more than one C-channel.

    In addition, one separate SCTP stream SHOULD be used for all
    MPH (link related) messages.

and the iana considerations assigning an sctp payload ident and the
port number.


of course, this is a generic issue with sigtran et alia.  i will
not formally stop this document, but wish to point out the issue
of inconsistancy with our recommending that the rfced not publish
draft-ogura-mapos-nsp-multiexp-02.txt.

randy