datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

IESG Agenda: 2014-04-24

See also: Documents on Future IESG Telechat Agendas and IESG Discuss Positions.

1. Administrivia

1.1 Roll Call

1.2 Bash the Agenda

1.3 Approval of the Minutes of Past Telechats

1.4 List of Remaining Action Items from Last Telechat

OUTSTANDING TASKS

     Last updated: April 14, 2014

  o Joel Jaeggli to write a note to ICANN indicating that the IESG is 
    considering allocating Special-use Top-Level Domain Names for Peer-
    to-Peer Applications and requesting feedback.

  o Ted Lemon to propose changes to the DISCUSS criteria to handle 
    pervasive monitoring.

2. Protocol Actions

Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?"

2.1 WG Submissions

2.1.1 New Items

draft-ietf-precis-framework [txt] - IETF stream
PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols (Proposed Standard)
Token: Pete Resnick (app area)
IANA Review: IANA - Review Needed
Consensus: Yes
Last call expires: 2014-04-23
draft-ietf-mpls-ldp-applicability-label-adv [txt] - IETF stream
Label Advertisement Discipline for LDP FECs (Proposed Standard)
Token: Adrian Farrel (rtg area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes
draft-ietf-idr-aigp [txt] - IETF stream
The Accumulated IGP Metric Attribute for BGP (Proposed Standard)
IPR:

Token: Alia Atlas (rtg area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes

2.1.2 Returning Items

NONE

2.2 Individual Submissions

2.2.1 New Items

NONE

2.2.2 Returning Items

NONE

2.3 Status Changes

2.3.1 New Items

NONE

2.3.2 Returning Items

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 Items

NONE

3.1.2 Returning Items

draft-ietf-opsec-vpn-leakages [txt] - IETF stream
Virtual Private Network (VPN) traffic leakages in dual-stack hosts/ networks (Informational)
Token: Joel Jaeggli (ops area)
IANA Review: Version Changed - Review Needed
Consensus: Yes

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 Items

NONE

3.2.2 Returning Items

draft-housley-pkix-oids [txt] - IETF stream
Object Identifier Registry for the PKIX Working Group (Informational)
Token: Stephen Farrell (sec area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes

3.3 Status Changes

Reviews should focus on these questions: "Are the proposed changes to document status appropriate? Have all requirements for such a change been met? If not, what changes to the proposal would make it appropriate?"

3.3.1 New Items

status-change-ipv4-address-mapping-classes-to-historic [txt] - IETF stream
RFC 796 (Address Mappings) to Historic (None)
Token: Ted Lemon (ietf area)

3.3.2 Returning Items

NONE

3.4 IRTF and Independent Submission Stream Documents

The IESG will use RFC 5742 responses: 1) The IESG has concluded that there is no conflict between this document and IETF work; 2) The IESG has concluded that this work is related to IETF work done in WG <X>, but this relationship does not prevent publishing; 3) The IESG has concluded that publication could potentially disrupt the IETF work done in WG <X> and recommends not publishing the document at this time; 4) The IESG has concluded that this document violates IETF procedures for <Y> and should therefore not be published without IETF review and IESG approval; or 5) The IESG has concluded 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.

The document shepherd must propose one of these responses in the conflict-review document, and the document shepherd may supply text for an IESG Note in that document. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd and agreement that the IESG should request inclusion of the IESG Note.

Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document.

3.4.1 New Items

conflict-review-dunbar-armd-arp-nd-scaling-practices-01 [txt]
IETF conflict review for draft-dunbar-armd-arp-nd-scaling-practices
draft-dunbar-armd-arp-nd-scaling-practices-07 [txt]
Practices for scaling ARP and ND for large data centers (ISE: Informational)
Token: Brian Haberman

3.4.2 Returning Items

conflict-review-andrews-dnsext-expire-00 [txt]
IETF conflict review for draft-andrews-dnsext-expire
draft-andrews-dnsext-expire-04 [txt]
EDNS EXPIRE OPTION (ISE: Experimental)
Token: Ted Lemon

4. Working Group Actions

4.1 WG Creation

4.1.1 Proposed for IETF Review

NONE

4.1.2 Proposed for Approval

NONE

4.2 WG Rechartering

4.2.1 Under Evaluation for IETF Review

NONE

4.2.2 Proposed for Approval

JavaScript Object Notation (json)
Area: APP (Pete Resnick)

5. IAB News We Can Use

6. Management Issues

6.1 Approve Russ Housley as designated expert (Stephen Farrell)

6.2 RFC 7001 designated experts and independent submissions (Barry Leiba)

7. Working Group News