IETF Logo Mail Archive

RE: Status of WGLCs

Santosh P K <santoshpk@juniper.net> Mon, 25 May 2015 10:06 UTC

Return-Path: <santoshpk@juniper.net>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22EAB1B2B5E for <rtg-bfd@ietfa.amsl.com>; Mon, 25 May 2015 03:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qUBbnUmiYfLw for <rtg-bfd@ietfa.amsl.com>; Mon, 25 May 2015 03:06:03 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0126.outbound.protection.outlook.com [207.46.100.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ABBA1B2B60 for <rtg-bfd@ietf.org>; Mon, 25 May 2015 03:05:59 -0700 (PDT)
Received: from SN1PR0501MB1760.namprd05.prod.outlook.com (25.163.130.27) by SN1PR0501MB1760.namprd05.prod.outlook.com (25.163.130.27) with Microsoft SMTP Server (TLS) id 15.1.166.22; Mon, 25 May 2015 10:05:58 +0000
Received: from SN1PR0501MB1760.namprd05.prod.outlook.com ([25.163.130.27]) by SN1PR0501MB1760.namprd05.prod.outlook.com ([25.163.130.27]) with mapi id 15.01.0166.017; Mon, 25 May 2015 10:05:58 +0000
From: Santosh P K <santoshpk@juniper.net>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: Status of WGLCs
Thread-Topic: Status of WGLCs
Thread-Index: AQHQk85WglJXGArXzk2RfjP3ZW3WWZ2MfP3A
Date: Mon, 25 May 2015 10:05:57 +0000
Message-ID: <SN1PR0501MB1760B49EF4A8090400E41986B3CD0@SN1PR0501MB1760.namprd05.prod.outlook.com>
References: <20150521135940.GA25032@pfrc.org>
In-Reply-To: <20150521135940.GA25032@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=santoshpk@juniper.net;
x-originating-ip: [116.197.184.11]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0501MB1760;
x-microsoft-antispam-prvs: <SN1PR0501MB1760A6DA9C1B6AFCDD422894B3CD0@SN1PR0501MB1760.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(520002)(3002001); SRVR:SN1PR0501MB1760; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0501MB1760;
x-forefront-prvs: 058707456E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(377454003)(199003)(51704005)(189002)(66066001)(19580405001)(2501003)(76576001)(50986999)(2656002)(87936001)(19580395003)(86362001)(76176999)(54356999)(64706001)(102836002)(5001770100001)(106116001)(68736005)(107886002)(81156007)(62966003)(99286002)(189998001)(122556002)(101416001)(92566002)(2950100001)(5001860100001)(5001830100001)(97736004)(4001540100001)(74316001)(106356001)(33656002)(40100003)(2900100001)(46102003)(5001960100002)(105586002)(77156002)(17423001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0501MB1760; H:SN1PR0501MB1760.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 May 2015 10:05:57.6353 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB1760
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/OtlPNEBYAZqj8wTrnZ2y2Xo0FbY>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 May 2015 10:06:07 -0000

I am not aware for IPR related to S-BFD documents. 

Thanks
Santosh P K 

> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Jeffrey Haas
> Sent: Thursday, May 21, 2015 7:30 PM
> To: rtg-bfd@ietf.org
> Subject: Status of WGLCs
> 
> The S-BFD documents - use cases, base and IP - have passed WGLC.
> However, there are authors who still haven't made their IPR attestations.
> Thus the S-BFD documents are in a holding pattern until we get these last
> attestations.
> 
> For draft-ietf-bfd-rfc5884-clarifications, we still haven't gotten IPR
> attestations from Kalyani Rajaraman and Sam Aldrin.  More importantly, no
> one has actually stated that they believe this document is ready to progress.
> Santosh P K has also noted some items that must be addressed before the
> document can progres.
> 
> -- Jeff

v2.23.0 | Report a Bug | By Email