IETF Logo Mail Archive

Re: [I2nsf] [IPsec] Last Call: <draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt> (Software-Defined Networking (SDN)-based IPsec Flow Protection) to Proposed Standard

tom petch <daedulus@btconnect.com> Wed, 23 September 2020 10:39 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B3E3A0E49; Wed, 23 Sep 2020 03:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 iPV-bK1qMcfQ; Wed, 23 Sep 2020 03:39:35 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70102.outbound.protection.outlook.com [40.107.7.102]) (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 CC44E3A0BC0; Wed, 23 Sep 2020 03:39:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bVBOxlcEetOKX8aQXRRxK3NeObyYsX1JvIeH2o2BzK2md414/d4/VRhkQ4fOV9Pnn5qDXb7/lqv+ThpThRPbm3kuiVV1W48yzWAhMKbYE/RwF/25QbkgxavWnQnK7YWbIu9u3Akk9uTHnnZQwDbwz62oa8OdH8EIYKsMAbCaOmKJffmOUnZWInSZ/3joYRma4P8/BLs5WQoS4Z4zVnQB6kgRQDKONWAtzvLlchVMgwD6xtdtS5F/+YPVqPKhrHGnT5IjakAFBkTqIG95W/aZJXmv/5sVQKf/aUO+OTVMqI5IhQQnAZYVOASO5RZULJOxVMxC80YoS14Tf64iRdQs7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=s0OvRmLgLymSIa+6/WqIX3WjgyRMeL2kRJA9L1GzsEA=; b=dMXuRjPsyencAH/qortQD5qHFQmvKA+8x0JOJ60SbQE3WhWvObESnENRw/bDzxgX6DK/n6Sah5TvJMSl2ocZT5fZ2jvXOxMoKkk/DQxAF0eosdmtDGd/F3n9n72mh2y6xrDfP/QaxFGzA0gzwpMlkwLcuLXdndmBS9TVM69SD2H8TOouf5LsMZPTjGN+f3xgDWp2hHIyjsppoCpFlEoE3Xwxbe2iSqOSU1Ii3O7t46cBXBSF7ojkgcKX8EGBv2CySzFekxfZMVAM5hhZLuSSq4k/76F2ajnnlP9Ue17w0LLPCCTqoFhA9jKfMUFwxFZpJhG6BJKemsaJ/IfS/yRecw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=s0OvRmLgLymSIa+6/WqIX3WjgyRMeL2kRJA9L1GzsEA=; b=aV1BtUuVsbFpNM2vUc971qSQUG044cylWK/W5kl/+KmWCklAyY+N+NAsIwjeWGePIQjL0IvmpHrBT+ZLVxAkuUH5SB5c7TJcF63XLRgTp6wBoe87eiqsYQu5fZAFG1X1sI9HuG1zy16rbVV3A/kJGLXE0bNx2iXxKaQQhgnN4Es=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB2543.eurprd07.prod.outlook.com (2603:10a6:800:6f::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.15; Wed, 23 Sep 2020 10:39:30 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db%5]) with mapi id 15.20.3412.020; Wed, 23 Sep 2020 10:39:30 +0000
To: Fernando Pereñíguez García <fernando.pereniguez@cud.upct.es>, Tero Kivinen <kivinen@iki.fi>
References: <5F44E66D.6080408@btconnect.com> <CAB=gXc6UmJm4cUi2eFqVjvy2MgpMvCupnHKwAju50WvNfs2n6g@mail.gmail.com> <24426.14679.827153.422523@fireball.acr.fi> <CAB=gXc5=X=5qFbZqM3GPCcN1cA=e3wyE-a=HQX2Eubq_iiskEw@mail.gmail.com>
Cc: Roman Danyliw <rdd@cert.org>, i2nsf@ietf.org, draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org, "ipsec@ietf.org WG" <ipsec@ietf.org>, LAST-CALL@ietf.org, i2nsf-chairs@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F6B25DF.8010508@btconnect.com>
Date: Wed, 23 Sep 2020 11:39:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <CAB=gXc5=X=5qFbZqM3GPCcN1cA=e3wyE-a=HQX2Eubq_iiskEw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO2P265CA0205.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::25) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.153.136.175) by LO2P265CA0205.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3412.20 via Frontend Transport; Wed, 23 Sep 2020 10:39:29 +0000
X-Originating-IP: [86.153.136.175]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 00d39633-184f-4fb0-8dce-08d85facf3c7
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2543:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB2543D89D52A65DA382B61AD6C6380@VI1PR0701MB2543.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 5cIwYDLvQ0Y1YsmFHx1WAuR3QGiEe7J9KMV6/8Hxeq7PUZCG7It3+ePt/lKJL++D/izhO3ORa0xk97hme38V8/JMv/TVif8lGK6zulT9suPdi3FcOmy0+F6ZJNBH6pcpZMOlp/KvSyvxOYGpDhVDLrmd4gIMRvKScmgqo9lFNadz9OsDowS0lgmvVqpMdLIyp5kMG1u+4Q94/hpGo2MQmeIb2lFI/9mLLl1bLv/sZct6ivdESv4IUZBvQ0a6LSBYdf5n69P+QJMv+AhK8OtlPQV6xoyhcHa6hkHFG4SZlYLDUpnwa/1Sgk30h1HYuc1hkkPi1YMi/jUyKiW52cHIwQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(396003)(366004)(39860400002)(376002)(346002)(8676002)(478600001)(4326008)(8936002)(66574015)(110136005)(316002)(16576012)(5660300002)(2616005)(16526019)(53546011)(33656002)(66946007)(52116002)(66476007)(26005)(6486002)(87266011)(86362001)(83380400001)(2906002)(54906003)(956004)(36756003)(186003)(66556008); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: uOEwTgJyUv6BuFGczl/bUCGyWcgucfg0RD98oAPYnv2kk0fsh4CoAs/Bym476HhzSi2EiY5si1Fs3nJP/askOLnFNg9Blzt4prvx7414zAwbu1lXihRdwR7PJA2QkiXZU2B0XB38+zBFkxpPYFuGOFiIwxIAz29olhrq4nUqHl2QQOwSrrWGcATX9TWimCElRakRydInkV1ZtdtwMhhJtTPt+9sQCJ1rEqErb/fBb7q/+MqY38L0Vn7CZ8vMQFhb6C9L8AXV0Xt9kr+GW7OhiN/hay03fySkIMZ/wX/eZtvPYDGOK4vk8CkqGttGkcSBpi9TvP15KzZSUeGhEX3pzmVLH518LOdme9YPiNSEIGary7cOd2gBNiBca75LU24HQAqf5oCgbjPD+Hoyn5RpYkblpflSE0DMD+isHAGqwg/x7mJQ2kmOVzTg0NHpjU4hRXsydddYlcYiXFXeSI36xWOqxAACwVdU1ZP3VkZ1gvRmecX1+rtDDNPfh/Ugb0RZtBxBIMR0QzSKQHXwjtr5cvse1q2cPQhDrh+PIVm7LmBCI1wMj7/vr6OyQmANOvxtj8v9kqgezwqu+vadUCVoLcxGXGSy4uXU+0FtKp76X3zsqdExEBgk5JwgyxoC1DHdb+GY83GzDJ9OMGfW2I7sJA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 00d39633-184f-4fb0-8dce-08d85facf3c7
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Sep 2020 10:39:30.3981 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 2dqQY9gX8TI4u4raM6ixiX+K9+R4pjvL+RcrXgkmCYL5FtVi7onOVHcBHXt9qIBvibF46Cr3L4v+V+EC6E4eNw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2543
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/PqSfy2LjgsDflLz4exLWp7TxRHU>
Subject: Re: [I2nsf] [IPsec] Last Call: <draft-ietf-i2nsf-sdn-ipsec-flow-protection-08.txt> (Software-Defined Networking (SDN)-based IPsec Flow Protection) to Proposed Standard
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 10:39:37 -0000

On 23/09/2020 07:16, Fernando Pereñíguez García wrote:
> Hi Tero,
>
> Thank you very much for your clarification. We will update reference RFC
> 822 accordingly in our draft.
>
> Tom, you proposed us to replace RFC 822 with 2822, but it is also obsoleted
> by 5322. So, if you agree, we will reference RFC 5322 instead.

That is fine by me; my comment was that RFC822 is obsoleted by RCC2822 
so you should consider a more up-to-date version not that RFC2822 was 
the correct update!

You said previously that you did not understand my comment on RFC6020 in 
IANA Considerations.  It is fine.  What I was trying to say is that in 
most places, RFC7950 is the better reference so RFC6020 should not be 
used but for IANA Considerations, RFC6020 is the better reference so 
when updating elsewhere in the I-D, leave IANA Considerations alone.

Tom Petch

> Best regards,
> Fernando.
>
> El mar., 22 sept. 2020 a las 19:50, Tero Kivinen (<kivinen@iki.fi>)
> escribió:
>
>> Fernando Pereñíguez García writes:
>>>      I note that RFC822 and RFC3280 are Obsoleted which makes their use
>>>      problematic.
>>>
>>> [Authors]  Following your recommendation, we have replaced RFC 3280 with
>> RFC
>>> 5280. Regarding RFC 822, we reference it because the IKEv2 protocol
>>> specification (RFC 7296) explicitly defines RFC 822 emails address (see
>> page
>>> 90) as a valid identification type. If we replace RFC 822 with RFC 2821,
>> we
>>> don't know its impact on IKEv2.
>>
>> IKEv2 talks about RFC 822 email addresses, the reference points
>> Internationalized Email Headers RFC 6532, with comment of:
>>
>>        Because of [EAI], implementations would be wise to treat this
>>        field as UTF-8 encoded text, not as pure ASCII.
>>
>> So it uses RFC822 as name not as reference. There should not be any
>> problems to replace that with newer versions. Most of the
>> implementations simply consider that as a string and some cases they
>> actually do not even follow the string email address format, as they
>> add some routing information for AAAA in the end or something.
>> --
>> kivinen@iki.fi
>>
>
>

v2.23.0 | Report a Bug | By Email