Re: [BEHAVE] [Behave] Re: Some comments about draft-chen-behave-rsnat-00

Chen Gang <phdgang@gmail.com> Wed, 22 July 2009 10:57 UTC

Return-Path: <phdgang@gmail.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F4A428C368 for <behave@core3.amsl.com>; Wed, 22 Jul 2009 03:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.129
X-Spam-Level:
X-Spam-Status: No, score=-1.129 tagged_above=-999 required=5 tests=[AWL=1.469, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOsOTTIuqoMg for <behave@core3.amsl.com>; Wed, 22 Jul 2009 03:57:02 -0700 (PDT)
Received: from mail-px0-f184.google.com (mail-px0-f184.google.com [209.85.216.184]) by core3.amsl.com (Postfix) with ESMTP id 3FFAE3A6948 for <behave@ietf.org>; Wed, 22 Jul 2009 03:57:02 -0700 (PDT)
Received: by pxi14 with SMTP id 14so88785pxi.29 for <behave@ietf.org>; Wed, 22 Jul 2009 03:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=UpYTXLeJ00iq1BxFXSsiq+MJvfcLx1FLHbxiq3bIKvw=; b=hAomEAbpFQAlgmcltyG1K3ZCXkc8MYlYBrSTC7iK8d583ObDZYK5bIVbXskg01EI+l x0nxPrigpOAZw2fMT9j9nHTikX1dZVNjA8LTl7jS14MjAhv5nF0ohRHveWPoPF7iW347 gHBJ1x98uRlfta2vunM+jk9CGVRc7M/P3SQJc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SBr6Ifk173W1Ya+8VQI5s6RbT9dzRDBEVOnf2lQ4Td+8ZilAvrsH7GS9R9HFqefTYU 0w0vAB2xSmBujSNPy3dQ0adOIZVlIma3/iizDkNFvc6JnSkt11o7DHoeEt392jtjnxqS IT0Vr7RObW1M1WHphOvQpDYj8t20JtfqBVE64=
MIME-Version: 1.0
Received: by 10.142.164.10 with SMTP id m10mr216437wfe.140.1248260189554; Wed, 22 Jul 2009 03:56:29 -0700 (PDT)
In-Reply-To: <08BA2C59E081884DB2AAE4A0BE9D6DC13FA965@ftrdmel0.rd.francetelecom.fr>
References: <08BA2C59E081884DB2AAE4A0BE9D6DC13FA6E1@ftrdmel0.rd.francetelecom.fr> <36ba02b00907210904l6f43d50bn916bbfa4f1923bd3@mail.gmail.com> <08BA2C59E081884DB2AAE4A0BE9D6DC13FA965@ftrdmel0.rd.francetelecom.fr>
Date: Wed, 22 Jul 2009 18:56:29 +0800
Message-ID: <36ba02b00907220356w64a3b2bl104c2b85f4569b46@mail.gmail.com>
From: Chen Gang <phdgang@gmail.com>
To: mohamed.boucadair@orange-ftgroup.com
Content-Type: multipart/alternative; boundary="000e0cd242042f8b15046f493992"
Cc: denghui02@gmail.com, xmw@csnet1.cs.tsinghua.edu.cn, behave@ietf.org, songlinjian@csnet1.cs.tsinghua.edu.cn, zhouboyj@chinamobile.com, cuiyong@tsinghua.edu.cn
Subject: Re: [BEHAVE] [Behave] Re: Some comments about draft-chen-behave-rsnat-00
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2009 10:57:03 -0000

Hello Med,

My reply is inline.

Thanks.
2009/7/22 <mohamed.boucadair@orange-ftgroup.com>

>  Dear Gang, all,
>
> Please see inline.
>
> Cheers,
> Med
>
>
> => The terms "reliable" and "scalable" is a sort of qualitative definition
> other than quantitative indicators. Therefore, it's hard to find some
> paremeters to evaluate. The evaluation could be made compared to the
> situation without this mechanisms.
>
 [Med]  I think that providing a set of parameters to qualify scalability is
> useful.
>

=> It could be better. Could you propose some text on that?


>       [original text]5.1.  Address mapping Attribute
>
     Address mapping attribute is an optional transitive attribute that is
>    composed of a set of TLVs.  The type code of the attribute is to be
>    assigned by IANA.  Each TLV contains information corresponding to a
>    particular tunnel technology.  The TLV is structured as follows:
>
>    [comments]A new BGP capability attribute should also be defined to avoid
> session failure  when not supported by both BGP speakers.
>
>    => What does the "new BGP capability attribute" mean? Is new path
> attribute not enough to carry mapping information?
>

> [Med] the capability attribute is required to prevent session failure when
> one of the BGP speakers do not support the @ mapping attribute.
>

=> I guess adding a new capability attributes is an alternative solution to
switch mapping information. However, corresponding to the new capablity
attribute, we might need to define respective message and extend the error
handling. Compared to that, extending path attribute might more easily be
deployed.  Actually, the redundancy mechanisms only need best-effort
performance.

Thanks for your constructive comments.

Gang



>
>