[trill] Re. draft-ietf-trill-p2mp-bfd

"MALLIK MUDIGONDA (mmudigon)" <mmudigon@cisco.com> Wed, 19 April 2017 06:10 UTC

Return-Path: <mmudigon@cisco.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA62D131519 for <trill@ietfa.amsl.com>; Tue, 18 Apr 2017 23:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_MIME_MALF=0.01, 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 n05UIHW-IPYv for <trill@ietfa.amsl.com>; Tue, 18 Apr 2017 23:10:18 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E35A313151C for <trill@ietf.org>; Tue, 18 Apr 2017 23:10:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19292; q=dns/txt; s=iport; t=1492582217; x=1493791817; h=from:to:subject:date:message-id:mime-version; bh=ML+CzjAC05Q6VkXoaHFqh6M79jFEYOnQsNBCbVrHKl8=; b=KlwvwJPgiznkILieLs/nH0gcW6FuiVDCLX3RJOpAARBxgzAjLTnUJPhl cG5uPgohLivUX+cXKvubmXl2qQ6sZ2xZpR0QghEXglRxMTvn8UxY15JUg NbRGugJzn3mT/uopwwGWls2shNMb0hSlgrvlPXrZwrXIXCotOLbRy5qQ6 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAQDY/vZY/49dJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm5lYYELB4NgihWSUocuiA+FNIIPIQEKhXgCGoNePxgBAgEBAQEBAQFrHQuFFQEHASErPQEZAwECDRsDAgQdAgYKARQJCgQPBAEcBIgMMYEjAxUOAptakAiCJiuHEA2DaQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GUoFdK4I5NIJRR4FWCYIsOi6CMQWJLJM7OwEbhmiHIIRGggBVhFyKF4sLhFuEJwEfOBIsR2MVRBEBhFQcgWN1B4gBgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.37,219,1488844800"; d="scan'208,217";a="232518804"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2017 06:10:16 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3J6AG3F030302 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <trill@ietf.org>; Wed, 19 Apr 2017 06:10:16 GMT
Received: from xch-rtp-016.cisco.com (64.101.220.156) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Apr 2017 02:10:15 -0400
Received: from xch-rtp-016.cisco.com ([64.101.220.156]) by XCH-RTP-016.cisco.com ([64.101.220.156]) with mapi id 15.00.1210.000; Wed, 19 Apr 2017 02:10:15 -0400
From: "MALLIK MUDIGONDA (mmudigon)" <mmudigon@cisco.com>
To: "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Re. draft-ietf-trill-p2mp-bfd
Thread-Index: AQHSuNOc17MUZDEv7Eal379T8nGegQ==
Date: Wed, 19 Apr 2017 06:10:15 +0000
Message-ID: <770FC83B-469C-4B03-95CF-D037539BA708@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.65.62.87]
Content-Type: multipart/alternative; boundary="_000_770FC83B469C4B0395CFD037539BA708ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/lBQtzCTIe9dwzA9HHSMd0J7VGHc>
Subject: [trill] Re. draft-ietf-trill-p2mp-bfd
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 06:10:20 -0000

Hi,

I support this draft and think it is ready for standardization.

Regards
Mallik
------------------------------------------
From: "Susan Hares" <shares@ndzh.com<mailto:shares@ndzh.com>>
To: <trill@ietf.org<mailto:trill@ietf.org>>
Date: Tue, 7 Feb 2017 11:53:04 -0500
Message-ID: <019f01d28162$a67b9220$f372b660$@ndzh.com<mailto:019f01d28162$a67b9220$f372b660$@ndzh.com>>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01D28138.BDA69B90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdKBYcaNCIttSHamSIWQlu+T7bZSDw==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com<mailto:skh@ndzh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/54KtM2G6PXjIttN8nEGyMDHMOgM>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com<mailto:d3e3e3@gmail.com>>, 'Jon Hudson' <jon.hudson@gmail.com<mailto:jon.hudson@gmail.com>>
Subject: [trill] WG LC on draft-ietf-p2mp-bfd-04.txt - 2/7/2016 to 2/21/2016
X-BeenThere: trill@ietf.org<mailto:trill@ietf.org>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:57:33 -0000

This begins a 2 week WG LC on draft-ietf-trill-p2mp-bfd.  The draft can be
obtained at:



https://datatracker.ietf.org/doc/draft-ietf-trill-p2mp-bfd/



In your comments please consider,



1)      Does the support of multi-point BFD aid deployments?

2)      Are the suggested additions to RFC7177 bootstrapping sufficient for
this technology?

3)      Do you feel this technology is ready for standardization?



Sue Hares

Trill Co-chair