draft-ietf-ippm-twamp-time-format-05.txt | draft-ietf-ippm-twamp-time-format-06.txt | |||
---|---|---|---|---|
Network Working Group G. Mirsky | Network Working Group G. Mirsky | |||
Internet-Draft ZTE Corp. | Internet-Draft ZTE Corp. | |||
Intended status: Standards Track I. Meilik | Intended status: Standards Track I. Meilik | |||
Expires: September 13, 2017 Broadcom | Expires: October 14, 2017 Broadcom | |||
March 12, 2017 | April 12, 2017 | |||
Support of IEEE-1588 time stamp format in Two-Way Active Measurement | Support of IEEE-1588 time stamp format in Two-Way Active Measurement | |||
Protocol (TWAMP) | Protocol (TWAMP) | |||
draft-ietf-ippm-twamp-time-format-05 | draft-ietf-ippm-twamp-time-format-06 | |||
Abstract | Abstract | |||
This document describes an OPTIONAL feature for active performance | This document describes an OPTIONAL feature for active performance | |||
measurement protocols allowing use of the Precision Time Protocol | measurement protocols allowing use of the Precision Time Protocol | |||
time stamp format defined in IEEE-1588v2-2008, as an alternative to | time stamp format defined in IEEE-1588v2-2008, as an alternative to | |||
the Network Time Protocol that is currently used. | the Network Time Protocol that is currently used. | |||
Status of This Memo | Status of This Memo | |||
skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on September 13, 2017. | This Internet-Draft will expire on October 14, 2017. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2017 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 2, line 22 ¶ | skipping to change at page 2, line 22 ¶ | |||
1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3 | 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 3 | |||
2. OWAMP and TWAMP Extensions . . . . . . . . . . . . . . . . . 3 | 2. OWAMP and TWAMP Extensions . . . . . . . . . . . . . . . . . 3 | |||
2.1. Timestamp Format Negotiation in Setting Up Connection in | 2.1. Timestamp Format Negotiation in Setting Up Connection in | |||
OWAMP . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | OWAMP . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
2.2. Timestamp Format Negotiation in Setting Up Connection in | 2.2. Timestamp Format Negotiation in Setting Up Connection in | |||
TWAMP . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | TWAMP . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
2.3. OWAMP-Test and TWAMP-Test Update . . . . . . . . . . . . 5 | 2.3. OWAMP-Test and TWAMP-Test Update . . . . . . . . . . . . 5 | |||
2.3.1. Consideration for TWAMP Light mode . . . . . . . . . 6 | 2.3.1. Consideration for TWAMP Light mode . . . . . . . . . 6 | |||
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | |||
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | |||
6. Normative References . . . . . . . . . . . . . . . . . . . . 7 | 6. Normative References . . . . . . . . . . . . . . . . . . . . 7 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
1. Introduction | 1. Introduction | |||
One-Way Active Measurement Protocol (OWAMP) [RFC4656] defines that | One-Way Active Measurement Protocol (OWAMP) [RFC4656] defines that | |||
only the NTP [RFC5905] format of a time stamp can be used in OWAMP- | only the NTP [RFC5905] format of a time stamp can be used in OWAMP- | |||
Test protocol. Two-Way Active Measurement Protocol (TWAMP) [RFC5357] | Test protocol. Two-Way Active Measurement Protocol (TWAMP) [RFC5357] | |||
adopted the OWAMP-Test packet format and extended it by adding a | adopted the OWAMP-Test packet format and extended it by adding a | |||
format for a reflected test packet. Both the sender's and | format for a reflected test packet. Both the sender's and | |||
skipping to change at page 4, line 8 ¶ | skipping to change at page 4, line 8 ¶ | |||
extension mechanism [RFC6038]. The new feature requires one bit | extension mechanism [RFC6038]. The new feature requires one bit | |||
position for Server and Control-Client to negotiate which timestamp | position for Server and Control-Client to negotiate which timestamp | |||
format can be used in some or all test sessions invoked with this | format can be used in some or all test sessions invoked with this | |||
control connection. The end-point of the test session, Session- | control connection. The end-point of the test session, Session- | |||
Sender and Session-Receiver or Session-Reflector, that supports this | Sender and Session-Receiver or Session-Reflector, that supports this | |||
extension MUST be capable to interpret NTP and PTPv2 timestamp | extension MUST be capable to interpret NTP and PTPv2 timestamp | |||
formats. If the end-point does not support this extension, then the | formats. If the end-point does not support this extension, then the | |||
value of PTPv2 Timestamp flag MUST be 0 because it is in Must Be Zero | value of PTPv2 Timestamp flag MUST be 0 because it is in Must Be Zero | |||
field. If the value of PTPv2 Timestamp flags is 0, then the | field. If the value of PTPv2 Timestamp flags is 0, then the | |||
advertising node can use and interpret only NTP timestamp format. | advertising node can use and interpret only NTP timestamp format. | |||
Implementations of OWAMP and/or TWAMP MAY provide a configuration | ||||
knob to bypass the timestamp format negotiation process and to use | ||||
the locally configured values instead. | ||||
Use of PTPv2 Timestamp flags is discussed in the following sub- | Use of PTPv2 Timestamp flags is discussed in the following sub- | |||
sections. For details on the assigned values and bit positions see | sections. For details on the assigned values and bit positions see | |||
the Section 3. | the Section 3. | |||
2.1. Timestamp Format Negotiation in Setting Up Connection in OWAMP | 2.1. Timestamp Format Negotiation in Setting Up Connection in OWAMP | |||
In OWAMP-Test [RFC4656] the Session-Receiver and/or Fetch-Client | In OWAMP-Test [RFC4656] the Session-Receiver and/or Fetch-Client | |||
interpret collected timestamps. Thus, the Server uses the Modes | interpret collected timestamps. Thus, the Server uses the Modes | |||
field timestamp format to indicate which formats the Session-Receiver | field timestamp format to indicate which formats the Session-Receiver | |||
End of changes. 5 change blocks. | ||||
5 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |