Re: [Openv6] A new APONF use case FW: New Version Notification for draft-bi-aponf-sdsavi-00.txt

"Guang Yao" <> Wed, 09 July 2014 05:19 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 69BFF1A0327 for <>; Tue, 8 Jul 2014 22:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lmT0h3IKKZB5 for <>; Tue, 8 Jul 2014 22:19:40 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D821C1A026C for <>; Tue, 8 Jul 2014 22:19:39 -0700 (PDT)
Received: from AndrewYaoPC (unknown []) by centos (Coremail) with SMTP id AQAAf3AL3wLi0LxTuEMTAA--.542S2; Wed, 09 Jul 2014 13:19:30 +0800 (CST)
From: "Guang Yao" <>
To: "'Hosnieh Rafiee'" <>, <>
References: <007c01cf9823$edf92840$c9eb78c0$> <>
In-Reply-To: <>
Date: Wed, 9 Jul 2014 13:19:29 +0800
Message-ID: <006401cf9b35$5c439a60$14cacf20$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHanPkWuaRxubkJINqi6cMysuRZzQLHbqkhm2rtU5A=
Content-Language: zh-cn
X-Coremail-Antispam: 1UD129KBjvJXoWxJF4fZrWrXw1DKr1DGF4fAFb_yoWrXryrpa nIqFZrGrWkAr1xCw4vqw1jgr1F9FWrJFW7JF98J34kAFy3XF129Fy09r15Z345XryfJr40 qr4UuryUCw1fX3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUgYb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_Gr0_Xr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVW8Jr0_Cr1UM28EF7xvwVC2z280aVCY1x0267AKxVW8Jr 0_Cr1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40Ex7xfMcIj 6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lF7 xvr2IYc2Ij64vIr40E4x8a64kEw24lc2xSY4AK67AK6r4rMxAIw28IcxkI7VAKI48JMI8I 3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxV WUXVWUAwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8I cVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87 Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZF pf9x07jOxhLUUUUU=
X-CM-SenderInfo: 51drw3xdqjquphuqv3oohg3hdfq/
Subject: Re: [Openv6] A new APONF use case FW: New Version Notification for draft-bi-aponf-sdsavi-00.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Jul 2014 05:19:42 -0000

Dear Hosnieh,

Thank you very much for your comments. 

At first, I can well understand "Openv6", but currently I'm not quite sure
about "APONF". This doc is originally written for "Openv6"; however, I'm
still not sure about it is an APONF-style "application" even after we try to
use the concepts specified in APONF. I think this doc is a requirement doc
rather than a solution design.

I'm not sure I fully understand your question, but I will try to answer it
to my best of my understanding. I think the first step is the SAVI
application should have a way to identify which nodes are important, and
thus their addresses. We suppose such an interface should be provided by
APONF, e.g., it can tells which nodes are servers, which nodes are hosts.
What the SAVI application need is just prevent the hosts from spoofing the
addresses of servers. If the node is dynamic attached, APONF may still have
some way to tell its role, then things will be much the same. 

If APONF does not intent to support this, we will check what APONF can
provide to SAVI and re-design it. Though APONF is supposed to provide an
"Abstract View" to the applications, currently there is not a detailed doc
on it. At least the SAVI application deeply depends on the view can be
achieved. We sincerely expect the doc.

Best regards,

-----Original Message-----
From: Openv6 [] On Behalf Of Hosnieh Rafiee
Sent: Monday, July 07, 2014 3:50 PM
Subject: Re: [Openv6] A new APONF use case FW: New Version Notification for

I have read this version. I found a typo and have a question.


- " and the decide" -> remove "the"

- I actually skimmed some of SAVI documents. What I understand from those
documents is that they try to create a bindings between the port and the
node. So, IMHO, still there might be a risk in initial steps where nodes
identify themselves to SAVI device. In this step, if there is a bad guy in
the network, he can claim the address of any other nodes. This is , of
course, no risk if the IP addresses does not have any meaning. In other
words, the IP addresses are not the IP addresses of nodes who are important
in the network. I think this risk is almost zero for the case where SeND is
in use but when there is DHCP server in use then this risk is still possible
since a node can advertise any IP address. So, I guess, in this case for
important nodes, even for initial steps, human interaction is needed.

Now the question is how do you plan to handle this when you want to have
also a dynamic port? 

Thank you,

-----Original Message-----
From: [] 
Sent: Saturday, July 5, 2014 2:42 AM
To: Jun Bi; Guang Yao; Guang Yao; Jun Bi
Subject: New Version Notification for draft-bi-aponf-sdsavi-00.txt

A new version of I-D, draft-bi-aponf-sdsavi-00.txt has been successfully
submitted by Guang Yao and posted to the IETF repository.

Name:		draft-bi-aponf-sdsavi
Revision:	00
Title:		Software Defined SAVI
Document date:	2014-07-04
Group:		Individual Submission
Pages:		4

   This document is about the APONF use case for SAVI.


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

The IETF Secretariat

Openv6 mailing list

Openv6 mailing list