Re: [OSPF] Ospfv3 Options
Acee Lindem <acee@cisco.com> Wed, 19 April 2006 09:46 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FW9G4-00071t-81; Wed, 19 Apr 2006 05:46:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FW9G2-00071o-Si for ospf@ietf.org; Wed, 19 Apr 2006 05:45:58 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW9G1-0000cR-Kg for ospf@ietf.org; Wed, 19 Apr 2006 05:45:58 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 19 Apr 2006 02:45:57 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.04,133,1144047600"; d="scan'208"; a="26180497:sNHT23000568"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k3J9jvTL017745; Wed, 19 Apr 2006 05:45:57 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 19 Apr 2006 05:45:57 -0400
Received: from [10.82.208.175] ([10.82.208.175]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 19 Apr 2006 05:45:56 -0400
Message-ID: <444606D1.1040405@cisco.com>
Date: Wed, 19 Apr 2006 05:45:53 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vivek Dubey <vivek_ospf@rediffmail.com>
Subject: Re: [OSPF] Ospfv3 Options
References: <20060419075656.28760.qmail@webmail36.rediffmail.com>
In-Reply-To: <20060419075656.28760.qmail@webmail36.rediffmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Apr 2006 09:45:56.0799 (UTC) FILETIME=[0E9C0CF0:01C66396]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: OSPF List <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
Hi Vivek, Vivek Dubey wrote: >draft-ietf-ospf-ospfv3-update-08: >A.2 The Options field - V6 bit and R-bit > >How does Ospf for Ipv6 decides whether to "set/clear" these bits in Options advertised. Are they part of configuration? > > The R bit allows a router to be reachable via it's stub networks without being used for transit traffic. I would expect this to be a configuration option for multi-homed hosts. It also could be set in situations where the router is running BGP and it has not yet converged (ala, RFC 3137). The V6 bit was an attempt at supporting multiple address families in OSPFv3. However, more protocol constructs than this bit are needed. You can reference the drafts we are currently considering for support of multiple topologies/address families. >Or "draft-ietf-ospf-cap-08.txt" could be used to advertise these capabilities. > > This draft wouldn't be applicable here. It is for optional OSPFv2/OSPFv3 capabilities. Hope this helps, Acee >Thanks >Vivek > > > > > > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >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
- [OSPF] Ospfv3 Options Vivek Dubey
- Re: [OSPF] Ospfv3 Options Acee Lindem