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

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

(Russ Housley; former steering group member) Yes

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

(Alex Zinin; former steering group member) No Objection

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

(Allison Mankin; former steering group member) No Objection

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

(Bert Wijnen; former steering group member) No Objection

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

(Bill Fenner; former steering group member) No Objection

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

(Brian Carpenter; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

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

(Jon Peterson; former steering group member) No Objection

No Objection (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.

(Margaret Cullen; former steering group member) No Objection

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

(Mark Townsley; former steering group member) No Objection

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

(Sam Hartman; former steering group member) No Objection

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

(Scott Hollenbeck; former steering group member) No Objection

No Objection (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.

(Ted Hardie; former steering group member) No Objection

No Objection (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?