IETF Logo Mail Archive

Re: [v6ops] WG Doc? draft-gont-v6ops-ipv6-ehs-packet-drops

Joe Touch <touch@isi.edu> Tue, 05 April 2016 17:41 UTC

Return-Path: <touch@isi.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C0912D901 for <v6ops@ietfa.amsl.com>; Tue, 5 Apr 2016 10:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 de-c74LYUX48 for <v6ops@ietfa.amsl.com>; Tue, 5 Apr 2016 10:41:00 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31A8212D53D for <v6ops@ietf.org>; Tue, 5 Apr 2016 10:41:00 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u35HejMh023309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 5 Apr 2016 10:40:46 -0700 (PDT)
To: Mark Smith <markzzzsmith@gmail.com>, joel jaeggli <joelja@bogus.com>
References: <CAHw9_iLbqEvsw0x4dDcA3Zy3SXKUROcQuy5nSynsL9Xi+xrZLg@mail.gmail.com> <56E892B8.9030902@foobar.org> <394925FE-FAB1-4FFC-B1CF-4F64CC58F613@employees.org> <56E94275.20700@foobar.org> <3AE1DE20-D735-4262-A3FB-7C01F30BAFA2@employees.org> <56E96F74.7000206@foobar.org> <CALx6S37zP4UvCtBJsvnPN6OmDB0OQDMfRrJNy1XF0t4COStUjQ@mail.gmail.com> <56E98086.5040209@foobar.org> <EE17974D-EDA4-4732-B29E-B2B3BC36DB86@employees.org> <20160328183844.GR62900@Space.Net> <56F9A22B.2030301@isi.edu> <5E619124-0A60-45BB-86AA-7F7D5CC614AD@cisco.com> <56F9AE53.8060903@gmail.com> <56F9BEA3.9050409@isi.edu> <4542AA33-F4FA-4F52-B5FE-9ABF2627CD5E@cisco.com> <56F9C856.2030403@gmail.com> <56F9C915.9070408@isi.edu> <E2C0BF9F-806C-4ACC-86CE-1B678628E687@employees.org> <CAO42Z2z2R9N4b1Y=zQCuw2niwYzaRtten+8mDHpsjfYXSh8pJQ@mail.gmail.com> <47A7C6D0-9DCA-4FE3-9CBF-8A9101D48763@employees.org> <91a3ea5b-f12b-f1b1-d0e1-885faa2d1e90@bogus.com> <CAO42Z2xZ=A0nTVGdX74q2M1fSN7chPzMz9gwZSEv-pzMejFdHA@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <5703F89D.3080203@isi.edu>
Date: Tue, 05 Apr 2016 10:40:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2xZ=A0nTVGdX74q2M1fSN7chPzMz9gwZSEv-pzMejFdHA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/7VwYxqgK5Zp0LtHa6ebvIVK-z_E>
Cc: v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] WG Doc? draft-gont-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 17:41:01 -0000


On 4/5/2016 10:00 AM, Mark Smith wrote:
> Adding, deleting or changing EHs in the network would be silent about
> who made the changes (except when modification records who did the
> change e.g. RH0). In this case the packet source address has lost its
> much of its clarity, because there are now multiple sources of the
> information in the packet.

Given the pervasive presence of NAT and other header rewriting devices,
there are already many such sources. Unless the header is authenticated,
there are no assurances as to exactly where the information therein
originated.

Joe

v2.23.0 | Report a Bug | By Email