Re: [OSPF] Anycast Extension to OSPFv3 draft-wang-aospf-00

Acee Lindem <acee@cisco.com> Tue, 12 December 2006 22:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuGJR-0004se-8E; Tue, 12 Dec 2006 17:41:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuGJO-0004sK-RF for OSPF@ietf.org; Tue, 12 Dec 2006 17:41:23 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuGJM-0004VP-Uh for OSPF@ietf.org; Tue, 12 Dec 2006 17:41:22 -0500
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-5.cisco.com with ESMTP; 12 Dec 2006 14:41:20 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id kBCMfKB4003025 for <OSPF@ietf.org>; Tue, 12 Dec 2006 14:41:20 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kBCMfIdI022174 for <OSPF@ietf.org>; Tue, 12 Dec 2006 14:41:20 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Dec 2006 17:41:19 -0500
Received: from [10.82.208.75] ([10.82.208.75]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Dec 2006 17:41:19 -0500
Message-ID: <457F300E.6030009@cisco.com>
Date: Tue, 12 Dec 2006 17:41:18 -0500
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
Subject: Re: [OSPF] Anycast Extension to OSPFv3 draft-wang-aospf-00
References: <22b5a47b0612010106i477c1814p982523d5bacd4698@mail.gmail.com> <457F2DE4.7060009@cisco.com>
In-Reply-To: <457F2DE4.7060009@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Dec 2006 22:41:19.0399 (UTC) FILETIME=[A4243370:01C71E3E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1135; t=1165963280; x=1166827280; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acee@cisco.com; z=From:=20Acee=20Lindem=20<acee@cisco.com> |Subject:=20Re=3A=20[OSPF]=20Anycast=20Extension=20to=20OSPFv3=20draft-wa ng-aospf-00 |Sender:=20; bh=wld9j9wjMlm/8MFDrjL0UdW/PkekVFl/PUD/e595LMA=; b=Sh3hmqLsbjyBK2o3r/50zAr+27OKFVGUg6vTlCQAQ09TQgxo0VO8EDwrRiIRBfz1igzUe3ej tbWggx2245Pe40UqZDnRqF6cJAUA6YV+mDXiwZE8wezI0OY23OeeDXrU;
Authentication-Results: sj-dkim-5; header.From=acee@cisco.com; dkim=pass (si g from cisco.com/sjdkim5002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: OSPF@ietf.org
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

Speaking as a WG Member and author of the RFC 2740 respin:

My opinion is that the protocol extensions described in the draft
are completely unnecessary and the OSPFv3 (RFC 2740 and its
update) already can support anycast addresses as /128 prefixes.
One simply uses the lowest cost path. Note that the protocol
already support configuration of host routes as described in appendix
C.7.

Thanks,
Acee

Acee Lindem wrote:
> Speaking as WG Chair:
>
> I'd like to initiate discussion on this draft so that we can let the 
> authors
> know whether the WG wants to presue it furthers.
>
> Thanks,
> Acee
>
> Yue Wang wrote:
>> This document describes AOSPF (Anycast Extensions to OSPFv3),
>>   a routing protocol which extends OSPFv3 to support anycast, which
>>   we implemented and tested successfully in our IPv6 test bed. And
>>   the performance analysis shows the overhead of AOSPF is low.
>>
>> http://www.ietf.org/internet-drafts/draft-wang-aospf-00.txt
>>
>>
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf
>

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