[savi] RFC6620 Page 17 - Control Trigger
"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Wed, 07 May 2014 06:46 UTC
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 951B41A03B3
for <savi@ietfa.amsl.com>; Tue, 6 May 2014 23:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id F-DHn3iV7Tpq for <savi@ietfa.amsl.com>;
Tue, 6 May 2014 23:46:30 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com
[IPv6:2607:f8b0:400e:c02::235])
by ietfa.amsl.com (Postfix) with ESMTP id 7E3181A024E
for <savi@ietf.org>; Tue, 6 May 2014 23:46:30 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id w10so643698pde.26
for <savi@ietf.org>; Tue, 06 May 2014 23:46:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=from:to:cc:subject:date:message-id:mime-version:content-type
:content-transfer-encoding:thread-index:content-language;
bh=vFQpNRH6E5GluvHmK2HIQrkGisCw8HKj+LzfouuG6FA=;
b=NdsHsxJ9CnFC/30iS+mX8aWK1tP5phVV8VSiJXcyoG6Appstxxr1hI0ytwCXx9rUyQ
s0zrxe09Bf07ZDzOp/YCVCDXYVPgQUAq3bcmHbeXJcc/FUPEaheQLI0BSGJfKCW5gsig
mHFIOm097g38xX5phq5VEIcVCekGKrfGRoZ8FEEOiBLW30zCzegeWNPKFUriQzz5FEAO
sii1IwF6hjrTgF4EKnDzpFitrTD5GNktESgEpCyUxOmftv7nwmjY4+AvPkDga/y6GEZ0
E7Oe/YYRHRmq+9EXe7+UyYp3IsqTuUSU1L1Ndv+DldC7KOdm+VbeRlR+ZkNGYxYZjkys
Bzsw==
X-Received: by 10.66.141.197 with SMTP id rq5mr15502650pab.64.1399445186469;
Tue, 06 May 2014 23:46:26 -0700 (PDT)
Received: from PC ([218.241.103.232])
by mx.google.com with ESMTPSA id qv3sm1294184pbb.87.2014.05.06.23.46.24
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Tue, 06 May 2014 23:46:25 -0700 (PDT)
X-Google-Original-Message-ID: <006b01cf69c0$0f769260$2e63b720$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'SAVI Mailing List'" <savi@ietf.org>,
"'marcelo bagnulo braun'" <marcelo@it.uc3m.es>,
"'Eric Levy- Abegnoli \(elevyabe\)'" <elevyabe@cisco.com>
Date: Wed, 7 May 2014 14:46:20 +0800
Message-ID: <5369d6c1.238b440a.702c.3ae4@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9pwAuOurvC4VDpRCeYZdh2JeuHWg==
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/savi/zrfD1NqNPBAhDyGJiHdvc3YdulY
Subject: [savi] RFC6620 Page 17 - Control Trigger
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 07 May 2014 06:46:31 -0000
More finding in RFC6620, section 3.2.3, page 17 @ VALID
<quote>
o If ... a DAD_NA
packet with the Target Address set to IPAddr is received through a
Validating Port P' other than P, then the SAVI device will execute
the process of sending DAD_NS messages... two NS messages
for that address will be sent by the SAVI device... The DAD_NS message
will be forwarded to
the port P. The state is moved to TESTING_VP...In any case, it MUST
NOT forward the data
packets until the binding has been verified.
</quote>
I am trying to think about when the VP' could received DAD_NA with the
target address as IPAddr.
It sounds the IPAddr is a valid address of the host, which connects under
the VP'.
The only possible case is when the host with IPAddr moves from VP to VP'
during the lifetime of VALID.
But even in this case, when the SAVI device receive a DAD_NS from TP or
VP'', per the following statements in section 3.2.3, page 17 of RFC6620,
<quote>
o If a DAD_NS is received from a Trusted Port, then the DAD_NS
message is forwarded to port P and is also forwarded to the
Trusted Ports....
o If a DAD_NS packet with the Target Address set to IPAddr is
received through a Validating Port P' other than P, ....The DAD_NS
messages will
be forwarded to the port P.
</quote>
the DAD_NS will not forward to the VP' mention above. Right?
So I guess DAD_NA will not happen to receive from the VP'.
Best Regards,
Leaf