From autoconf-bounces@ietf.org Tue Aug 01 15:55:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G80KU-0006DG-VU; Tue, 01 Aug 2006 15:55:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G80KT-0006C7-T2 for autoconf@ietf.org; Tue, 01 Aug 2006 15:55:01 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80KR-0000i6-HH for autoconf@ietf.org; Tue, 01 Aug 2006 15:55:01 -0400 Received: by ug-out-1314.google.com with SMTP id m2so1562695uge for ; Tue, 01 Aug 2006 12:54:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=lofu4S1jMgUdMUShDet2pEuDsLJ+6/KZheWpxoG/lW5XekQp8XLD+G17qpvSzsmYgQ/V5ntULqAZFE+cemxPZ+etKJOEKzN8rRgK2130Tm6Cg10qYgTq41uBEeA2ZkhG3xBhnoYhs0aiBbcCPK4ngSdJzFJ1GW4d80KaApxuBC8= Received: by 10.66.216.6 with SMTP id o6mr66218ugg; Tue, 01 Aug 2006 12:54:58 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Tue, 1 Aug 2006 12:54:58 -0700 (PDT) Message-ID: <374005f30608011254r1da9dac2le38d17f9914ac0d3@mail.gmail.com> Date: Tue, 1 Aug 2006 12:54:58 -0700 From: "Ian Chakeres" To: manet , autoconf@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: "Thomas Heide Clausen \(home\)" Subject: [Autoconf] MANET Architecture Document Now Available - draft-chakeres-manet-arch-00.txt X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org I'd like to announce our ID regarding MANET Architecture. Please send myself and/or the lists (manet@ietf.org & autoconf@ietf.org) comments. I suspect there will be some discussion regarding several items, especially the terminology. I will start new threads on two specific discussions I would like to have regarding the terminology. Ian Chakeres ---------- Forwarded message ---------- From: Internet-Drafts@ietf.org Date: Jul 31, 2006 12:50 PM Subject: I-D ACTION:draft-chakeres-manet-arch-00.txt To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Mobile Ad Hoc Network Architecture Author(s) : I. Chakeres, et al. Filename : draft-chakeres-manet-arch-00.txt Pages : 17 Date : 2006-7-31 This document discusses Mobile Ad hoc NETworks (MANETs). It discusses some basic MANET architectural concepts, related taxonomies, and MANETs' relationship to the Internet architecture. It also discusses the relevant node, interface, and network characteristics that influence Internet protocol development in MANETs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chakeres-manet-arch-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chakeres-manet-arch-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-chakeres-manet-arch-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Aug 01 17:54:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G82CV-0007i4-6A; Tue, 01 Aug 2006 17:54:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G82CU-0007gZ-8p for autoconf@ietf.org; Tue, 01 Aug 2006 17:54:54 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80RO-0001V0-GX for autoconf@ietf.org; Tue, 01 Aug 2006 16:02:10 -0400 Received: from ug-out-1314.google.com ([66.249.92.171]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G80Md-0005mZ-8R for autoconf@ietf.org; Tue, 01 Aug 2006 15:57:16 -0400 Received: by ug-out-1314.google.com with SMTP id m2so1563448uge for ; Tue, 01 Aug 2006 12:57:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=mHjuRBU6W2Xln9er3viSg2iAgKHYQcO+2b6YXlu+Y11fIXwRgh/gJKj0hPwiHtXq7g/EqOYcjv7aDzTAsrD7mGf6pD++kPTWiYOQO83tPUZOxjiWv1wGxZBRDJpZUNLVg0/Un8kQWWKYq6jZ6kptlQQMgN8sTmif1xVkT/RCeS8= Received: by 10.67.93.7 with SMTP id v7mr67426ugl; Tue, 01 Aug 2006 12:57:14 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Tue, 1 Aug 2006 12:57:14 -0700 (PDT) Message-ID: <374005f30608011257l3df5309eqd9b6ca61d7e06c7f@mail.gmail.com> Date: Tue, 1 Aug 2006 12:57:14 -0700 From: "Ian Chakeres" To: manet , autoconf@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: -2.4 (--) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: "Thomas Heide Clausen \(home\)" Subject: [Autoconf] manet-arch-00 Terminology #2 X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org A link is commonly defined as a communication facility between which nodes can pass IP packets without IP forwarding. Here is the current definition from draft-chakeres-manet-arch-00.txt: Link A communication facility on a layer below IP, over which nodes exchange IP packets. In a MANET, links may change quality on short time scales, present unique views of their local neighborhood, and have other challenging properties. MANETs might use a link that is slightly different from existing like types (e.g. non-broadcast (NBMA) and broadcast). With NBMA, broadcast is not available. In a broadcast network all devices are assumed to be able to broadcast to each other; a completely connected set. In MANET (see Section 3 in arch-00) you can have something in between NBMA & full-broadcast. That is, a node can broadcast to a reachable set of nodes (not necessarily bi-directionally) and each nodes' reachable set is not necessarily the same. I propose we term this link type as partial-broadcast multiple access (PBMA - thanks to Fred Templin for the suggestion), as only a part the set is reachable. NBMA < PBMA <= full-broadcast. Using this type of link, existing definitions for link, neighbor, and interface need not be modified. Regarding the draft arch-00, link, neighbor, BI, & WBI might be revised given discussion on this topic. Ian Chakeres _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Aug 01 18:34:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G82oN-0001Aq-UB; Tue, 01 Aug 2006 18:34:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G82jz-0006Pa-2s for autoconf@ietf.org; Tue, 01 Aug 2006 18:29:31 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80RP-0001WS-IH for autoconf@ietf.org; Tue, 01 Aug 2006 16:02:11 -0400 Received: from ug-out-1314.google.com ([66.249.92.171]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G80M8-0005mZ-Nt for autoconf@ietf.org; Tue, 01 Aug 2006 15:56:45 -0400 Received: by ug-out-1314.google.com with SMTP id m2so1563448uge for ; Tue, 01 Aug 2006 12:56:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=Bk4lWnrJMzI+LN+LNhMihm6R4K3girTVSeKnGDu4dvPK+ABYk1TdVtbCEU9DIw+PZRV0AoqLJh7Jjie13vXiYtkqWQbA3kAwou4KhTqslL3JcbdioU/46RkKOXtDEnOW5NlWm3oGgDDRMsmYMgjnQRxwE4fnBycEOzkREur8PuY= Received: by 10.66.216.6 with SMTP id o6mr68227ugg; Tue, 01 Aug 2006 12:56:41 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Tue, 1 Aug 2006 12:56:41 -0700 (PDT) Message-ID: <374005f30608011256r4fb5755djcbef2f962813cf0e@mail.gmail.com> Date: Tue, 1 Aug 2006 12:56:41 -0700 From: "Ian Chakeres" To: manet , autoconf@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: -2.3 (--) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: "Thomas Heide Clausen \(home\)" Subject: [Autoconf] manet-arch-00 Terminology #1 X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org We are attempting to capture the idea of a MANET and its border with other subnetworks. To define this idea we have reused the term AS. I have provided the definition for AS & MANET from draft-chakeres-manet-arch-00.txt. Autonomous System (AS) An Autonomous System (AS) is a network topology that consists of a collection of routers and their subnetworks (with hosts attached) interconnected by a set of routes. The subnetworks and the routers are expected to be under the control of a single operations and maintenance (O&M) organization. Within an AS, routers use the same routing protocol. An AS is expected to present to other ASs the appearance of a coherent interior routing plan, and a consistent picture of the reachable nodes. MANET A MANET is an AS made up of affiliated/associated MRs (and their connected nodes) that maintain a routing structure in arbitrarily dynamic network topologies, as illustrated in Figure 1. I am afraid the term AS might be too associated with BGP. We also considered calling the collection of MANET Routers (MRs) an "area", but this has a strong association with OSPF. We also considered calling the collection of MRa a region, but region seemed loose. Do you have a suggestion for a more succinct definition to aid in defining the border of a MANET? Ian Chakeres _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Aug 29 14:50:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GI8ez-0000Ci-QN; Tue, 29 Aug 2006 14:50:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GI8ez-0000Ca-22; Tue, 29 Aug 2006 14:50:05 -0400 Received: from slb-smtpout-01.boeing.com ([130.76.64.48] helo=slb-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GI8ev-0004FB-KI; Tue, 29 Aug 2006 14:50:05 -0400 Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/SMTPOUT) with ESMTP id k7TInYtp027211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Aug 2006 11:49:34 -0700 (PDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_SMTPIN) with ESMTP id k7TInwwg015781; Tue, 29 Aug 2006 11:49:58 -0700 (PDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id k7TInjYh014872; Tue, 29 Aug 2006 11:49:47 -0700 (PDT) Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 Aug 2006 11:49:46 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6CB9B.E5449F0D" Date: Tue, 29 Aug 2006 11:49:45 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A101774264@XCH-NW-7V2.nw.nos.boeing.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-templin-manet-autoconf-link-00.txt Thread-Index: AcbK/X0ubfpUUUCPTbGdYm2UHDYJawAneXXA From: "Templin, Fred L" To: "manet" , X-OriginalArrivalTime: 29 Aug 2006 18:49:46.0186 (UTC) FILETIME=[E5C462A0:01C6CB9B] X-Spam-Score: 2.0 (++) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: Subject: [Autoconf] FW: I-D ACTION:draft-templin-manet-autoconf-link-00.txt X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ad Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C6CB9B.E5449F0D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please see below for an I-D announcement that may be of interest in MANET/Autoconf and other contexts. Comments to the list or to the author. Fred fred.l.templin@boeing.com=20 -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Monday, August 28, 2006 3:50 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-templin-manet-autoconf-link-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts=20 directories. Title : Observations on ^Link^ in MANET/Autoconf and Other Contexts Author(s) : F. Templin Filename : draft-templin-manet-autoconf-link-00.txt Pages : 10 Date : 2006-8-28 =09 Mobile Ad-hoc Networks (MANETs) comprise MANET routers, and connect to other networks via one or more MANET border routers. MANET routers communicate over semi-broadcast links which present interesting considerations for the classical IP model that are subject matter for this document. In particular, the term ""link"" requires careful examination in MANET/Autoconf and other contexts. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-templin-manet-autoconf-link-00 .txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message.=20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then=20 "get draft-templin-manet-autoconf-link-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-templin-manet-autoconf-link-00.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C6CB9B.E5449F0D Content-Type: application/octet-stream; name="ATT946160.TXT" Content-Transfer-Encoding: base64 Content-Description: ATT946160.TXT Content-Disposition: attachment; filename="ATT946160.TXT" Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi04LTI4MTYzODM2LkktREBpZXRmLm9yZz4NCg0KRU5D T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXRlbXBsaW4tbWFuZXQtYXV0 b2NvbmYtbGluay0wMC50eHQNCg== ------_=_NextPart_001_01C6CB9B.E5449F0D Content-Type: application/octet-stream; name="draft-templin-manet-autoconf-link-00.TXT" Content-Transfer-Encoding: base64 Content-Description: draft-templin-manet-autoconf-link-00.TXT Content-Disposition: attachment; filename="draft-templin-manet-autoconf-link-00.TXT" Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJbmFtZT0iZHJhZnQtdGVtcGxp bi1tYW5ldC1hdXRvY29uZi1saW5rLTAwLnR4dCI7DQoJc2l0ZT0iZnRwLmlldGYub3JnIjsgYWNj ZXNzLXR5cGU9ImFub24tZnRwIjsNCglkaXJlY3Rvcnk9ImludGVybmV0LWRyYWZ0cyINCg0KQ29u dGVudC1UeXBlOiB0ZXh0L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi04LTI4MTYzODM2LkktREBp ZXRmLm9yZz4NCg0K ------_=_NextPart_001_01C6CB9B.E5449F0D Content-Type: text/plain; name="ATT946161.txt" Content-Transfer-Encoding: base64 Content-Description: ATT946161.txt Content-Disposition: attachment; filename="ATT946161.txt" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C6CB9B.E5449F0D Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www1.ietf.org/mailman/listinfo/autoconf ------_=_NextPart_001_01C6CB9B.E5449F0D--