Re: [v6ops] Fwd: 82nd IETF DRAFT Agenda

Xing Li <xing@cernet.edu.cn> Wed, 26 October 2011 13:55 UTC

Return-Path: <xing@cernet.edu.cn>
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 60CB621F8AD9 for <v6ops@ietfa.amsl.com>; Wed, 26 Oct 2011 06:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.356
X-Spam-Level:
X-Spam-Status: No, score=-99.356 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, FH_HAS_XAIMC=2.696, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6MKHGlz0xiy for <v6ops@ietfa.amsl.com>; Wed, 26 Oct 2011 06:55:44 -0700 (PDT)
Received: from cernet.edu.cn (mail.cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id 31EEB21F8AB0 for <v6ops@ietf.org>; Wed, 26 Oct 2011 06:55:43 -0700 (PDT)
Received: from [127.0.0.1]([125.34.40.27]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54ea820da; Wed, 26 Oct 2011 21:55:43 +0800
Message-ID: <4EA8115C.5090704@cernet.edu.cn>
Date: Wed, 26 Oct 2011 21:55:40 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.23) Gecko/20110920 Thunderbird/3.1.15
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
References: <20111013211312.B6C7421F8AFF@ietfa.amsl.com> <619C3B81-1CDC-4341-8180-EC8472864CC0@cisco.com> <4EA53FB7.6090603@cernet.edu.cn> <4EA62DE7.8040504@bogus.com>
In-Reply-To: <4EA62DE7.8040504@bogus.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: vMRxDT1B
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>
Subject: Re: [v6ops] Fwd: 82nd IETF DRAFT Agenda
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: Wed, 26 Oct 2011 13:55:45 -0000

Hi, Joel,

Thanks for the comments. Answers are inline.


于 2011/10/25 11:32, Joel jaeggli 写道:
> two thoughts...
>
> wg cohchair hat on -
> 	I think the request deserves our consideration and certainly
> 	discussion on the mailing list and probably in the meeting.

Thanks.

> wg cochair hat off -
> 	A well known address that I pretty much have to accept is imo 	
> 	a super attractive DOS source address and the security 		
> 	considerations section does little to mollify that concern for
> 	me. non-exclusive advertisement for the purpose of defeating
> 	urpf doesn't really excite me either.

This well-konwn address block is only used as source address of ICMP
packets and will never be used as destination address. Therefore,

    Packet firewall filters should be configured to treat addresses in
    the IANA-assigned /24 network as martian addresses by discarding all
    non-ICMP packets that use the IANA-assigned /24 network as a source
    address, and all packets that use the IANA-assigned /24 network as a
    destination address.

It may be the case that some ISPs are slow to add this block as martian
addresses. However, if we can move forward the ISPs will have time to
take action, before more and more IPv4/IPv6 translators being deployed.

> 	I haven't studied the issue deeply but it seems like there is
> 	substantial opportunity to spoof traffic to a 	
> 	stateless translator, that results in the third party of my
> 	choice recieving the icmp messages that are rather hard to
> 	determine the source of.

I believe it is not worse than an ISP whoes infrastructure is configured 
using
RFC1918 addresses. It is very difficult to trace back. But when treat this
block as martian address, the risk can be minimized.

Regards,

xing


> On 10/24/11 03:36 , Xing Li wrote:
>> Hi, Fred and All,
>>
>> 于 2011/10/14 5:52, Fred Baker 写道:
>>> The initial version of the agenda has been posted. It places v6ops on
>>> Wednesday and Friday mornings, a total of 4.5 hours. I personally am
>>> satisfied with it, but if folks have issues I can pass them along.
>>>
>>> I'll note that the deadline for -00 drafts is 24 October, and the
>>> deadline for updated drafts is a week later. For discussion in the
>>> working group meetings, I'm looking for a draft posted after 25 July,
>>> with supporting email discussion on the list.
>>>
>>> I'm looking for (and in some cases have seen) commentary on each of:
>>>
>>> -rw-rw-r--  1 fred  fred  13796 Jul 25 23:59
>>> draft-xli-v6ops-ivi-icmp-address-00.txt
>> I would like to request that the V6ops WG adopt
>> draft-xli-v6ops-ivi-icmp-address-00.txt as a WG adoption.
>>
>> The draft describes the operational considerations of mapping ICMPv6
>> packets through an RFC6145 gateway where the IPv6 address is not
>> directly translatable into an IPv4 address, and requests an IANA Special
>> Purpose IPv4 address allocation (192.70.192.0/24) to allow this address
>> mapping to take place using a protocol-specific designated address block
>> in IPv4.
>>
>> The authors are hopeful that this will not require any valuable
>> face-to-face WG time at IETF 82 and the WG's consideration of this
>> document can be undertaken entirely on the mailing list.
>>
>> Regards,
>>
>> xing
>>
>>> -rw-rw-r--  1 fred  fred  34974 Sep 14 10:45
>>> draft-ietf-v6ops-happy-eyeballs-04.txt
>>> -rw-rw-r--  1 fred  fred  26625 Sep 27 13:22
>>> draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-04.txt
>>> -rw-rw-r--  1 fred  fred  25341 Oct  2 11:39
>>> draft-jjmb-v6ops-comcast-ipv6-experiences-02.txt
>>> -rw-rw-r--  1 fred  fred  28127 Oct  6 14:13
>>> draft-gashinsky-v6ops-v6nd-problems-00.txt
>>> -rw-rw-r--  1 fred  fred  45016 Oct  7 12:39
>>> draft-ietf-v6ops-6204bis-00.txt
>>> -rw-rw-r--  1 fred  fred   8877 Oct 10 09:00
>>> draft-ietf-v6ops-ipv6-discard-prefix-00.txt
>>> -rw-rw-r--  1 fred  fred  15656 Oct 12 20:38
>>> draft-carpenter-v6ops-label-balance-00.txt
>>>
>>> plus any new drafts that are posted.
>>>
>>> Begin forwarded message:
>>>
>>>> From: IETF Agenda<agenda@ietf.org>
>>>> Date: October 13, 2011 2:13:10 PM PDT
>>>> To: Working Group Chairs<wgchairs@ietf.org>
>>>> Cc:irsg@irtf.org
>>>> Subject: 82nd IETF DRAFT Agenda
>>>>
>>>> The DRAFT agenda is ready for viewing.  Please note the cutoff date for
>>>> requests to reschedule Working Group and BOF meetings is October 17,
>>>> 2011
>>>> 17:00 PT.  The final agenda will be published on October 21, 2011.
>>>>
>>>> https://datatracker.ietf.org/meeting/82/agenda.html
>>>> https://datatracker.ietf.org/meeting/82/agenda.txt
>>>>
>>>> http://www.ietf.org/meeting/82/index.html
>>>>
>>>>
>>>> Thanks,
>>>> Wanda
>>>>
>>>> Only 30 days until Taipei, 82nd IETF!
>>>> Online registration for the IETF meeting is at:
>>>> http://www.ietf.org/meeting/register.html
>>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>