RFC 3753 on Mobility Related Terminology
rfc-editor@rfc-editor.org Thu, 10 June 2004 13:23 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02490 for <ietf-announce-archive@ietf.org>; Thu, 10 Jun 2004 09:23:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYPWf-0002Iq-DJ for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:23:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYPRq-0000le-00 for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:18:26 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BYPNa-00074O-00; Thu, 10 Jun 2004 09:14:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYOpd-0003HL-4V; Thu, 10 Jun 2004 08:38:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYDKp-0006UX-AQ for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 20:22:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05472 for <ietf-announce@ietf.org>; Wed, 9 Jun 2004 20:22:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYDKn-0004oY-Jj for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:22:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYDJV-0003qG-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:21:02 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BYDHn-0001M0-00; Wed, 09 Jun 2004 20:19:15 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5A0HmJ11642; Wed, 9 Jun 2004 17:17:48 -0700 (PDT)
Message-Id: <200406100017.i5A0HmJ11642@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Jun 2004 17:17:48 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Thu, 10 Jun 2004 08:38:44 -0400
Cc: seamoby@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 3753 on Mobility Related Terminology
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries.
RFC 3753
Title: Mobility Related Terminology
Author(s): J. Manner, Ed., M. Kojo, Ed.
Status: Informational
Date: June 2004
Mailbox: jmanner@cs.helsinki.fi, kojo@cs.helsinki.fi
Pages: 36
Characters: 74143
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-seamoby-mobility-terminology-06.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3753.txt
There is a need for common definitions of terminology in the work to
be done around IP mobility. This document defines terms for mobility
related terminology. The document originated out of work done in the
Seamoby Working Group but has broader applicability for terminology
used in IETF-wide discourse on technology for mobility and IP
networks. Other working groups dealing with mobility may want to take
advantage of this terminology.
This document is a product of the Context Transfer and Handoff
Candidate Discovery Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
- RFC 3753 on Mobility Related Terminology rfc-editor