[Hipsec] Thread-Topic: Changing the reference type in draft-ietf-hip-rfc4423-bis
"Card, Stu" <stu.card@axenterprize.com> Wed, 31 March 2021 13:08 UTC
Return-Path: <stu.card@axenterprize.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809DF3A288A for <hipsec@ietfa.amsl.com>; Wed, 31 Mar 2021 06:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=axenterprize.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 nijCIvEnsybR for <hipsec@ietfa.amsl.com>; Wed, 31 Mar 2021 06:08:11 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 6BC033A281B for <hipsec@ietf.org>; Wed, 31 Mar 2021 06:08:07 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id w3so30010644ejc.4 for <hipsec@ietf.org>; Wed, 31 Mar 2021 06:08:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=axenterprize.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=0fDiA6R7LiRtaUlFeyhEhtFAvw8eqJZPmsa9T+LemHc=; b=rSu5MVnoaaDTdMTlbGzJnX/78Mj1Ks8ZzONWquVjGZj5PAvLVoGi6WVCNAEu0+a70+ qTthaM2DbEho39JnUZOs5hoRrooRi+zWcCOetbl4+PTUU3YQ9e+tZ9TOFQyq+GabibAM TDaRs2Tt9ohHqVPKE3iRW6tZLGUVY71cdeDnc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0fDiA6R7LiRtaUlFeyhEhtFAvw8eqJZPmsa9T+LemHc=; b=uRZdArFC5Bmzk5pSbnm8zkKNoD63m1LSCta9cf9Nv8zlygx/knvdRibd+u9ZROlm50 x1OQwOa8btjqsruBdWfrd3EUEieCXm9Ld5qFfe3+VcXRuN6kXscnKn4/M3ern66WmsiM P6AGZyoUgaBli+4yb3Q4nDUadkt2gmr7VvlGe/D0gj29ljY7eM0QF159FaPBoO/BIfpi VMjMTq/0afZToblKaL7WLqSMZQoDd4IBKi0UZ+WJ4lGVQzXO8AMVSRm0SQ8GDo1FVIYi dLfsA+YPUbEHh9CA+X37AOgb+ieIU2w9Z7iuEJgMXJ2Q1NN4VmpemrvITrnuqo/zx7YI tHdw==
X-Gm-Message-State: AOAM5324d7wHOml0Dn5Cgih84d2GZx+t+QwQ2dzUYGA0TQ7I+mlIcuiY re7oOWunVGmiF4gC4pD76I7b6qr5+LwOrzZkamaIXmc/zambZet5
X-Google-Smtp-Source: ABdhPJxZzdzwPzZlI6JE9t3UpYW1HpZNED5viHJ/5yCm58EQYKlbj78/4Bsd4WymE7/ikZqbOjCYo8auq16KBFzlZA8=
X-Received: by 2002:a17:906:9888:: with SMTP id zc8mr3540453ejb.310.1617196085088; Wed, 31 Mar 2021 06:08:05 -0700 (PDT)
MIME-Version: 1.0
From: "Card, Stu" <stu.card@axenterprize.com>
Date: Wed, 31 Mar 2021 09:07:55 -0400
Message-ID: <CAKM0pYPGmAkZiRZ9YTcYqPQZJGJOQ5PE+k+DjYuy+rYucFt6iQ@mail.gmail.com>
To: hipsec@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002f25c105bed4ce42"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/gBAyL2RkDzqy8y9FHT9rjpSL-7I>
Subject: [Hipsec] Thread-Topic: Changing the reference type in draft-ietf-hip-rfc4423-bis
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2021 13:08:22 -0000
Eric wrote: ... draft-ietf-hip-dex does not progress very well and in order to release the RFC Editor cluster C386 [1], I intend to request the RFC Editor to change the reference to draft-ietf-hip-dex from normative to informative. The change would immediately release draft-ietf-hip-native-nat-traversal and draft-ietf-hip-rfc4423-bis... I (Stu) consider the architecture revision and NAT traversal far more important than DEX, so if this is all that would be needed to move those drafts to where they would be eligible for publication as RFCs, it seems a small price for a great benefit.