From nobody Fri Feb 1 13:01:44 2019 Return-Path: X-Original-To: flexip@ietfa.amsl.com Delivered-To: flexip@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1F6124408 for ; Fri, 1 Feb 2019 13:01:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlp3DBD2DEJu for ; Fri, 1 Feb 2019 13:01:38 -0800 (PST) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99E23130E8F for ; Fri, 1 Feb 2019 13:01:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id F0C04615E5 for ; Fri, 1 Feb 2019 16:01:33 -0500 (EST) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Y0PkrOI9BIlE for ; Fri, 1 Feb 2019 16:01:26 -0500 (EST) Received: from lx121e.htt-consult.com (unknown [192.168.160.20]) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id B01F660D1B for ; Fri, 1 Feb 2019 16:01:26 -0500 (EST) References: <154889632033.10606.17220363824543706439.idtracker@ietfa.amsl.com> To: flexip@ietf.org From: Robert Moskowitz X-Forwarded-Message-Id: <154889632033.10606.17220363824543706439.idtracker@ietfa.amsl.com> Message-ID: <20af6af5-02b4-91c5-d12a-8ba4c88e7351@labs.htt-consult.com> Date: Fri, 1 Feb 2019 16:01:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <154889632033.10606.17220363824543706439.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------B63B448EF59D5DCD62AEE843" Content-Language: en-US Archived-At: Subject: [Flexip] Fwd: New Version Notification for draft-moskowitz-flexip-addressing-00.txt X-BeenThere: flexip@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Flexible Internet addressing and Flexible routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2019 21:01:43 -0000 This is a multi-part message in MIME format. --------------B63B448EF59D5DCD62AEE843 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Well I finally got down to stopping trying to make more changes and just publishing version 00 Let's see if we can get a conversation started.  I have NOT settled on what the FlexIP header looks on the wire.  With the variable source and destination addresses this will have to be carefully considered.  I have looked at 6lo, but did not get any take-aways from that.  I am trying to unearth old PIP information to see what Paul had there. All help greatly appreciated. Bob -------- Forwarded Message -------- Subject: New Version Notification for draft-moskowitz-flexip-addressing-00.txt Date: Wed, 30 Jan 2019 16:58:40 -0800 From: internet-drafts@ietf.org To: Robert Moskowitz , Guangpeng Li , Shoushou Ren A new version of I-D, draft-moskowitz-flexip-addressing-00.txt has been successfully submitted by Robert Moskowitz and posted to the IETF repository. Name: draft-moskowitz-flexip-addressing Revision: 00 Title: FlexIP Addressing Document date: 2019-01-30 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/internet-drafts/draft-moskowitz-flexip-addressing-00.txt Status: https://datatracker.ietf.org/doc/draft-moskowitz-flexip-addressing/ Htmlized: https://tools.ietf.org/html/draft-moskowitz-flexip-addressing-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-moskowitz-flexip-addressing Abstract: This memo proposes an unbounded Flexible Address Space (FAS), consisting of a publicly routable Global Address Part (GP) and a locally routable Local Address Part (LP). It expands GP and LP to provide address privacy and special LP formats. Use cases are also provided. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --------------B63B448EF59D5DCD62AEE843 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Well I finally got down to stopping trying to make more changes and just publishing version 00

Let's see if we can get a conversation started.  I have NOT settled on what the FlexIP header looks on the wire.  With the variable source and destination addresses this will have to be carefully considered.  I have looked at 6lo, but did not get any take-aways from that.  I am trying to unearth old PIP information to see what Paul had there.

All help greatly appreciated.

Bob


-------- Forwarded Message --------
Subject: New Version Notification for draft-moskowitz-flexip-addressing-00.txt
Date: Wed, 30 Jan 2019 16:58:40 -0800
From: internet-drafts@ietf.org
To: Robert Moskowitz <rgm@labs.htt-consult.com>, Guangpeng Li <liguangpeng@huawei.com>, Shoushou Ren <renshoushou@huawei.com>



A new version of I-D, draft-moskowitz-flexip-addressing-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.

Name: draft-moskowitz-flexip-addressing
Revision: 00
Title: FlexIP Addressing
Document date: 2019-01-30
Group: Individual Submission
Pages: 11
URL: https://www.ietf.org/internet-drafts/draft-moskowitz-flexip-addressing-00.txt
Status: https://datatracker.ietf.org/doc/draft-moskowitz-flexip-addressing/
Htmlized: https://tools.ietf.org/html/draft-moskowitz-flexip-addressing-00
Htmlized: https://datatracker.ietf.org/doc/html/draft-moskowitz-flexip-addressing


Abstract:
This memo proposes an unbounded Flexible Address Space (FAS),
consisting of a publicly routable Global Address Part (GP) and a
locally routable Local Address Part (LP). It expands GP and LP to
provide address privacy and special LP formats. Use cases are also
provided.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--------------B63B448EF59D5DCD62AEE843--