A YANG Data Model for SNMP Configuration
draft-ietf-netmod-snmp-cfg-08
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2014-12-16
|
08 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2014-11-28
|
08 | Jean Mahoney | Closed request for Telechat review by GENART with state 'No Response' |
2014-11-17
|
08 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
2014-11-02
|
08 | (System) | RFC Editor state changed to RFC-EDITOR from AUTH |
2014-10-27
|
08 | (System) | RFC Editor state changed to AUTH from EDIT |
2014-10-24
|
08 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2014-10-23
|
08 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
2014-10-22
|
08 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2014-10-22
|
08 | (System) | IANA Action state changed to In Progress from On Hold |
2014-10-06
|
08 | (System) | IANA Action state changed to On Hold from In Progress |
2014-10-06
|
08 | (System) | IANA Action state changed to In Progress from On Hold |
2014-09-22
|
08 | Cindy Morgan | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2014-09-22
|
08 | (System) | RFC Editor state changed to EDIT |
2014-09-22
|
08 | (System) | Announcement was received by RFC Editor |
2014-09-22
|
08 | (System) | IANA Action state changed to On Hold from In Progress |
2014-09-22
|
08 | (System) | IANA Action state changed to In Progress |
2014-09-22
|
08 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent::AD Followup |
2014-09-22
|
08 | Amy Vezza | IESG has approved the document |
2014-09-22
|
08 | Amy Vezza | Closed "Approve" ballot |
2014-09-22
|
08 | Amy Vezza | Ballot approval text was generated |
2014-09-22
|
08 | Amy Vezza | Ballot writeup was changed |
2014-09-19
|
08 | Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'No Response' |
2014-09-18
|
08 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2014-09-18
|
08 | Martin Björklund | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2014-09-18
|
08 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-08.txt |
2014-09-18
|
07 | Cindy Morgan | IESG state changed to Approved-announcement to be sent::Revised I-D Needed from IESG Evaluation |
2014-09-18
|
07 | Alia Atlas | [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas |
2014-09-18
|
07 | Ted Lemon | [Ballot Position Update] New position, No Objection, has been recorded for Ted Lemon |
2014-09-18
|
07 | Adrian Farrel | [Ballot Position Update] New position, No Objection, has been recorded for Adrian Farrel |
2014-09-17
|
07 | Pete Resnick | [Ballot Position Update] New position, No Objection, has been recorded for Pete Resnick |
2014-09-17
|
07 | Richard Barnes | [Ballot comment] Though a YANG model for SNMP feels a little self-referential. Do we have a NETCONF MIB, just for completeness? ;) |
2014-09-17
|
07 | Richard Barnes | [Ballot Position Update] New position, No Objection, has been recorded for Richard Barnes |
2014-09-17
|
07 | Barry Leiba | [Ballot comment] -- Section 4.1 -- identity san-rfc822-name { base cert-to-name; description "Maps … [Ballot comment] -- Section 4.1 -- identity san-rfc822-name { base cert-to-name; description "Maps a subjectAltName's rfc822Name to a name. The local part of the rfc822Name is passed unaltered but the host-part of the name must be passed in lowercase. This mapping results in a 1:1 correspondence between equivalent subjectAltName rfc822Name values and name values except that the host-part of the name MUST be passed in lowercase. For example, the rfc822Name field FooBar@Example.COM is mapped to name FooBar@example.com."; reference "SNMP-TLS-TM-MIB.snmpTlstmCertSANRFC822Name"; } The repetition in here, and the two different "must/MUST be passed in lowercase" seems odd. Can this be reworded to say the same thing but remove the odd repetition? |
2014-09-17
|
07 | Barry Leiba | [Ballot Position Update] New position, No Objection, has been recorded for Barry Leiba |
2014-09-17
|
07 | Jari Arkko | [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko |
2014-09-16
|
07 | Alissa Cooper | [Ballot comment] Section 4.10: I know the term "privacy" is used here to match how it's used in RFC 3414, but given that we … [Ballot comment] Section 4.10: I know the term "privacy" is used here to match how it's used in RFC 3414, but given that we now know that privacy can be about many things beyond confidentiality, I'm wondering if it's possible to have the language here match that current understanding a bit better, e.g.: s/"when privacy is used, authentication must also be used";/"when privacy (confidentiality) is used, authentication must also be used"; If the container could be called "confidentiality" rather than "priv" that would be good too. |
2014-09-16
|
07 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2014-09-16
|
07 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
2014-09-16
|
07 | Stephen Farrell | [Ballot comment] - 2.7: I wondered if this gatewaying would change the security considerations for SNMP proxies? (Not that I really know what those are, … [Ballot comment] - 2.7: I wondered if this gatewaying would change the security considerations for SNMP proxies? (Not that I really know what those are, but combining g/ws and proxies is often a way to create new vulnerabilities.) - 2.10: "However, the localized key can be changed. This implies that if the engine id is changed, all users keys need to be changed as well." Can you explain that a bit more? It doesn't sound so good, but I'm not sure if its avoidable or not. And I don't think that paragraph is clear as-is to be honest. - 2.12 (and more generally): I had a look at this and how it maps to RFC6353 and it wasn't entirely clear to me how the client|server-fingerprint here mapped to a 6353 implementation. For example, is the fingerprint a fingerprint of the SubjectPublicKeyInfo (as used in DANE and elsewhere), or of the full cert? Similarly can it be a fingerprint for an end-entity cert or of any or a particular CA in a (or any?) chain that certifies the client cert? I think most of this is somewhere here or in the refs but just wanted to check. - 2.12: (and more generally) Did the WG consider the kinds of issue that the websec WG considered for HTTP pinngin? For example, HTTP pins allow for a backup pin in case you brick your site and the same might (or might not) be useful here. - Should (or are) some or all of the 2.x things mandatory to implement? That wasn't clear to me. |
2014-09-16
|
07 | Stephen Farrell | [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell |
2014-09-15
|
07 | Martin Stiemerling | [Ballot Position Update] New position, No Objection, has been recorded for Martin Stiemerling |
2014-09-15
|
07 | Brian Haberman | [Ballot Position Update] New position, No Objection, has been recorded for Brian Haberman |
2014-09-14
|
07 | Joel Jaeggli | [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli |
2014-09-11
|
07 | Jean Mahoney | Request for Telechat review by GENART is assigned to Roni Even |
2014-09-11
|
07 | Jean Mahoney | Request for Telechat review by GENART is assigned to Roni Even |
2014-09-05
|
07 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2014-09-04
|
07 | (System) | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
2014-09-04
|
07 | Benoît Claise | Ballot has been issued |
2014-09-04
|
07 | Benoît Claise | [Ballot Position Update] New position, Yes, has been recorded for Benoit Claise |
2014-09-04
|
07 | Benoît Claise | Created "Approve" ballot |
2014-09-04
|
07 | Benoît Claise | Ballot writeup was changed |
2014-09-04
|
07 | Benoît Claise | Changed consensus to Yes from Unknown |
2014-09-04
|
07 | Benoît Claise | Placed on agenda for telechat - 2014-09-18 |
2014-09-04
|
07 | Benoît Claise | IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead |
2014-09-04
|
07 | Benoît Claise | IESG state changed to Waiting for AD Go-Ahead from Waiting for Writeup |
2014-08-15
|
07 | Tero Kivinen | Request for Last Call review by SECDIR Completed: Ready. Reviewer: Phillip Hallam-Baker. |
2014-08-13
|
07 | Martin Björklund | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
2014-08-13
|
07 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-07.txt |
2014-08-11
|
06 | (System) | IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed |
2014-08-11
|
06 | Pearl Liang | IESG/Authors/WG Chairs: IANA has reviewed draft-ietf-netmod-snmp-cfg-06. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon … IESG/Authors/WG Chairs: IANA has reviewed draft-ietf-netmod-snmp-cfg-06. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible. We received the following comments/questions from the IANA's reviewer: IANA understands that, upon approval of this document, there are three actions which IANA must complete. First,in the IETF XML namespaces registry located at: http://www.iana.org/assignments/xml-registry/ a new namespace is to be registered as follows: ID: yang:ietf-snmp URI: urn:ietf:params:xml:ns:yang:ietf-snmp Filename: Reference: [ RFC-to-be ] Second, in the YANG Module Names subregistry of the YANG Parameters registry located at: http://www.iana.org/assignments/yang-parameters/ two, new module names will be added to the registry as follows: Name: ietf-snmp Namespace: urn:ietf:params:xml:ns:yang:ietf-snmp Prefix: snmp Module: Reference: [ RFC-to-be ] Name: ietf-x509-cert-to-name Namespace: urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name Prefix: x509c2n Module: Reference: [ RFC-to-be ] Third, also in the YANG Module Names subregistry of the YANG Parameters registry located at: http://www.iana.org/assignments/yang-parameters/ ten, new submodule names for module 'ietf-snmp' will be added to the registry as follows: Name: ietf-snmp-common Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-engine Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-community Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-notification Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-target Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-vacm Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-usm Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-tsm Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-tls Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] Name: ietf-snmp-ssh Namespace: Prefix: Module: ietf-snmp Reference: [ RFC-to-be ] IANA understands that these three actions are the only ones required to be completed upon approval of this document. Note: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. |
2014-08-11
|
06 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2014-08-01
|
06 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Phillip Hallam-Baker |
2014-08-01
|
06 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Phillip Hallam-Baker |
2014-07-31
|
06 | Jean Mahoney | Request for Last Call review by GENART is assigned to Roni Even |
2014-07-31
|
06 | Jean Mahoney | Request for Last Call review by GENART is assigned to Roni Even |
2014-07-30
|
06 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Thomas Nadeau |
2014-07-30
|
06 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Thomas Nadeau |
2014-07-28
|
06 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2014-07-28
|
06 | Amy Vezza | The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: Reply-To: ietf@ietf.org Sender: Subject: Last Call: (A YANG Data Model for … The following Last Call announcement was sent out: From: The IESG To: IETF-Announce CC: Reply-To: ietf@ietf.org Sender: Subject: Last Call: (A YANG Data Model for SNMP Configuration) to Proposed Standard The IESG has received a request from the NETCONF Data Modeling Language WG (netmod) to consider the following document: - 'A YANG Data Model for SNMP Configuration' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-08-11. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines a collection of YANG definitions for configuring SNMP engines. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-netmod-snmp-cfg/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-netmod-snmp-cfg/ballot/ No IPR declarations have been submitted directly on this I-D. |
2014-07-28
|
06 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2014-07-28
|
06 | Benoît Claise | Last call was requested |
2014-07-28
|
06 | Benoît Claise | Last call announcement was generated |
2014-07-28
|
06 | Benoît Claise | Ballot approval text was generated |
2014-07-28
|
06 | Benoît Claise | Ballot writeup was generated |
2014-07-28
|
06 | Benoît Claise | IESG state changed to Last Call Requested from AD Evaluation::AD Followup |
2014-07-23
|
06 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2014-07-23
|
06 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-06.txt |
2014-07-11
|
05 | Benoît Claise | Expecting a version 6 |
2014-07-11
|
05 | Benoît Claise | IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation |
2014-05-19
|
05 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-05.txt |
2014-04-30
|
04 | Benoît Claise | IESG state changed to AD Evaluation from Publication Requested |
2014-04-30
|
04 | Benoît Claise | IESG process started in state Publication Requested |
2014-04-30
|
04 | (System) | Earlier history may be found in the Comment Log for /doc/draft-bjorklund-netmod-snmp-cfg/ |
2014-04-30
|
04 | Benoît Claise | Working group state set to Submitted to IESG for Publication |
2014-04-30
|
04 | Benoît Claise | Changed document writeup |
2014-02-10
|
04 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-04.txt |
2014-01-14
|
03 | Benoît Claise | Shepherding AD changed to Benoit Claise |
2014-01-14
|
03 | Thomas Nadeau | Document shepherd changed to Thomas Nadeau |
2014-01-04
|
03 | Jürgen Schönwälder | Document shepherd changed to David Kessens |
2014-01-04
|
03 | Jürgen Schönwälder | Document shepherd changed to (None) |
2014-01-04
|
03 | Jürgen Schönwälder | Document shepherd changed to (None) |
2014-01-04
|
03 | Jürgen Schönwälder | Document shepherd changed to (None) |
2013-11-05
|
03 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-03.txt |
2013-04-25
|
02 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-02.txt |
2013-04-03
|
01 | Jürgen Schönwälder | Annotation tag Revised I-D Needed - Issue raised by WGLC set. |
2013-04-03
|
01 | Jürgen Schönwälder | Intended Status changed to Proposed Standard from None |
2013-02-11
|
01 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-01.txt |
2012-06-05
|
00 | Martin Björklund | New version available: draft-ietf-netmod-snmp-cfg-00.txt |