Re: [savi] AD review of draft-ietf-savi-framework
"Jun Bi" <junbi@cernet.edu.cn> Fri, 27 May 2011 11:56 UTC
Return-Path: <junbi@cernet.edu.cn>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DDAE0679 for <savi@ietfa.amsl.com>; Fri, 27 May 2011 04:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.489
X-Spam-Level:
X-Spam-Status: No, score=-97.489 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FH_HAS_XAIMC=2.696, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BorIgYpMA-eG for <savi@ietfa.amsl.com>; Fri, 27 May 2011 04:56:22 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id 88715E0688 for <savi@ietf.org>; Fri, 27 May 2011 04:56:20 -0700 (PDT)
Received: from junbiVAIOz138([59.66.24.191]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm114ddfc44c; Fri, 27 May 2011 19:56:18 +0800
Message-ID: <44FC25D1DD22493EAC47AAA563439C61@junbiVAIOz138>
From: Jun Bi <junbi@cernet.edu.cn>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>, savi@ietf.org
References: <4DDC19D4.2040104@piuha.net><634BEF66B2B74684B180B35F2C94BCEB@junbiVAIOz138> <4DDF50BD.7080301@it.uc3m.es>
In-Reply-To: <4DDF50BD.7080301@it.uc3m.es>
Date: Fri, 27 May 2011 19:56:16 +0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="response"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3508.1109
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3508.1109
X-AIMC-AUTH: junbi
X-AIMC-MAILFROM: junbi@cernet.edu.cn
X-AIMC-Msg-ID: OyWevZ0B
Subject: Re: [savi] AD review of draft-ietf-savi-framework
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/savi>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2011 11:56:23 -0000
Yes, marcelo is right. I rememer in the round of WG chair review, it was discussed, so I think the text below in the curren verison already reflects the Marcelo's meaning. "is to minimize the complexity of the common case: many link deployments today either ...... or, equivalently from the perspective of the SAVI method, separate IP address assignment methods into different IP address prefixes. " thanks, Jun -----原始邮件----- From: marcelo bagnulo braun Sent: Friday, May 27, 2011 3:20 PM To: savi@ietf.org Subject: Re: [savi] AD review of draft-ietf-savi-framework one reply El 25/05/11 3:46, Jun Bi escribió: > >> configuration method, in addition to the variant that handles all IP >> address assignment methods, is to minimize the complexity of the >> common case: many link deployments today either are constrained to a >> single IP address assignment methods or, equivalently from the >> perspective of the SAVI method, separate IP address assignment >> methods into different IP address prefixes. The SAVI method for such >> links can be simpler than the SAVI method for links with multiple IP >> address assignment methods per IP address prefix. >> > The reason to develop SAVI method variants for each single IP address > > Hmm. I'm not sure I buy this. First of all, I would claim that many > links support multiple address assignment methods. For instance, dual > stack links typically today support SLAAC for IPv6 and DHCP for IPv4. > And its obvious that to fly in the IETF, the SAVI solution needs to > support multiple methods. I would just replace the above text with: > The difficult case here is when different methods are used to assign addresses _from the same prefix_ This case is complicated because different methods can assign the same address and SAVI needs to be able to determine which is the winning method. So, while i agree with you that it is fairly common the case where multiple address assignment methods are used in a given link, i believe that the case where multiple address assignement methods assign addresses from the same prefix is much less common. I guess we need to make the distinction clearer in the document. Regards, marcelo _______________________________________________ savi mailing list savi@ietf.org https://www.ietf.org/mailman/listinfo/savi
- [savi] AD review of draft-ietf-savi-framework Jari Arkko
- Re: [savi] AD review of draft-ietf-savi-framework Jun Bi
- Re: [savi] AD review of draft-ietf-savi-framework marcelo bagnulo braun
- Re: [savi] AD review of draft-ietf-savi-framework Jun Bi
- Re: [savi] AD review of draft-ietf-savi-framework Jun Bi
- Re: [savi] AD review of draft-ietf-savi-framework Jari Arkko