datatracker.ietf.org
Sign in
Version 5.8.1, 2014-12-18
Report a bug

IESG Agenda: 2014-12-18

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: December 18, 2014

  o Barry Leiba to find a Designated Expert for RFC 3688 [IANA #788722].

  o Barry Leiba to find a Designated Expert for LDAP.

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-mpls-tp-te-mib [txt] - IETF stream
MPLS-TP Traffic Engineering (TE) Management Information Base (MIB) (Proposed Standard)
Token: Adrian Farrel (rtg area)
IANA Review: Version Changed - Review Needed
Consensus: Yes
draft-ietf-json-text-sequence [txt] - IETF stream
JavaScript Object Notation (JSON) Text Sequences (Proposed Standard)
Token: Pete Resnick (app area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes

2.1.2 Returning Items

draft-ietf-ppsp-peer-protocol [txt] - IETF stream
Peer-to-Peer Streaming Peer Protocol (PPSPP) (Proposed Standard)
Token: Martin Stiemerling (tsv area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes
draft-ietf-eman-battery-mib [txt] - IETF stream
Definition of Managed Objects for Battery Monitoring (Proposed Standard)
Token: Joel Jaeggli (ops area)
IANA Review: Version Changed - Review Needed
Consensus: Yes

2.1.3 For Action

draft-ietf-eman-energy-monitoring-mib [txt] - IETF stream
Power, Energy Monitoring and Control MIB (Proposed Standard)
IPR:

Token: Joel Jaeggli (ops area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes
draft-ietf-eman-energy-aware-mib [txt] - IETF stream
Energy Object Context MIB (Proposed Standard)
IPR:

Token: Joel Jaeggli (ops area)
IANA Review: IANA OK - Actions Needed
Consensus: Yes
draft-ietf-opsawg-capwap-hybridmac [txt] - IETF stream
IEEE 802.11 MAC Profile for CAPWAP (Proposed Standard)
Token: Benoit Claise (ops area)
IANA Review: Version Changed - Review Needed
Consensus: Yes

2.2 Individual Submissions

2.2.1 New Items

NONE

2.2.2 Returning Items

NONE

2.2.3 For Action

draft-josefsson-pkix-textual [txt] - IETF stream
Textual Encodings of PKIX, PKCS, and CMS Structures (Proposed Standard)
Token: Kathleen Moriarty (None area)
IANA Review: IANA OK - No Actions Needed
Consensus: Yes

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

draft-ietf-mptcp-attacks [txt] - IETF stream
Analysis of MPTCP residual threats and possible fixes (Informational)
Token: Martin Stiemerling (tsv area)
IANA Review: IANA OK - No Actions Needed
Consensus: Yes

3.1.2 Returning Items

NONE

3.1.3 For Action

draft-ietf-jose-cookbook [txt] - IETF stream
Examples of Protecting Content using JavaScript Object Signing and Encryption (JOSE) (Informational)
Token: Kathleen Moriarty (sec area)
IANA Review: IANA OK - No Actions Needed
Consensus: Yes
draft-ietf-ianaplan-icg-response [txt] - IETF stream
Draft Response to the Internet Coordination Group Request for Proposals on the IANA protocol parameters registries (Informational)
Token: Jari Arkko (gen 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

NONE

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

NONE

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

NONE

3.4.2 Returning Items

NONE

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

NONE

5. IAB News We Can Use

6. Management Issues

6.1 IESG Re-organization to-do list and timeline discussion (Brian Haberman)

6.2 ISOC-ICANN Meeting (Jari Arkko)

7. Working Group News