UDP Port Allocation for the Receiver Port in Two-Way Active Measurement Protocol (TWAMP)
draft-mirsky-ippm-twamp-refl-registered-port-02

Document Type Active Internet-Draft (individual)
Last updated 2017-04-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          G. Mirsky
Internet-Draft                                                 ZTE Corp.
Updates: 5357 (if approved)                                   M. Perumal
Intended status: Standards Track                                Ericsson
Expires: October 15, 2017                                       R. Foote
                                                                   Nokia
                                                         L. M. Contreras
                                                              Telefonica
                                                                L. Jalil
                                                                 Verizon
                                                          April 13, 2017

UDP Port Allocation for the Receiver Port in Two-Way Active Measurement
                            Protocol (TWAMP)
            draft-mirsky-ippm-twamp-refl-registered-port-02

Abstract

   This document arguments and requests allocation of an UDP port number
   from the User Ports range for a Reflector in Two-Way Active
   Measurement Protocol (TWAMP) .  This document, if accepted, will be
   an update to the TWAMP Test protocol specified in RFC 5357.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on October 15, 2017.

Copyright Notice

   Copyright (c) 2017 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

Mirsky, et al.          Expires October 15, 2017                [Page 1]
Internet-Draft  Registered Receiver Port Number in TWAMP      April 2017

   (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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Impact to TWAMP-Control Protocol  . . . . . . . . . . . . . .   3
   4.  Impact to TWAMP-Test Protocol . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   One particular compelling vision of the Two-Way Active Measurement
   Protocol (TWAMP) [RFC5357] is widespread deployment of open servers
   that would make IP Performance Metrics (IPPM) measurements a
   commonplace.  This is complemented by the proliferation of the
   Internet of Things (IoT) devices, such as sensors, and the need for
   obtaining IPPM measurements from those devices by the service
   provider.  IoT devices are often constrained by limited processing
   power and memory and benefit from TWAMP Light, as defined in
   Appendix I [RFC5357].

   TWAMP Light provides a simple solution for devices to act as test
   points in the network, by avoiding the need for the TWAMP-Control
   protocol [RFC5357].  In the absence of TWAP-Control, a registered
   (default) UDP port that can be used as the Receiver Port for TWAMP-
   Test will simplify configuration and management of the TWAMP-Light
   test sessions.

   This document requests allocation of the UDP port number from the
   User Port range [RFC6335] as Receiver Port for TWAMP-Test.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text