RE: One question on draft "draft-vgovindan-l2vpn-evpn-bfd-01"

"Vengada Prasad Govindan (venggovi)" <venggovi@cisco.com> Fri, 28 March 2014 07:15 UTC

Return-Path: <venggovi@cisco.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23081A0496 for <l2vpn@ietfa.amsl.com>; Fri, 28 Mar 2014 00:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 tcEkM-UlYfO5 for <l2vpn@ietfa.amsl.com>; Fri, 28 Mar 2014 00:15:20 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 807681A0488 for <l2vpn@ietf.org>; Fri, 28 Mar 2014 00:15:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8350; q=dns/txt; s=iport; t=1395990918; x=1397200518; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=cZ56wn8f8+VCrRbJRqe/X1p3RZrRk4trgWSCDqT1Els=; b=d3UhLLyiU4bPXLjktwBUhAfHhooaUyARdRtHLm/RjO9f0osrc57oqN1u rmJJIHxDNXnKs6AC8KmOsRemNo5LaQTa6VieS4hIPy6Le7ezCSsxJBfdT qSHN6x+QyYyPneP/s1gZHOlnRMnxHrl0TtL8hCtaDZsLWGYodeHgNEo9K Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAAshNVOtJXHA/2dsb2JhbABZgkJEO1fCbYEaFnSCJQEBAQQtTBACAQgRBAEBCx0HMhQJCAEBBAENBQiHcdFkF45KMQYBgySBFASrAoMwgis
X-IronPort-AV: E=Sophos; i="4.97,749,1389744000"; d="scan'208,217"; a="313584210"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 28 Mar 2014 07:15:17 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2S7FHuk004407 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Mar 2014 07:15:17 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.137]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Fri, 28 Mar 2014 02:15:16 -0500
From: "Vengada Prasad Govindan (venggovi)" <venggovi@cisco.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>, "Samer Salam (ssalam)" <ssalam@cisco.com>, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Subject: RE: One question on draft "draft-vgovindan-l2vpn-evpn-bfd-01"
Thread-Topic: One question on draft "draft-vgovindan-l2vpn-evpn-bfd-01"
Thread-Index: Ac9EClS5DAhT3OoaSgue2MZc8q991wFZO9zgADlsvKA=
Date: Fri, 28 Mar 2014 07:15:16 +0000
Message-ID: <315041E4211CB84E86EF7C25A2AB583D339E17E0@xmb-rcd-x15.cisco.com>
References: <C02846B1344F344EB4FAA6FA7AF481F10F3E136E@SZXEMA502-MBS.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F10F3E136E@SZXEMA502-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.143.1.30]
Content-Type: multipart/alternative; boundary="_000_315041E4211CB84E86EF7C25A2AB583D339E17E0xmbrcdx15ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/eoi-VPuz6ASCu0mgqXiQpady5-g
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Mar 2014 07:15:23 -0000

Hello Frank,
  Sorry for the delay in my response. The reason why IP encapsulation is not preferred is that the BFD packet may go out-of-band since the DIP of the packet inside the MPLS-BFD is 127/8 (different from the IP a data packet may use). Any node hashing on the DIP may cause it take an out-of-band path especially when the packet does not carry an entropy label in the MPLS label stack. Since this issue is not present in the GAL/ G-Ach case the draft recommends that option.
Thanks
Prasad

From: Xialiang (Frank) [mailto:frank.xialiang@huawei.com]
Sent: Thursday, March 27, 2014 9:18 AM
To: Vengada Prasad Govindan (venggovi); Samer Salam (ssalam); Ali Sajassi (sajassi)
Cc: l2vpn@ietf.org
Subject: RE: One question on draft "draft-vgovindan-l2vpn-evpn-bfd-01"

Hi authors, ping your echo.

From: Xialiang (Frank)
Sent: Thursday, March 20, 2014 3:02 PM
To: 'venggovi@cisco.com'.com'; 'ssalam@cisco.com'.com'; 'sajassi@cisco.com'
Cc: l2vpn@ietf.org<mailto:l2vpn@ietf.org>
Subject: One question on draft "draft-vgovindan-l2vpn-evpn-bfd-01"

Hi authors,
I have one question about BFD packet encapsulation: you point out 2 ways: by GAL/G-ACH, or by IP. And you think that the way by IP is not suitable because BFD packets will follow a different path than that of data packets when they use different destination IP address.
Can you clarify the specific reason? And why can the way by GAL/G-ACH avoid this problem of different path?
Thanks!

B.R.
Frank