[Autoconf] Lining up Autoconf documents

"Teco Boot" <teco@inf-net.nl> Wed, 14 November 2007 10:12 UTC

Return-path: <autoconf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsFEN-0007hk-5l; Wed, 14 Nov 2007 05:12:23 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1IsFEL-0007hN-St for autoconf-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 05:12:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsFEL-0007hA-CA for autoconf@ietf.org; Wed, 14 Nov 2007 05:12:21 -0500
Received: from hpsmtp-eml16.kpnxchange.com ([213.75.38.116]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsFEK-00038y-9c for autoconf@ietf.org; Wed, 14 Nov 2007 05:12:20 -0500
Received: from hpsmtp-eml02.kpnxchange.com ([213.75.38.102]) by hpsmtp-eml16.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Nov 2007 11:12:18 +0100
Received: from M90Teco ([86.83.9.22]) by hpsmtp-eml02.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Nov 2007 11:12:18 +0100
From: Teco Boot <teco@inf-net.nl>
To: autoconf@ietf.org
Date: Wed, 14 Nov 2007 11:12:06 +0100
Message-ID: <006e01c826a6$d0c7c9c0$72575d40$@nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acgmps9JazNMyiOwQRuvsSKC2lljrQ==
Content-Language: nl
X-OriginalArrivalTime: 14 Nov 2007 10:12:18.0523 (UTC) FILETIME=[D6807AB0:01C826A6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
Subject: [Autoconf] Lining up Autoconf documents
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0171022121=="
Errors-To: autoconf-bounces@ietf.org

Hi,

 

In some private / public discussions, we struggled with terms related to
Autoconf.

I think all Autoconf terms shall be defined in autoconf-statement. Some
terms specific to MANET only may be defined in autoconf-manetarch.

 

I prefer a clear definition on Border Router. Some suggest there is a
difference in Border Router and Internet Gateway. I understand the
difference very well, but lacking a defined term for Internet Gateway I use
Border Router (BR). I suggest lining up both Autoconf WG drafts, as they are
using the same term for both. And verify with the charter, this text use
Internet Gateway and not Border Router.

 

On addresses, the Autoconf charter defines very well what is needed:

- unique local addresses

- globally routable unique addresses

The first is called MANET Local Address (MLA) in autoconf-statement, I will
use this term in a next version of my personal I-D.

For the second one, I introduced MGA, MANET Generated Address. I could
update this into MANET Global Address, keeping the MGA abbreviation and
using wording in line with MLA. Any other term is OK for me, as long as it
is consistently used and well defined.

 

I think Carlos Bernardos (et alia) has published good documents on Autoconf.
Lining up terms with these documents doesn't harm. And we should discuss
accepting these documents as WG docs in Vancouver, for being published as
informational RFC. I suggest chairs prepare a proposal for both
draft-bernardos-autoconf-evaluation-considerations and
draft-bernardos-autoconf-solution-space. AD approval could be required, I
suggest a break-of-silence procedure here.

 

Cheers, Teco

 

_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www1.ietf.org/mailman/listinfo/autoconf