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

Jari Arkko <jari.arkko@piuha.net> Thu, 28 October 2010 06:06 UTC

Return-Path: <jari.arkko@piuha.net>
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 8FA383A683C for <ipv6@core3.amsl.com>; Wed, 27 Oct 2010 23:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.458
X-Spam-Level:
X-Spam-Status: No, score=-102.458 tagged_above=-999 required=5 tests=[AWL=0.141, 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 7Lrw5bD-BtS6 for <ipv6@core3.amsl.com>; Wed, 27 Oct 2010 23:06:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 67F0A3A6831 for <ipv6@ietf.org>; Wed, 27 Oct 2010 23:06:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5C3FF2CC34; Thu, 28 Oct 2010 09:08:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGIztWbCEm2h; Thu, 28 Oct 2010 09:08:24 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 836C02CC32; Thu, 28 Oct 2010 09:08:24 +0300 (EEST)
Message-ID: <4CC91357.2050805@piuha.net>
Date: Thu, 28 Oct 2010 09:08:23 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: review of draft-krishnan-6man-rs-mark-08
References: <4CC88D56.5040900@piuha.net> <4CC8E939.5070408@ericsson.com>
In-Reply-To: <4CC8E939.5070408@ericsson.com>
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: Thu, 28 Oct 2010 06:06:48 -0000

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.

>> 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.

Jari