Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers
RFC 6205

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

Lars Eggert No Objection

(Adrian Farrel; former steering group member) Yes

Yes ()
No email
send info

(Alexey Melnikov; former steering group member) No Objection

No Objection (2011-01-20)
No email
send info
I am missing some text about byte order for 16bit fields.

(Dan Romascanu; former steering group member) No Objection

No Objection ()
No email
send info

(David Harrington; former steering group member) No Objection

No Objection ()
No email
send info

(Gonzalo Camarillo; former steering group member) No Objection

No Objection ()
No email
send info

(Peter Saint-Andre; former steering group member) No Objection

No Objection ()
No email
send info

(Ralph Droms; former steering group member) No Objection

No Objection ()
No email
send info

(Robert Sparks; former steering group member) No Objection

No Objection ()
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Sean Turner; former steering group member) No Objection

No Objection ()
No email
send info

(Stewart Bryant; former steering group member) No Objection

No Objection (2011-01-19)
No email
send info
"In the scenario of Figure 1, consider the setting up of a bidirectional LSP from ingress switch 1 to egress switch 9 using
 GMPLS RSVP-TE."

Figure 1 shows them as nodes

=======

To deal with the widening scope of MPLS into the optical and time domains

I think that you mean ... optical switching and time division multiplexing domains.

======= 
In a case, the label indicates the wavelength to be used for the LSP. 

Do you mean "In this case.." ?

======

(Tim Polk; former steering group member) No Objection

No Objection ()
No email
send info