Re: Working Group Last Call for "Traffic Engineering Extensions to OSPF version 3"

Adrian Farrel <olddog@CLARA.CO.UK> Mon, 23 May 2005 10:43 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12096 for <ospf-archive@LISTS.IETF.ORG>; Mon, 23 May 2005 06:43:19 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <11.010563DA@cherry.ease.lsoft.com>; Mon, 23 May 2005 6:43:18 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 72164807 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 23 May 2005 06:43:17 -0400
Received: from 80.168.70.150 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Mon, 23 May 2005 06:33:16 -0400
Received: from claranet by oceanus.uk.clara.net with local (Exim 4.22) id 1DaAFI-0000Cg-9V; Mon, 23 May 2005 11:33:16 +0100
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Remote_Addr: 156.106.205.33
Message-ID: <E1DaAFI-0000Cg-9V@oceanus.uk.clara.net>
Date: Mon, 23 May 2005 11:33:16 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Adrian Farrel <olddog@CLARA.CO.UK>
Subject: Re: Working Group Last Call for "Traffic Engineering Extensions to OSPF version 3"
Comments: cc: adrian@olddog.co.uk
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi, 

Two comments... 

1. Would it be possible to clarify the behavior if the scope is
  set to some value other than 01? Is it a requirement that the
  scope be ignored in that case, that TE information be allowed
  to be flooded out of the area, or that the LSA is rejected? 

  Given the setting of the U-bit, this may be hard to control
  properly and I suspect the best you can do is say MUST
  be transmitted as 01 and SHOULD only be flooded within
  the area. 

2. Section 4 - Router IPv6 Address TLV 

  "The Router IPv6 Address TLV has type 3, length 16, and a value
   containing a 16 octet local IPv6 address.  It MUST appear in exactly
   one Traffic Engineering LSA originated by an OSPFv3 router supporting
   the TE extensions." 

  I am confused by 'MUST appear in exactly one'.
  Can a router advertise multiple Router addresses? (Hint, please talk to
  the CCAMP ASON Routing design team for a very good reason why the answer
  is "yes".)
  Can a TE LSA contain "orphaned" TLVs? I.e. can we have a continuation TE
  LSA that does not carry a Router Address TLV?
  Given that a router has (probably) more than one "stable IPv6 address
  that is always reachable if there is connectivity to the OSPFv3 router"
  must all of these be advertised in Router Address TLVs? 

  The text needs to cover all of these questions. 

Cheers,
Adrian