Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-discriminator-00.txt

"Nobo Akiya (nobo)" <nobo@cisco.com> Wed, 21 May 2014 01:18 UTC

Return-Path: <nobo@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5DF1A03F6; Tue, 20 May 2014 18:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.152
X-Spam-Level:
X-Spam-Status: No, score=-115.152 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.651, 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 BUStCZViQsG0; Tue, 20 May 2014 18:18:09 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05A1B1A03F5; Tue, 20 May 2014 18:18:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3305; q=dns/txt; s=iport; t=1400635088; x=1401844688; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wlTV2nqSKdI/05rByGrVdKIBeJJX65/hWG9um09piZw=; b=ZmGFPkfpBjVnGnZiIMf28L+X5cSDxhZsX85RReJO1IcpX9MD9bSr54wz cJg57sBKKUnxap4Gx3jWwaeX5LjAZE8WBX4NjslzsVgR5FnDmNBpr4zne 4GqwyRlW68DswXjSVB4K9Gj4PBKc/Z15v3z0CDTc9BmvwY6pbjx25A0J5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al0FAKv9e1OtJA2E/2dsb2JhbABZgmUhgSnEJQGBGBZ0giUBAQEEOj0CDAQCAQgRBAEBCxQJBzIUCQgCBAENBQiIOQHUTheOHTEHBoMlgRUBA60IgXiBQIIw
X-IronPort-AV: E=Sophos;i="4.98,877,1392163200"; d="scan'208";a="326360151"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-1.cisco.com with ESMTP; 21 May 2014 01:18:07 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s4L1I7WF016171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 May 2014 01:18:07 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Tue, 20 May 2014 20:18:07 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Mach Chen <mach.chen@huawei.com>, Hannes Gredler <hannes@juniper.net>
Thread-Topic: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-discriminator-00.txt
Thread-Index: AQHPasw+3TfBhqItW0CgAHCwI2S40Zs3F30AgAliegCAABUCAIAAARwAgAACvoD//61T8IAAWImA//+vVVCAAFe9gP//sQWwAC1upQAAAPyhsAEWkeyAAAVxzVA=
Date: Wed, 21 May 2014 01:18:06 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E157C55@xmb-aln-x01.cisco.com>
References: <20140508144606.23448.98448.idtracker@ietfa.amsl.com> <F3ADE4747C9E124B89F0ED2180CC814F23D873B9@xmb-aln-x02.cisco.com> <9DDF3832-A276-40F1-AF24-2CEAB31E63DC@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F23DB5518@xmb-aln-x02.cisco.com> <922372D3-6CE8-461E-9BD4-94C2B050C37D@juniper.net> <20140514153641.GC13993@pfrc> <CECE764681BE964CBE1DFF78F3CDD3941E14ED44@xmb-aln-x01.cisco.com> <20140514155739.GA14148@juniper.net> <CECE764681BE964CBE1DFF78F3CDD3941E14EDA1@xmb-aln-x01.cisco.com> <7F0CA0C7-CFD2-4B51-BA0A-A7F167B05B42@juniper.net> <CECE764681BE964CBE1DFF78F3CDD3941E14EE6A@xmb-aln-x01.cisco.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25D9C4A26@SZXEMA510-MBX.china.huawei.com> <CECE764681BE964CBE1DFF78F3CDD3941E150962@xmb-aln-x01.cisco.com> <7347100B5761DC41A166AC17F22DF1121B7BFAA3@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7BFAA3@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.255.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/e9rdD7NnCp2PjFdr6HKpysw3hts
Cc: "Les Ginsberg \(ginsberg\)" <ginsberg@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-discriminator-00.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 May 2014 01:18:10 -0000

Hi Greg,

That's true, the whole paragraph in the section 7 of S-BFD base document is just describing some possible implementation techniques. How about we change the paragraph:

[old]
   Note that incoming BFD control packets destined to BFD target
   identifier types may be IPv4, IPv6 or MPLS based.  For those BFD
   target identifier types, implementations MAY either allow the same
   reflector BFD session to handle all incoming BFD control packets in
   address family agnostic fashion, or setup multiple reflector BFD
   sessions to handle incoming BFD control packets with different
   address families.  This policy is again a local matter, and is
   outside the scope of this document.

[new]
   Note that incoming BFD control packets destined to BFD target
   identifier types may be IPv4, IPv6 or MPLS based.  How such packets
   reach an appropriate reflector BFD session is a local matter, and is
   outside the scope of this document.

-Nobo

> -----Original Message-----
> From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
> Sent: Tuesday, May 20, 2014 6:46 PM
> To: Nobo Akiya (nobo); Mach Chen; Hannes Gredler
> Cc: Les Ginsberg (ginsberg); rtg-bfd@ietf.org; isis-wg@ietf.org
> Subject: RE: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-
> discriminator-00.txt
> 
> Dear All,
> according to Section 7 of the S-BFD Base document differentiation among
> address families by S-BFD is optional and mention in connection to separate
> S-BFD reflectors to act as per-AF reflectors. Perhaps I've missed that part of
> S-BFD Base discussion but I don't see the benefit of supporting such mode.
> BFD control packets been AF-agnostic since RFC 5880 and I think that S-BFD
> should maintain that approach.
> 
> I agree with Mach that discriminators in S-BFD, as well as in BFD, are and
> must remain AF blind.
> 
> 	Regards,
> 		Greg
> 
> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Nobo Akiya
> (nobo)
> Sent: Thursday, May 15, 2014 7:07 AM
> To: Mach Chen; Hannes Gredler
> Cc: Les Ginsberg (ginsberg); rtg-bfd@ietf.org; isis-wg@ietf.org
> Subject: RE: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-
> discriminator-00.txt
> 
> Hi Mach, Hannes, et al,
> 
> > IMHO, the capability issue should not be a S-BFD specific issue, even
> > not BFD specified issue. It is actually a forwarding capability issue,
> > it is about whether the target node can process IPv4, IPv6, MPLS, SR
> > encapsulated BFD packets.
> 
> I agree Mach, mostly :)
> 
> I can also see one arguing that forwarding supporting X does not always
> mean S-BFD is supported on X. If we want to address this, then it is an S-BFD
> specific issue, and we _may_ want to solve this via introducing S-BFD
> capability advertisements.
> 
> With that said, S-BFD discriminator advertisement is one area which the
> capability problem can be solved, but not necessary a problem that has to
> be solved with S-BFD discriminator advertisement. Rather I don't think the
> two should be bundled together.
> 
> Let us continue the capability discussion separate from the discriminator
> advertisements?
> 
> -Nobo
>