[pim] PIM RP register mechanism
"CTO YAO Chunyan" <Chunyan.YAO@alcatel-sbell.com.cn> Fri, 16 June 2006 09:57 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrB5Q-0000eA-T0; Fri, 16 Jun 2006 05:57:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrB5Q-0000c9-01 for pim@ietf.org; Fri, 16 Jun 2006 05:57:56 -0400
Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177] helo=mail.alcatel-sbell.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrB5O-0000rF-6v for pim@ietf.org; Fri, 16 Jun 2006 05:57:55 -0400
Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1]) by mail.alcatel-sbell.com.cn (8.12.11/8.12.11/Alcanet1.0) with ESMTP id k5G9rAQ7001299 for <pim@ietf.org>; Fri, 16 Jun 2006 17:53:10 +0800
Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Fri, 16 Jun 2006 17:57:51 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [pim] PIM RP register mechanism
Date: Fri, 16 Jun 2006 17:57:51 +0800
Message-ID: <9570C1261494D54D9D3115BC2C83429A023F112C@asbmail2.sbell.com.cn>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [pim] PIM RP register mechanism
Thread-Index: AcaRE/HYNbXGdjEzTjydSTMtBWDr/gAEB04w
From: CTO YAO Chunyan <Chunyan.YAO@alcatel-sbell.com.cn>
To: pim@ietf.org
X-OriginalArrivalTime: 16 Jun 2006 09:57:51.0021 (UTC) FILETIME=[54472DD0:01C6912B]
X-imss-version: 2.040
X-imss-result: Passed
X-imss-approveListMatch: *@alcatel-sbell.com.cn
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Errors-To: pim-bounces@ietf.org
Dear all: I have a question on PIM-SM RP register mechanism: Why there
needs this term "( SwitchToSptDesired(S,G) AND ( inherited_olist(S,G) ==
NULL ))" in pseudocode describing action when RP receiving following a
Register message in PIM-SM protocol (v2-new-12)?
The text is as the following:
"draft-ietf-pim-sm-v2-new-12.txt", Part 4.4.2---- Receiving Register
Messages at the RP:
When an RP receives a Register message, the course of action is decided
according to the following pseudocode:
packet_arrives_on_rp_tunnel( pkt )
{
if( I_am_RP(G) AND outer.dst == RP(G) ) {
.....
if ( SPTbit(S,G) OR
( SwitchToSptDesired(S,G) AND ( inherited_olist(S,G) == NULL
))) {
send Register-Stop(S,G) to outer.src
sentRegisterStop = TRUE;
}
......
} else {.....
}
}
many thanks!
Chunyan
_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim
- [pim] PIM RP register mechanism CTO YAO Chunyan