Re: [arch-d] Fwd: Re: [spring] Draft-ietf-spring-network-programming ipv6 addressing architecture - was draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?

S Moonesamy <sm+ietf@elandsys.com> Thu, 12 March 2020 22:31 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6576B3A08CD for <architecture-discuss@ietfa.amsl.com>; Thu, 12 Mar 2020 15:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 0_lzu7ySSzSG for <architecture-discuss@ietfa.amsl.com>; Thu, 12 Mar 2020 15:31:00 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6963A08CB for <architecture-discuss@iab.org>; Thu, 12 Mar 2020 15:30:57 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.72.36]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 02CMUikS013241 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Mar 2020 15:30:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1584052256; x=1584138656; i=@elandsys.com; bh=wO+L5W0sb/DnfMVvy4GuqJNXfuiS7+RNraPfEvDaWwE=; h=Date:To:From:Subject; b=3bpQw5RdmePohtiNIR8N5OLqeccyb/GiGA6VVmUBPYfYDiQ6GVFy2YApuYWEcZhFZ 4LML8s3Dwi/p+bnrvJFWdkmDYj/qqGri0CSycOYipKkdlPMs1Oy8r9g3425ZR83bKn eis/wCWJjlaIrskHbJzjh5IboN9o6N+xV7KKVqqs=
Message-Id: <6.2.5.6.2.20200312144637.0b369838@elandsys.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 12 Mar 2020 15:30:25 -0700
To: Fernando Gont <fgont@si6networks.com>, architecture-discuss@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/2oi-BrLgaosxRL-Q6KXuHaO8S7o>
Subject: Re: [arch-d] Fwd: Re: [spring] Draft-ietf-spring-network-programming ipv6 addressing architecture - was draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2020 22:31:03 -0000

Hi Fernando,
At 07:17 AM 12-03-2020, Fernando Gont wrote:
>These are yet more architectural changes taking place, without 
>proper oversight. In this case, the document being the "IPV6 
>Addressing Architecture".
>
>Just felt like raising it, like I did for others, IMHO without much success.

The IAB does not do architecture oversight of documents intended to 
be "standards".  I just noticed that an IAB member is not advocating 
for a position which the IAB took.  Anyway, that is not what you 
asked about.  Please see below.

The Area Directors responsible for ensuring that the working groups 
falling within their Area produced architecturally consistent 
output.  My guess is that it happens when the Area Director(s) is an 
expert on the working group topic.  It can be controversial if an 
Area Director is too insistent about architectural purity.

Regards,
S. Moonesamy