[CCAMP] Confirming plan for Issue #48: (Was: Closing G.709 open issues)

[Lou Berger <[e-mail]>]

Authors/WG,
	From the mail on the list it seems to me that we've reached closure on
Issue #48: "Document no explicit indication of TSG in the label"
(http://trac.tools.ietf.org/wg/ccamp/trac/ticket/48)  I'd like to
confirm my reading.

As I read the list, this issue will be resolved by making the following
change to draft-ietf-ccamp-gmpls-signaling-g709v3.

OLD
  Note that the
  Length field in the label format MAY be used to indicate the TS
  type of the HO ODUk (i.e., TS granularity at 1.25Gbps or 2.5Gbps)
  since the HO ODUk type can be known from IF_ID RSVP_HOP Object. In
  some cases when there is no Link Management Protocol (LMP) or
  routing to make the two end points of the link to know the TSG,
  the TSG information used by another end can be deduced from the
  label format. For example, for HO ODU2 link, the value of the
  length filed will be 4 or 8, which indicates the TS granularity is
  2.5Gbps or 1.25Gbps, respectively.

NEW
  Please note that the TS granularity of an HO ODUk can be inferred from
  the length of the label. The values of 4 and 16 indicate a TS
  granularity of 2.5Gps, while the values 2, 8, 32 and 80 indicate a TS
  granularity of 1.25Gps.

Please speak up if you disagree with this resolution.

Thanks,
Lou

On 5/9/2013 9:41 PM, Fatai Zhang wrote:
> For point 1), "1" should be dropped and "7" should be corrected to "8" in your proposed text. 
>