BGP Traffic Engineering Attribute
RFC 5543

Note: This ballot was opened for revision 04 and is now closed.

(Jari Arkko) Yes

(Mark Townsley) Yes

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

Lars Eggert No Objection

(Pasi Eronen) No Objection

(Russ Housley) No Objection

Comment (2009-01-29)
No email
send info
  Please fix the email address for Yakov to be instead of as listed in the draft.

(Cullen Jennings) No Objection

(Chris Newman) No Objection

(Jon Peterson) No Objection

(Tim Polk) No Objection

(Dan Romascanu) No Objection

(Magnus Westerlund) No Objection

Comment (2009-01-29)
No email
send info
Section 3:

   When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,
   the Switching Capability specific information field includes Minimum
   LSP Bandwidth and Interface MTU.

       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
      |                  Minimum LSP Bandwidth                        |
      |           Interface MTU       |

   The Minimum LSP Bandwidth is encoded in a 4 octet field in the IEEE
   floating point format.  The units are bytes (not bits!) per second.
   The Interface MTU is encoded as a 2 octet integer.

I don't think this text is that clear. First of all, is the MTU value in octets or bits? I also assume that it is an unsigned integer, rather than a signed which the current language defaults to. 

The I wonder, is it clear on what level the MTU measurement is performed on. I know to little about what is actually represented by PSC-1 to PSC-4 to determine if the point in the stack the measurement is taken is always clear.

(David Ward) Recuse