Re: [Seamoby] DMHA framework draft architecture
"James Kempf" <kempf@docomolabs-usa.com> Mon, 14 January 2002 18:56 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12666 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 13:56:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19300; Mon, 14 Jan 2002 13:38:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19272 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 13:38:26 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11642 for <seamoby@ietf.org>; Mon, 14 Jan 2002 13:38:22 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id g0EIbLS04006; Mon, 14 Jan 2002 10:37:36 -0800 (PST)
Message-ID: <013901c19d2a$4fbf9f30$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Marco Liebsch <Marco.Liebsch@ccrle.nec.de>, Seamoby <seamoby@ietf.org>
References: <3C42D563.BE04F6F5@ccrle.nec.de>
Subject: Re: [Seamoby] DMHA framework draft architecture
Date: Mon, 14 Jan 2002 10:35:44 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit
Marco, I had been thinking about this change myself. So the basic idea is that the composite paging agent contains that part of the tracking agent that does IP paging area tracking, dormant mode monitoring agent, and that part of the paging agent which initiates IP paging. Another part of the paging agent and tracking agent sits in the access routers. The part in the access router is responsible for taking the L3 paging and tracking protocol and converting it into an L2 paging and tracking protocol, or, if the L2 does not support such a protocol, translating into a last hop L3 protocol to the MN (which actually might be the same as the incoming L3 tracking and paging protocol). I think this architecture would facilitate failover if the composite paging agent for an IP paging area fails. Consider the following scenario. The composite agent keeps track of the subnets it is currently covering. Periodically, it propagates that information to other, neighboring paging agents, just like routing protocols do. Now suppose a paging agent fails and the neighboring agents notice due to an update failing to arrive. The neighboring agents could use a dynamic paging area protocol to arrange for the hosts under the control of the failed paging agent to receive new paging area location informing them that their paging area changed. This would allow the hosts to continue receiving service even though their paging agent failed, without having to use a server duplication protocol for the composite agent. So paging area resiliency would work somewhat like routing resilency, which is a proven benefit of Internet routing. jak ----- Original Message ----- From: "Marco Liebsch" <Marco.Liebsch@ccrle.nec.de> To: "Seamoby" <seamoby@ietf.org> Sent: Monday, January 14, 2002 4:56 AM Subject: [Seamoby] DMHA framework draft architecture > Hi all, > > referring to the functional architecture for DMHA in RFC 3154, currently > the protocol base line draft describes a composite architecture. > Appendix C of draft-renker-paging-ipv6-01.txt illustrates a mapping > between the described architecture and the functional elements given in > RFC 3154. In order to come up with a first cut of a framework draft, I > would like to request a WG consensus of taking over the proposed > architecture, having a composite Paging Agent node (PA node) addressing > paging related attendant functional entities within ARs. Actually, > taking the description of the Paging Agent Functional Entity (FE) as it > is described in RFC 3154, this functional entity could be split into a > master FE, currently assigned to the PA node, and multiple attendant > FEs, located in ARs, responsible for local paging function and mapping > L3 paging requests to lower layer specifics. > > Comments are welcome. > > marco > > > > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- Re: [Seamoby] DMHA framework draft architecture James Kempf
- [Seamoby] DMHA framework draft architecture Marco Liebsch
- Re: [Seamoby] DMHA framework draft architecture Marco Liebsch