IETF Logo Mail Archive

Re: [NSIS] AD comments on draft-ietf-nsis-qspec-21

Gerald Ash <gash5107@yahoo.com> Mon, 26 October 2009 17:47 UTC

Return-Path: <gash5107@yahoo.com>
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AE3428C11E for <nsis@core3.amsl.com>; Mon, 26 Oct 2009 10:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.703
X-Spam-Level:
X-Spam-Status: No, score=-99.703 tagged_above=-999 required=5 tests=[AWL=2.334, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 W9tUcuyWfiaP for <nsis@core3.amsl.com>; Mon, 26 Oct 2009 10:47:57 -0700 (PDT)
Received: from web63606.mail.re1.yahoo.com (web63606.mail.re1.yahoo.com [69.147.97.76]) by core3.amsl.com (Postfix) with SMTP id CF9AD28C33C for <nsis@ietf.org>; Mon, 26 Oct 2009 10:47:55 -0700 (PDT)
Received: (qmail 56864 invoked by uid 60001); 26 Oct 2009 17:48:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1256579285; bh=PAFFcqSJ7FkvPf/DHVpLn+e8S7T7wuX4ghx7W78kfC8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PKyESZ7e0mkwSL4dT3WCarJ7FH1BUSicjuvD+UOUqoMS24vcyFgSkhWbGY4YOwhFiStfoYNr/D7iLlPI3AyYxd3Ekdi3AcsiBjhHzuRgMTaqHwXItPXXnI+cdBMUbeIUCgeJROJ+WFFnwArFhtPAg3UzjdNrIkxUByf1stwVBOA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=cwYtPooHCyKABfYKlOyW6TsWM6v/5SGcd7Rk+5PUmMzeZraj5l78K1Vm6nmN/2KbqKpkHwz/3dAecEFQ1NEu2OLEXEx4uvw17srVBE2epDvdicxjRpZKqiKWMGcEnRWU2MKwqgFF330mpV86bSlJgKTbErzlshnrcTkW/a0WOsM=;
Message-ID: <823546.56279.qm@web63606.mail.re1.yahoo.com>
X-YMail-OSG: wXCu0DYVM1m.lO117251aaVyJ8inSxjPb8OqKQw.XdeV28bU7fELmvdQHGVA8tDn29ykPUvK2PQVc_Pr4ohdTj1B14LRRn08oNOMOysFg.d49AvPP5YZe3qT8FTpZQeSl07SQtXm48jJgNm7dw6kBBD6xlMpVBxXKZ.Mj9SxOFxm6oMmfbZW3qEm9VMWtWc9.eRezk2MQxW1xmiqK8kjagrnG39eHshPt_VwZSsp9n2uAKFJP59FOs1WLKpDZCU98r5VSyZN6QscJtoKtnK_l6IEjWN1WZL.M1MMPLjo_wGqK7GFDA0R4UZhHqmIrh1u7ISHG0ZotD_vVp6_OEnk2Lv0pRc6lqZp
Received: from [24.91.148.40] by web63606.mail.re1.yahoo.com via HTTP; Mon, 26 Oct 2009 10:48:05 PDT
X-Mailer: YahooMailClassic/7.0.14 YahooMailWebService/0.7.347.3
Date: Mon, 26 Oct 2009 10:48:05 -0700
From: Gerald Ash <gash5107@yahoo.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Georgios Karagiannis <karagian@cs.utwente.nl>
In-Reply-To: <ng9VWQuf.1256369635.9685840.karagian@ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1005407972-1256579285=:56279"
Cc: NSIS <nsis@ietf.org>, "draft-ietf-nsis-qspec@tools.ietf.org" <draft-ietf-nsis-qspec@tools.ietf.org>, David Black <black_david@emc.com>
Subject: Re: [NSIS] AD comments on draft-ietf-nsis-qspec-21
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsis>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 17:47:58 -0000

Hi Georgios,
 
I agree with your suggestion, thank you for that.
 
Magnus, does Georgios' suggestion take care of your comment #11?
 
Thanks,
Regards,
Jerry

--- On Sat, 10/24/09, Georgios Karagiannis <karagian@cs.utwente.nl> wrote:


From: Georgios Karagiannis <karagian@cs.utwente.nl>
Subject: Re: [NSIS] AD comments on draft-ietf-nsis-qspec-21
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>, "Gerald Ash" <gash5107@yahoo.com>
Cc: "David Black" <black_david@emc.com>, "draft-ietf-nsis-qspec@tools.ietf.org" <draft-ietf-nsis-qspec@tools.ietf.org>, "NSIS" <nsis@ietf.org>
Date: Saturday, October 24, 2009, 3:33 AM


Hi Magnus

Regarding comment 11:
>>> 11. This may seem out of context but I do want to know the answer to how
>>> the situation is handled when QNI and QNR are neighbors on a non QoS
>>> enabled network.
>>  
>> What "situation" are you referring to here?  IMO you can't have a QNI
>> and QNR in a "non QoS enabled network".  By definition, a QNI and QNR
>> are only defined in an NSIS enabled network (i.e., a QoS enabled network).
>
>I am asking what is happening in these cases where a QNI has the QNR as
>peer and there are no network support. Clearly you will not get any QoS,
>but is it clear to both QNI and QNR that this is the situation?
>

I think that the solution for this situation is provided by QoS-NSLP. In
particular, this situation is detected by uing the generic flag BREAK
(B), see Section 5.1.1 Common header, in the QoS-NSLP draft, see below:

BREAK (B) - when set, indicates that there are routers along the path
where QoS cannot be provided.

Maybe it will be good to add a sentence in the QSPEC draft that
emphasizes."

"As specified in QoS-NSLP, when there are routers along the path between
QNI and QNR where QoS cannot be provided then the QoS-NSLP generic flag
BREAK (B) is set."

Best regards,
Georgios

v2.23.0 | Report a Bug | By Email