DCCP Transport Parameter for RSerPool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

Magnus has asked me to make sure that using in

http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-15.txt

the following text make sense to DCCP experts.

Any comments?

Best regards
Michael



3.3.  DCCP Transport Parameter

   This parameter defines a TLV that describes a user transport using
   DCCP protocol.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Type = 0x3             |      Length = variable        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         DCCP port             |          (reserved)           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      DCCP service code                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   :                     IPv4 or IPv6 Address                      :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Length: 16 bits (unsigned integer)
      Indicates the entire length of the parameter in number of octets,
      including the Type, Length, DCCP port, reserved fields, and IP
      address parameter.

   DCCP port: 16 bits (unsigned integer)
      The DCCP port number signed to this DCCP user transport.

   DCCP service code: 32 bits (unsigned integer)
      The DCCP service code signed to this DCCP user transport.

   IPv4 or IPv6 Address
      Indicates an IPv4 or IPv6 address parameter (as defined above in
Section 3.1 and Section 3.2) assigned to this DCCP user transport.
      Unlike in an SCTP transport parameter, only one IP address
      parameter can be present in a DCCP transport parameter.

Note: A DCCP port MUST NOT be used for control information. For this
   reason, no Transport Use field is provided.  DCCP MUST always be
   treated as a "Data Only" type transport use.




[Index of Archives]     [Linux Kernel Development]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]

  Powered by Linux