Re: [AVTCORE] Technical - Re: [Editorial Errata Reported] RFC7273 (4450)

Kevin Gross <kevin.gross@avanw.com> Wed, 02 September 2015 20:29 UTC

Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8182D1B2EC3 for <avt@ietfa.amsl.com>; Wed, 2 Sep 2015 13:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 9.279
X-Spam-Level: *********
X-Spam-Status: Yes, score=9.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, NORMAL_HTTP_TO_IP=0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFc19nMNNBBh for <avt@ietfa.amsl.com>; Wed, 2 Sep 2015 13:29:20 -0700 (PDT)
Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:169]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72B151B2CC7 for <avt@ietf.org>; Wed, 2 Sep 2015 13:29:20 -0700 (PDT)
Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-10v.sys.comcast.net with comcast id CLUJ1r0034s37d401LVLBm; Wed, 02 Sep 2015 20:29:20 +0000
Received: from mail-io0-f182.google.com ([209.85.223.182]) by resomta-po-01v.sys.comcast.net with comcast id CLTK1r00P3wk7A901LTL8i; Wed, 02 Sep 2015 20:27:20 +0000
Received: by iofh134 with SMTP id h134so34595604iof.0 for <avt@ietf.org>; Wed, 02 Sep 2015 13:27:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.154.15 with SMTP id c15mr17365919ioe.197.1441225639883; Wed, 02 Sep 2015 13:27:19 -0700 (PDT)
Received: by 10.79.102.131 with HTTP; Wed, 2 Sep 2015 13:27:19 -0700 (PDT)
In-Reply-To: <20150818173656.46E36180092@rfc-editor.org>
References: <20150818173656.46E36180092@rfc-editor.org>
Date: Wed, 2 Sep 2015 14:27:19 -0600
Message-ID: <CALw1_Q0HojZUoJrTqNDe8kNK+xzYJPH+A5cuXQ_xgtU=6A5mFw@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary=001a1140f6364e79c0051ec97e41
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1441225760; bh=rS35zhPD+tvSya2hSH79R8CLtwSnD1da3CGIo9Igaa0=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=SKMxO6VB998+aBfo0qc+9fGIgoxCRir24rDDBa06p0rFKX3YYOplwGijr0UFz8Dnj B/ptLs/pCp4JUADJ9/phGlG/XWoquNKksgIQgKVVz6VJyhM9xD+D1FNcCIn56HcZoX 46HPsrwiXbQbmAIEb8XEgvylha/15wnThdy3NWDWIL7cSnt+tNgiw4w4LAesgFXjMh JOdpbZTJIMLbdc8W348nb77Qq+47Laaytpah4PB5hRrZpcw1AnnNapHkQ7x7SkG59z tepLcEVJhjUI+ZInejZPmF+ekkRyg0IrmxJ5mJxvL1FV6mJJjTU9nLKivybiwkRqm5 qLM/yFQvspPgA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/kCdYn9s07IZm9aVnxySuiKEplsI>
X-Mailman-Approved-At: Thu, 03 Sep 2015 16:26:39 -0700
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Technical - Re: [Editorial Errata Reported] RFC7273 (4450)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 20:29:23 -0000

The authors have done some research on this issue and have determined that
all current implementations that signal IEEE 1588-2008 reference clock use
the notation from the examples, not the ABNF notation. We would like to
consider an alternate means of resolving the inconsistency in the RFC in a
manner consistent with existing implementations.

Change:

   ; PTP domain allowed number range: 0-127 (IEEE 1588-2008)
   ptp-domain-nmbr = "domain-nmbr=" ptp-domain-dgts
   ptp-domain-dgts = ptp-domain-n1 / ptp-domain-n2 / ptp-domain-n3
   ptp-domain-n1   = DIGIT             ; 0-9
   ptp-domain-n2   = POS-DIGIT DIGIT   ; 10-99
   ptp-domain-n3   = ("10"/"11") DIGIT ; 100-119
                   / "12" %x30-37      ; 120-127
To this:

   ; PTP domain allowed number range: 0-127 (IEEE 1588-2008)
   ptp-domain-nmbr = ":" ptp-domain-dgts
   ptp-domain-dgts = ptp-domain-n1 / ptp-domain-n2 / ptp-domain-n3
   ptp-domain-n1   = DIGIT             ; 0-9
   ptp-domain-n2   = POS-DIGIT DIGIT   ; 10-99
   ptp-domain-n3   = ("10"/"11") DIGIT ; 100-119
                   / "12" %x30-37      ; 120-127

For consistency, if we take this route we may also want to change:

   ; PTP domain allowed characters: 0x21-0x7E (IEEE 1588-2002)
   ptp-domain-name = "domain-name=" 1*16ptp-domain-char
   ptp-domain-char = %x21-7E

To this:

   ; PTP domain allowed characters: 0x21-0x7E (IEEE 1588-2002)
   ptp-domain-name = ":" 1*16ptp-domain-char
   ptp-domain-char = %x21-7E

The authors are aware of no implementations that signal a IEEE 1588-2002
reference clock.

Any comments from the group on the preferred way to address this?

Kevin Gross - AVA Networks

On Tue, Aug 18, 2015 at 11:36 AM, <rfc-editor@rfc-editor.org> wrote:

> FYI, the type of this erratum has been changed to Technical because it is
> not "a spelling, grammar, punctuation, or syntax error that does not affect
> the technical meaning".
>
> Thank you.
> RFC Editor/ar
>
> On Aug 18, 2015, at 7:49 AM, RFC Errata System <rfc-editor@rfc-editor.org>
> wrote:
>
> The following errata report has been submitted for RFC7273,
> "RTP Clock Source Signalling".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7273&eid=4450
>
> --------------------------------------
> Type: Editorial
> Reported by: Kevin Gross <kevin.gross@avanw.com>
>
> Section: 5.5
>
> Original Text
> -------------
> 5.5.  Examples
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 239.0.0.2/255
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/8
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:0
> a=mediaclk:offset=963214424
>
> Figure 6: Media clock directly referenced to IEEE 1588-2008
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 239.0.0.2/255
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/44100/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:0
> a=mediaclk:offset=963214424 rate=1000/1001
>
> Figure 7: "Oddball" sample rate directly refernced to IEEE 1588-2008
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 224.2.228.230/32
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:0
> a=mediaclk:rtp=IN IP4 239.0.0.1 5004 00:60:2b:20:12:if
>
> Figure 8: Stream media clock derived from another RTP multicast
> stream
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 224.2.228.230/32
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:0
> a=mediaclk:IEEE1722=38-D6-6D-8E-D2-78-13-2F
>
> Figure 9: Stream media clock derived from another RTP multicast
> stream
>
>
> Corrected Text
> --------------
> 5.5.  Examples
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 239.0.0.2/255
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/8
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:domain-nmbr=0
> a=mediaclk:offset=963214424
>
> Figure 6: Media clock directly referenced to IEEE 1588-2008
>
> Figure 7 shows an example SDP description 2 channels of 24-bit, 44056
> kHz NTSC "pull-down" media clock derived directly from an IEEE 1588-
> 2008 reference clock
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 239.0.0.2/255
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/44100/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:domain-nmbr=0
> a=mediaclk:offset=963214424 rate=1000/1001
>
> Figure 7: "Oddball" sample rate directly refernced to IEEE 1588-2008
>
> Figure 8 shows the same 48 kHz audio transmission from Figure 6 with
> media clock derived from another RTP multicast stream.  The stream
> providing the media clock must use the same reference clock as this
> stream that references it.
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 224.2.228.230/32
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:domain-nmbr=0
> a=mediaclk:rtp=IN IP4 239.0.0.1 5004 00:60:2b:20:12:if
>
> Figure 8: Stream media clock derived from another RTP multicast
> stream
>
> Figure 9 shows the same 48 kHz audio transmission from Figure 6 with
> media clock derived from an IEEE 1722 AVB stream.  The stream
> providing the media clock must be synchronized with the IEEE 1588-
> 2008 reference clock used by this stream.
>
> v=0
> o=- 1311738121 1311738121 IN IP4 192.168.1.1
> c=IN IP4 224.2.228.230/32
> s=
> t=0 0
> m=audio 5004 RTP/AVP 96
> a=rtpmap:96 L24/48000/2
> a=sendonly
> a=ts-refclk:ptp=IEEE1588-2008:39-A7-94-FF-FE-07-CB-D0:domain-nmbr=0
> a=mediaclk:IEEE1722=38-D6-6D-8E-D2-78-13-2F
>
> Figure 9: Stream media clock derived from another RTP multicast
> stream
>
>
> Notes
> -----
> There is an inconsistency between ABNF in section 4.8 and examples in
> section 5.5. It would be cleaner to correct the examples and that is what
> is proposed above. There is evidence, however, that current implementations
> are working to what is shown in the examples, not according to the ABNF
> specification.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC7273 (draft-ietf-avtcore-clksrc-11)
> --------------------------------------
> Title               : RTP Clock Source Signalling
> Publication Date    : June 2014
> Author(s)           : A. Williams, K. Gross, R. van Brandenburg, H.
> Stokking
> Category            : PROPOSED STANDARD
> Source              : Audio/Video Transport Core Maintenance RAI
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
>