Network Service Header (NSH) Context Header Allocation: Timestamp
draft-mymb-sfc-nsh-allocation-timestamp-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-01-12
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
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 T. Mizrahi
Internet-Draft I. Yerushalmi
Intended status: Informational D. Melman
Expires: July 16, 2017 Marvell
R. Browne
Intel
January 12, 2017
Network Service Header (NSH) Context Header Allocation: Timestamp
draft-mymb-sfc-nsh-allocation-timestamp-00
Abstract
This memo defines an allocation for the Context Headers of the
Network Service Header (NSH), which incorporates the packet's ingress
timestamp, a sequence number, and a source interface identifier.
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 July 16, 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
(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
Mizrahi, et al. Expires July 16, 2017 [Page 1]
Internet-Draft NSH Ingress Timestamp January 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. NSH Context Header Allocation Allocation . . . . . . . . . . 3
4. Ingress Timestamping Use Cases . . . . . . . . . . . . . . . 4
4.1. Network Analytics . . . . . . . . . . . . . . . . . . . . 4
4.2. Alternate Marking . . . . . . . . . . . . . . . . . . . . 5
4.3. Consistent Updates . . . . . . . . . . . . . . . . . . . 5
5. Synchronization Considerations . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
The Network Service Header (NSH), defined in [I-D.ietf-sfc-nsh], is
an encapsulation header that is used in Service Function Chains
(SFC).
The NSH specification [I-D.ietf-sfc-nsh] supports two possible
methods of including metadata in the NSH; MD Type 0x1 and MD Type
0x2. When using MD Type 0x1 the NSH includes 16 octets of Context
Header fields. The current memo proposes an allocation for the MD
Type 0x1 Context Headers, which incorporates the ingress timestamp of
the packet, a sequence number, and a source interface identifier.
In a nutshell, packets that enter the SFC-Enabled Domain are
timestamped. The ingress timestamp is measured by the Classifier
[RFC7665], and incorporated in the NSH. The ingress timestamp may be
used for various different purposes, including delay measurement,
packet marking for passive performance monitoring, and timestamp-
based policies. Notably, the timestamp does not increase the packet
length, since it is incorporated in the MD Type 0x1 Mandatory Context
Headers.
The source interface identifier indicates the interface through which
the packet was received at the classifier. This identifer may
Show full document text