[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Proposed response to ITU-T SG15 Questions 12 and 14 on ASON Lexicography
Hello Adrian,
I have provided some clarification of the assumptions in-line below,
which may be helpful in determining whether the CCAMP comments are
appropriate.
Regards,
Ben
> -----Original Message-----
> From: owner-ccamp@ops.ietf.org
> [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Adrian Farrel
> Sent: Tuesday, July 19, 2005 6:59 AM
> To: ccamp@ops.ietf.org
> Cc: 'Kireeti Kompella'; zinin@psg.com; Bill Fenner; Scott Bradner
> Subject: Proposed response to ITU-T SG15 Questions 12 and 14
> on ASON Lexicography
>
> Hi,
>
> Please comment on this draft response liaison which I intend
> to send on
> Monday 25th July.
> You can see the original incoming liaison at
> http://www.olddog.co.uk/incoming.htm
>
> Thanks,
> Adrian
> =====
> To: ITU-T SG15 Questions 12 and 14
> From: IETF CCAMP Working Group
> Subject: Response to your liaison on GMPLS/ASON Lexicography
> For: Action
> Deadline: August 31st 2005
>
> The CCAMP Working Group would like to thank SG15 and
> especially Questions
> 12 and 14 for the time and effort they put into providing input and
> feedback on the GMPLS/ASON lexicography Internet-Draft that is being
> developed by CCAMP. Much of the material supplied as direct
> comments or as
> mark-ups to the Internet-Draft has been incorporated into the latest
> revision which is available at
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-aso
> n-lexicography-03.txt
>
> In your liaison you state some assumptions which we would
> like to comment
> on as follows.
>
> - The purpose of the document is to enable those familiar with ASON
> to understand GMPLS terminology in an ASON context
>
> Correct.
>
> - GMPLS terms are described informally in the document in a way that
> is generally consistent with GMPLS (existing RFCs and work
> in progress)
>
> While the definition of GMPLS terms would be helpful for understanding
> GMPLS terms in a GMPLS context, that is not the purpose of
> this document.
This assumption is intended to convey that the descriptions in this
draft
are not definitional (authoritative), but that they can be used as a
basis
for the ASON interpretation (since concise defintions of GMPLS terms are
not available, in part due to the fact that some GMPLS terms in the Lex
draft are not yet used in GMPLS RFCs or internet drafts).
It was not intended to convey anything about their use in a GMPLS
context.
>
> - Based on these descriptions, interpretations of these GMPLS terms
> in ASON terminology are provided
>
> It is intended that the interpretation of the GMPLS terms is
> not based on
> these descriptions, but based on the full meaning of the
> GMPLS terms. The
> descriptions of the GMPLS terms are provided in this
> Internet-Draft for
> context and a brief summary.
This presents a difficult problem. It is not feasible for the ITU
experts to review the ASON interpretations without some basis.
If the intended basis is existing GMPLS RFCs and drafts, a proper
review would require reading and understanding all the uses
of GMPLS terms in those documents. I have attempted this, for
the normative references, and I believe it is unreasonable to expect
this to be an effective method of review. For example, as noted
above, some terms in the Lex draft are not used in the normative
references. In other cases, terms are not used consistently and
it would be difficult for reviewers to determine which uses are
"correct." As a result, a review on this basis may not be feasible
given the time available to ITU experts.
This assumption was included to make the review process tractable.
The ITU experts provided comments based on the descriptions
of GMPLS terms in the Lex draft. If this is not what CCAMP is
expecting, some clarification of the expectations would be helpful.
>
> - CCAMP has primarily responsibility for the descriptions of
> GMPLS terms
>
> Correct.
>
> - Q12/15 has responsibility to provide input to the GMPLS-ASON
> interpretations (based on the descriptions in this draft)
>
> We welcome this assumption of responsibility by Q12/15 to
> provide input to
> the Internet-Draft. While the Internet-Draft remains under the overall
> editorial control of the CCAMP working group, we hope to be
> able to use
> the text supplied by Q12/15 with only editorial changes.
This is the understanding of SG15 as well (that SG15 would provide
comments, not finished text). The comments were provided in the
liaison as edited text as a convenience, not intended as final text.
>
>
Snip...
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================