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

"Nobo Akiya (nobo)" <nobo@cisco.com> Sat, 15 November 2014 19:34 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 BE2811A1BBC for <rtg-bfd@ietfa.amsl.com>; Sat, 15 Nov 2014 11:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.095
X-Spam-Level:
X-Spam-Status: No, score=-115.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Zh9qL-GTGuOW for <rtg-bfd@ietfa.amsl.com>; Sat, 15 Nov 2014 11:34:44 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E587A1A1B8D for <rtg-bfd@ietf.org>; Sat, 15 Nov 2014 11:34:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2519; q=dns/txt; s=iport; t=1416080083; x=1417289683; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=GH15eJ++Z+gcwcQXUM7mRIWdHyeH5EDAVX7mHDedc0s=; b=HlH1IobKYcMNQE0ogODo/oixnoYj7mohbbYvIjw0Xao5g8Q4ttrGP0eM 41ZZvGoVNNk0xe9JN84EilXT/EMlHSa2kVERxsIeky7YMnv3b4JHEivGx ETTPddadrKkLADzbB+W5p9s1eUpNvj9Opph8TePvyQlcEyIH6RIBZpHGN U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAD6qZ1StJA2M/2dsb2JhbABbgmsjgS4E1GICgRIWAQEBAQF9hAIBAQEEOksEAgEIEQQBAQsUCQcyFAkDBQEBBAESCIg5AdB4AQEBAQEBAQEBAQEBAQEBAQEBAQEBF5BxOAaDJ4EeAQSQH4IojTmDVI1ohAqDfG2BSIEDAQEB
X-IronPort-AV: E=Sophos;i="5.07,392,1413244800"; d="scan'208";a="96986736"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-8.cisco.com with ESMTP; 15 Nov 2014 19:34:43 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id sAFJYhi4008625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Nov 2014 19:34:43 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0195.001; Sat, 15 Nov 2014 13:34:42 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.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+eKRAA6JQPgABibFWA=
Date: Sat, 15 Nov 2014 19:34:42 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3943F528E8A@xmb-aln-x01.cisco.com>
References: <CECE764681BE964CBE1DFF78F3CDD3943F5279D0@xmb-aln-x01.cisco.com> <7347100B5761DC41A166AC17F22DF1121B88381A@eusaamb106.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B88381A@eusaamb106.ericsson.se>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/7s5q2yKxBN8nGPXw9zRQ9Xd6Qbo
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:34:46 -0000

Hi Greg,

Many thanks for taking time to provide your comments.

Thanks!

-Nobo

> -----Original Message-----
> From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
> Sent: Friday, November 14, 2014 9:57 PM
> To: Nobo Akiya (nobo); rtg-bfd@ietf.org
> Subject: RE: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim
> 
> Hi Nobo, et. al,
> please find my notes in-line and tagged GIM>>.
> 
> 	Regards,
> 		Greg
> 
> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Nobo Akiya
> (nobo)
> Sent: Thursday, November 13, 2014 8:04 PM
> To: 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?
> 
> GIM>> I think it makes sense to have use cases related to S-BFD in one
> document. Support.
> 
> (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?
> 
> GIM>> After discussing structure of BFD for multi-point networks document
> I realized that keeping protocol extensions in separate documents has its
> value, especially if an extension is optional. Hence I change my previously
> stated position and support progress alert discriminator document
> separately from S-BFD base.
> 
> Thanks!
> 
> -Nobo