A Transport Network View of the Link Management Protocol (LMP)
RFC 4394

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

(Alex Zinin; former steering group member) Yes

Yes ()
No email
send info

(Allison Mankin; former steering group member) No Objection

No Objection ()
No email
send info

(Bert Wijnen; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Margaret Cullen; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection (2005-09-14)
No email
send info
  It is pretty late in the document before the reader learns which
  ITU-T Recommendations make up the "the ITU-T discovery work."  I
  think this should be defined in the front of the document.

(Ted Hardie; former steering group member) No Objection

No Objection ()
No email
send info

(Brian Carpenter; former steering group member) No Record

No Record (2005-09-14)
No email
send info
This draft illustrates a major terminology confusion that we have
between the IETF and the ITU-T.

We use "transport" to mean Layer 4 transport protocols and issues.

They use "transport" to mean, well, I don't know for sure,
but it seems to mean "moving bits."

I believe this terminology clash needs to be explained right at
the beginning of this draft - even its title fooled me.

Extreme example: in this draft, TCP means Termination Connection Point