Re: review of draft-krishnan-6man-rs-mark-08

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 29 October 2010 22:43 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21ACC3A67D6 for <ipv6@core3.amsl.com>; Fri, 29 Oct 2010 15:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level:
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1I68Gj6ECcZs for <ipv6@core3.amsl.com>; Fri, 29 Oct 2010 15:43:18 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 217C83A6403 for <ipv6@ietf.org>; Fri, 29 Oct 2010 15:43:18 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o9TN5tB3031460; Fri, 29 Oct 2010 18:05:56 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.2.234.1; Fri, 29 Oct 2010 18:45:06 -0400
Message-ID: <4CCB4DBA.2000701@ericsson.com>
Date: Fri, 29 Oct 2010 18:42:02 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: review of draft-krishnan-6man-rs-mark-08
References: <4CC88D56.5040900@piuha.net> <4CC8E939.5070408@ericsson.com> <4CC91357.2050805@piuha.net>
In-Reply-To: <4CC91357.2050805@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 22:43:20 -0000

Hi Jari,

On 10-10-28 02:08 AM, Jari Arkko wrote:
> Suresh,
> 
>>>> The applicability is limited to the N:1 VLAN allocation model.
>>>>   
>>> Since this is in the abstract, could you expand "N:1 VLAN" to 
>>> something a bit more descriptive? I know what it is, you know what it 
>>> is, but some other persons later reading this RFC may not be clear 
>>> about it without sufficient DSL architecture background.
>> Does replacing "N:1 VLAN allocation model" with
>>
>> "broadband network deployment scenarios where multiple user ports are 
>> mapped to the same virtual interface on the Edge Router."
>>
>> work?
> 
> Yes.

OK. Will update this.

> 
>>> Don't we need an "ID Type" field or similar, so that we can specify 
>>> different encodings. You could start with ID Type = 0 which has only 
>>> local significance. 
>> The way I say it, the line ID was an opaque field. Do we need to 
>> define what is inside?
> 
> That's one approach, but -08 does not even say that. If that's the 
> approach we're taking with regards to this field, then you should say 
> something like "The contents of this field are not standardized and have 
> only local significance."
> 
> However, I would personally probably insert a type octet in front so 
> that it would be possible to add different types of identification 
> later. But I don't feel strongly about it.

Sounds good. Will do. Ole also suggested using something like the relay 
agent Remote-ID (RFC4649).

Thanks
Suresh