RE: I-D ACTION:draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt

["zafar ali" <zali@cisco.com>]

Hi John, 

Sorry for the delay in reply. In this ID we combined the following two
drafts: 

1. Component Link Recording and Resource Control for GMPLS Link Bundles,
http://www.ietf.org/internet-drafts/draft-zamfir-explicit-resource-control-b
undle-03.txt. We had discuss and agreement on the content on this draft
(especially need for RRO sub-object). 

2. Identification of Component Links of Unnumbered Interfaces,
http://www.ietf.org/internet-drafts/draft-farrel-ccamp-ifid-unnum-00.txt. 

I think your question is for the portion of ID that came from (2), correct? 

Assuming this, here is the rationale. 

RFC3471 defines the following TLVs for IF_ID RSVP_HOP Object. 

   Type Length Format     Description
   --------------------------------------------------------------------
    1      8   IPv4 Addr. IPv4
    2     20   IPv6 Addr. IPv6
    3     12   See below  IF_INDEX                (Interface Index)
    4     12   See below  COMPONENT_IF_DOWNSTREAM (Component interface)
    5     12   See below  COMPONENT_IF_UPSTREAM   (Component interface)

We need following new TLVs to describe Numbered IF_IDs using IF_ID RSVP_HOP
Object.

IPv4 - DOWNSTREAM (Component IF)
IPv4 - UPSTREAM (Component IF)
IPv6 - DOWNSTREAM (Component IF)
IPv6 - UPSTREAM (Component IF)

As the definition in RFC3471 are not sufficient to identify the above
mentioned cases. Agreed? This is where the discussion started. 

It was pointed out that some implementations have IF index assignment such
that IF indexes are only unique within the TE link they belong to. I.e.,
assumption that IF_indexes are NOT box wide unique is not valid across
implementations. In order to accommodate such implementation, we came up
with what is in the ID at the present moment. 

Given this, can you please provide more feedback on how you can improve the
ID? 

Thanks

Regards... Zafar


>-----Original Message-----
>From: owner-ccamp@ops.ietf.org 
>[mailto:owner-ccamp@ops.ietf.org] On Behalf Of John Drake
>Sent: Monday, May 17, 2004 12:05 PM
>To: ccamp@ops.ietf.org
>Subject: FW: I-D 
>ACTION:draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt
>
>
>Zafar,
>
>I'm sorry but I'm a little confused.
>
>What problem is it that you are addressing with this draft 
>that isn't already addressed by RFC 3471/3473/3477 and the 
>bundling draft?
>
>Thanks,
>
>John
>
>-----Original Message-----
>From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
>Sent: Friday, May 14, 2004 12:40 PM
>To: i-d-announce@ietf.org
>Subject: I-D 
>ACTION:draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt
>
>A New Internet-Draft is available from the on-line 
>Internet-Drafts directories.
>
>
>	Title		: Generalized Multi-Protocol Label 
>Switching (GMPLS)
>RSVP-TE 
>			  signaling using Bundled Traffic 
>Engineering (TE)
>Links
>	Author(s)	: Z. Ali, et al.
>	Filename	:
>draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt
>	Pages		: 14
>	Date		: 2004-5-14
>	
>This document is a companion to the Generalized Multi-Protocol Label
>   Switching (GMPLS) RSVP-TE signaling. It extends the TLV definitions
>   of [RFC3471] to provide the means to identify component links of
>   unnumbered link bundles within the IF_ID_RSVP_HOP and IF_ID
>   ERROR_SPEC objects. It also defines the extensions to GMPLS RSVP-TE
>   in support of component link identifiers for explicit resource
>   control and recording over link bundles.
>
>A URL for this Internet-Draft is: 
>http://www.ietf.org/internet-drafts/draft-dimitri-ccamp-gmpls-r
svp-te-bundle
d-links-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-dimitri-ccamp-gmpls-rsvp-te-bundled-links-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.