RE: [spring] Spirit and Letter of the Law - non-technical side note

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 09 September 2019 15:02 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB097120803 for <ipv6@ietfa.amsl.com>; Mon, 9 Sep 2019 08:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 H5d_obBhnqvr for <ipv6@ietfa.amsl.com>; Mon, 9 Sep 2019 08:02:41 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 534B71201EA for <ipv6@ietf.org>; Mon, 9 Sep 2019 08:02:41 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x89F244p017965; Mon, 9 Sep 2019 16:02:04 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9ED612203C; Mon, 9 Sep 2019 16:02:04 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id 88F6622032; Mon, 9 Sep 2019 16:02:04 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x89F22Ik007876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Sep 2019 16:02:03 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Chengli (Cheng Li)'" <chengli13@huawei.com>, 'Mark Smith' <markzzzsmith@gmail.com>, 'Xiejingrong' <xiejingrong@huawei.com>
Cc: 'Fernando Gont' <fgont@si6networks.com>, '6man WG' <ipv6@ietf.org>, 'Robert Raszuk' <robert@raszuk.net>
References: <ca6e7a10-1b84-445f-053d-8a666ab4ec90@si6networks.com> <3D8725E7-EAA3-4615-ABA2-FFA53D2F1B14@employees.org> <d81ea605-53d7-61d8-f517-5d9cf1e42339@gmail.com> <CA+b+ER=+VASk4s8EvQ_gXxoLGkuVkCJFTROaW7Tv8pcm5aX1Tw@mail.gmail.com> <0A645A66-D64F-4570-9731-31E7030D51F7@cisco.com> <CALx6S341KOQ7+xa-dRQdXE42VJ6Wax5iNyki8VSk2Eytn2mZCQ@mail.gmail.com> <CAOj+MMG0uzEKn_jbBZATFQtgNyKWsy1iR1jFvFdzLS+ybwQQ_Q@mail.gmail.com> <5d74557e.1c69fb81.d65a7.8f43SMTPIN_ADDED_BROKEN@mx.google.com> <CAO42Z2z3AfUSGofA12HjF=wRwQQQj5AYYVd2XvTevzT2M7d70w@mail.gmail.com> <C7C2E1C43D652C4E9E49FE7517C236CB026D0930@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB026D0930@dggeml529-mbx.china.huawei.com>
Subject: RE: [spring] Spirit and Letter of the Law - non-technical side note
Date: Mon, 09 Sep 2019 16:02:02 +0100
Organization: Old Dog Consulting
Message-ID: <066901d5671f$8a7fdc20$9f7f9460$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_066A_01D56727.EC444420"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJ8Kr6LtOQfHvAfIdTRvXD4ffEArQL7jltyAv2FG3EA0DUuLgJ6VzkgAg3TOssBTJPjBQHsjUfzAc47Vx8BzMqMUqVEu+fA
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24898.007
X-TM-AS-Result: No--18.867-10.0-31-10
X-imss-scan-details: No--18.867-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24898.007
X-TMASE-Result: 10--18.867100-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbCA64TWjSz46Ub4EdIZGxuCu4Zk6VW131YNn qL0QkVNVfpHiTGdzQjag4759nkzOqmIKfYx0qES3elGHXZKLL2u7xmCZDXrutd+gRbw3K+dvq+S rFrqVBTwy0cTVl0yqLZhl+M5E4O1lJa+FAG1BTBP4AIbmhYnu0l+BoH4JnCIGOtbatF9N8as/Sd UXWOZQGwpdPYZUL22SuCfBDnhGS5sZkn/2nXiZsBRROHBHC6aTG0Oe0T+pTlHht8l26i7kl0zFW LAGbjggwfolb/M3gEqcNz++hPdLOi/33TWoSUH6N19PjPJahlLBnL3AaGm9o0hcmj54ab4UFA7u NHNvzLd9qkdOTM2zLT3lvbv1Aogj21GsmlE4tJ8f0eUint9QESl06rL9FnHs3YFXUkbF35lug1n lMCT3kt6Oe25X9ITZidrLudrdHSX4OHXAoi3l0LkM+JfpduJWvMRNh9hLjFl7fBdO8ExSLgHvYy r9Z+5lq2m/jiFpwFrBI/aJUl6FNAvXHvfuOjTITG680mNjQJ4bjptZsmSxlQbYcy9YQl6enAN4t 2JkGOxR24PibmvoBilfiqmET+QOKJOd7SLvnk70VCHd+VQiHni8nDfxuQATWGzy6KaAc0JI6iia 8EJZLvLnzWbGJbcQh0x1ir1fZT1XKa5mdWEgieyNEc7z2JzC4/qn72YRaUJpifu1ea0XM1sdTs2 /LSlqjK5iVt35bfvgS3hlhJAVa/Jbg34lbMQrx/Stmah0FpbfVqwz+CynaalVRHRK9i1KzEVDGn c+EfKahG/i8Ja1Y7dYFVfIRaXS7zgtUFe2gc6eAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyI9euiYe 3o8eIfXlp5S9cfAOwBXM346/+yo47NaV8fl1RP3ed0WruMQitRWRHn7lGCcp7wKaT7AXq2eVDK8 F9Vj
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Ypnpw-oneCb7W6s41dVZGMok0Nw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 15:02:45 -0000

Hi Cheng,

 

The text is trying to say…

*	If you receive and IPv6 packet

*	Look in the destination address field
*	If the address is not one of your addresses

*	Do not process, insert, or delete any AH (except the HBH option header)

 

I believe that you are correct that the node at the end of a segment will find one of its addresses in the destination address field. That is good news because the node at the end of a segment needs to update the ERH.

 

Adrian

 

From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Chengli (Cheng Li)
Sent: 09 September 2019 15:50
To: Mark Smith <markzzzsmith@gmail.com>; Xiejingrong <xiejingrong@huawei.com>
Cc: Fernando Gont <fgont@si6networks.com>; 6man WG <ipv6@ietf.org>; Robert Raszuk <robert@raszuk.net>
Subject: RE: [spring] Spirit and Letter of the Law - non-technical side note

 

Honestly, my mother language is NOT English, but Hainanese(Hainan dialect, between Mandarin and Cantonese), 

so I always use Google translate to make sure that I understand fully.

 

Does any one can help me understand this sentence?

 

   Extension headers (except for the Hop-by-Hop Options header) are not

   processed, inserted, or deleted by any node along a packet's delivery

   path, until the packet reaches the node (or each of the set of nodes,

   in the case of multicast) identified in the Destination Address field

   of the IPv6 header.

        From https://tools.ietf.org/html/rfc8200#section-4

 

What kind of node is the node that identified in the Destination Address field of the IPv6 header? 

 

Does the SRv6 Segment Endpoint node that will appear in the Destination Address field of the IPv6 header is a node like that?

 

Many thanks,

Cheng

 

 

 

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Mark Smith
Sent: Sunday, September 08, 2019 12:18 PM
To: Xiejingrong <xiejingrong@huawei.com <mailto:xiejingrong@huawei.com> >
Cc: 6man WG <ipv6@ietf.org <mailto:ipv6@ietf.org> >; Robert Raszuk <robert@raszuk.net <mailto:robert@raszuk.net> >; Fernando Gont <fgont@si6networks.com <mailto:fgont@si6networks.com> >
Subject: Re: [spring] Spirit and Letter of the Law - non-technical side note

 

 

On Sun, 8 Sep 2019, 10:42 Xiejingrong, <xiejingrong@huawei.com <mailto:xiejingrong@huawei.com> > wrote:

+1.
EH insertion has been discussed for years and no fundamental showstoppers on either side.

 

That's entirely incorrect.

 

The discussion caused updates to the text in RFC 8200, just for people who were claiming the following text was ambiguous.

 

"With one exception, extension headers are not examined or processed

   by any node along a packet's delivery path, until the packet reaches
   the node (or each of the set of nodes, in the case of multicast)
   identified in the Destination Address field of the IPv6 header.

 

They were being disingenuous. 

 

It may need a major change/clarification on 8200, but it's a true tech point of discussion on going. 

 

Do you have any production network operational experience, where resolving faults as soon as possible for paying customers is critical?

 

Ease of troubleshooting needs to be a consideration for anything the IETF invents.

 


Thanks
Jingrong

From:Robert Raszuk <robert@raszuk.net <mailto:robert@raszuk.net> >

To:Tom Herbert <tom@herbertland.com <mailto:tom@herbertland.com> >

Cc:Fernando Gont <fgont@si6networks.com <mailto:fgont@si6networks.com> >;6man WG <ipv6@ietf.org <mailto:ipv6@ietf.org> >

Date:2019-09-08 02:54:27

SubjectRe: [spring] Spirit and Letter of the Law - non-technical side note

 

 

Extension header insertion WAS considered by the 6man WG.
draft-voyer-6man-extension-header-insertion was discussed at length.
(https://mailarchive.ietf.org/arch/msg/ipv6/VSMm27TQFeJbvsD6pDnIPA4w4Yw).

 

I think all are very reasonable comments and looking at the diffs some of them already went into the document between version -02 & -04. Some are still missing. 

 

Not sure if there was any follow up since version -04 was posted, but I really see no fundamental showstoppers on either side.

 

I do hope current authors of this draft will complete the updates, move document to standards track and ask 6man wg for review of the changes. 

 

Many thx,
Robert.

 

 

 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org <mailto:ipv6@ietf.org> 
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------