From suketusoni@hotmail.com Wed Sep 2 01:17:25 2009 Return-Path: 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 F35B43A68E2 for ; Wed, 2 Sep 2009 01:17:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.121 X-Spam-Level: ** X-Spam-Status: No, score=2.121 tagged_above=-999 required=5 tests=[AWL=2.119, BAYES_50=0.001, HTML_MESSAGE=0.001] 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 kC1O5tsRdino for ; Wed, 2 Sep 2009 01:17:24 -0700 (PDT) Received: from bay0-omc2-s14.bay0.hotmail.com (bay0-omc2-s14.bay0.hotmail.com [65.54.246.150]) by core3.amsl.com (Postfix) with ESMTP id 3E31A3A6781 for ; Wed, 2 Sep 2009 01:17:24 -0700 (PDT) Received: from BAY144-W5 ([65.55.155.40]) by bay0-omc2-s14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Sep 2009 00:59:42 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_ebbf2e45-5305-4021-88bb-d43033d1f1cc_" X-Originating-IP: [47.152.204.133] From: suketu soni To: Date: Wed, 2 Sep 2009 07:59:41 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 02 Sep 2009 07:59:42.0000 (UTC) FILETIME=[53DAEB00:01CA2BA3] Subject: [OSPF] Describing a point-to-point link in Router LSA X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Sep 2009 08:55:26 -0000 --_ebbf2e45-5305-4021-88bb-d43033d1f1cc_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi=2C A point-to-point link type is included twice in a Router-LSA. 1) As Link Type =3D 1 (p2p)=2C with neighboring router's RID as Link ID. Th= is happens when the adjacency status is FULL. 2) As Link Type =3D 3 (stub)=2C with IP subnet address as Link ID. This hap= pens when the interface state is point-to-point=2C regardless of the status= of adjacency. I found out that if a point-to-point link is used as passive-interface=2C t= hen adjacency will not be formed. Hence=2C link type =3D 1 advertizement wi= ll be absent. However=2C a link type =3D 3 advertizement of such a link mak= es it reachable. Please share more examples where it helps to advertize a p2p link type in t= wo ways. My intention is to understand the need for having two types of adv= ertizements for the same p2p link. Thank you. Best wishes Suketu Soni _________________________________________________________________ Log on to MSN India for a lowdown on what=92s hot in the world today http://in.msn.com= --_ebbf2e45-5305-4021-88bb-d43033d1f1cc_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi=2C

A point-to-point link type is included twice in a Router-LSA.<= BR>
1) As Link Type =3D 1 (p2p)=2C with neighboring router's RID as Link= ID. This happens when the adjacency status is FULL.

2) As Link Type= =3D 3 (stub)=2C with IP subnet address as Link ID. This happens when the i= nterface state is point-to-point=2C regardless of the status of adjacency.<= BR>
I found out that if a point-to-point link is used as passive-interfa= ce=2C then adjacency will not be formed. Hence=2C link type =3D 1 advertize= ment will be absent. However=2C a link type =3D 3 advertizement of such a l= ink makes it reachable.

Please share more examples where it helps to= advertize a p2p link type in two ways. My intention is to understand the n= eed for having two types of advertizements for the same p2p link.

Th= ank you.

Best wishes
Suketu Soni
One blink is all it t= akes for the world to change. One click and MSN India helps you catch up Try it! = --_ebbf2e45-5305-4021-88bb-d43033d1f1cc_-- From prvs=489c1a11f=acee@redback.com Wed Sep 2 10:47:52 2009 Return-Path: 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 6D55428C16A for ; Wed, 2 Sep 2009 10:47:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.113 X-Spam-Level: X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, J_CHICKENPOX_93=0.6] 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 52H-wfPprCO5 for ; Wed, 2 Sep 2009 10:47:51 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id 8AB1E28C113 for ; Wed, 2 Sep 2009 10:47:44 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.44,319,1249282800"; d="scan'208";a="4969806" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 02 Sep 2009 10:39:49 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 324DABB1A6; Wed, 2 Sep 2009 10:39:49 -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 01983-04; Wed, 2 Sep 2009 10:39:49 -0700 (PDT) Received: from [IPv6???1] (svilogin-1.sj.us.am.ericsson.se [155.53.154.39]) by prattle.redback.com (Postfix) with ESMTP id A1A7DBB1A7; Wed, 2 Sep 2009 10:39:48 -0700 (PDT) In-Reply-To: <20090901010503.C0199312E15@bosco.isi.edu> References: <20090901010503.C0199312E15@bosco.isi.edu> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Acee Lindem Date: Wed, 2 Sep 2009 13:39:47 -0400 To: Daniel Joyal , Vishwas Manral X-Mailer: Apple Mail (2.753.1) Cc: OSPF List Subject: Re: [OSPF] RFC 5643 on Management Information Base for OSPFv3 X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Sep 2009 18:11:58 -0000 Dan, Vishwas, Thanks to all the hard work on this MIB. This document has special significance to me as it is was the only unfinished item that was on the OSPF WG charter when I started as a co-chair. Acee On Aug 31, 2009, at 9:05 PM, rfc-editor@rfc-editor.org wrote: > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5643 > > Title: Management Information Base for OSPFv3 > Author: D. Joyal, Ed., > V. Manral, Ed. > Status: Standards Track > Date: August 2009 > Mailbox: djoyal@nortel.com, > vishwas@ipinfusion.com > Pages: 95 > Characters: 192945 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-ospf-ospfv3-mib-15.txt > > URL: http://www.rfc-editor.org/rfc/rfc5643.txt > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in IPv6-based internets. In > particular, it defines objects for managing the Open Shortest Path > First (OSPF) Routing Protocol for IPv6, otherwise known as OSPF > version 3 (OSPFv3). [STANDARDS TRACK] > > This document is a product of the Open Shortest Path First IGP > Working Group of the IETF. > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and > suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/ > rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > USC/Information Sciences Institute > > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf From prvs=489c1a11f=acee@redback.com Wed Sep 2 16:32:36 2009 Return-Path: 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 4C5C43A69E8 for ; Wed, 2 Sep 2009 16:32:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.414 X-Spam-Level: X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 5u6jQaVbgFZn for ; Wed, 2 Sep 2009 16:32:35 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id 52DAA3A67FD for ; Wed, 2 Sep 2009 16:32:35 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.44,321,1249282800"; d="scan'208,217";a="4977528" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 02 Sep 2009 16:32:10 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 3F9849AA9B4; Wed, 2 Sep 2009 16:32:10 -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 24380-09; Wed, 2 Sep 2009 16:32:10 -0700 (PDT) Received: from [IPv6???1] (svilogin-1.sj.us.am.ericsson.se [155.53.154.39]) by prattle.redback.com (Postfix) with ESMTP id CBB5C9AA9B3; Wed, 2 Sep 2009 16:32:09 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: multipart/alternative; boundary=Apple-Mail-5-896705659 Message-Id: From: Acee Lindem Date: Wed, 2 Sep 2009 19:32:08 -0400 To: suketu soni X-Mailer: Apple Mail (2.753.1) Cc: ospf@ietf.org Subject: Re: [OSPF] Describing a point-to-point link in Router LSA X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Sep 2009 23:32:36 -0000 --Apple-Mail-5-896705659 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi Suketu, See inline. On Sep 2, 2009, at 3:59 AM, suketu soni wrote: > Hi, > > A point-to-point link type is included twice in a Router-LSA. > > 1) As Link Type = 1 (p2p), with neighboring router's RID as Link > ID. This happens when the adjacency status is FULL. > > 2) As Link Type = 3 (stub), with IP subnet address as Link ID. This > happens when the interface state is point-to-point, regardless of > the status of adjacency. > > I found out that if a point-to-point link is used as passive- > interface, then adjacency will not be formed. Hence, link type = 1 > advertizement will be absent. However, a link type = 3 > advertizement of such a link makes it reachable. > > Please share more examples where it helps to advertize a p2p link > type in two ways. My intention is to understand the need for having > two types of advertizements for the same p2p link. The two links serve completely different purposes. The type 1 link is to advertise connectivity to the other router, i.e., an edge in the SPF graph, while the type 3 link is to advertise the IP subnet. Thanks, Acee > > Thank you. > > Best wishes > Suketu Soni > One blink is all it takes for the world to change. One click and > MSN India helps you catch up Try it! > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf --Apple-Mail-5-896705659 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=US-ASCII Hi Suketu, 
See inline. 
On Sep 2, 2009, at = 3:59 AM, suketu soni wrote:

= Hi,

A point-to-point link type is included twice in a = Router-LSA.

1) As Link Type =3D 1 (p2p), with neighboring = router's RID as Link ID. This happens when the adjacency status is = FULL.

2) As Link Type =3D 3 (stub), with IP subnet address as = Link ID. This happens when the interface state is point-to-point, = regardless of the status of adjacency.

I found out that if a = point-to-point link is used as passive-interface, then adjacency will = not be formed. Hence, link type =3D 1 advertizement will be absent. = However, a link type =3D 3 advertizement of such a link makes it = reachable.

Please share more examples where it helps to advertize = a p2p link type in two ways. My intention is to understand the need for = having two types of advertizements for the same p2p = link.

The two links serve completely = different purposes. The type 1 link is to advertise connectivity to the = other router, i.e., an edge in the SPF graph, while the type 3 link is = to advertise the IP = subnet. 

Thanks,
Acee 
<= div>


Thank you.

Best = wishes
Suketu Soni
One blink is all it takes for the world to = change. One click and MSN India helps you catch up Try it!
OSPF mailing list
=

= --Apple-Mail-5-896705659-- From wwwrun@core3.amsl.com Fri Sep 4 08:33:38 2009 Return-Path: X-Original-To: ospf@ietf.org Delivered-To: ospf@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id E48053A6A3C; Fri, 4 Sep 2009 08:33:38 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090904153338.E48053A6A3C@core3.amsl.com> Date: Fri, 4 Sep 2009 08:33:38 -0700 (PDT) Cc: ospf mailing list , ospf chair , Internet Architecture Board , RFC Editor Subject: [OSPF] Protocol Action: 'OSPFv2 HMAC-SHA Cryptographic Authentication' to Proposed Standard X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2009 15:33:39 -0000 The IESG has approved the following document: - 'OSPFv2 HMAC-SHA Cryptographic Authentication ' as a Proposed Standard This document is the product of the Open Shortest Path First IGP Working Group. The IESG contact persons are Ross Callon and Adrian Farrel. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ospf-hmac-sha-07.txt Technical Summary This document describes how the NIST Secure Hash Standard family of algorithms can be used with OSPF version 2's built-in cryptographic authentication mechanism. This updates, but does not supercede, the cryptographic authentication mechanism specified in RFC 2328. Working Group Summary No dissent reported (see PROTO writeup by Acee Lindem). Both WG members and members of the security community have reviewed the document. There was controversy as to how the HMAC-SHA digest would be computed and the subject draft is the agreed upon solution. Document Quality The document has been updated in response to Gen-Art and Sec-dir reviews. There is at least one prototype implementation. Personnel Acee Lindem is the Document Shepherd for this document. Ross Callon is the Responsible Area Director. From vishwas.ietf@gmail.com Fri Sep 4 10:17:37 2009 Return-Path: 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 28E8A3A6910 for ; Fri, 4 Sep 2009 10:17:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.163 X-Spam-Level: X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_00=-2.599, J_CHICKENPOX_93=0.6] 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 wlhwKf71JK8u for ; Fri, 4 Sep 2009 10:17:36 -0700 (PDT) Received: from mail-yx0-f190.google.com (mail-yx0-f190.google.com [209.85.210.190]) by core3.amsl.com (Postfix) with ESMTP id 3D33C3A67FE for ; Fri, 4 Sep 2009 10:17:36 -0700 (PDT) Received: by yxe28 with SMTP id 28so936838yxe.19 for ; Fri, 04 Sep 2009 10:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=c/Lv0gh2boWDEVawCoBBK62v3Si6Ya22EPjO9b6KXMk=; b=d4FvNs0QeeshmTgI2+Nq19dKns22AmlkSRmGaGF1QIYuuTAt4QjIxFiUHnrFENGDKQ ll6AUaKDFrYU3WxAclMMjY6Ffyb8sCWUxpZ9U8gkSg4egobs837/ts0JMr0T8fqfEsCw HYhBJGzJ//e/mIsYA/5zR4eC3x3Wx5RT9PjWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xUTXjRNShs+mb97EjqsGgKRnD/D8RQTdWm6NwdDZwlSdZTaOUi6ZilsPVYqLHGaaYo jqIfLlKxrS2TGcbQFdyUWGfXaVFFM24GbDjJm5IOzU0nV+Q3SgANtInD0WHAlx3H21mg txliNum1Ns64ipmQpoy/2Jpy6cDOkhlq67Vu0= MIME-Version: 1.0 Received: by 10.150.175.8 with SMTP id x8mr18901715ybe.40.1252084479392; Fri, 04 Sep 2009 10:14:39 -0700 (PDT) In-Reply-To: References: <20090901010503.C0199312E15@bosco.isi.edu> Date: Fri, 4 Sep 2009 10:14:39 -0700 Message-ID: <77ead0ec0909041014m22981218s1909e882c5ee0bbf@mail.gmail.com> From: Vishwas Manral To: Acee Lindem Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: OSPF List Subject: Re: [OSPF] RFC 5643 on Management Information Base for OSPFv3 X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2009 17:17:37 -0000 Hi Acee, Thanks a lot to you for shepherding this and helping us all along the proce= ss. Thanks again, Vishwas On Wed, Sep 2, 2009 at 10:39 AM, Acee Lindem wrote: > Dan, Vishwas, > Thanks to all the hard work on this MIB. This document has special > significance to me as it is was the only unfinished item that was on the > OSPF WG charter when I started as a co-chair. > Acee > On Aug 31, 2009, at 9:05 PM, rfc-editor@rfc-editor.org wrote: > >> >> A new Request for Comments is now available in online RFC libraries. >> >> >> =A0 =A0 =A0 =A0RFC 5643 >> >> =A0 =A0 =A0 =A0Title: =A0 =A0 =A0Management Information Base for OSPFv3 >> =A0 =A0 =A0 =A0Author: =A0 =A0 D. Joyal, Ed., >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0V. Manral, Ed. >> =A0 =A0 =A0 =A0Status: =A0 =A0 Standards Track >> =A0 =A0 =A0 =A0Date: =A0 =A0 =A0 August 2009 >> =A0 =A0 =A0 =A0Mailbox: =A0 =A0djoyal@nortel.com, >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0vishwas@ipinfusion.com >> =A0 =A0 =A0 =A0Pages: =A0 =A0 =A095 >> =A0 =A0 =A0 =A0Characters: 192945 >> =A0 =A0 =A0 =A0Updates/Obsoletes/SeeAlso: =A0 None >> >> =A0 =A0 =A0 =A0I-D Tag: =A0 =A0draft-ietf-ospf-ospfv3-mib-15.txt >> >> =A0 =A0 =A0 =A0URL: =A0 =A0 =A0 =A0http://www.rfc-editor.org/rfc/rfc5643= .txt >> >> This memo defines a portion of the Management Information Base (MIB) >> for use with network management protocols in IPv6-based internets. =A0In >> particular, it defines objects for managing the Open Shortest Path >> First (OSPF) Routing Protocol for IPv6, otherwise known as OSPF >> version 3 (OSPFv3). =A0[STANDARDS TRACK] >> >> This document is a product of the Open Shortest Path First IGP Working >> Group of the IETF. >> >> This is now a Proposed Standard Protocol. >> >> STANDARDS TRACK: This document specifies an Internet standards track >> protocol for the Internet community,and requests discussion and >> suggestions >> for improvements. =A0Please refer to the current edition of the Internet >> Official Protocol Standards (STD 1) for the standardization state and >> status of this protocol. =A0Distribution of this memo is unlimited. >> >> This announcement is sent to the IETF-Announce and rfc-dist lists. >> To subscribe or unsubscribe, see >> =A0http://www.ietf.org/mailman/listinfo/ietf-announce >> =A0http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >> >> For searching the RFC series, see >> http://www.rfc-editor.org/rfcsearch.html. >> For downloading RFCs, see http://www.rfc-editor.org/rfc.html. >> >> Requests for special distribution should be addressed to either the >> author of the RFC in question, or to rfc-editor@rfc-editor.org. =A0Unles= s >> specifically noted otherwise on the RFC itself, all RFCs are for >> unlimited distribution. >> >> >> The RFC Editor Team >> USC/Information Sciences Institute >> >> >> _______________________________________________ >> 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 > From prvs=496597817=acee@redback.com Wed Sep 9 08:51:08 2009 Return-Path: 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 ECA1D3A69AC for ; Wed, 9 Sep 2009 08:51:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.382 X-Spam-Level: X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 1rLfvGJaapTb for ; Wed, 9 Sep 2009 08:51:07 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id CA7633A6932 for ; Wed, 9 Sep 2009 08:51:07 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.44,359,1249282800"; d="scan'208";a="5106459" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 09 Sep 2009 08:51:38 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 3CEBB9B5E80 for ; Wed, 9 Sep 2009 08:51:38 -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 23239-07 for ; Wed, 9 Sep 2009 08:51:38 -0700 (PDT) Received: from [IPv6???1] (svilogin-1.sj.us.am.ericsson.se [155.53.154.39]) by prattle.redback.com (Postfix) with ESMTP id C1D179B5E7F for ; Wed, 9 Sep 2009 08:51:37 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v753.1) Content-Transfer-Encoding: 7bit Message-Id: <020D8A94-B5BF-43A2-A3AC-DD7AF536E9A6@redback.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: OSPF List From: Acee Lindem Date: Wed, 9 Sep 2009 11:51:36 -0400 X-Mailer: Apple Mail (2.753.1) Subject: [OSPF] FYI: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 15:52:38 -0000 Hi all, This is a 2nd reminder of the Call for Nominations that is underway. We *really* need more nominations in order to properly execute the task of selecting candidates for the open positions. At this time, the number of nominations for all the positions is about 1/2 of what is necessary for the Nomcom to do a conscientious job of evaluating the nominees and we are over 2/3 of the way through the nominations period. Nomcom cannot do their job without this important input from the community. So, please consider making nominations for the open positions - it takes just a few minutes of your time - the details are below. Right now, we just need the names/email addresses for the nominees - we'll be soliciting feedback later. Also, consider that over 1/2 the nominees are not able to accept the nominations for a variety of reasons - e.g., lack of funding, lack of sponsor support, etc. Thus, please consider nominating more than one individual for each of the positions. As well as the reminder for the call for nominations, this email also serves as a reminder for: 2) Local Office Hours 3) Questionnaires available for nominees Best Regards, Mary Barnes nomcom-chair@ietf.org mary.h.barnes@gmail.com mary.barnes@nortel.com ======================================================================== = 1) Call for Nominations ------------------------ The nomination period ends in less than 2 weeks on Sept. 18th, 2009. We appreciate the folks that have taken the time to make nominations thus far. But, we do need more nominations. Please use the online tool to nominate - it's fast, easy and secure: https://wiki.tools.ietf.org/group/nomcom/09/nominate Details on the open positions, as well as other details and options for making nominations are available on the Nomcom homepage: https://wiki.tools.ietf.org/group/nomcom/09/ Please consider that the sooner you make the nominations, the more time your nominee(s) will have to complete the necessary questionnaire (item 3 below). As well, please consider nominating more than one person for a particular position. You will have the opportunity to provide additional feedback later and it's important to consider that not all nominees will be able to accept the nomination. 2) Local office hours ----------------------- In order facilitate additional feedback, the Nomcom has decided to make themselves available for office areas at various geographic locations for 3 weeks in September, starting on the 8th. Below please find the list of locations where Nomcom members will be available for these f2f meetings . Unless dates are identified below, the Nomcom member is generally available for part of the day during the weeks of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than English in which the Nomcom member is fluent are identfied. Please contact a Nomcom member in a specific geographic location to arrange a convenient meeting time and place. Most Nomcom members are flexible as to meeting locations - i.e., we can travel to your office, meet at our offices or somewhere in between. As a reminder folks can always contact any Nomcom member to provide feedback at anytime - i.e., you don't need to participate in these f2f sessions to provide feedback. Belgium: Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be (Sept 21-25) (Languages: French) Boston, Mass, USA: Stephen Kent - kent@bbn.com (Sept 16-18) Boulder, CO, USA: Wassim Haddad - wmhaddad@gmail.com (Sept 14-18) Dallas/Ft. Worth, TX, USA: Mary Barnes - mary.h.barnes@gmail.com Lucy Yong - lucyyong@huawei.com (Languages: Chinese) Helsinki, Finland: Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages: Finnish) Ithaca, NY, USA: Scott Brim - scott.brim@gmail.com Montevideo, Uruguay: Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages: Spanish, Portuguese) Montreal, Quebec, Canada Wassim Haddad - wmhaddad@gmail.com (Sept 8-11) -- Can also be available in Ottawa if folks are interested Paris, France: Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be (Sept 15-18) (Languages: French) San Diego, CA, USA: Randall Gellens - rg+ietf@qualcomm.com Dave Crocker - dcrocker@bbiw.net (Sept 16-18) Silicon Valley/SF Bay, CA, USA: Dave Crocker - dcrocker@bbiw.net (Sept 8-11, Sept 14-15, Sept 21-25) Dorothy Gellert - Dorothy.gellert@gmail.com 3) Questionnaires available for nominees: For folks that have been notified that they have been nominated for any of the positions, the questionnaires are now available on the Nomcom09 tools website: https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire If you have any questions, please let me know. I will be contacting everyone individually, as well as sending reminders. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From prvs=496597817=acee@redback.com Wed Sep 9 12:18:46 2009 Return-Path: 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 8718B3A6803 for ; Wed, 9 Sep 2009 12:18:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.382 X-Spam-Level: X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217, 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 ygbNeobVcpxP for ; Wed, 9 Sep 2009 12:18:45 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id EF9343A67E7 for ; Wed, 9 Sep 2009 12:18:31 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.44,359,1249282800"; d="scan'208";a="5110894" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 09 Sep 2009 12:19:05 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 3D0F3436F; Wed, 9 Sep 2009 12:19:05 -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 10888-05; Wed, 9 Sep 2009 12:19:05 -0700 (PDT) Received: from [IPv6???1] (svilogin-1.sj.us.am.ericsson.se [155.53.154.39]) by prattle.redback.com (Postfix) with ESMTP id 9A864436E; Wed, 9 Sep 2009 12:19:04 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0D911DD0-5F08-492E-B392-5BE7B45BA58B@redback.com> Content-Transfer-Encoding: 7bit From: Acee Lindem Date: Wed, 9 Sep 2009 15:19:05 -0400 To: OSPF List X-Mailer: Apple Mail (2.753.1) Cc: Adrian Farrel Subject: [OSPF] Extensions to OSPF to Support Mobile Ad Hoc Networking (draft-ietf-ospf-manet-or-02.txt) - Change for IANA Allocation Policy Compliance X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 19:18:46 -0000 Since the OSPFv3 Options bits are only allocated through Standards Action (RFC 4940) and this is an experimental draft, the authors have agreed to move the bits to the OSPF LLS type 1 extended options. The alternative would be to re-spin RFC 4940 to change the allocation policy. For your reference, here are the excerpted bit descriptions. 3.2.1 The I Option Bit A new I bit is defined in the OSPFv3 option field. The bit is defined for Hello packets and indicates that only incremental information is present. See Section 3.4 for placement of the I bit within the OSPFv3 options field. 3.3.5 The F Option Bit A single new option bit, the F bit, is defined in the OSPFv3 option field. The F bit indicates that the node supports the Optimized Flooding mechanism as specified in this draft. See Section 3.4 for placement of the F bit. If anyone has any concerns with this change, please speak now or forever hold your peace. Thanks, Acee From wwwrun@core3.amsl.com Wed Sep 30 07:11:03 2009 Return-Path: X-Original-To: ospf@ietf.org Delivered-To: ospf@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id C282C3A67BE; Wed, 30 Sep 2009 07:11:03 -0700 (PDT) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090930141103.C282C3A67BE@core3.amsl.com> Date: Wed, 30 Sep 2009 07:11:03 -0700 (PDT) Cc: ospf@ietf.org Subject: [OSPF] Last Call: draft-ietf-ospf-af-alt (Support of address families in OSPFv3) to Proposed Standard X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ietf@ietf.org List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2009 14:11:03 -0000 The IESG has received a request from the Open Shortest Path First IGP WG (ospf) to consider the following document: - 'Support of address families in OSPFv3 ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-10-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-ospf-af-alt-08.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11690&rfc_flag=0 From wwwrun@core3.amsl.com Wed Sep 30 07:14:37 2009 Return-Path: X-Original-To: ospf@ietf.org Delivered-To: ospf@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 8D6083A67B4; Wed, 30 Sep 2009 07:14:37 -0700 (PDT) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090930141437.8D6083A67B4@core3.amsl.com> Date: Wed, 30 Sep 2009 07:14:37 -0700 (PDT) Cc: ospf@ietf.org Subject: [OSPF] Last Call: draft-ietf-ospf-te-node-addr (Advertising a Router's Local Addresses in OSPF TE Extensions) to Proposed Standard X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ietf@ietf.org List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2009 14:14:37 -0000 The IESG has received a request from the Open Shortest Path First IGP WG (ospf) to consider the following document: - 'Advertising a Router's Local Addresses in OSPF TE Extensions ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-10-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-addr-06.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11748&rfc_flag=0