Re: [CCAMP] I-D Action: draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt

Fatai Zhang <> Wed, 19 June 2013 02:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 832D721F9A86 for <>; Tue, 18 Jun 2013 19:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fDUlxAyD8lVu for <>; Tue, 18 Jun 2013 19:06:29 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F22CE21F995B for <>; Tue, 18 Jun 2013 19:06:28 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.5-GA FastPath queued) with ESMTP id AUA90907; Wed, 19 Jun 2013 02:06:26 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 19 Jun 2013 03:05:54 +0100
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 19 Jun 2013 03:06:25 +0100
Received: from ([]) by ([::1]) with mapi id 14.01.0323.007; Wed, 19 Jun 2013 10:06:21 +0800
From: Fatai Zhang <>
To: Lou Berger <>, CCAMP <>
Thread-Topic: [CCAMP] I-D Action: draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt
Thread-Index: AQHObJGX991QFQCCj0SnZlBuDw3Gew==
Date: Wed, 19 Jun 2013 02:06:20 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Jun 2013 02:06:34 -0000

Hi Lou and all,

A new version has been submitted to address the 2nd WG Last Call comments on this draft.

Please take a look and any further comments are appreciated.

Best Regards


-----Original Message-----
From: [] On Behalf Of Lou Berger
Sent: Saturday, June 15, 2013 6:15 AM
Subject: [CCAMP] 2nd WG Last Call comments on signaling-g709v3 (editorial only)

	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,

CCAMP mailing list