[CCAMP] 2nd WG Last Call comments on signaling-g709v3 (editorial only)

Lou Berger <lberger@labn.net> Fri, 14 June 2013 22:15 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5393221F9AE2 for <ccamp@ietfa.amsl.com>; Fri, 14 Jun 2013 15:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.033
X-Spam-Status: No, score=-102.033 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id V23v9RDRI51T for <ccamp@ietfa.amsl.com>; Fri, 14 Jun 2013 15:15:25 -0700 (PDT)
Received: from oproxy14-pub.unifiedlayer.com (oproxy14-pub.unifiedlayer.com []) by ietfa.amsl.com (Postfix) with SMTP id 1493B21E804D for <ccamp@ietf.org>; Fri, 14 Jun 2013 15:15:24 -0700 (PDT)
Received: (qmail 7851 invoked by uid 0); 14 Jun 2013 22:15:24 -0000
Received: from unknown (HELO box313.bluehost.com) ( by oproxy14.unifiedlayer.com with SMTP; 14 Jun 2013 22:15:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=vFdtxVPSGFQaFVqGJSKb/TWpnbw9K1xv6Ch0PWMNbI8=; b=I+/yj/oWn1hbXVDgxGgyb30csfPf1gvlMpcGAfkpbK4UXxtc+ZW1OdiY4AVO9DKQ9IVH0vXQrYrEI6WyjGDFJoDDAqaEJbxSZO/m4tmbK6iSHVvxT3S1a+zJfBfr8Gqv;
Received: from box313.bluehost.com ([]:52368 helo=[]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UncHE-0002oW-8C; Fri, 14 Jun 2013 16:15:24 -0600
Message-ID: <51BB95F9.5000401@labn.net>
Date: Fri, 14 Jun 2013 18:15:21 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: CCAMP <ccamp@ietf.org>, "draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org" <draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org>
References: <51A8CB9D.40009@labn.net>
In-Reply-To: <51A8CB9D.40009@labn.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth authed with lberger@labn.net}
Subject: [CCAMP] 2nd WG Last Call comments on signaling-g709v3 (editorial only)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 22:15:29 -0000

	The following are comments as part of my LC review of
draft-ietf-ccamp-gmpls-signaling-g709v3-09.  Note that I'm the document
shepherd, see RFC 4858 for more information.

As with other documents:
- This and the other g709v3 documents should be consistent in usage of
"TS granularity" versus "TSG".  Sometimes one is used rather than the
other, sometimes both are used in the same document (as is the case in
this document).  Please pick either one and update the four documents to
be consistent.

- Another and related comment is please define and use a consistent
plural form of "TS".  You initially define "TSs" to expand to "Time
Slots", but then use "TS" as the plural form in many (but not all
cases).  I personally think "TSs" in all plural cases makes the most sense.

- Also same comment for TSGs.

- Please be consistent in usage of "Gbps".  Some inconsistent examples:
 "1.25Gps", "1.25 Gbps" and "1.25 Gbps".  (I personally
 prefer the final form, but any common form is fine.)

Please see
for line numbers used in this message.

Line 47:
 s/updates/provides an alternative to

Line 49:
 s/evolving OTN addressing ODUk multiplexing and new/full set of OTN

Line 97:
 s/updates/provides an alternative to

Line 132:

Line 143:
 drop "needs to be updated because it"

Line 330:
 "Here:" what?  Do you mean "Where:"?

Line 373:

Line 379:
 s/MAY not/may not

Lines 388/9:
 Tolerance no longer signaled.  Suggest saying as much.

Lines 581:
 s/ignored/ignored on receipt.

Section 6.
 You should consistently use formal object names throughout this
section, which can be found at
e.g, "Label Set" --> "LABEL_SET Object".

Line 591:
 s/MAY not/need not

Line 611:
  As repeating whats in 3473, suggest lower case usage of 2119 terms.

Line 624,625,626/7:
  s/TS type/TSG

Line 879.
 How about adding to the beginning of the paragraph something along the
lines of:
   This document is a modification to [RFC3473] and [RFC4328], and only
   differs in specific information communicated. As such, this document

Lines 888-897
  How about:
   Upon approval of this document, IANA will make the following
   assignments in the "Class Types or C-Types ‒ 9 FLOWSPEC" and
   "Class Types or C-Types ‒ 12 SENDER_TSPEC" section of the "RSVP
   Parameters" registry located at

   Value     Description         Reference
    7*       OTN-TDM             [This.I-D]

   (*) Suggested value

Lines 905-909:
   Drop lines

Line 911->928:
  to match registry, Replace with:
   Value Type                            Technology       Reference
   ===== ======================          ==========
   47    G.709 ODU-2.5G                  G.709 ODUk      [RFC4328],
         (IANA to update Type field)                     [This.I-D]
   56    SBCON/ESCON                     G.709 ODUk,     [RFC4328],
         (IANA to update Type field)       Lambda, Fiber [This.I-D]
   59*   Framed GFP                      G.709 ODUk      [This.I-D]
   60*   STM-1                           G.709 ODUk      [This.I-D]
   61*   STM-4                           G.709 ODUk      [This.I-D]
   62*   InfiniBand                      G.709 ODUflex   [This.I-D]
   63*   SDI (Serial Digital Interface)  G.709 ODUk      [This.I-D]
   64*   SDI/1.001                       G.709 ODUk      [This.I-D]
   65*   DVB_ASI                         G.709 ODUk      [This.I-D]
   66*   G.709 ODU-1.25G                 G.709 ODUk      [This.I-D]
   67*   G.709 ODU-Any                   G.709 ODUk      [This.I-D]
   68*   Null Test                       G.709 ODUk      [This.I-D]
   69*   Random Test                     G.709 ODUk      [This.I-D]
   70*   64B/66B GFP-F Ethernet          G.709 ODUk      [This.I-D]

Line 930:
  Add "Upon approval of this document, IANA will define a "OTN

Line 931/932
  Drop to end of sentence starting with "will be defined by ..."

Line 956:
    New values are to be assigned via Standards Action as defined in

Lines 1006-1023:
  Aren't these all normative references?

That's it,