Re: [v6ops] [saag] ITU-T SG17 IPv6 security work items liaison

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 14 June 2011 07:20 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 D899611E8111; Tue, 14 Jun 2011 00:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.423
X-Spam-Level:
X-Spam-Status: No, score=-105.423 tagged_above=-999 required=5 tests=[AWL=-0.820, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFC4dtBetRgx; Tue, 14 Jun 2011 00:20:03 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 39E2011E8070; Tue, 14 Jun 2011 00:20:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 5114715356B; Tue, 14 Jun 2011 08:19:56 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=date :subject:from:x-mailer:message-id:content-type :content-transfer-encoding:mime-version:in-reply-to:references :received:received:x-virus-scanned; s=cs; t=1308035995; bh=2883g 9CmH7gUGjXVhpis5QtP7w9of6b9492MzLkdFx8=; b=GYUhs7mKtMTfTjB89UNZG IjQnCGr3w5fi3aNWPWmnMSIRIZMMbZpuLBvGaUxsC/p+XQGGWzlxD5wzBilYfUgW GTx9N/O1JQAVcrHOz6jOCMZa3xrECCkIpgj1UxMPkyhn98LS/myOwYMXj5Ot1FEr 5qltKMkd3hkLfxjsB59SaEY7huvTJa1CHd1KLR2zPu8QyTpYT1D2inmDIodxHZ8Z 99I/dM5xcOiMMOENkiW4OjHlmrN0PgRy3htmvq73O3nAU7kfM5sdieQDZOjZGr6v JYYb+qpfVSu9XoyryHhWt2xXXLgjKhCtMnGkQcVxS/uG8RcmbXbyVilKXwgNCNQA A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Pjz+6LKmtmjs; Tue, 14 Jun 2011 08:19:55 +0100 (IST)
Received: from [10.87.48.6] (unknown [86.42.18.245]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C321A15356A; Tue, 14 Jun 2011 08:19:54 +0100 (IST)
References: <4DEA6323.4070302@cs.tcd.ie> <4DF69899.2050606@cs.tcd.ie> <D4359E14-EFD7-4780-9EB1-02F4AFF9A35D@vigilsec.com> <22C01597-E89D-4200-8251-2F3979ABB0B6@gmail.com>
In-Reply-To: <22C01597-E89D-4200-8251-2F3979ABB0B6@gmail.com>
Mime-Version: 1.0 (iPhone Mail 8H7)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Message-Id: <FB844410-7F3F-4E81-85F4-8827295F1B63@cs.tcd.ie>
X-Mailer: iPhone Mail (8H7)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Tue, 14 Jun 2011 08:19:52 +0100
To: Bob Hinden <bob.hinden@gmail.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Russ Housley <housley@vigilsec.com>, "saag@ietf.org" <saag@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [v6ops] [saag] ITU-T SG17 IPv6 security work items liaison
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Jun 2011 07:20:05 -0000

On 14 Jun 2011, at 05:51, Bob Hinden <bob.hinden@gmail.com> wrote:

> Russ,
> 
> On Jun 14, 2011, at 2:57 AM, Russ Housley wrote:
> 
>> Stephen:
>> 
>> Comments below.
>> 
>> Russ
>> 
>> 
>>> From:  IETF Security Area
>>> To: Study Group 17, Questions 2 and 3
>>> Title: Work on Security of IPv6
>>> 
>>> FOR ACTION
>>> 
>>> The IETF thanks Study Group 17 for its liaison LS-206 "Liaison on IPv6
>>> security issues".  As the world transitions to IPv6, new opportunities
>>> and challenges and challenges arise.  SG17's new focus on deployment and
>> 
>> s/and challenges and challenges/and challenges/
>> s/new//
>> 
>>> implementation considerations reflects this reality.   We would like to
>>> bring to your attention the following work which we believe may prove a
>>> useful basis for both X.ipv6-secguide and X.mgv6:
>>> 
>>>  * RFC 4294 – "IPv6 Node Requirements" (N.B., this work is currently
>>>    under revision)
>> 
>> Why not just reference the bis document?
> 
>> 
>>>  * draft-ietf-6man-node-req-bis (work in progress) – "IPv6 Node
>>>    Requirements RFC 4294-bis"
> 
> 
> The draft could also say that the working group has reached consensus and has submitted it to the IESG for publication on 25 May 2011.

Will do,
S

> 
> Bob
> 
> 
>>>  * RFC 4864 – "Local Network Protection for IPv6"
>>>  * RFC 6092 – "Recommended Simple Security Capabilities in Customer
>>>    Premise Equipment (CPE) for Providing Residential IPv6 Internet
>>>    Service"
>>>  * RFC 6105 – "IPv6 Router Advertisement Guard"
>>>  * RFC 6106 – "IPv6 Router Advertisement Options for DNS
>>>    Configuration", §7 in particular.
>>> 
>>> As you are aware, every RFC contains a Security Considerations section.
>>> In developing either a implementation or deployment guide, contributors
>>> are strongly encouraged to review the RFCs and Internet-Drafts that
>>> support any underlying function.
>>> 
>>> In addition, we bring to your attention the following IETF Working
>>> Groups that are working on security-related work of IPv6:
>>> 
>>> Working Group  Purpose                     Mailing list address
>>> Name
>>> 
>>> 6man           IPv6 Maintenance            ipv6@ietf.org
>>> savi           Source Address Validation   savi@ietf.org
>>>             Improvements
>>> dhc            Dynamic Host Configuration  dhcwg@ietf.org
>>> v6ops          IPv6 Operations             v6ops@ietf.org
>>> opsec          Operational Security        opsec@ietf.org
>>>             Capabilities for an IP
>>>             Network
>>> 
>>> In addition to the above working groups, the Security Area of the IETF
>>> maintains a mailing list for general discussion, saag@ietf.org.  We
>>> encourage and invite open and informal discussion in these or other
>>> relevant IETF fora on this very important topic. As with all IETF
>>> working groups, any and all interested parties can choose to directly
>>> contribute via the mailing lists above.
>>> 
>>> As in other areas, the Security Area of the IETF invites SG17 to bring
>>> any new-found concerns about IETF protocols to our attention so that as
>>> and when we revise our documents we can make appropriate amendments to
>>> IETF protocols. In particular, as this planned work matures, we would
>>> welcome hearing about it in more detail, perhaps via an invited
>>> presentation at a saag meeting or via review of draft documents as may
>>> be appropriate.
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>