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

Hosnieh Rafiee <> Mon, 07 July 2014 07:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 37D1C1B2791 for <>; Mon, 7 Jul 2014 00:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.852
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xuM7-e3LybND for <>; Mon, 7 Jul 2014 00:50:12 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 80FBD1A8BB3 for <>; Mon, 7 Jul 2014 00:50:11 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BJR88373; Mon, 07 Jul 2014 07:50:10 +0000 (GMT)
Received: from ([fe80::b810:863:a57e:3ff]) by ([::1]) with mapi id 14.03.0158.001; Mon, 7 Jul 2014 08:50:06 +0100
From: Hosnieh Rafiee <>
To: "" <>
Thread-Topic: [Openv6] A new APONF use case FW: New Version Notification for draft-bi-aponf-sdsavi-00.txt
Thread-Index: Ac+YI+oyl/kqmL/6STObUCWuBm5jRgBkNkbw
Date: Mon, 7 Jul 2014 07:50:05 +0000
Message-ID: <>
References: <007c01cf9823$edf92840$c9eb78c0$>
In-Reply-To: <007c01cf9823$edf92840$c9eb78c0$>
Accept-Language: zh-CN, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Mon, 07 Jul 2014 07:50:13 -0000

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