IETF Logo Mail Archive

Re: WGLC for draft-ietf-bfd-vxlan, ending November 9

"Srihari Raghavan (srihari)" <srihari@cisco.com> Fri, 19 October 2018 07:03 UTC

Return-Path: <srihari@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 343F512777C; Fri, 19 Oct 2018 00:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.564
X-Spam-Level:
X-Spam-Status: No, score=-14.564 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 mohITAEq3-bp; Fri, 19 Oct 2018 00:03:44 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A07D126BED; Fri, 19 Oct 2018 00:03:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2024; q=dns/txt; s=iport; t=1539932624; x=1541142224; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aF2/7HkRHtE1Jj36H9Zw4xEP34BpVCBSNSgET92+sls=; b=loE62rVBz+UCie6GHAA/LVJc1hGpk2PcK7P34BEwa4jjnH319CQ7y8hF ERrnzGmNiLNH943uff5h58VcINakNBSLnKXeIwbhB4rxs8ngDO4OcZEuL GX3zaLZnSCn6tc4Mppc4Jw3gBmc29EqNpMsjtBl6isa8A7jgM+ut+f6ag 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAACrgMlb/4UNJK1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGCBGZ/KAqDa4gYjiiIeI4XFIFmCwEBI4RJAheEbCE0DQ0BAwEBAgEBAm0cDIU5AQEBBB0GEToXBAIBCA4DAwEBAQMCJgICAh8RFQgIAgQBEoMhAYFpAxUPpkuBLoQsARFAgwINghMFgQuKQxeCAIERJx+CTIJWRQIDAYElT4JsMYImAp4NLgkChluGaYMkF4FPhHODFIZTjFB3iFoCERSBJh04gVVwFTsqAYJBixiFPm+KWoEfAQE
X-IronPort-AV: E=Sophos;i="5.54,399,1534809600"; d="scan'208";a="187734091"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2018 07:03:43 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id w9J73g95031096 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Oct 2018 07:03:43 GMT
Received: from xch-rtp-008.cisco.com (64.101.220.148) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 19 Oct 2018 03:03:42 -0400
Received: from xch-rtp-008.cisco.com ([64.101.220.148]) by XCH-RTP-008.cisco.com ([64.101.220.148]) with mapi id 15.00.1395.000; Fri, 19 Oct 2018 03:03:42 -0400
From: "Srihari Raghavan (srihari)" <srihari@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-vxlan@ietf.org" <draft-ietf-bfd-vxlan@ietf.org>
Subject: Re: WGLC for draft-ietf-bfd-vxlan, ending November 9
Thread-Topic: WGLC for draft-ietf-bfd-vxlan, ending November 9
Thread-Index: AQHUZmbQvPcFC9gPr0W78brQSaVmZKUmJUMggACg7IA=
Date: Fri, 19 Oct 2018 07:03:41 +0000
Message-ID: <6B05170E-0D38-44E5-BAB8-9D9A68703955@cisco.com>
References: <20181017221400.GI17157@pfrc.org> <09bf20fa0e2741abbfb46bba1e5f0162@XCH-RCD-020.cisco.com>
In-Reply-To: <09bf20fa0e2741abbfb46bba1e5f0162@XCH-RCD-020.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.143.25.115]
Content-Type: text/plain; charset="utf-8"
Content-ID: <12266A824E92D3428B9F1D6F288D138A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.148, xch-rtp-008.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/tFxEZ2WCS25Dj5y0bNRavevONJ4>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 19 Oct 2018 07:03:46 -0000

Read through the draft and support the same.

Thanks
Srihari
    -----Original Message-----
    From: Jeffrey Haas <jhaas@pfrc.org> 
    Sent: Thursday, October 18, 2018 03:44
    To: rtg-bfd@ietf.org; draft-ietf-bfd-vxlan@ietf.org
    Subject: WGLC for draft-ietf-bfd-vxlan, ending November 9
    
    Working Group,
    
    This starts the Working Group Last Call for BFD for VxLAN.  This last call ends the Friday after IETF, November 9.
    
    https://datatracker.ietf.org/doc/draft-ietf-bfd-vxlan/
    
    Please comment whether you believe this document is ready to advance or not..
    
    There is currently one IPR statement on this draft:
    https://datatracker.ietf.org/ipr/3193/
    
    Authors, please publicly state to the mailing list whether you know of any additional IPR that impacts this draft.
    
    -- Jeff & Reshad
    
    
    
    ----- Forwarded message from Greg Mirsky <gregimirsky@gmail.com> -----
    
    Date: Mon, 8 Oct 2018 07:47:19 -0700
    From: Greg Mirsky <gregimirsky@gmail.com>
    To: rtg-bfd WG <rtg-bfd@ietf.org>, Marc Binderberger <marc@sniff.de>
    Cc: bfd-chairs@ietf.org
    Subject: Fwd: New Version Notification for draft-ietf-bfd-vxlan-03.txt
    
    Dear All,
    the new version is to address comments from Marc (big thank you, Marc).
    Please note that IDNits err on downref to the normative reference to Informational RFC 7348.
    
    Regards,
    Greg

v2.23.0 | Report a Bug | By Email