Re: [savi] savi for mixed address assignment environment

"Jun Bi" <junbi@tsinghua.edu.cn> Mon, 08 November 2010 02:33 UTC

Return-Path: <junbi@tsinghua.edu.cn>
X-Original-To: savi@core3.amsl.com
Delivered-To: savi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B95E43A6953 for <savi@core3.amsl.com>; Sun, 7 Nov 2010 18:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.664
X-Spam-Level:
X-Spam-Status: No, score=-97.664 tagged_above=-999 required=5 tests=[AWL=-0.839, BAYES_05=-1.11, CN_BODY_35=0.339, DNS_FROM_RFC_DSN=1.495, MIME_CHARSET_FARAWAY=2.45, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
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 kJgfJZRDZgGz for <savi@core3.amsl.com>; Sun, 7 Nov 2010 18:33:24 -0800 (PST)
Received: from smtp.tsinghua.edu.cn (smtp.tsinghua.edu.cn [166.111.8.81]) by core3.amsl.com (Postfix) with ESMTP id 920AB3A6952 for <savi@ietf.org>; Sun, 7 Nov 2010 18:33:21 -0800 (PST)
Received: from th053201.ip.tsinghua.edu.cn ([59.66.53.201] helo=junbiVAIO) by smtp.tsinghua.edu.cn with esmtpa (Exim 4.69) (envelope-from <junbi@tsinghua.edu.cn>) id 1PFHYC-0006d5-BT for savi@ietf.org; Mon, 08 Nov 2010 10:33:40 +0800
Message-ID: <D627631482624D6C91B6E27548A36149@junbiVAIO>
From: Jun Bi <junbi@tsinghua.edu.cn>
To: SAVI Mailing List <savi@ietf.org>
References: <15152C9F9364411CB3D94E4E2AA92CB1@junbiVAIO> <4CD75FD5.2080909@it.uc3m.es>
In-Reply-To: <4CD75FD5.2080909@it.uc3m.es>
Date: Mon, 08 Nov 2010 10:33:41 +0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="gb2312"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
x-mimeole: Produced By Microsoft MimeOLE V15.4.3502.922
Subject: Re: [savi] savi for mixed address assignment environment
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 08 Nov 2010 02:33:25 -0000

May thanks to Marcelo's quick reply.

The corrent link should be:

https://datatracker.ietf.org/doc/draft-bi-savi-mix

Sorry for any inconvinient.

Best Regards,
Jun Bi

-----原始邮件----- 
From: marcelo bagnulo braun
Sent: Monday, November 08, 2010 10:26 AM
To: Jun Bi
Subject: Re: [savi] savi for mixed address assignment environment

i haven't been able to access to the document, does the link work?


El 08/11/10 3:22, Jun Bi escribió:
> Dear SAVI WG members,
> Please read the draft of savi for mixed address assignment environment
> and provide your comments.
> http://www.ietf.org/staging/draft-bi-savi-mix-00.txt.
> I am going to present it at SAVI WG meeting.
> If you remember, the reason we have this new draft is because during
> my presentation on draft-ietf-savi-dhcp
> in last SAVI WG meeting, the WG decided to move the part of handling
> of dhcp-slaac mixed senario to a new draft .
> The current savi-mix draft considered more mixed senarios for
> co-exisentence of dhcp, slaac, SeND, and static
> (static address assigned and manually configured by administrator at
> SAVI device). Shall we consider this to be
> a preliminary version of WG draft?
> Best Regards,
> Jun Bi
>
>
> _______________________________________________
> savi mailing list
> savi@ietf.org
> https://www.ietf.org/mailman/listinfo/savi