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

Lou Berger <lberger@labn.net> Fri, 14 June 2013 20:32 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 B02F921E805F for <ccamp@ietfa.amsl.com>; Fri, 14 Jun 2013 13:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[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 MHpNT2bFrnKh for <ccamp@ietfa.amsl.com>; Fri, 14 Jun 2013 13:32:09 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com []) by ietfa.amsl.com (Postfix) with SMTP id 252C611E80E0 for <ccamp@ietf.org>; Fri, 14 Jun 2013 13:32:08 -0700 (PDT)
Received: (qmail 4352 invoked by uid 0); 14 Jun 2013 20:31:46 -0000
Received: from unknown (HELO box313.bluehost.com) ( by oproxy9.bluehost.com with SMTP; 14 Jun 2013 20:31:46 -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=Qd/kd3MoFhwQnwtpmXVSWsx7E37wGThDjD2wl+wVZEM=; b=cCepzZtL/dYuXhMk/2tvPTfOeOFEdzRms9Itvl30vyqOZ13KhiLgjyh74zrnJ0mzUmSRkiwZ+u8OOXsKTAGwsTSBuJhBDjgbqz2Jwpp/ZtKoXxszCkc9nsxNKARizk2U;
Received: from box313.bluehost.com ([]:58850 helo=[]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1Unaev-0002y1-Uf; Fri, 14 Jun 2013 14:31:46 -0600
Message-ID: <51BB7DAE.30203@labn.net>
Date: Fri, 14 Jun 2013 16:31:42 -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-ospf-g709v3@tools.ietf.org" <draft-ietf-ccamp-gmpls-ospf-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="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 ospf-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 20:32:13 -0000

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

Please see
for line numbers used in this message.

The draft needs to be nit free before being passed to the IESG. The
following nits show in the above URL:
  Miscellaneous warnings:


  == Using lowercase 'not' together with uppercase 'MUST', 'SHALL',
     or 'RECOMMENDED' is not an accepted usage according to RFC 2119.
     use uppercase 'NOT' together with RFC 2119 keywords (if that is
what you

     Found 'MUST not' in this paragraph:

     - Unreserved Bandwidth (32 bits): This field indicates the
     Unreserved Bandwidth at a particular priority level.  This field
     set to the bandwidth, in bits/s in IEEE floating point format,
     at the indicated Signal Type for a particular priority level.  One
     MUST be present for each bit set in the Priority field, and is
ordered to
     match the Priority field. Fields MUST not be present for priority
     that are not indicated in the Priority field.This field is REQUIRED for
     Type 2 (variable container) TLVs, and MUST NOT be used for Type 1 TLVs.

  -- The document date (April 4, 2013) is 71 days in the past.  Is this

  Checking references for intended status: Proposed Standard


     (See RFCs 3967 and 4897 for information about using normative
     to lower-maturity documents in RFCs)

  == Outdated reference: A later version (-12) exists of

  == Outdated reference: A later version (-08) exists of

  == Outdated reference: A later version (-09) exists of

I also have the following editorial comments:

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.25/2.5", "1.25Gps", "1.25 GBps" and "1.25 Gbps".  (I personally
 prefer the final form, but any common form is fine.)

- RFC 4203 uses the field name "Switching Capability-specific
  information" while the document uses "Switch Capability Specific
  Information", so throughout the document please
  s/Switch Capability/Switching Capability

- per RFC4203, fix capitalization when referring to the filed name:
  s/MAX LSP bandwidth/MAX LSP Bandwidth

lines 2-5:
  Shouldn't this document be identified as an update to 4203?

Lines 24-32:
  The Abstract is really in need of a make over.  How about something
  like the following:

   This document describes Open Shortest Path First - Traffic
   Engineering (OSPF-TE) routing protocol extensions to support
   Generalized MPLS (GMPLS) control of Optical Transport Networks
   (OTN) specified in ITU-T Recommendation G.709 as published in 2012.
   It extends mechanisms defined in RFC4203.

Line 102:
   Expand ODU

Lines 105/6:
   Drop "which is being standardized in ITU-T"

Line 107:
   s/the routing process/routing

Lines 108:
   You should mentioned the base OSPF TE document here.  How about:
   s/OSPF-TE/use in GMPLS OSPF-TE as defined in [RFC4203].

Line 115:
  s/The routing/Routing

Line 143-145:
  I think this text reads a bit backwards, it is the need for the ISCD
  that drives the new type/swcap, not the other way around  I also
  suggest adding informative reference to
  draft-ietf-ccamp-swcaps-update, perhaps something like:

   leads to the need to define a new Switching Capability value and
   associated new Switching Capability for the Interface Switching
   Capability Descriptor (ISCD).
   These capabilities are carried in the Interface Switching
   Capability Descriptor (ISCD) Switching Capability-specific
   information field using formats defined in this document.
   As discussed in [swcaps-update], the use of a technology specific
   Switching Capability-specific information field necessitates
   the definition of a new Switching Capability value and
   associated new Switching Capability.

Line 178:
  Drop "on this traffic card"

Lines 192/3:
  "The TE-Link is referred to as OTUk-TE-Link."
  This term is used just once in the document.  Suggest dropping it.

Lines 193/4:
  Doesn't the TE link for an OTUk physical Link always provide ODUk
  capacity? Either way this text needs to be fixed/clarified.

Lines 196, 206:
  Is this an OTUk or ODUk TE link? You first says the former then the
  latter.  I suspect you mean former, i.e., s/ODUk/OTUk

Line 209/10:
  "Such TE-Links are also termed ODUk-TE-Links."
  This term is used just once in the document.  Suggest dropping it.

Lines 210-212,221:
  ODUj vs ODUk.  Isn't it the case that a multi hop TE link could
  represent either ODUj or ODUk resources?  This isn't clear from the
  current text/usage of ODUj/k.

Line 229:
  s/[RFC4202]/and is defined in [RFC4203]

Lines 249-257:
  The document already says 4203 MUST be followed, so no need to provide
  normative language for 4203-defined behavior.  Specifically:
  s/field MUST be used/field is used
  s/MUST be in/is in

Lines 286/7:
  Isn't this sentence redundant with the prior sentence?  Suggest

Line 291:

Line 293/4:
  Types are defined in this document.
  Suggest adding:
   Note that type values are defined in this document and not [RFC3630].

Line 301:
  SCSI acronym not defined.

Line 301,302:

Line 302:
  To clarify and to add a transition to the next paragraph, I suggest
  adding something along the lines of:
   Each container type is identified by a Signal Type.  Signal Type
   values are defined in [OTN-SIG].

Line 469/470:
   The sentence starting "This field is ..." isn't used consistently
   (i.e., not present for Unreserved ODUj, Unreserved Padding, and
    Maximum LSP Bandwidth).  It should be dropped, or parallel
   statements should be added for the other cases.

Line 1112:
  I think the first sentence is a bit hard to follow.  How about:
   This document, as [RFC4203], specifies
   This document extends [RFC4203]. As with[RFC4203], it specifies

Line 1133:

Line 1145:
 How about the following as the registry name:
   "Types for sub-TLVs of OTN-TDM SCSI (Switch Capability Specific

Lines 1153-1159
  To be aligned with what you want to see with the registry, and fix
type 2 description:

  Value		Sub-TLV 			Reference
  0		Reserved 			[This.I-D]
  1             Unreserved Bandwidth    	[This.I-D]
   		for fixed containers
  2             Unreserved/Max Bandwidth 	[This.I-D]
   		for flexible containers
Lines 1161/2
  You some parts of the IANA "formula", how about:
    New TLV type values may be allocated only by an IETF Consensus
    action.  The request Registration Procedures are Standards Action.
    Types are to be assigned via Standards Action as defined in

Lines 1247-1249:
  Shouldn't [G.709-2012] be normative?

That's it,