Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA)
RFC 4442

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

(Russ Housley) Yes

(Brian Carpenter) (was Discuss) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

Comment (2005-12-12 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The document notes that NTP may be used as an out-of-band mechanism for synchronization, and it assigns this a SHOULD when piggybacking timestamp information is not appropriate (as when the
media receiver is not the MIKEY initiator).  Is there any general set of characteristics for out-of-band mechanisms which would allow someone to know whether a mechanism might substitute for NTP in a specific environment?

(Sam Hartman) No Objection

(Scott Hollenbeck) No Objection

Comment (2005-12-06 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The "IANA Considerations" section should explain which registry must be used to register the described parameters and values.

(David Kessens) No Objection

(Allison Mankin) No Objection

(Jon Peterson) No Objection

Comment (2005-12-14 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The expansion of the acronyms SIP and SDP, and inclusion of corresponding references for those protocols, might be appropriate.

(Mark Townsley) No Objection

(Bert Wijnen) No Objection

(Alex Zinin) No Objection