RE: Working Group Last Call on draft-ietf-ccamp-gmpls-rsvp-te-call-00.txt

"Ong, Lyndon" <Lyong@Ciena.com> Thu, 15 June 2006 15:59 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FquFv-0004dG-3S for ccamp-archive@ietf.org; Thu, 15 Jun 2006 11:59:39 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FquFp-0005KZ-HH for ccamp-archive@ietf.org; Thu, 15 Jun 2006 11:59:39 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1Fqu8x-000NcK-LI for ccamp-data@psg.com; Thu, 15 Jun 2006 15:52:27 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE, SPF_SOFTFAIL autolearn=no version=3.1.1
Received: from [63.118.39.27] (helo=mdmxm02.ciena.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <Lyong@Ciena.com>) id 1Fqu8o-000Nbp-DH for ccamp@ops.ietf.org; Thu, 15 Jun 2006 15:52:18 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C69093.AE083D1B"
Subject: RE: Working Group Last Call on draft-ietf-ccamp-gmpls-rsvp-te-call-00.txt
Date: Thu, 15 Jun 2006 11:52:16 -0400
Message-ID: <0901D1988E815341A0103206A834DA07DEB8FB@mdmxm02.ciena.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Working Group Last Call on draft-ietf-ccamp-gmpls-rsvp-te-call-00.txt
Thread-Index: AcaI5F2W4YawH5vOSeW8BFFL//gd9wGVg6gA
From: "Ong, Lyndon" <Lyong@Ciena.com>
To: "Brungard, Deborah A, ALABS" <dbrungard@att.com>, ccamp@ops.ietf.org
Cc: Adrian Farrel <adrian@olddog.co.uk>
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874

Hi Deborah,
 
Sorry for the lateness of the comments, but the draft is quite detailed.
Some
of the questions I have are more on the thought behind the procedures
than
the correctness of the procedures.
 
General Comment:
 
Not sure whether this is part of WG Last Call or not, but I certainly
think it would be good
to pass this through ITU Q.12 and Q.14/15 before it is submitted to the
IESG, so that the
definitions and procedures for call can be reviewed for any
inconsistencies.  Hopefully we
will in that way avoid having multiple definitions or defining
procedures that do not fit what
is desired for ASON.
 
I leave it to you and Adrian as to the right way to go about doing this.
 
More Detailed Comments:
 
1. Although the draft does not define a format for the Long Call ID, a
format has been
defined in ITU-T Recommendation G.7713.2, and it might be worth pointing
to this.
 
2. Want to be sure I understand the procedures for the Short Call ID.
Since the field is labeled 
"MUST be zero" in RFC 3209, there could be multiple interpretations:
-- a non-zero value will be received and discarded (zero inserted on
transmission)
-- a non-zero value will be treated as an error and generate an error
response
-- a non-zero value will be treated as an error and the message
discarded
 
It's noted in section 7 that the only way to successfully create
an LSP through a transit node following behavior's (a) or (b) above
would be to upgrade
the LSP - does this mean you could potentially have successful call
setup but failure
of the associated connection setup if the transit LSP behavior is not
correct?
 
3. Are there procedures for when to send a LINK_CAPABILITY object?  It
seems to
be totally optional at both ends.  Is this determined by policy?
 
4. Why is the procedure in section 6.2.1 that the responding side should
assume that the call is successful
if it does not receive an ack to its Notify message?  
 
5. Is refresh of the NOTIFY really necessary if there are active LSPs in
the call?  Possibly the LSP refresh 
could be sufficient, since this carries the short Call ID.  Is it
possible that the call would be dropped while
there are still active LSPs?
 
Cheers,
 
Lyndon