RE: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim

"Nobo Akiya (nobo)" <nobo@cisco.com> Sat, 15 November 2014 19:36 UTC

Return-Path: <nobo@cisco.com>
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 155BB1A1B5C for <rtg-bfd@ietfa.amsl.com>; Sat, 15 Nov 2014 11:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.094
X-Spam-Level:
X-Spam-Status: No, score=-115.094 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, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 z67ZuD4HUoo5 for <rtg-bfd@ietfa.amsl.com>; Sat, 15 Nov 2014 11:36:07 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BB2B1A0089 for <rtg-bfd@ietf.org>; Sat, 15 Nov 2014 11:36:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15830; q=dns/txt; s=iport; t=1416080166; x=1417289766; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=MZt6w43315yyDAznNQHvBg9qFoIF0i4nGZVP2xT2pgE=; b=Zz0fafegWlGXUNBi/WwWYSelkAM3rWqSKS8ucKA0IA9N3gnYqWNxxebo GCShXhHjyc4o4UWIhzCyYjuEL4pW/SJEFWeRZvXs5vKJx/jv1+EXtSBFO Y8bZ6HdCQYoIUOxmckBRt30JvQ2pHJxuhkVz8Hl9AI529XkZTb8bV9/Q/ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAPypZ1StJA2H/2dsb2JhbABbgkgjI1VZBNRiAoESFgEBAQEBfYQCAQEBBC1cAgEIEQMBAQELHQcyFAkDBQEBBAESCIg5AdB3AQEBAQEBAQEBAQEBAQEBAQEBAQEBF5BxIBcBgy2BHgWQH4IojTmRPIQKg3xtgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,392,1413244800"; d="scan'208,217";a="372850901"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP; 15 Nov 2014 19:36:05 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sAFJa5E4001724 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtg-bfd@ietf.org>; Sat, 15 Nov 2014 19:36:05 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Sat, 15 Nov 2014 13:36:05 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "MALLIK MUDIGONDA (mmudigon)" <mmudigon@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim
Thread-Topic: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim
Thread-Index: Ac//wAdQ8oS8wTAIRaCZduflS+eKRABcLHWAAAlemEA=
Date: Sat, 15 Nov 2014 19:36:04 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3943F528E9A@xmb-aln-x01.cisco.com>
References: <CECE764681BE964CBE1DFF78F3CDD3943F5279D0@xmb-aln-x01.cisco.com> <D08D4586.27631%mmudigon@cisco.com>
In-Reply-To: <D08D4586.27631%mmudigon@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.98.48]
Content-Type: multipart/alternative; boundary="_000_CECE764681BE964CBE1DFF78F3CDD3943F528E9Axmbalnx01ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/euO-ZfcHupc60bU74zjIVyUoo0k
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: Sat, 15 Nov 2014 19:36:09 -0000

Hi Mallik,

Many thanks for providing your comments.

Thanks!

-Nobo


From: MALLIK MUDIGONDA (mmudigon)
Sent: Saturday, November 15, 2014 2:33 AM
To: Nobo Akiya (nobo); rtg-bfd@ietf.org
Subject: Re: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim

Hi Nobo,

Replies inline

Regards
Mallik

From: "Nobo Akiya (nobo)" <nobo@cisco.com<mailto:nobo@cisco.com>>
Date: Friday, 14 November 2014 9:34 am
To: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Subject: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim

[Speaking as an individual S-BFD contributor]

Hi BFD WG,

There were couple of questions I need your input on draft-akiya-bfd-seamless-alert-discrim.


(1) Should the "extended" S-BFD use cases move to draft-ietf-bfd-seamless-use-case?

My opinion is yes. Once the "extended" S-BFD use cases have been incorporated into draft-ietf-bfd-seamless-use-case, then we should try to move draft-ietf-bfd-seamless-use-case forward.

How does the WG feel about this?

Mallik>> Agree. Since this is another use case of SBFD it makes sense to have all in one place.


(2) Should the alert discriminator proposal move to draft-ietf-bfd-seamless-base?

My opinion is no . Instead we should position this as an optional feature of S-BFD (hence separate document than the base), especially considering we likely need to think through additional security concerns raised by this.

A question was raised by Greg on how does a node find out if the target supports the optional alert discriminator or not. We can define a mandatory diagnostic value that must be implemented when the alert discriminator is implemented. One can send an S-BFD control packet with the alert discriminator with this diagnostic value to check if the target supports the alert discriminator mechanism.

How does the WG feel about this?

Mallik>> Agree. Since this is an optional feature using the base proposal of SBFD, we can have it as a separate document.

Thanks!

-Nobo