Internet DRAFT - draft-vaughn-cnmp-trans
draft-vaughn-cnmp-trans
INTERNET-DRAFT K. Vaughn
Intended Status: Standards Track Trevilon LLC
Expires: May 24, 2014 A. Triglia
OSS Nokalva, Inc.
R. Rausch
Transcore, LP
November 20, 2013
Transport Mappings for Condensed Network Management Protocol (CNMP)
draft-vaughn-cnmp-trans-00
Abstract
This document defines the transport of the Condensed Network
Management Protocol (SNMP) messages over various protocols.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
K. Vaughn Expires May 24, 2014 [Page 1]
INTERNET DRAFT Document Roadmap for CNMP November 20, 2013
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. CNMP over UDP over IPv4 . . . . . . . . . . . . . . . . . . . 3
3.1. Serialization . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Well-known Values . . . . . . . . . . . . . . . . . . . . 3
3.3. Size Constraints . . . . . . . . . . . . . . . . . . . . . 3
4. CNMP over T2 over Null . . . . . . . . . . . . . . . . . . . . 3
4.1. Serialization . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Well-known Values . . . . . . . . . . . . . . . . . . . . 4
4.3. Size Constraints . . . . . . . . . . . . . . . . . . . . . 4
5. Serialization using the Octet Encoding Rules . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1 Normative References . . . . . . . . . . . . . . . . . . . 5
8.2 Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
K. Vaughn Expires May 24, 2014 [Page 2]
INTERNET DRAFT Document Roadmap for CNMP November 20, 2013
1. Introduction
This document provides the recommended transport mapping for CNMP.
For a detailed overview of the documents that describe the Condensed
Network Management Protocol, please refer to [Intro].
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Within this INTERNET-DRAFT and all referenced documents, CNMP is to
be considered another version of SNMP. It is only given a different
name because the protocol encoding does not follow the same message
format as SNMP messages and the protocol will use a different binding
with the transport layer.
3. CNMP over UDP over IPv4
This is the preferred transport mapping.
3.1. Serialization
Each instance of a message SHALL be serialized (i.e., encoded
according to the convention of [OER]) onto a single UDP [RFC0768]
over IPv4 [RFC0791] datagram.
3.2. Well-known Values
It is suggested that administrators configure their SNMP entities
supporting command responder applications to listen on UDP port TBD1.
Further, it is suggested that SNMP entities supporting notification
receiver applications be configured to listen on UDP port TBD2.
3.3. Size Constraints
When an SNMP entity uses this transport mapping, it SHALL be capable
of accepting messages up to and including 484 octets in size. It
SHOULD be capable of accepting messages of up to 1472 octets in size.
It MAY be capable of accepting messages of larger sizes.
4. CNMP over T2 over Null
This is an alternate transport mapping.
4.1. Serialization
K. Vaughn Expires May 24, 2014 [Page 3]
INTERNET DRAFT Document Roadmap for CNMP November 20, 2013
Each instance of a message SHALL be serialized (i.e., encoded
according to the convention of [OER]) onto a single T2 [T2] datagram.
4.2. Well-known Values
It is suggested that administrators configure their SNMP entities
supporting command responder applications to listen on UDP port TBD1.
Further, it is suggested that SNMP entities supporting notification
receiver applications be configured to listen on UDP port TBD2.
4.3. Size Constraints
When an SNMP entity uses this transport mapping, it SHALL be capable
of accepting messages up to and including 484 octets in size. It
SHOULD be capable of accepting messages of up to 1472 octets in size.
It MAY be capable of accepting messages of larger sizes.
5. Serialization using the Octet Encoding Rules
When encoding an object whose syntax is described using the BITS
construct, the value SHALL be encoded as an OCTET STRING, in which
all the named bits in (the definition of) the bitstring, commencing
with the first bit and proceeding to the last bit, are placed in bits
8 (high order bit) to 1 (low order bit) of the first octet, followed
by bits 8 to 1 of each subsequent octet in turn, followed by as many
bits as are needed of the final subsequent octet, commencing with bit
8. Remaining bits, if any, of the final octet are set to zero on
generation and ignored on receipt.
Examples of applying OER are provided in Appendix A of [Intro].
6. Security Considerations
CNMP offers different levels of security based on user needs.
It is recommended that the implementors consider the security
features as provided by the CNMP framework. Specifically, the use of
the User-based Security Model STD 62, RFC 3414 [RFC3414], the
Transport Security Model [RFC5590], and the View-based Access Control
Model STD 62, RFC 3415 [RFC3415] is recommended.
It is then a customer/user responsibility to ensure that the entity
giving access to a MIB is properly configured to give access to the
objects only to those principals (users) that have legitimate rights
to indeed GET or SET (change) them.
7. IANA Considerations
K. Vaughn Expires May 24, 2014 [Page 4]
INTERNET DRAFT Document Roadmap for CNMP November 20, 2013
IANA should assign a User Port number number from the Service Name
and Transport Protocol Port Number Registry
<http://www.iana.org/assignments/port-numbers> for TBD1 and TBD2,
both of which are referenced in both Clauses 3.2 and 4.2.
8. References
8.1 Normative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, December
2002.
[RFC5590] Harrington, D. and J. Schoenwaelder, "Transport Subsystem
for the Simple Network Management Protocol (SNMP)",
RFC 5590, June 2009.
[OER] "Information Technology - ASN.1 encoding rules:
Specification of Octet Encoding Rules (OER)", published by
International Telecommunications Union. Initial Draft
X.oer, January 2014.
[T2] "Transportation Transport Profile", published by American
Association of State Highway Officials (AASHTO), Institute
of Transportation Engineers (ITE), and National Electrical
Manufacturers Association (NEMA). NTCIP (National
Transportation Communications for ITS Protocol) 2201:2003
v01.15, September 2005.
8.2 Informative References
[Intro] Vaughn, K., "Document Roadmap for Condensed Network
Management Protocol (CNMP)", Internet-Draft draft-vaughn-
cnmp-intro-00, November 2013.
K. Vaughn Expires May 24, 2014 [Page 5]
INTERNET DRAFT Document Roadmap for CNMP November 20, 2013
Authors' Addresses
Kenneth Vaughn
Trevilon LLC
6606 FM 1488 RD
STE 148-503
Magnolia, TX 77316
USA
Phone: +1-571-331-5670
Email: kvaughn@trevilon.com
Alessandro Triglia
OSS Nokolva, Inc.
1 Executive Drive
Suite 450
Somerset, NJ 08873
Email: sandro@oss.com
Robert Rausch
Transcore, LP
192 Technology Parkway
Suite 500
Norcross, GA 30092
Email: robert.rausch@transcore.com
K. Vaughn Expires May 24, 2014 [Page 6]
