RE: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case

John E Drake <jdrake@juniper.net> Thu, 26 July 2018 13:46 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC6C130E62; Thu, 26 Jul 2018 06:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level:
X-Spam-Status: No, score=-0.71 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 yrwUHvDeNrwl; Thu, 26 Jul 2018 06:46:44 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA049130E25; Thu, 26 Jul 2018 06:46:44 -0700 (PDT)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6QDdT9h017712; Thu, 26 Jul 2018 06:46:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=GzDvhA2FVk7SCD/syvyfv6CiScKuvWXiYzr6aK6thkQ=; b=pByJ6qxlGZHLStU+YQcvsR6PadOTVzEARWIjUc8FZHwIm5UFnDEtYnKfkK7s68VooyDy HoIzHcvbzFgoFaogy7nPlOyrWEaeLZFzYPI9IfxuV6A2a0tgvfRIWT+l730yq80bfd08 FGE3JW6a2SiqyZh94vn0LhQV4CO/DvD9m2iAKw57IF28RaDQLeFHskIVCqUZzr2dLnNP lZ4xdPccffPh1Ce/qP24gmUj0CxImBs9eJ0jmpv/FZRqX2dA6pc9F0zry6MJIkBNUmC2 qKIcKblh7nw8SLRNZZkodQUlcWnUhGuoFiZLa/chwPISpcn08wUJOLAsBH3UCJtfWxgu bQ==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0048.outbound.protection.outlook.com [216.32.180.48]) by mx0a-00273201.pphosted.com with ESMTP id 2kf9c3rhr9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 26 Jul 2018 06:46:42 -0700
Received: from CY4PR05MB2935.namprd05.prod.outlook.com (10.169.183.145) by CY4PR05MB2790.namprd05.prod.outlook.com (10.169.182.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.995.12; Thu, 26 Jul 2018 13:46:40 +0000
Received: from CY4PR05MB2935.namprd05.prod.outlook.com ([fe80::68a1:4c03:2a14:b3f2]) by CY4PR05MB2935.namprd05.prod.outlook.com ([fe80::68a1:4c03:2a14:b3f2%3]) with mapi id 15.20.1017.000; Thu, 26 Jul 2018 13:46:40 +0000
From: John E Drake <jdrake@juniper.net>
To: Chris Bowers <chrisbowers.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case
Thread-Topic: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case
Thread-Index: AQHUCLY/LO+n8uVNlEC9c6R2Fp2wyqSL6kuAgBXQXdA=
Date: Thu, 26 Jul 2018 13:46:40 +0000
Message-ID: <CY4PR05MB293512BDFF3D45DAB5A7EB54C72B0@CY4PR05MB2935.namprd05.prod.outlook.com>
References: <CAHzoHbvoV209Xq_B_+TUL=YzHy6FDzn=wpi83CAjm=A2yG371g@mail.gmail.com> <CAHzoHbthPcSfsK5B69z5-S9P=WsCQDfbmjMNyHeYb=ZbaDU_cg@mail.gmail.com>
In-Reply-To: <CAHzoHbthPcSfsK5B69z5-S9P=WsCQDfbmjMNyHeYb=ZbaDU_cg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR05MB2790; 6:5ChRsv7avlobpmRBt+excIvSUsC871dx2G8yXSzEJe0GCdxY3fVu5cTzcpZ1nfsx9YGo/pv0QhTyti2/RxouVEzhkx8064EShjMjdkRjIJ7w3Z/IARB56P72oltgUa0ZT2ASCR2dNHxIZYBva4ZXi7K2yQ+E7sEcklmPhP4GxFrjGqGgiduwRshrNZr8D9dCYuSoYzkkCCGvl1mvNC44flcCNP96fzXD0tMgAe5jPkx7TlMFqCA3nr3+ZdOHW33STEWyVj1KbfdIl2b9HtY9HaBjR16mpbOfqwN8nkNH+jwpNr26PEx6MTcX5qAVkwIs00SFFvxyBWFeZywduoyRE39czfMG94wmF788Hd8KKc3Ld/+mtFCPuhkN6Vh6SxeXaAyRZ1KTDVr4/bOFIkCA9Ik2xZ59anEhgWzFvkmmX/DkYtUNjHgwA0xXXIG0RMrbJX5+3GGsRpqGr/UPJEccQg==; 5:BeX1eNRF4wtWyhV8C1R/GYwliV/ApF8ql5Nvbj98s2q+LPktev+rK7bZxPBgriFUq7MEugL80mAkjiL1RAoFHkWyOHLQRBV5lDjwQVx5j07wPK8IdB9rRFcy7yDBnID5D+H69io6jN5MKC4bpXyj92Ph/mv5eQmOl1eD5q/lORg=; 7:oIj3rFn3nSs+gDAlmNRxqvBZjLCxlsvXtE1aUkgurq6lBXUd9nw+S19d2Zvr/e0/MxpEZ7SmxLMXrzJ/f9gSCEfDewibl+Da7i4JcOhbTpgSsWChzsjywS5kEGR46yKjjQeAyaXG5IZvevBJODdmW1Oi7uPZIMXwScEZIOPboSy2cl8YN+rCMJurWU7EtfK9I/gCjVCnGKC508VUSQOHgyNize7vVDNJuWvOlnABKgjIUoXpaOGRwQYWqSLbacWU
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: b3869a60-77c2-4834-b21e-08d5f2fe3745
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600073)(711020)(4618075)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:CY4PR05MB2790;
x-ms-traffictypediagnostic: CY4PR05MB2790:
x-microsoft-antispam-prvs: <CY4PR05MB2790A50A04849A9951D0C4F1C72B0@CY4PR05MB2790.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(120809045254105)(85827821059158)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3231311)(944501410)(52105095)(3002001)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:CY4PR05MB2790; BCL:0; PCL:0; RULEID:; SRVR:CY4PR05MB2790;
x-forefront-prvs: 07459438AA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(39860400002)(346002)(376002)(396003)(189003)(52254002)(199004)(478600001)(105586002)(966005)(106356001)(2900100001)(68736007)(66066001)(53936002)(86362001)(606006)(33656002)(97736004)(256004)(2906002)(229853002)(102836004)(6436002)(8936002)(55016002)(2501003)(236005)(790700001)(74316002)(8676002)(5250100002)(5660300001)(81166006)(25786009)(476003)(54896002)(9686003)(6306002)(81156014)(3846002)(486006)(6116002)(39060400002)(14454004)(6246003)(7696005)(6506007)(53546011)(26005)(76176011)(186003)(11346002)(446003)(7736002)(19609705001)(99286004)(110136005)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB2790; H:CY4PR05MB2935.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 7uwB5OGCUjX4yA8yjJH48u3mfY6V2rblhT3iyL+31ECoNyXeO4Pr5k3URanH/vdh+HV0SLK+Nkj5UZ4IWk9+Qm9jDkQid632YpVKe2W/fS1bKW/CTfsWfpZ9fK8hIk2KkZnN7oCqJ60JV1rCYxa6tRR52J5ZdE0AY6gnrFnCtePdJwblv1JF4Q+L1v2jumYXKviqLQAQDYynlXa5nREfPvO9+gMmMYt/bqgpiDh2iEPcl2I3R3MpxZwsW8fCAt4QpSdVJWCOfu8cqT+w3KcJACOw55bakf/OdDjZ2Kj9oHCZHAY6Jf9+Ue3a/hk68mU5TIrroag3ua5Wyh1smqjWB3Bsm2N4PASKvAZqHW87/zg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR05MB293512BDFF3D45DAB5A7EB54C72B0CY4PR05MB2935namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: b3869a60-77c2-4834-b21e-08d5f2fe3745
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2018 13:46:40.4541 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB2790
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-26_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1807260143
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/JRAFUDuCK7_bIlCxsT_w5RHlaqw>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2018 13:46:48 -0000

Chris,

I saw your note, below, and read the draft.  It seems to me to be a straightforward and useful application of P2MP BFD to improve VRRP performance.

Yours Irrespectively,

John

From: rtgwg <rtgwg-bounces@ietf.org>; On Behalf Of Chris Bowers
Sent: Thursday, July 12, 2018 12:32 PM
To: RTGWG <rtgwg@ietf.org>;; rtg-bfd@ietf.org
Subject: Re: working group adoption poll for draft-mirsky-bfd-p2mp-vrrp-use-case

RTGWG,

This WG adoption poll ended last Friday.

One author and one non-author expressed support for adoption,
while no one expressed opposition to adoption. This adoption poll did
not produce any discussion or detailed feedback from anyone about the
draft itself.

I think there needs to be more technical discussion about the mechanism
proposed in this draft on the RTGWG list before consensus can be judged
either way..  I would encourage anyone interested in working on the
mechanism proposed in this draft to provide detailed feedback on the list..

Thanks,
Chris


On Wed, Jun 20, 2018 at 11:46 AM, Chris Bowers <chrisbowers.ietf@gmail.com<mailto:chrisbowers.ietf@gmail.com>> wrote:
RTGWG,

The authors of draft-mirsky-bfd-p2mp-vrrp-use-case have requested
that RTGWG adopt this draft as a WG document.
https://datatracker.ietf.org/doc/draft-mirsky-bfd-p2mp-vrrp-use-case/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dmirsky-2Dbfd-2Dp2mp-2Dvrrp-2Duse-2Dcase_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=UGesBa8K-cFmdWFoJiRJAr3d-wmz1tjG4QkPou--BBA&s=JE54j1T5HCOFFMSpIdJeJDt6-vnvxvAXCmvPIxWG4dI&e=>

Please indicate whether or not you support adoption of the draft
as a WG document.  An explanation of why or why not is also very helpful.

The two authors have already indicated that they know of no relevant IPR
other than what has already been disclosed. The draft has two IPR disclosures.
https://datatracker.ietf.org/ipr/3133/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_3133_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=UGesBa8K-cFmdWFoJiRJAr3d-wmz1tjG4QkPou--BBA&s=pk16VtPdqbuOIUplRaIaqQkLZC5jLktLBIFi-IHpy-A&e=>
https://datatracker.ietf.org/ipr/3135/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_3135_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=UGesBa8K-cFmdWFoJiRJAr3d-wmz1tjG4QkPou--BBA&s=XDjKpJ5diMIKS2QsfDqNVTrpGkNSWFZBwSBPV7SZ9RU&e=>

For some history related to this draft, please see:
https://www.ietf.org/mail-archive/web/rtgwg/current/msg06572.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail-2Darchive_web_rtgwg_current_msg06572.html&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=UGesBa8K-cFmdWFoJiRJAr3d-wmz1tjG4QkPou--BBA&s=gQ7Z41wa7_BikpO07YOBcJXMlKJSdvG7DRWJLZzBa5k&e=>

For information about IPR in IETF technology, see RFC 8179.
https://datatracker.ietf.org/doc/rfc8179/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_rfc8179_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=UGesBa8K-cFmdWFoJiRJAr3d-wmz1tjG4QkPou--BBA&s=44SV9gx_BGbW8zWgoAJfTuxz5JmneP2d4ila-ObeKxo&e=>

Note that one of the basic principles regarding how the IETF deals with IPR claims (from RFC 8179)
is that: "The IETF will make no determination about the validity of any particular IPR claim."

Since Jeff Tantsura is a co-author, he will not be involved in judging consensus.

The closing date for this poll is Friday, July 6th.

Thanks,
Chris