[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[OPS-NM] FW: PRELIMINARY Agenda and Package for July 19, 2007 Telechat
Please find below the preliminary agenda of the IESG telechat on 7/19. If there are any comments or concerns please let me know until Wednesday 7/18 COB.
Dan
2.1 WG Submissions
2.1.1 New Item
o draft-ietf-sipping-v6-transition-05.txt
IPv6 Transition in the Session Initiation Protocol (SIP) (Proposed
Standard) - 1 of 5
Token: Jon Peterson
o draft-ietf-xcon-bfcp-connection-05.txt
Connection Establishment in the Binary Floor Control Protocol (BFCP)
(Proposed Standard) - 2 of 5
Note: Adam Roach is the PROTO Shepherd Note to SEC ADs for IESG
review: We
need to look at IPv6 addresses and certificates in this draft. May
result
in some small changes to document.
Token: Cullen Jennings
o draft-ietf-rmt-bb-fec-raptor-object-09.txt
Raptor Forward Error Correction Scheme for Object Delivery (Proposed
Standard) - 3 of 5
Token: Magnus Westerlund
o draft-ietf-rohc-sigcomp-sip-07.txt
Applying Signaling Compression (SigComp) to the Session Initiation
Protocol
(SIP) (Proposed Standard) - 4 of 5
Token: Magnus Westerlund
o draft-ietf-sip-acr-code-05.txt
Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)
(Proposed Standard) - 5 of 5
Note: The document shepherd is Dean Willis. Note IETF LC ends the day
of
the call. Cullen will hold discuss on waiting for LC comments.
Token: Cullen Jennings
2.1.2 Returning Item
o draft-ietf-dhc-server-override-04.txt
DHCP Server Identifier Override Suboption (Proposed Standard) - 1 of 1
Note: Bringing this document back to agenda, hopefully with the past
issue
solved
Token: Jari Arkko
2.2 Individual Submissions
2.2.1 New Item
o draft-hutzler-spamops-08.txt
Email Submission Operations: Access and Accountability Requirements
(BCP) -
1 of 1
Note: Dave Crocker is the PROTO shepherd.
Token: Dan Romascanu
2.2.2 Returning Item
NONE
3. Document Actions
3.1 WG Submissions
Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"
3.1.1 New Item
o draft-ietf-bmwg-igp-dataplane-conv-meth-13.txt
Benchmarking Methodology for IGP Data Plane Route Convergence
(Informational) - 1 of 3
Token: Ron Bonica
o draft-ietf-bmwg-igp-dataplane-conv-term-13.txt
Terminology for Benchmarking IGP Data Plane Route Convergence
(Informational) - 2 of 3
Token: Ron Bonica
o draft-ietf-bmwg-igp-dataplane-conv-app-13.txt
Considerations for Benchmarking IGP Data Plane Route Convergence
(Informational) - 3 of 3
Token: Ron Bonica
3.1.2 Returning Item
NONE
3.2 Individual Submissions Via AD
Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"
3.2.1 New Item
o Two-document ballot: - 1 of 4
- draft-weiler-dnssec-dlv-iana-00.txt
DNSSEC Lookaside Validation (DLV) IANA Registry (Informational)
- draft-weiler-dnssec-dlv-03.txt
DNSSEC Lookaside Validation (DLV) (Informational)
Token: Russ Housley
o draft-huston-6to4-reverse-dns-07.txt
6to4 Reverse DNS Delegation Specification (Informational) - 2 of 4
Note: Document shepherd: Peter Koch <pk at DENIC.DE> Individual
submission sponsored by AD
Token: Ron Bonica
o draft-taylor-megaco-obsol3525-01.txt
Reclassification of RFC 3525 to Historic (Historic) - 3 of 4
Token: Cullen Jennings
o draft-dawkins-nomcom-start-earlier-01.txt
IAB and IESG Selection, Confirmation, and Recall Process: Revision of
the
Nominating and Recall Committees Timeline (Informational) - 4 of 4
Token: Russ Housley
3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
The IESG will use RFC 3932 responses: 1) The IESG has not
found any conflict between this document and IETF work; 2) The
IESG thinks that this work is related to IETF work done in WG
<X>, but this does not prevent publishing; 3) The IESG thinks
that publication is harmful to work in WG <X> and recommends
not publishing at this time; 4) The IESG thinks that this
document violates the IETF procedures for <X> and should
therefore not be published without IETF review and IESG
approval; 5) The IESG thinks that this document extends an
IETF protocol in a way that requires IETF review and should
therefore not be published without IETF review and IESG approval.
Other matters may be recorded in comments to be passed on
to the RFC Editor as community review of the document.
3.3.1 New Item
o draft-foschiano-udld-03.txt
Cisco Systems UniDirectional Link Detection (UDLD) Protocol
(Informational)
- 1 of 1
Token: Russ Housley
_______________________________________________
OPS-NM mailing list
OPS-NM at ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm