RE: OSPF ASON Routing Solution

["Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>]

Hi Acee,

I agree that the hierarchy used by ASON can be implemented by specifying
how redistribution (i.e. import/export) is done between parent/child
Routing Areas.  In fact, that's captured appendix I of G.7715.

What I am unclear on is what you mean by "OSPF instances".  Since the
import/export is done between ASON areas, this can also be done between
OSPF areas.  If you mean "OSPF instance" in the context of a single OSPF
area, then we are in complete agreement.


Looking forward to productively moving this work forward,

Jonathan Sadler

-----Original Message-----
From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On
Behalf Of Acee Lindem
Sent: Thursday, July 20, 2006 4:40 PM
To: Adrian Farrel
Cc: ccamp@ops.ietf.org
Subject: Re: OSPF ASON Routing Solution

Hi Adrian, Dimitri, et al,

No objection on my part. However, I wanted to make a clarification that
may or may not be obvious to everyone. In Montreal, Dimitri
and I sat down and discussed my comments on the hierarchical
dissemination of ASON routing information between RAs (Routing Areas
in ASON parlance).

Today OSPF does not support an area hierarchy other than the
backbone and non-backbone areas. This specification for ASON  should
not be considered a partial specification of support in OSPF for a new
area hierarchy (specific requirements are stated in the CCAMP
document references). Rather, it should be conceptually viewed as rules
for importing and exporting GMPLS TE data between separate
OSPF instances  (one instance per ASON RA). This was the motivation
for my comment on restating the inter-RA advertisement rules in term of
import/export rather than flooding.

Thanks,
Acee 

Adrian Farrel wrote:
> Just a refresh in case you were travelling.
>
> I am seeking objections to this draft becoming a WG document.
>
> Adrian
> ----- Original Message ----- From: "Adrian Farrel"
<adrian@olddog.co.uk>
> To: <ccamp@ops.ietf.org>
> Sent: Wednesday, July 12, 2006 8:10 PM
> Subject: OSPF ASON Routing Solution
>
>
>> Hi,
>> On Monday in CCAMP we discussed 
>> draft-dimitri-ccamp-gmpls-ason-routing-ospf-00.txt the solutions 
>> draft for OSPF in ASON routing.
>>
>> There is agreement from the OSPF WG chair that we are not treading on

>> toes, and the meeting seemed to say that this was pretty stable.
>>
>> So a this is a quick poll to see if anyone objects to this becoming a

>> WG draft.
>> NB, this is a charter item and we have an obligation to work on this 
>> for the ITU-T.
>>
>> Thanks,
>> Adrian
>>
>> PS Note that a solution does not have to be 100% perfect to become a 
>> WG draft.
>>
>>
>>
>>
>>
>
>
============================================================
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
============================================================