Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement
RFC 5556

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

(Lisa Dusseault; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Mark Townsley; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Chris Newman; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Cullen Jennings; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Dan Romascanu; former steering group member) (was Discuss) No Objection

No Objection (2009-03-25)
No email
send info
Section 2.5 is titled 'Other Ethernet Protocol Extensions' while its content includes a list of protocols standardized in IEEE 802.1 which is not the Ethernet but the bridging and interworking working group in the IEEE 802.

(David Ward; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection (2009-01-29 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Supporting Russ Discuss regarding the TSV-dir review.

(Pasi Eronen; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Ross Callon; former steering group member) (was No Record, No Objection) No Objection

No Objection (2009-01-29)
No email
send info
Section 3.5 reads:

   ... TRILL must manage all traffic, including 
   multicast and broadcast traffic, so as not to create feedback loops 
   on Ethernet segments with multiple TRILL attachment points. This 
   includes multiple attachments to a single TRILL node and attachments 
   to multiple TRILL nodes. 

In reading this, I couldn't figure out what a "feedback loop" means in this context. Is this a potential problem with control traffic? Can this be clarified?

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection (2009-01-28)
No email
send info
  The Gen-ART Review by Francis Dupont posted on 27-Nov-2008 included
  some editorial comments.

  - 2.1 page 4 (twice): Mbps -> Mbits/s ?
  - 2.3 page 6: perhaps the RSTP abbrev should be introduced (IMHO it is
    far from to be necessary)?
  - 5 page 14: SEND was published some years ago so why you said it is
    "under development"?
  - Author's Addresses -> Authors' Address
  - +1 (310) ... -> +1 310 ... (according to ITU-T E.123)

(Tim Polk; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info