From seal_sum@yahoo.co.in Fri Jun 12 02:45:27 2009 Return-Path: X-Original-To: isis-wg@core3.amsl.com Delivered-To: isis-wg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45F1F3A6B31 for ; Fri, 12 Jun 2009 02:45:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 Rntp9m3YxIsl for ; Fri, 12 Jun 2009 02:45:26 -0700 (PDT) Received: from web8504.mail.in.yahoo.com (web8504.mail.in.yahoo.com [202.43.219.166]) by core3.amsl.com (Postfix) with SMTP id C578F3A67CC for ; Fri, 12 Jun 2009 02:45:25 -0700 (PDT) Received: (qmail 62684 invoked by uid 60001); 12 Jun 2009 09:45:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s1024; t=1244799929; bh=4HfjwVkaMOL3c2/smh+agVk6aTvZydCVwIl8WmyAnPU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=JGlA6XHh7sGpkU+Bcm/1gyUX+VjZWDbz0mbgnXY44eenYu2xPzJBoJDeNlOAOa1t8VWJLVzOoUZlQSZuxJfqq/vcQbHpoBOY5RvcWMqQD0NkfYY3MhpkE7JjSRWKzRFxne3oU//rEJgrZa8QgOwQhKrmr365s9vUV1YFS04f7qc= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=VdeZDlv2aKZD2+sjWdKP3Kc02jtJV/7QyAFKayxsZXx5PiSmXryAVICoHUYxc/jojZuPHwLuMBP72FjRHMRzwFJ2wCGtTzkdBthO2/K9cS8vF1PZeGB+sxIkx2va0L9O8zDjcHfvH6PmzG9A5kL8E3kMm8JhHeMV2nA4OK6VnKU=; Message-ID: <425831.62155.qm@web8504.mail.in.yahoo.com> X-YMail-OSG: DnTs.5QVM1l_FnVue_oDAN5mrap3SZZVqhpXdn.eXjjggEtPGk92hyfyurCLHd0jSRl0f1p.cjBihl.AyKBMS97Eznw9axPwR_neQN_8IV7IHiYx5ilMOaIZhTuq2kKCG_OM3AGAMus7yfSaBq241n3nYcTz5pRBMTlzwEKvEdtdEVGW.fWToCqzztDWeUFPQwfikYoMuCwY2d71.4jEQ1I2WQXW6w-- Received: from [121.243.14.254] by web8504.mail.in.yahoo.com via HTTP; Fri, 12 Jun 2009 15:15:29 IST X-Mailer: YahooMailClassic/5.4.12 YahooMailWebService/0.7.289.15 Date: Fri, 12 Jun 2009 15:15:29 +0530 (IST) From: Sumanta Seal To: isis-wg@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-248019892-1244799929=:62155" Subject: Re: [Isis-wg] RFC 5306 on Restart Signaling for IS-IS X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 09:45:27 -0000 --0-248019892-1244799929=:62155 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, The new RFC 5306 obsoletes the existing one for ISIS GR=0A(3847). But this = new RFC does not includes any update or modification=0Aor correction over t= he existing one. I am wondering why this new RFC=0Awas introduced obsoletin= g the old one. Can anybody please let me know=0Athe reason behind it. Thanks, Sumanta=0A=0A=0A Bollywood news, movie reviews, film trailers and more= ! Go to http://in.movies.yahoo.com/ --0-248019892-1244799929=:62155 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi all,

The new RFC 5306 obsolete= s the existing one for ISIS GR=0A(3847). But this new RFC does not includes= any update or modification=0Aor correction over the existing one. I am won= dering why this new RFC=0Awas introduced obsoleting the old one. Can anybod= y please let me know=0Athe reason behind it.

Thanks,
Sumanta

=0A=0A=0A
Cricket on= your mind? Visit the ultimate cricket website. Enter now! --0-248019892-1244799929=:62155-- From mshand@cisco.com Fri Jun 12 03:21:37 2009 Return-Path: X-Original-To: isis-wg@core3.amsl.com Delivered-To: isis-wg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 231AE3A6BE3 for ; Fri, 12 Jun 2009 03:21:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 eNSSTz89SyIt for ; Fri, 12 Jun 2009 03:21:36 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id B4D1F3A68CC for ; Fri, 12 Jun 2009 03:21:35 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.42,209,1243814400"; d="scan'208";a="42654823" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 12 Jun 2009 10:21:41 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5CALfP0011891; Fri, 12 Jun 2009 12:21:41 +0200 Received: from [10.61.103.81] (dhcp-10-61-103-81.cisco.com [10.61.103.81]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5CALeeD007138; Fri, 12 Jun 2009 10:21:41 GMT Message-ID: <4A322C30.8010905@cisco.com> Date: Fri, 12 Jun 2009 11:21:36 +0100 From: mike shand User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Sumanta Seal References: <425831.62155.qm@web8504.mail.in.yahoo.com> In-Reply-To: <425831.62155.qm@web8504.mail.in.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1281; t=1244802101; x=1245666101; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshand@cisco.com; z=From:=20mike=20shand=20 |Subject:=20Re=3A=20[Isis-wg]=20RFC=205306=20on=20Restart=2 0Signaling=20for=20IS-IS |Sender:=20; bh=QkUAf66XlRjpXnlLqtG5bXkUPMyZCElXQZDgrVP5+5M=; b=nUG6BNcH/3pDvZFhs56Fjma8CE6k19eRA5Nh82deivp5BHG5mn7ARjomDY zNrxNq2jAdhbfcU6WIRE10wUYIZrlr7hXto0+xkAZ1rONtWeZYoiRD60iynO xYD3I0QIvH; Authentication-Results: ams-dkim-2; header.From=mshand@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: isis-wg@ietf.org Subject: Re: [Isis-wg] RFC 5306 on Restart Signaling for IS-IS X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 10:21:37 -0000 It is purely procedural. The old one was "informational", whereas the new one is "standards track". Since the IS-IS protocol is technically "owned" by ISO, any IETF work on IS-IS could only be informational. However, following an agreement with ISO, IP related IS-IS work can now become standards track. Hence the change of status, which required the issuance of a new RFC. Similar changes have been made to other IS-IS RFCs. Mike Sumanta Seal wrote: > Hi all, > > The new RFC 5306 obsoletes the existing one for ISIS GR (3847). But > this new RFC does not includes any update or modification or > correction over the existing one. I am wondering why this new RFC was > introduced obsoleting the old one. Can anybody please let me know the > reason behind it. > > Thanks, > Sumanta > > > ------------------------------------------------------------------------ > Cricket on your mind? Visit the ultimate cricket website. Enter now! > > ------------------------------------------------------------------------ > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg > From seal_sum@yahoo.co.in Mon Jun 15 02:40:14 2009 Return-Path: X-Original-To: isis-wg@core3.amsl.com Delivered-To: isis-wg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F27CF3A6931 for ; Mon, 15 Jun 2009 02:40:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 BDhGiBnLSfMU for ; Mon, 15 Jun 2009 02:40:12 -0700 (PDT) Received: from web8506.mail.in.yahoo.com (web8506.mail.in.yahoo.com [202.43.219.168]) by core3.amsl.com (Postfix) with SMTP id 082F03A680E for ; Mon, 15 Jun 2009 02:40:11 -0700 (PDT) Received: (qmail 69481 invoked by uid 60001); 15 Jun 2009 09:40:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s1024; t=1245058801; bh=rnpHoHfp+flSQpQ0nRZo/rQIyrnMOftOUBsiex1+DnE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=AlfT4yJBOybl8WzFpJH6bJOlfYVHKj7W4WU8lZkFpOr6iWoqbr3gWSybVVrXXRWCYje29KUeX3Tq0pZMfZGNVHR80l/5OvOr4LtLPRx0I6QLO7WLCW13KGXuTtxDxcmSldR+Tgxhxw3Uu95y0UaOZ+cZTwbvJL0eU90ir0H9BsA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=dV8C5nW5Glaf3Mko9WJH1ejsiqOzflA+EjutAeJdENd9DpY7w1qfJ0+6blllB/vZg1pUrp9QpH52aqWdkTPJEYLEEZyv0R2/Jf3SBzi51/Y9cQxzmdLNk1PyWmIlziplnXWqoYFfQB+geyTH9b10mLGd6H0x9cnufIFf1qgb2J4=; Message-ID: <971799.69301.qm@web8506.mail.in.yahoo.com> X-YMail-OSG: uLrBFQsVM1l592e5aQ.UkyiqyUe1_9whi1T9xzS2atI93BUuJVpPzsyWE5WwbOj7TS.FsAEZ2m9Lz.q5L9jjKxjZ9qsSxMV0VJDMfUuWkWquD0lFVAY5ljja4a5dQP8njTTug9E2IFph78PJJMy2sd5evy69ZLjz71lS9GY9Eaeexen3mojDAB0Gijr8U_fmybIBDpAYp3MvR0BSG6h9C8zBOqFQ7Q-- Received: from [121.243.14.254] by web8506.mail.in.yahoo.com via HTTP; Mon, 15 Jun 2009 15:10:01 IST X-Mailer: YahooMailClassic/5.4.12 YahooMailWebService/0.7.289.15 Date: Mon, 15 Jun 2009 15:10:01 +0530 (IST) From: Sumanta Seal To: mike shand MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-972738387-1245058801=:69301" Cc: isis-wg@ietf.org Subject: Re: [Isis-wg] RFC 5306 on Restart Signaling for IS-IS X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 09:40:14 -0000 --0-972738387-1245058801=:69301 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Mike. ... Sumanta --- On Fri, 12/6/09, mike shand wrote: From: mike shand Subject: Re: [Isis-wg] RFC 5306 on Restart Signaling for IS-IS To: "Sumanta Seal" Cc: isis-wg@ietf.org Date: Friday, 12 June, 2009, 3:51 PM It is purely procedural. The old one was "informational", whereas the new o= ne is "standards track". Since the IS-IS protocol is technically "owned" by= ISO, any IETF work on IS-IS could only be informational. However, followin= g an agreement with ISO, IP related IS-IS work can now become standards tra= ck. Hence the change of status, which required the issuance of a new RFC. Similar changes have been made to other IS-IS RFCs. =A0=A0=A0Mike Sumanta Seal wrote: > Hi all, >=20 > The new RFC 5306 obsoletes the existing one for ISIS GR (3847). But this = new RFC does not includes any update or modification or correction over the= existing one. I am wondering why this new RFC was introduced obsoleting th= e old one. Can anybody please let me know the reason behind it. >=20 > Thanks, > Sumanta >=20 >=20 > ------------------------------------------------------------------------ > Cricket on your mind? Visit the ultimate cricket website. Enter now! > ------------------------------------------------------------------------ >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg >=A0=A0=A0 =0A=0A=0A Explore and discover exciting holidays and getaways with Yah= oo! India Travel http://in.travel.yahoo.com/ --0-972738387-1245058801=:69301 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

Thanks Mike.

... Sumanta
<= br>


--- On Fri, 12/6/09, mike shand <mshand@cisco.com= > wrote:

From: mike shand <ms= hand@cisco.com>
Subject: Re: [Isis-wg] RFC 5306 on Restart Signaling = for IS-IS
To: "Sumanta Seal" <seal_sum@yahoo.co.in>
Cc: isis-wg= @ietf.org
Date: Friday, 12 June, 2009, 3:51 PM

It is purely procedural. The old one was "informational", whereas th= e new one is "standards track". Since the IS-IS protocol is technically "ow= ned" by ISO, any IETF work on IS-IS could only be informational. However, f= ollowing an agreement with ISO, IP related IS-IS work can now become standa= rds track. Hence the change of status, which required the issuance of a new RFC.

Similar changes have been made to other IS-IS RFCs.

&nb= sp;  Mike

Sumanta Seal wrote:
> Hi all,
>
= > The new RFC 5306 obsoletes the existing one for ISIS GR (3847). But th= is new RFC does not includes any update or modification or correction over = the existing one. I am wondering why this new RFC was introduced obsoleting= the old one. Can anybody please let me know the reason behind it.
> =
> Thanks,
> Sumanta
>
>
> ----------------= --------------------------------------------------------
> Cricket on= your mind? Visit the ultimate cricket website. Enter now! <http://in.rd.yahoo.com/tagline_cricket_1/*http://beta.cricke= t.yahoo.com>
> -----------------------------------------------= -------------------------
>
> _______________________________________________
> Isis-wg mailing li= st
> Isis-wg@ietf.org
> https://www.ietf.org/mailma= n/listinfo/isis-wg
>   

=

=0A
Share files, take= polls, and make new friends - all under one roof. Click here= . --0-972738387-1245058801=:69301--