IETF Logo Mail Archive

Re: [Softwires] Mail regarding draft-tsou-softwire-bfd-ds-lite

"Zhouqian (Cathy)" <cathy.zhou@huawei.com> Mon, 28 April 2014 09:30 UTC

Return-Path: <cathy.zhou@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 375861A0786 for <softwires@ietfa.amsl.com>; Mon, 28 Apr 2014 02:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 d3XpXwRL_9HO for <softwires@ietfa.amsl.com>; Mon, 28 Apr 2014 02:30:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 740E11A0707 for <softwires@ietf.org>; Mon, 28 Apr 2014 02:30:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDP07114; Mon, 28 Apr 2014 09:30:28 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 28 Apr 2014 10:28:56 +0100
Received: from SZXEMA410-HUB.china.huawei.com (10.82.72.42) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 28 Apr 2014 10:30:06 +0100
Received: from SZXEMA512-MBX.china.huawei.com ([169.254.7.124]) by SZXEMA410-HUB.china.huawei.com ([10.82.72.42]) with mapi id 14.03.0158.001; Mon, 28 Apr 2014 17:29:59 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "draft-tsou-softwire-bfd-ds-lite@tools.ietf.org" <draft-tsou-softwire-bfd-ds-lite@tools.ietf.org>
Thread-Topic: Mail regarding draft-tsou-softwire-bfd-ds-lite
Thread-Index: Ac9aQnAh6MBF9X6xTia1JEN4vf3AgQIUsJGg
Date: Mon, 28 Apr 2014 09:29:58 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF3A5133BA@SZXEMA512-MBX.china.huawei.com>
References: <CECE764681BE964CBE1DFF78F3CDD3941E10B311@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10B311@xmb-aln-x01.cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.76.105]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/57dByJLRk_Os99fwZClYp9EEyNU
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] Mail regarding draft-tsou-softwire-bfd-ds-lite
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 09:30:34 -0000

Hi Nobo,
Sorry for late reply. Please see inline.

Best Regards,
Cathy


> -----Original Message-----
> From: Softwires [mailto:softwires-bounces@ietf.org] On Behalf Of Nobo Akiya
> (nobo)
> Sent: Thursday, April 17, 2014 9:56 PM
> To: draft-tsou-softwire-bfd-ds-lite@tools.ietf.org
> Cc: softwires@ietf.org
> Subject: [Softwires] Mail regarding draft-tsou-softwire-bfd-ds-lite
> 
> Hi Authors,
> 
> Couple of questions around proposed the BFD solution.
> 
> 1. Is the goal for B4 to detect [lack of] reachability to AFTR? Or does the goal
> include AFTR to keep state of which B4s are *speaking to it*?


It depends on specific technology, e.g., if PCP is used, AFTR does not keep the state of which B4s it is speaking to .
But if some bidirectional technology is used, e.g., BFD, AFTR will keep the state.
> 
> 2. It's fairly clear how BFD session can be instantiated/maintained on B4 (to
> AFTR). However, I'm not clear on how BFD sessions are
> instantiated/maintained on AFTR (to B4s). Is there some sort of automatic
> mechanism, or is this configured?
BFD sessions could be sent from AFTR only after B4 firstly initiated the session. So the answer is that this is configured.
> 
> -Nobo
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires

v2.41.0 | Report a Bug | By Email | System Status