RE: [pim] About Concluded working group
"CTO YAO Chunyan" <Chunyan.YAO@alcatel-sbell.com.cn> Thu, 17 August 2006 02:54 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDY1M-0005Oz-Ui; Wed, 16 Aug 2006 22:54:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDY1L-0005OJ-P8 for pim@ietf.org; Wed, 16 Aug 2006 22:54:11 -0400
Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177] helo=mail.alcatel-sbell.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDY1H-00009R-1L for pim@ietf.org; Wed, 16 Aug 2006 22:54:11 -0400
Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1]) by mail.alcatel-sbell.com.cn (8.12.11/8.12.11/Alcanet1.0) with ESMTP id k7H2lf42005481; Thu, 17 Aug 2006 10:47:49 +0800
Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Thu, 17 Aug 2006 10:53:54 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [pim] About Concluded working group
Date: Thu, 17 Aug 2006 10:52:55 +0800
Message-ID: <9570C1261494D54D9D3115BC2C83429A02A52C38@asbmail2.sbell.com.cn>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [pim] About Concluded working group
Thread-Index: Aca/lH+2DsFu4gk0QAW4B/88XKtIOgCEzmyw
From: CTO YAO Chunyan <Chunyan.YAO@alcatel-sbell.com.cn>
To: prashantj@huawei.com, Stig Venaas <stig.venaas@uninett.no>
X-OriginalArrivalTime: 17 Aug 2006 02:53:54.0551 (UTC) FILETIME=[60926070:01C6C1A8]
X-imss-version: 2.042
X-imss-result: Passed
X-imss-approveListMatch: *@alcatel-sbell.com.cn
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: ycai@cisco.com, pim@ietf.org
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Errors-To: pim-bounces@ietf.org
Dear all, Thanks for your answers.
Sometimes an IETF working group may be concluded, eg. "ngtrans", but some RFCs worked out by that working group is still on the standard track. So who will update the RFCs in standard track after the relative working group being concluded?
With regards!
Yao
-----Original Message-----
From: Prashant Jhingran [mailto:prashantj@huawei.com]
Sent: 2006年8月14日 18:38
To: 'Stig Venaas'; CTO YAO Chunyan
Cc: ycai@cisco.com; pim@ietf.org
Subject: RE: [pim] About anycast RP
Perhaps it might be RFC4610....
http://ring.aist.go.jp/archives/doc/RFC/authors/rfc4610.txt
Cheers,
Prashant
-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no]
Sent: Monday, August 14, 2006 4:57 PM
To: CTO YAO Chunyan
Cc: ycai@cisco.com; pim@ietf.org
Subject: Re: [pim] About anycast RP
CTO YAO Chunyan wrote:
> Dear all,
> Now Anycast RP 's latest description is in
> "draft-ietf-pim-anycast-rp-07.txt";
> Many vendors' routers support it ( Alcatel's SR 7750, Cisco's
> Router,....)
> Why it is still in Internet-draft now? and is it intended for entering
> into IETF standard track?
It's in the RFC Editor's queue and should be an RFC soon now. It's been
waiting for the new PIM spec. These are all in AUTH48, which means that
they should be out very soon (historically AUTH48 used to take only 48
hours but...).
Stig
>
> Best wishes,
>
> Yao
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim
_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim
- RE: [pim] About Concluded working group CTO YAO Chunyan