Re: [OSPF] OSPF WG Last Call for Traffic Engineering Extensions to OSPFversion 3 - draft-ietf-ospf-ospfv3-traffic-10.txt

Acee Lindem <acee@redback.com> Sat, 05 April 2008 15:50 UTC

Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9FAD28C2CE; Sat, 5 Apr 2008 08:50:29 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BD9A3A6A96 for <ospf@core3.amsl.com>; Sat, 5 Apr 2008 08:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.206
X-Spam-Level:
X-Spam-Status: No, score=-2.206 tagged_above=-999 required=5 tests=[AWL=0.393, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0smCy1V7Ser for <ospf@core3.amsl.com>; Sat, 5 Apr 2008 08:50:26 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id D53683A6BBD for <ospf@ietf.org>; Sat, 5 Apr 2008 08:50:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id B4537289F0D; Sat, 5 Apr 2008 08:50:27 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32451-08; Sat, 5 Apr 2008 08:50:27 -0700 (PDT)
Received: from [?*???n?IPv6???1] (login004.redback.com [155.53.12.57]) by prattle.redback.com (Postfix) with ESMTP id EE10A289F09; Sat, 5 Apr 2008 08:50:26 -0700 (PDT)
In-Reply-To: <003001c8968d$ea0217e0$0300a8c0@your029b8cecfe>
References: <A09921AC-BB2D-4450-8476-7CE0C2F24149@redback.com> <003001c8968d$ea0217e0$0300a8c0@your029b8cecfe>
Mime-Version: 1.0 (Apple Message framework v753)
X-Priority: 3
Message-Id: <90CE7EEE-1F2F-44DD-8B58-A5F9C6A49C4B@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Sat, 05 Apr 2008 11:50:25 -0400
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: CCAMP List <ccamp@ops.ietf.org>, OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] OSPF WG Last Call for Traffic Engineering Extensions to OSPFversion 3 - draft-ietf-ospf-ospfv3-traffic-10.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Adrian,

Thanks for the review.

On Apr 4, 2008, at 3:56 PM, Adrian Farrel wrote:

> Hi,
>
> Just a couple of comments...
>
> ===
> Section 1
> s/proposes the addition of/defines/

Changed.


> ===
> Section 4
> Forgive me for not remembering this discussion...
> The draft says that we cannot use the Link ID sub-TLV "due to the  
> protocol
> differences."

The link-ID is cannot be used since, in the case of multi-access  
network, it contains the IPv4 address of the Designated Router (DR).  
OSPFv3 doesn't have this information.


> It then says that the Link ID sub-TLV SHOULD NOT be included  
> (implying that
> it MAY be included under certain circumstances) but MUST be ignored.

This is the spirit of being conservative in what one sends and  
liberal in what one excepts.



> 1. Does ignored mean "continue to be flooded" or "stripped from the  
> LSA"?

In OSPF, only the originator should modify an LSA. So, it means neither.



> 2. Is it not possible to consider operating a GMPLS control plane  
> in an IPv6
> network where the routers use IPv6 addresses to communicate (so all  
> control
> plane messages will be addressed using IPv6, and the router address  
> will be
> IPv6 as described in Section 3) but where the data channel  
> identifiers are
> assigned from an IPv4 address space? Recall that in GMPLS the  
> interfaces
> used for OSPF exchange are not those used for data exchange.

I believe it is probable that IPv4 and IPv6 will coexist. However,  
OSPFv3 doesn't know the IPv4 address of the DR (at least it is not  
standardized). Hence, this isn't the right sub-TLV to reflect this  
topology.



>
> Whatever the answers, I think it would help if the reasons were  
> clarified
> beyond "protocol differences."

I'll expand this to describe the multi-access network case. Sound good?

Thanks,
Acee



> ===
>
> Cheers,
> Adrian
>
> PS I wouldn't mind if you spelled my name right in the acks  
> section :-)
>
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf