From nsis-bounces@ietf.org Thu Dec 01 06:49:31 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EhmwN-00031K-AW; Thu, 01 Dec 2005 06:49:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EhmwJ-0002zQ-QV
	for nsis@megatron.ietf.org; Thu, 01 Dec 2005 06:49:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02544
	for <nsis@ietf.org>; Thu, 1 Dec 2005 06:48:41 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhnGj-0001ua-7h
	for nsis@ietf.org; Thu, 01 Dec 2005 07:10:37 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB1BmjWA017061;
	Thu, 1 Dec 2005 11:48:46 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Dec 2005 11:48:43 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCB6@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
Thread-Index: AcX1ACzQvhfm/SYuTlyZhIsPStGxEwBa0EPA
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Roland Bless" <bless@tm.uka.de>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [NSIS] RE: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi,

although it's true that GIST knows the mapping between
MRI (flow) and SID, at the moment my instinct is that
these primitives should continue to work in terms of the
MRI only.=20

the rationale is that these primitives all (basically)
refer to changes in layer 3 (network topology) state,=20
which should not depend on the SID. however, there may
be several SIDs for the same MRI. therefore, if you put
the SID in the API primitive, you inevitably end up=20
looping over the SIDs/MRI. my main concern about this=20
would be understanding the pathological cases, e.g. where
you only get API calls about a subset of the SIDs, or
GIST/NSLP operations about a SID get mixed up in time
with a sequence of API events (quite apart from any=20
efficiency considerations).=20

i assume the motivation is that you don't want the NSLP
to have to maintain an index of its state by MRI but
only by SID? i am not sure whether it is possible to
eliminate this functionality from the average NSLP.

r.

> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de]=20
> Sent: 29 November 2005 16:15
> To: nsis@ietf.org; Hancock, Robert
> Subject: GIST API: Adding SessionID to NetworkNotification,=20
> SetStateLifetime, InvalidateRoutingState?
>=20
>=20
> Hi,
>=20
> our implementation experience suggests that it might
> be a good thing to add the SessionID to the above API
> calls. So in case GIST wants to issue a NetworkNotification
> to an NSLP, this NSLP has no idea to which session the flow
> belongs. GIST should have that information anyway.
> In the other direction (SetStateLifetime, InvalidateRoutingState) GIST
> must loop over all sessions.
>=20
> Any objections?
>=20
> Roland
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 01 10:45:17 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EhqcX-0003xA-36; Thu, 01 Dec 2005 10:45:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EhqcV-0003wS-LM
	for nsis@megatron.ietf.org; Thu, 01 Dec 2005 10:45:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06709
	for <nsis@ietf.org>; Thu, 1 Dec 2005 10:44:29 -0500 (EST)
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ehqwl-0002Ed-Cq
	for nsis@ietf.org; Thu, 01 Dec 2005 11:06:27 -0500
Received: (qmail 8376 invoked by uid 0); 1 Dec 2005 15:44:42 -0000
Received: from 194.39.131.40 by www85.gmx.net with HTTP;
	Thu, 1 Dec 2005 16:44:42 +0100 (MET)
Date: Thu, 1 Dec 2005 16:44:42 +0100 (MET)
From: "Thomas Herzog" <thomas.herzog@gmx.li>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
MIME-Version: 1.0
References: <A632AD91CF90F24A87C42F6B96ADE5C57EBCB6@rsys005a.comm.ad.roke.co.uk>
Subject: =?ISO-8859-1?Q?Re:_[NSIS]_RE:_GIST_API:_Adding_SessionID_to_NetworkNotifi?=
	=?ISO-8859-1?Q?cation, =09SetStateLifetime, _InvalidateRoutingState=3F?=
X-Priority: 3 (Normal)
X-Authenticated: #4469397
Message-ID: <15289.1133451882@www85.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA06709
Cc: bless@tm.uka.de, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi, see inline!

> i assume the motivation is that you don't want the NSLP
> to have to maintain an index of its state by MRI but
> only by SID? i am not sure whether it is possible to
> eliminate this functionality from the average NSLP.

The motivation was, that GIST maintains state per-MRI, per-SID and
per-NSLPID.

It is logically inconsistent, to signal the state of one specific entry v=
ia
a primitive which refers to SEVERAL entries (all SIDs of a flow).

This does only apply to the NetworkNotification primitive, the other
primitives are directed from NSLP to GIST and it is feasible to not disce=
rn
between SIDs in this direction.

The NSLP is of course free to discard the SessionID information, but from
GISTs perspective, it should include the SessionID?

Cheers,
Thomas

--=20
10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
+++ GMX - die erste Adresse f=FCr Mail, Message, More +++

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 01 10:50:59 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ehqi3-0007Ek-G0; Thu, 01 Dec 2005 10:50:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ehqi2-0007DY-BA
	for nsis@megatron.ietf.org; Thu, 01 Dec 2005 10:50:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07444
	for <nsis@ietf.org>; Thu, 1 Dec 2005 10:50:12 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ehr2X-0002Sf-HF
	for nsis@ietf.org; Thu, 01 Dec 2005 11:12:10 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB1FoBWA015956;
	Thu, 1 Dec 2005 15:50:11 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no stack
	configuration data, which holds MA_HOLD_TIME)
Date: Thu, 1 Dec 2005 15:50:10 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCB9@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no
	stack configuration data, which holds MA_HOLD_TIME)
Thread-Index: AcXb/zN6V260yTuITfS5s+b3GQNDDgai67gw
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Roland Bless" <bless@tm.uka.de>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: quoted-printable
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

[changed the subject line to attract new readers ;-) ]

hi roland,

apologies for the belated reply. i never find this topic easy
to analyse.

i think i could summarise your argument as:
"if the Q-node applies a strong security policy, a MITM will
never be able to persuade it to set up an insecure MA at all;
if it applies a weak security policy, an MITM will be able to
modify the echoed R-node proposal in the Confirm. in either
case, echoing the R-node proposal in the Confirm provides no
added value."

i believe this argument is not complete, because actually there
is a range of policies that the Q-node could apply (not just
the choice "totally secure" vs. "nothing").

first, a concrete example: take 4 MA possibilities
A: a 'perfect' MA (TLS with AES ciphering/integrity protection,
   for example)
B1: an authenticated integrity-only MA (say TCP-MD5)
B2: a 'weakly secure' MA (e.g. something restricted to 40bit RC4)
C: a trivial MA (TCP only).

the Q and R nodes support all of them. the Q node wants to use
A if possible, but realises that not all peers will always offer
it (resource or regulatory constraints); however, the Q node
is able to enforce a policy "don't use C" for some of its=20
interfaces.

consider a Q-R handshake with an MITM who wants to read the
signalling messages.

Query: Q --> (A, B1, B2) --> MITM --> (A, B1, B2) --> R

The responder node will offer all the possibilities, but
the MITM wants to ensure A is not used (it can read the
traffic directly if B1 is used, or break it off-line if B2
is used), so we have:

Response: Q <-- (B1, B2, C) <-- MITM <-- (A, B1, B2, C) <--R

The Q-node discards the option C (policy constraint) and
sets up an MA with B1 or B2 as the security mechanisms

   Q <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D MA setup (B1/B2) =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> R

If this is as far as it goes, the MITM has succeeded: A
was available to both parties, but they didn't use it; instead,
there is a security association in place but which doesn't
protect the signaling data from interception (in real-time,
for B1, or off-line decryption, B2).

However, if we echo the R-node proposal in the Confirm,=20
we have

Confirm: Q --> (B1, B2, C) --> MITM --> (B1, B2, C) --> R
(the MITM can't break the integrity protection provided by
B1 or brute-force the key used in B2 within a single RTT)
et voila: R will detect the downgrade attack and call the
police.

so this is the combination of (type of attack, security
policy) that we are trying to prevent. a way of stating this
would be:

"without the echo of the R-node proposal in the Confirm, an
MITM can bid the level of security protection down to the
weakest policy that the Q-node accepts. with the echo of the
R-node proposal in the Confirm, the Q-node only needs to
enforce a minimal security policy [require integrity protection
that cannot be broken in real-time] to ensure that the optimal
level of MA security protection supported by both nodes is
actually used."

is this correct?

robert h.

> -----Original Message-----
> From: Roland Bless [mailto:bless@tm.uka.de]=20
> Sent: 28 October 2005 21:36
> To: Hancock, Robert
> Cc: Thomas Herzog; nsis@ietf.org
> Subject: Re: [NSIS] GIST Confirm contains no stack=20
> configuration data, which holds MA_HOLD_TIME
>=20
>=20
> Hi Robert,
>=20
> > I don't think this is quite right: an attack is possible whenever
> > the MITM is on the reverse path, whether or not it is on the forward
>=20
> Right.
>=20
> > path. And the defence against the attack works whether or not the
> > MITM is on the forward path, provided weak policies are not used.
>=20
> To be more precise: the defence works because _weak_ policies
> are not used. But that was not my point. Maybe I'm wrong, but
> echoing the R-Node SCD does not contribute to
> security if the MITM is also on the forward path and is able to
> modify the confirm. The attacker cannot do anything if only
> "secure" protocols are allowed by the policy, bidding down will
> have no effect. In case we have proposals A,B,C and C is weak
> then I see the follow attack:
>=20
>        Query:
> Q-Node --- A,B,C,D -> MITM - A,B,C,D --> R-Node
>        Response:
>        <--- C ------- MITM <-- A,B,C ---
>        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D MA C Setup =
=3D=3D=3D=3D=3D=3D=3D=3D=3D>
>        Confirm:
>        ---- C ------- MITM --- A,B,C -->
>=20
> I don't see how the echoed list in the confirm
> lets the R-Node effectively detect that something was modified
> in between. In case the R-Node proposes and accepts
> only A,B (i.e. a proposal w/o weak protocols) there is no
> problem anyway.
>=20
> Another scenario that I described:
>        Query:
> Q-Node --- A,B,C,D -> MITM - A,B,C,D --> R-Node
>        Response:
>        <--- C ------- MITM <-- A,B  ---
>        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D MA C Setup =
=3D=3D=3D=3D=3D=3D=3D=3D=3D>
>        (this works only in case R-Node awaits
>        C connections from other nodes etc.)
>        Confirm:
>        ---- C ------- MITM --- A,B --->
>=20
> The R-Node should detect that something is wrong by
> checking that the established MA C is not acceptable by
> the policy for the Q-Node (this must be checked anyway).
> But the echo of the Stack Proposal in the Confirm will
> not bring you more security.
>=20
> > i think this is one of those security/complexity tradeoffs which
> > are so hard to make. to me, the complexity seems not so great, and
>=20
> Complexity is not a problem here, only redundancy.
>=20
> > the circumstances where it is useful not so exceptional. but it=20
> > would be interesting to hear additional voices on this one.
>=20
> One could argue that it may be slightly more difficult for
> an attacker to manipulate the confirm than to modify the Response.
> The problem is somewhat similar to the last problem mentioned in sec.
> 8.6.
>=20
> Regards,
>  Roland
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 01 11:46:08 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EhrZP-0004ia-W5; Thu, 01 Dec 2005 11:46:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EhrZN-0004fy-TH
	for nsis@megatron.ietf.org; Thu, 01 Dec 2005 11:46:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15180
	for <nsis@ietf.org>; Thu, 1 Dec 2005 11:45:16 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX19Q3+Q413Dcc+7ybMVMLKNoUI0xEYX2/CQ=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ehrto-0004e0-Nn
	for nsis@ietf.org; Thu, 01 Dec 2005 12:07:15 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1EhrZB-0002Rp-B1; Thu, 01 Dec 2005 17:45:58 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 2D0AE7E2E;
	Thu,  1 Dec 2005 17:45:53 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1EhrZ7-0000AS-OY; Thu, 01 Dec 2005 17:45:53 +0100
Message-ID: <438F28BA.6000900@tm.uka.de>
Date: Thu, 01 Dec 2005 17:45:46 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
Subject: Re: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no stack
	configuration data, which holds MA_HOLD_TIME)
References: <A632AD91CF90F24A87C42F6B96ADE5C57EBCB9@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <A632AD91CF90F24A87C42F6B96ADE5C57EBCB9@rsys005a.comm.ad.roke.co.uk>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.2 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.2 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Robert,

> [changed the subject line to attract new readers ;-) ]
:-)

> apologies for the belated reply. i never find this topic easy
> to analyse.

No problem.

> If this is as far as it goes, the MITM has succeeded: A
> was available to both parties, but they didn't use it; instead,
> there is a security association in place but which doesn't
> protect the signaling data from interception (in real-time,
> for B1, or off-line decryption, B2).
> 
> However, if we echo the R-node proposal in the Confirm, 
> we have
> 
> Confirm: Q --> (B1, B2, C) --> MITM --> (B1, B2, C) --> R
> (the MITM can't break the integrity protection provided by
> B1 or brute-force the key used in B2 within a single RTT)

Ok, right. I guess the sentence in parentheses is exactly what
I was missing. In my scenario the MITM was able to re-establish
the original proposal:
Confirm: Q --> (B1, B2, C) --> MITM --> (A, B1, B2, C) --> R
This would be possible if B1,..,C are too weak.
So I think it is an important point and must be mentioned.

> et voila: R will detect the downgrade attack and call the
> police.
:-D

> so this is the combination of (type of attack, security
> policy) that we are trying to prevent. a way of stating this
> would be:
> 
> "without the echo of the R-node proposal in the Confirm, an
> MITM can bid the level of security protection down to the
> weakest policy that the Q-node accepts. with the echo of the
> R-node proposal in the Confirm, the Q-node only needs to
> enforce a minimal security policy [require integrity protection
> that cannot be broken in real-time] to ensure that the optimal
> level of MA security protection supported by both nodes is
> actually used."
> 
> is this correct?

Yep. But it's written rather compact. I'm not sure whether it's getting
clear that the essential point is the integrity protection of the
Confirm by the MA that prevents modification of the echoed proposal.

Regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 01 15:31:17 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ehv5J-0003ku-Sb; Thu, 01 Dec 2005 15:31:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ehv5I-0003i5-E8
	for nsis@megatron.ietf.org; Thu, 01 Dec 2005 15:31:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23533
	for <nsis@ietf.org>; Thu, 1 Dec 2005 15:30:28 -0500 (EST)
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EhvPp-0007F7-4G
	for nsis@ietf.org; Thu, 01 Dec 2005 15:52:30 -0500
Received: (qmail invoked by alias); 01 Dec 2005 20:31:03 -0000
Received: from p54986E47.dip.t-dialin.net (EHLO [192.168.2.102])
	[84.152.110.71]
	by mail.gmx.net (mp020) with SMTP; 01 Dec 2005 21:31:03 +0100
X-Authenticated: #29516787
Message-ID: <438F5D85.20208@gmx.net>
Date: Thu, 01 Dec 2005 21:31:01 +0100
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: NSIS <nsis@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: [NSIS] ietf#64 presentation slides / reminder
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi all,

in order to complete the meeting minutes we need the following 
presentation slides:
- NSIS Operation Over IP Tunnels
- QSPEC I-D
- Y.1541-QOSM I-D
- User Application-to-User Plane Vertical Interface
- NAT traversal for GIST

please send them to me and to john.

ciao
hannes


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 02 06:15:25 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ei8sv-0002BR-4j; Fri, 02 Dec 2005 06:15:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ei8st-0002BE-4K
	for nsis@megatron.ietf.org; Fri, 02 Dec 2005 06:15:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07666
	for <nsis@ietf.org>; Fri, 2 Dec 2005 06:14:36 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ei9DX-0002K4-MD
	for nsis@ietf.org; Fri, 02 Dec 2005 06:36:45 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB2BE2WA019969;
	Fri, 2 Dec 2005 11:14:02 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
Date: Fri, 2 Dec 2005 11:14:02 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCBE@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] RE: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
Thread-Index: AcX2jlks5lsPcdqWR2SoM5Z2olxuQQAoRnAw
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
Cc: bless@tm.uka.de, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi thomas,

i think the question here is how one sees the relationship
between
- the GIST routing state table
- API events
- the 'external' network events (e.g. IP-level re-routing)

if you regard the NetworkNotification API as a signal that
there has been a change in the GIST routing state table, it
is also logical to that it should include the session ID.

however, if you regard the NetworkNotification API as a=20
signal to signalling applications that something has changed
in the network, it probably doesn't - since the network=20
level changes are detected (in general) with session ID
independent means (e.g. a forwarding table change is SID
independent).

i tend to see the second as more fundamental; NSLPs should=20
not care about the GIST routing table structure, but do care
about the more fundamental re-routing (and other) events. so
i see GIST as manipulating the routing state table and=20
issuing API events as logically independent activities, both
of them triggered by events in the network.

robert h.

> -----Original Message-----
> From: Thomas Herzog [mailto:thomas.herzog@gmx.li]=20
> Sent: 01 December 2005 15:45
> To: Hancock, Robert
> Cc: bless@tm.uka.de; nsis@ietf.org
> Subject: Re: [NSIS] RE: GIST API: Adding SessionID to=20
> NetworkNotification, SetStateLifetime, InvalidateRoutingState?
>=20
>=20
> Hi, see inline!
>=20
> > i assume the motivation is that you don't want the NSLP
> > to have to maintain an index of its state by MRI but
> > only by SID? i am not sure whether it is possible to
> > eliminate this functionality from the average NSLP.
>=20
> The motivation was, that GIST maintains state per-MRI, per-SID and
> per-NSLPID.
>=20
> It is logically inconsistent, to signal the state of one=20
> specific entry via
> a primitive which refers to SEVERAL entries (all SIDs of a flow).
>=20
> This does only apply to the NetworkNotification primitive, the other
> primitives are directed from NSLP to GIST and it is feasible=20
> to not discern
> between SIDs in this direction.
>=20
> The NSLP is of course free to discard the SessionID=20
> information, but from
> GISTs perspective, it should include the SessionID?
>=20
> Cheers,
> Thomas
>=20
> --=20
> 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
> +++ GMX - die erste Adresse f=FCr Mail, Message, More +++
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 02 10:05:13 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EiCTJ-0004Bj-GM; Fri, 02 Dec 2005 10:05:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EiCTG-0004Al-Vt
	for nsis@megatron.ietf.org; Fri, 02 Dec 2005 10:05:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04157
	for <nsis@ietf.org>; Fri, 2 Dec 2005 10:04:22 -0500 (EST)
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EiCny-0002Fx-0l
	for nsis@ietf.org; Fri, 02 Dec 2005 10:26:34 -0500
Received: (qmail 21158 invoked by uid 0); 2 Dec 2005 15:04:55 -0000
Received: from 194.39.131.40 by www46.gmx.net with HTTP;
	Fri, 2 Dec 2005 16:04:55 +0100 (MET)
Date: Fri, 2 Dec 2005 16:04:55 +0100 (MET)
From: "Thomas Herzog" <thomas.herzog@gmx.li>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
MIME-Version: 1.0
Subject: =?ISO-8859-1?Q?RE:_[NSIS]_RE:_GIST_API:_Adding_SessionID_to_NetworkNotifi?=
	=?ISO-8859-1?Q?cation, =09SetStateLifetime, _InvalidateRoutingState=3F?=
X-Priority: 3 (Normal)
X-Authenticated: #4469397
Message-ID: <25568.1133535895@www46.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA04157
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi, thanks, this sounds OK, but I have one small point to argue:

Assume 2 GIST signaling paths for the same MRI but 2 different Sessions.

Assume that one signaling path has another GIST next hop.

This link may break, but it may happen that the second path via another G=
IST
next hop is not influenced.

This scenario may happen if one would implement e.g. Aggregation and a
specific GIST has been told by it's NSLP to drop out of the path for one
Session, but stay in the path for another Session.

In this case, GIST would signal "this Flow in this direction is broken", =
but
it would only be the case for one of its Sessions.

What about this case?

e.g.:

A --- B --- C --- D  breaks because of something happening to B

A --------- C --- D  stays intact, as B is irrelevant

Of course, the Flow itself may also be broken for the second path, but th=
is
cannot be decided by the GIST on node A. It could also happen that the fl=
ow
stays intact, simply rerouting around B and converging back in C.


Cheers, Thomas


> --- Urspr=FCngliche Nachricht ---
> Von: "Hancock, Robert" <robert.hancock@roke.co.uk>
> An: "Thomas Herzog" <thomas.herzog@gmx.li>
> Kopie: <bless@tm.uka.de>, <nsis@ietf.org>
> Betreff: RE: [NSIS] RE: GIST API: Adding SessionID to
> NetworkNotification,	SetStateLifetime, InvalidateRoutingState?
> Datum: Fri, 2 Dec 2005 11:14:02 -0000
>=20
> hi thomas,
>=20
> i think the question here is how one sees the relationship
> between
> - the GIST routing state table
> - API events
> - the 'external' network events (e.g. IP-level re-routing)
>=20
> if you regard the NetworkNotification API as a signal that
> there has been a change in the GIST routing state table, it
> is also logical to that it should include the session ID.
>=20
> however, if you regard the NetworkNotification API as a=20
> signal to signalling applications that something has changed
> in the network, it probably doesn't - since the network=20
> level changes are detected (in general) with session ID
> independent means (e.g. a forwarding table change is SID
> independent).
>=20
> i tend to see the second as more fundamental; NSLPs should=20
> not care about the GIST routing table structure, but do care
> about the more fundamental re-routing (and other) events. so
> i see GIST as manipulating the routing state table and=20
> issuing API events as logically independent activities, both
> of them triggered by events in the network.
>=20
> robert h.
>=20
> > -----Original Message-----
> > From: Thomas Herzog [mailto:thomas.herzog@gmx.li]=20
> > Sent: 01 December 2005 15:45
> > To: Hancock, Robert
> > Cc: bless@tm.uka.de; nsis@ietf.org
> > Subject: Re: [NSIS] RE: GIST API: Adding SessionID to=20
> > NetworkNotification, SetStateLifetime, InvalidateRoutingState?
> >=20
> >=20
> > Hi, see inline!
> >=20
> > > i assume the motivation is that you don't want the NSLP
> > > to have to maintain an index of its state by MRI but
> > > only by SID? i am not sure whether it is possible to
> > > eliminate this functionality from the average NSLP.
> >=20
> > The motivation was, that GIST maintains state per-MRI, per-SID and
> > per-NSLPID.
> >=20
> > It is logically inconsistent, to signal the state of one=20
> > specific entry via
> > a primitive which refers to SEVERAL entries (all SIDs of a flow).
> >=20
> > This does only apply to the NetworkNotification primitive, the other
> > primitives are directed from NSLP to GIST and it is feasible=20
> > to not discern
> > between SIDs in this direction.
> >=20
> > The NSLP is of course free to discard the SessionID=20
> > information, but from
> > GISTs perspective, it should include the SessionID?
> >=20
> > Cheers,
> > Thomas
> >=20
> > --=20
> > 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
> > +++ GMX - die erste Adresse f=FCr Mail, Message, More +++
> >=20
>=20

--=20
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen f=FCr GMX Partner: http://www.gmx.net/de/go/partner

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 02 20:23:55 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EiM83-0004Ml-0q; Fri, 02 Dec 2005 20:23:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EiM82-0004MZ-3t
	for nsis@megatron.ietf.org; Fri, 02 Dec 2005 20:23:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26109
	for <nsis@ietf.org>; Fri, 2 Dec 2005 20:23:06 -0500 (EST)
Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.24] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EiMSo-00043B-54
	for nsis@ietf.org; Fri, 02 Dec 2005 20:45:23 -0500
Received: From wagner With LocalMail ; Sat, 3 Dec 2005 12:23:48 +1100 
From: Muhammad Ali Malik <mamalik@cse.unsw.edu.au>
To: nsis@ietf.org
Date: Sat, 3 Dec 2005 12:23:48 +1100 (EST)
X-X-Sender: mamalik@wagner.orchestra.cse.unsw.EDU.AU
Message-ID: <Pine.LNX.4.61.0512031222070.24440@wagner.orchestra.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [NSIS] ns-2 implementation of nsis QoS
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

Is there any ns-2 implementation of nsis QoS. I am interested in 
impelmenting NSIS QoS in ns2, please advise me which document should i 
need to follow.

Regards,

Muhammad Malik

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Sun Dec 04 02:32:17 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EioM5-0003cO-R6; Sun, 04 Dec 2005 02:32:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EioM4-0003cF-6U
	for nsis@megatron.ietf.org; Sun, 04 Dec 2005 02:32:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13774
	for <nsis@ietf.org>; Sun, 4 Dec 2005 02:31:27 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eioh7-000256-4K
	for nsis@ietf.org; Sun, 04 Dec 2005 02:54:01 -0500
Received: from zeus.cs.utwente.nl (zeus.ewi.utwente.nl [130.89.10.12])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with ESMTP id jB47WCK4000444
	for <nsis@ietf.org>; Sun, 4 Dec 2005 08:32:12 +0100 (MET)
Received: from janus.cs.utwente.nl (janus [130.89.10.26])
	by zeus.cs.utwente.nl (8.12.10/8.12.10) with ESMTP id jB47WB5B023937
	for <nsis@ietf.org>; Sun, 4 Dec 2005 08:32:12 +0100 (MET)
Received: (from nobody@localhost)
	by janus.cs.utwente.nl (8.11.7p1+Sun/8.10.2) id jB47WCF00318;
	Sun, 4 Dec 2005 08:32:12 +0100 (MET)
Date: Sun, 4 Dec 2005 08:32:12 +0100 (MET)
X-Authentication-Warning: janus.cs.utwente.nl: nobody set sender to
	karagian@cs.utwente.nl using -f
To: nsis@ietf.org
Received: from 84.82.109.231 (auth. user karagian@imap2.cs.utwente.nl)
	by webmail.cs.utwente.nl with HTTP; Sun, 04 Dec 2005 07:32:11 +0000
X-IlohaMail-Blah: karagian@ewi.utwente.nl
X-IlohaMail-Method: mail() [mem]
X-IlohaMail-Dummy: moo
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <aRk8iQGG.1133681531.7392600.karagian@ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -5.576 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Sun, 04 Dec 2005 08:32:13 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Subject: [NSIS] Fwd: [Tsvwg] new version load control draft submitted to
	tsvwg
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


To be informed!

Best regards,
Georgios


--- Original Message ---
Date: 12/4/2005
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Subject: [Tsvwg] new version load control draft submitted to tsvwg



Hi all

Please note that we submitted a new version of the load control draft to
the tsvwg working group, see:

http://www.ietf.org/internet-drafts/draft-westberg-loadcntr-04.txt


The Load Control draft addresses the following issues:

     1. Admission control for real time data flows in stateless domains

     2. Dropping of flows in case of exceptional events, such as
        severe congestion after re-routing
Please note that the last version of this draft was submitted in April
2000.
The functionality concepts described in this version are not different
than
the ones described in the previous version.


Recently new drafts have been submitted aiming to standardize new
Diffserv PHB and define an architecture providing controlled load
services in
Diffserv domains [CL-Diffs, CL-PHB]. These proposals are very similar to
the two-bit marking scheme of Load Control. The major differences
are that in the admission control is based on the marking of the data
packets, i.e. without sending probe packets, and different methods of
marking of the ECN field.

During the tsvwg meeting of Vancouver, the tsvwg working group requested
from us and the authors of the [CL-Diffs, CL-PHB, RSVP-ECN] to cooperate
and converge. Therefore, the main goal of this draft is to provide, in
addition to the [CL-Diffs, CL-PHB, RSVP-ECN],  a starting point on the
cooperation between the authors of [CL-Diffs, CL-PHB, RSVP-ECN] and the
authors of the load control draft.
Note that the references [CL-Diffs, CL-PHB, RSVP-ECN] are:


[CL-Diffs]  Briscoe, B. et al. "A Framework for Admission Control over
   DiffServ using Pre-Congestion Notification", draft-briscoe-tsvwg-cl-
   architecture-01.txt, Work in progress, Oct 2005,;

[CL-PHB]  Briscoe, B. et al. "The Controlled Load per hop behaviour"
   draft-briscoe-tsvwg-cl-phb-00.txt, Work in progress, July 2005

[RSVP-ECN] Le Faucheur, F., et al. "RSVP Extensions for CL-ECN",
   draft-lefaucheur-rsvp-ecn-00.txt, Work in progress, Oct 2005


Best Regards,
Georgios

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 05 01:19:56 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ej9hc-00004s-C5; Mon, 05 Dec 2005 01:19:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ej9hb-0008WT-KN
	for nsis@megatron.ietf.org; Mon, 05 Dec 2005 01:19:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04558
	for <nsis@ietf.org>; Mon, 5 Dec 2005 01:19:05 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjA2p-0003QK-Gw
	for nsis@ietf.org; Mon, 05 Dec 2005 01:41:53 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jB56JZ44001289; Mon, 5 Dec 2005 08:19:36 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Dec 2005 08:19:35 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Dec 2005 08:19:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] ns-2 implementation of nsis QoS
Date: Mon, 5 Dec 2005 08:19:34 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D0171AF35@esebe100.NOE.Nokia.com>
Thread-Topic: [NSIS] ns-2 implementation of nsis QoS
Thread-Index: AcX3qMB00In53mm5QMGRyT7SmOXmDQBusXdg
To: <mamalik@cse.unsw.edu.au>, <nsis@ietf.org>
X-OriginalArrivalTime: 05 Dec 2005 06:19:35.0425 (UTC)
	FILETIME=[DCF80F10:01C5F963]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Muhammad,

>Is there any ns-2 implementation of nsis QoS.=20

Not that I am aware of.

> I am interested=20
>in impelmenting NSIS QoS in ns2, please advise me which=20
>document should i need to follow.

The QoS document is here:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-08.txt

I think you could make some shortcuts for the transport, but if you
wanted to be thorough, then you might also want to implement GIST as
a separate module:

http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-08.txt

Then, for more advanced features, implementing the basic QoS template
http://www.ietf.org/internet-drafts/draft-ietf-nsis-rmd-04.txt
would then give people the ability to try different QoS models.

thanks,
John

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 05 05:25:27 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjDXD-0002x9-TO; Mon, 05 Dec 2005 05:25:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjDXB-0002wr-LI
	for nsis@megatron.ietf.org; Mon, 05 Dec 2005 05:25:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27140
	for <nsis@ietf.org>; Mon, 5 Dec 2005 05:24:35 -0500 (EST)
Received: from smtp2.dei.uc.pt ([193.137.203.231] helo=smtp.dei.uc.pt)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjDsR-00033d-Iq
	for nsis@ietf.org; Mon, 05 Dec 2005 05:47:25 -0500
Received: from mail.dei.uc.pt (mail.dei.uc.pt [193.136.212.3])
	by smtp.dei.uc.pt (8.13.4/8.13.4) with ESMTP id jB5AQmmb027416;
	Mon, 5 Dec 2005 10:26:48 GMT
Received: from mail.dei.uc.pt (localhost.localdomain [127.0.0.1])
	by mail.dei.uc.pt (8.13.5/8.13.5) with ESMTP id jB5AOBDH032654;
	Mon, 5 Dec 2005 10:24:11 GMT
Received: (from nobody@localhost)
	by mail.dei.uc.pt (8.13.5/8.12.5/Submit) id jB5AOBw3032653;
	Mon, 5 Dec 2005 10:24:11 GMT
X-Authentication-Warning: mail.dei.uc.pt: nobody set sender to zhang@dei.uc.pt
	using -f
Received: from gtDEI-Vlans2.dei.uc.pt (gtDEI-Vlans2.dei.uc.pt
	[193.137.203.230]) by mail.dei.uc.pt (IMP) with HTTP 
	for <zhang@193.136.212.2>; Mon,  5 Dec 2005 10:24:11 +0000
Message-ID: <1133778251.4394154b19875@mail.dei.uc.pt>
Date: Mon,  5 Dec 2005 10:24:11 +0000
From: Jian Zhang <zhang@dei.uc.pt>
To: mamalik@cse.unsw.edu.au, nsis@ietf.org
Subject: RE: [NSIS] ns-2 implementation of nsis QoS
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-FCTUC-DEI-SIC-MailScanner-Information: Please contact helpdesk@dei.uc.pt for
	more information
X-FCTUC-DEI-SIC-MailScanner: Found to be clean
X-FCTUC-DEI-SIC-MailScanner-SpamCheck: not spam (whitelisted),
	SpamAssassin (score=-2.599, required 3, autolearn=not spam,
	BAYES_00 -2.60)
X-FCTUC-DEI-SIC-MailScanner-From: zhang@dei.uc.pt
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 8bit
Cc: Edmundo Monteiro <edmundo@dei.uc.pt>, cordeiro@dei.uc.pt
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi, Muhammad,

We at the LCT of Univ. of Coimbra have implemented the QoS-NSLP and GIST
according to the drafts:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-07.txt and
http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-07.txt. If you are
interested in them, please feel free to email to us. Now, we are in the course
of implementing QoS Models.

Cheers.

Jian Zhang (Ph.D.)
-- 
Laboratory of Communications and Telematics (LCT)
Dept. of Informatics Engineering
University of Coimbra
Polo II - Pinhal de Marrocos
3030-290 Coimbra
Portugal




_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 05 05:46:04 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjDrA-0007g2-06; Mon, 05 Dec 2005 05:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjDr7-0007fp-KD
	for nsis@megatron.ietf.org; Mon, 05 Dec 2005 05:46:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29167
	for <nsis@ietf.org>; Mon, 5 Dec 2005 05:45:11 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjECN-0003iP-Gj
	for nsis@ietf.org; Mon, 05 Dec 2005 06:08:01 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id jB5AjPCU022746; 
	Mon, 5 Dec 2005 11:45:25 +0100 (MET)
Message-ID: <00cd01c5f989$00ba91f0$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "Jian Zhang" <zhang@dei.uc.pt>, <mamalik@cse.unsw.edu.au>, <nsis@ietf.org>
References: <1133778251.4394154b19875@mail.dei.uc.pt>
Subject: Re: [NSIS] ns-2 implementation of nsis QoS
Date: Mon, 5 Dec 2005 11:45:23 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -5.608 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Mon, 05 Dec 2005 11:45:26 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: Edmundo Monteiro <edmundo@dei.uc.pt>, cordeiro@dei.uc.pt
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Jian

That is great!
I am also interested in these ns2 implementations and
I think that more people are interested in this!

It will be very great if you could provide us with an
URL link such that we can download the ns2-models!

Best Regards,
Georgios

----- Original Message ----- 
From: "Jian Zhang" <zhang@dei.uc.pt>
To: <mamalik@cse.unsw.edu.au>; <nsis@ietf.org>
Cc: "Edmundo Monteiro" <edmundo@dei.uc.pt>; <cordeiro@dei.uc.pt>
Sent: Monday, December 05, 2005 11:24 AM
Subject: RE: [NSIS] ns-2 implementation of nsis QoS


> Hi, Muhammad,
>
> We at the LCT of Univ. of Coimbra have implemented the QoS-NSLP and GIST
> according to the drafts:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-07.txt and
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-07.txt. If you 
> are
> interested in them, please feel free to email to us. Now, we are in the 
> course
> of implementing QoS Models.
>
> Cheers.
>
> Jian Zhang (Ph.D.)
> -- 
> Laboratory of Communications and Telematics (LCT)
> Dept. of Informatics Engineering
> University of Coimbra
> Polo II - Pinhal de Marrocos
> 3030-290 Coimbra
> Portugal
>
>
>
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 05 17:36:03 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjOwF-00006y-Mf; Mon, 05 Dec 2005 17:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjOwE-00006o-7t
	for nsis@megatron.ietf.org; Mon, 05 Dec 2005 17:36:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24188
	for <nsis@ietf.org>; Mon, 5 Dec 2005 17:35:12 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjPHa-0005Hb-Nz
	for nsis@ietf.org; Mon, 05 Dec 2005 17:58:08 -0500
Received: from p54849e0c.dip0.t-ipconnect.de ([84.132.158.12]
	helo=[134.76.81.226])
	by s4.ifi.informatik.uni-goettingen.de with asmtp
	(TLS-1.0:DHE_RSA_AES_128_CBC_SHA:16) (Exim 4.34)
	id 1EjOw8-0006Oh-8v; Mon, 05 Dec 2005 23:35:56 +0100
Message-ID: <4394C071.7070309@cs.uni-goettingen.de>
Date: Mon, 05 Dec 2005 23:34:25 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Muhammad Ali Malik <mamalik@cse.unsw.edu.au>
Subject: Re: [NSIS] ns-2 implementation of nsis QoS
References: <Pine.LNX.4.61.0512031222070.24440@wagner.orchestra.cse.unsw.EDU.AU>
In-Reply-To: <Pine.LNX.4.61.0512031222070.24440@wagner.orchestra.cse.unsw.EDU.AU>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Muhammad,

there's also an implementation of GIST from the University of Goettingen. Please 
follow this link to get the source.

http://user.informatik.uni-goettingen.de/~nsis/

Bernd

Muhammad Ali Malik wrote:
> Hi,
> 
> Is there any ns-2 implementation of nsis QoS. I am interested in 
> impelmenting NSIS QoS in ns2, please advise me which document should i 
> need to follow.
> 
> Regards,
> 
> Muhammad Malik

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 06 03:45:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjYRt-0005Qg-OH; Tue, 06 Dec 2005 03:45:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjYRq-0005QT-FC
	for nsis@megatron.ietf.org; Tue, 06 Dec 2005 03:45:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24005
	for <nsis@ietf.org>; Tue, 6 Dec 2005 03:44:26 -0500 (EST)
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjYnH-000863-W0
	for nsis@ietf.org; Tue, 06 Dec 2005 04:07:29 -0500
Received: from mail3.siemens.de (localhost [127.0.0.1])
	by david.siemens.de (8.12.6/8.12.6) with ESMTP id jB68j8vO001551;
	Tue, 6 Dec 2005 09:45:08 +0100
Received: from mhpahx2c.ww002.siemens.net (mhpahx2c.mch.sbs.de [139.25.165.55])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id jB68j8Br020437;
	Tue, 6 Dec 2005 09:45:08 +0100
Received: from blns00fa.ww002.siemens.net ([147.54.45.102]) by
	mhpahx2c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Dec 2005 09:45:07 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] ns-2 implementation of nsis QoS
Date: Tue, 6 Dec 2005 09:45:07 +0100
Message-ID: <391E6FBF5E786940B9E2F7CA6376C708DE4625@blns00fa.ww002.siemens.net>
Thread-Topic: [NSIS] ns-2 implementation of nsis QoS
Thread-Index: AcX3qMB00In53mm5QMGRyT7SmOXmDQBusXdgADdkmDA=
From: "Kappler, Cornelia" <cornelia.kappler@siemens.com>
To: <john.loughney@nokia.com>, <mamalik@cse.unsw.edu.au>, <nsis@ietf.org>
X-OriginalArrivalTime: 06 Dec 2005 08:45:07.0862 (UTC)
	FILETIME=[5C51F360:01C5FA41]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Muhammad,=20

note the basic QoS template is
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-07.txt. I
think John provided the wrong link.=20

Cornelia

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of john.loughney@nokia.com
> Sent: Montag, 5. Dezember 2005 07:20
> To: mamalik@cse.unsw.edu.au; nsis@ietf.org
> Subject: RE: [NSIS] ns-2 implementation of nsis QoS
>=20
>=20
> Hi Muhammad,
>=20
> >Is there any ns-2 implementation of nsis QoS.=20
>=20
> Not that I am aware of.
>=20
> > I am interested=20
> >in impelmenting NSIS QoS in ns2, please advise me which=20
> >document should i need to follow.
>=20
> The QoS document is here:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-08.txt
>=20
> I think you could make some shortcuts for the transport, but if you
> wanted to be thorough, then you might also want to implement GIST as
> a separate module:
>=20
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-08.txt
>=20
> Then, for more advanced features, implementing the basic QoS template
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-rmd-04.txt
> would then give people the ability to try different QoS models.
>=20
> thanks,
> John
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 06 03:58:19 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjYeR-0000QQ-6n; Tue, 06 Dec 2005 03:58:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjYeP-0000QI-FO
	for nsis@megatron.ietf.org; Tue, 06 Dec 2005 03:58:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25287
	for <nsis@ietf.org>; Tue, 6 Dec 2005 03:57:25 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjYzo-0008Tf-GF
	for nsis@ietf.org; Tue, 06 Dec 2005 04:20:27 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jB68w3ek023931; Tue, 6 Dec 2005 10:58:04 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Dec 2005 10:58:03 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Dec 2005 10:58:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] ns-2 implementation of nsis QoS
Date: Tue, 6 Dec 2005 10:58:01 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D0171B197@esebe100.NOE.Nokia.com>
Thread-Topic: [NSIS] ns-2 implementation of nsis QoS
Thread-Index: AcX3qMB00In53mm5QMGRyT7SmOXmDQBusXdgADdkmDAAAIALsA==
To: <cornelia.kappler@siemens.com>, <mamalik@cse.unsw.edu.au>, <nsis@ietf.org>
X-OriginalArrivalTime: 06 Dec 2005 08:58:03.0058 (UTC)
	FILETIME=[2A5F7920:01C5FA43]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Good catch Cornelia - cutting & pasting when kids are climbing on your
back
can cause problems ...

John=20

>-----Original Message-----
>From: ext Kappler, Cornelia [mailto:cornelia.kappler@siemens.com]=20
>Sent: 06 December, 2005 10:45
>To: Loughney John (Nokia-NRC/Helsinki);=20
>mamalik@cse.unsw.edu.au; nsis@ietf.org
>Subject: RE: [NSIS] ns-2 implementation of nsis QoS
>
>Hi Muhammad,=20
>
>note the basic QoS template is
>http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-07.tx
t. I think John provided the wrong link.=20
>
>Cornelia
>
>> -----Original Message-----
>> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf=20
>> Of john.loughney@nokia.com
>> Sent: Montag, 5. Dezember 2005 07:20
>> To: mamalik@cse.unsw.edu.au; nsis@ietf.org
>> Subject: RE: [NSIS] ns-2 implementation of nsis QoS
>>=20
>>=20
>> Hi Muhammad,
>>=20
>> >Is there any ns-2 implementation of nsis QoS.=20
>>=20
>> Not that I am aware of.
>>=20
>> > I am interested
>> >in impelmenting NSIS QoS in ns2, please advise me which document=20
>> >should i need to follow.
>>=20
>> The QoS document is here:
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-08.txt
>>=20
>> I think you could make some shortcuts for the transport, but if you=20
>> wanted to be thorough, then you might also want to implement=20
>GIST as a=20
>> separate module:
>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-08.txt
>>=20
>> Then, for more advanced features, implementing the basic QoS=20
>template=20
>> http://www.ietf.org/internet-drafts/draft-ietf-nsis-rmd-04.txt
>> would then give people the ability to try different QoS models.
>>=20
>> thanks,
>> John
>>=20
>> _______________________________________________
>> nsis mailing list
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>=20
>

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 06 17:26:52 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EjlGu-0004xO-Cj; Tue, 06 Dec 2005 17:26:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EjlGs-0004ty-3H
	for nsis@megatron.ietf.org; Tue, 06 Dec 2005 17:26:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00133
	for <nsis@ietf.org>; Tue, 6 Dec 2005 17:25:59 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX18OwSX8VrnBzkP/EeFIBiE5PH5oo00CdP0=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EjlcQ-0003vT-Tz
	for nsis@ietf.org; Tue, 06 Dec 2005 17:49:08 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1EjlGa-00005F-Fi; Tue, 06 Dec 2005 23:26:35 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 523F6B56B;
	Tue,  6 Dec 2005 23:26:32 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1EjlGZ-0008N4-GF; Tue, 06 Dec 2005 23:26:32 +0100
Message-ID: <43961020.8090800@tm.uka.de>
Date: Tue, 06 Dec 2005 23:26:40 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: john.loughney@nokia.com
Subject: Re: [NSIS] ns-2 implementation of nsis QoS
References: <1AA39B75171A7144A73216AED1D7478D0171AF35@esebe100.NOE.Nokia.com>
In-Reply-To: <1AA39B75171A7144A73216AED1D7478D0171AF35@esebe100.NOE.Nokia.com>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.2 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.2 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi John, Hi Muhammad,

> The QoS document is here:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-08.txt
> 
> I think you could make some shortcuts for the transport, but if you
> wanted to be thorough, then you might also want to implement GIST as
> a separate module:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-08.txt
> 
> Then, for more advanced features, implementing the basic QoS template
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-rmd-04.txt
> would then give people the ability to try different QoS models.

Our team at the University of Karlsruhe (Thomas Herzog, Markus Ott,
Matthias Friedrich) has nearly completed a full-featured implementation
of GIST, QoS-NSLP (both draft-08 versions) and QSPEC. We are planning to
release the source code under GPL in January. Our implementation is
multi-threaded and written in C++ (runs under Linux in user-space).
Thus, it may serve as basis for an ns-2 implementation (if one tries
to adapt/integrate the thread-based part).
First internal interop tests with the University of
Goettingen implementation were quite successful (thanks go to the team
there). Currently, further tests are performed, but the code is quite
complete now.

Best regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 07 13:34:15 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ek47L-0002Lm-B6; Wed, 07 Dec 2005 13:34:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek47K-0002LX-J6
	for nsis@megatron.ietf.org; Wed, 07 Dec 2005 13:34:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10249
	for <nsis@ietf.org>; Wed, 7 Dec 2005 13:33:22 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ek4T3-00022r-E2
	for nsis@ietf.org; Wed, 07 Dec 2005 13:56:42 -0500
Received: from sbz-30.cs.helsinki.fi (sbz-30.cs.helsinki.fi [128.214.9.98])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 07 Dec 2005 20:34:08 +0200
	id 000700D2.43972B20.00004F3C
Date: Wed, 7 Dec 2005 20:34:08 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: nsis@ietf.org
Message-ID: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [NSIS] Update on the QoS NSLP work
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi all,

Georgios, Andrew and I have worked on the QoS NSLP since the Vancouver
meeting. The document is close to being finalized. The main issue left is
a sanity check on whether and how mobility really works with the QoS NSLP.
Apart from that, we should be done.

A diff of the current version against -08 is available at:

http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html

All feedback is always appreciated.

Regards,
Jukka

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 07 15:01:05 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ek5TN-0001RY-6y; Wed, 07 Dec 2005 15:01:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek5TK-0001RQ-U2
	for nsis@megatron.ietf.org; Wed, 07 Dec 2005 15:01:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20522
	for <nsis@ietf.org>; Wed, 7 Dec 2005 15:00:10 -0500 (EST)
Received: from mail120.messagelabs.com ([216.82.255.211])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ek5p0-0005Q7-RF
	for nsis@ietf.org; Wed, 07 Dec 2005 15:23:32 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-11.tower-120.messagelabs.com!1133985601!10311233!9
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 23991 invoked from network); 7 Dec 2005 20:00:41 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-11.tower-120.messagelabs.com with SMTP;
	7 Dec 2005 20:00:41 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by
	attrh3i.attrh.att.com (7.2.052)
	id 4389E74D0015468B; Wed, 7 Dec 2005 15:00:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Update on the QoS NSLP work
Date: Wed, 7 Dec 2005 14:00:41 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9750@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: [NSIS] Update on the QoS NSLP work
Thread-Index: AcX7XT5f9S5sZGd2QxiijXYYKb5YHQACaoYA
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Jukka,

> A diff of the current version against -08 is available at:
> http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html
> All feedback is always appreciated.

Looks good.  A quick comment: shouldn't=20

   [I-D.ietf-nsis-qspec] Ash, J., "QoS NSLP QSPEC Template", draft-ietf-
   nsis-qspec-06 (work in progress), October 2005.=20

be a normative reference rather than an informative reference?  BTW,
QSPEC is in version 7 now (we plan to issue version 8 shortly), and I
believe the specific draft reference is supposed to be omitted.

Thanks,
Jerry

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 07 15:37:39 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ek62l-0002Sf-56; Wed, 07 Dec 2005 15:37:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek62j-0002SM-H8
	for nsis@megatron.ietf.org; Wed, 07 Dec 2005 15:37:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23788
	for <nsis@ietf.org>; Wed, 7 Dec 2005 15:36:45 -0500 (EST)
From: jmanner@cs.helsinki.fi
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ek6OO-0006Yp-1w
	for nsis@ietf.org; Wed, 07 Dec 2005 16:00:07 -0500
Received: from sbz-12.cs.helsinki.fi (sbz-12.cs.helsinki.fi [128.214.9.76])
	(AUTH: PLAIN cs-relay, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 07 Dec 2005 22:37:28 +0200
	id 00070102.43974808.00001CFF
Received: from sbz-12.cs.helsinki.fi (localhost [127.0.0.1])
	by sbz-12.cs.helsinki.fi (8.12.8/8.12.8) with ESMTP id jB7KbSlm011409; 
	Wed, 7 Dec 2005 22:37:28 +0200
Received: (from www@localhost)
	by sbz-12.cs.helsinki.fi (8.12.8/8.12.8/Submit) id jB7KbRiB011408;
	Wed, 7 Dec 2005 22:37:27 +0200
Date: Wed, 7 Dec 2005 22:37:27 +0200
X-Authentication-Warning: sbz-12.cs.helsinki.fi: www set sender to
	jmanner@cs.helsinki.fi using -f
To: gash@att.com, nsis@ietf.org
Subject: RE: [NSIS] Update on the QoS NSLP work
Received: from 80.186.10.27 (auth. user jmanner@courier)
	by iloha.cs.Helsinki.FI with HTTP; Wed, 07 Dec 2005 22:37:27 +0200
X-IlohaMail-Blah: jmanner@cs.helsinki.fi
X-IlohaMail-Method: mail() [mem]
X-IlohaMail-Dummy: moo
X-Mailer: IlohaMail/0.8.12+pk-7 (On: iloha.cs.Helsinki.FI)
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA09FA9750@KCCLUST06EVS1.ugd.att.com>
Message-ID: <xXIiueuX.1133987847.6269540.jmanner@cs.helsinki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 2.7 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi,

you are probably right, on all aspects. I haven't really worked on the
references lately. :)

The references, and the IANA considerations are things that will be
handled last, once all technical issues have been handled.

Cheers,
Jukka

On 12/7/2005, "Ash, Gerald R (Jerry), ALABS" <gash@att.com> wrote:
> Jukka,
>=20
> > A diff of the current version against -08 is available at:
> > http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html
> > All feedback is always appreciated.
>=20
> Looks good.  A quick comment: shouldn't=20
>=20
>    [I-D.ietf-nsis-qspec] Ash, J., "QoS NSLP QSPEC Template", draft-ietf-
>    nsis-qspec-06 (work in progress), October 2005.=20
>=20
> be a normative reference rather than an informative reference?  BTW,
> QSPEC is in version 7 now (we plan to issue version 8 shortly), and I
> believe the specific draft reference is supposed to be omitted.
>=20
> Thanks,
> Jerry

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 08 09:03:56 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkMNI-0002Kt-SS; Thu, 08 Dec 2005 09:03:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkMNB-0002Jt-Nl; Thu, 08 Dec 2005 09:03:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18000;
	Thu, 8 Dec 2005 09:02:49 -0500 (EST)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EkMMy-0001MK-D5; Thu, 08 Dec 2005 09:03:41 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5DC6B128E;
	Thu,  8 Dec 2005 15:03:26 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Dec 2005 15:01:44 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN re-markingwhen DSCP
	re-markingcan do it
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 8 Dec 2005 15:01:39 +0100
Message-ID: <F005CD411D18D3119C8F00508B087480139F4A2B@ehubunt100.eth.ericsson.se>
Thread-Topic: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN re-markingwhen DSCP
	re-markingcan do it
Thread-Index: AcXxV5l9yovCkXiBT8qKRKPVyhRjUAJxQmbw
From: =?iso-8859-1?Q?Attila_B=E1der_=28IJ/ETH=29?= <attila.bader@ericsson.com>
To: "Bob Briscoe" <rbriscoe@jungle.bt.co.uk>
X-OriginalArrivalTime: 08 Dec 2005 14:01:44.0735 (UTC)
	FILETIME=[EC2A3AF0:01C5FBFF]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d424907374faffed8e9e11e94f671eb2
Content-Transfer-Encoding: quoted-printable
Cc: philip.eardley@bt.com, Georgios Karagiannis <karagian@cs.utwente.nl>,
	tsvwg@ietf.org, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Bob, Thank you for your answer, please see my comments below.

Best regards, Attila

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org]
> Sent: Thursday, November 24, 2005 6:41 PM
> To: Georgios Karagiannis
> Cc: philip.eardley@bt.com; tsvwg@ietf.org; nsis@ietf.org
> Subject: Re: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN=20
> re-markingwhen
> DSCP re-markingcan do it
>=20
>=20
> Georgios,
>=20
> (long e-mail)
>=20
> We thought long and hard about which re-marking to use. My=20
> primary concern=20
> was to keep the Internet architecture consistent, which leads to the=20
> arguments below.
>=20
> 1/ Intended semantics of the Internet Architecture
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>=20
> 1.1/ Intended re-marking semantics of Diffserv & ECN
> --------------------------------------------------
> Diffserv re-marking was defined for two reasons:
>      i) To allow the ingress of a Diffserv domain to prevent=20
> traffic in=20
> excess of the contracted rate/burstiness from being given favourable=20
> treatment at downstream routers if they became congested themselves.
>      ii) To allow a border router to map the DSCP used for a per-hop=20
> behaviour in the upstream domain to that used for the same PHB in the=20
> downstream domain.
>=20
> ECN re-marking is used by a node to indicate that the node itself is=20
> approaching congestion. The intent is to reduce the load from=20
> the source,=20
> but marking is forwarded downstream in the expectation that=20
> it will be fed=20
> back to the source.
>=20
>      Thus, the intent of Diffserv re-marking is to alter the=20
> downstream per=20
> hop forwarding behaviour if necessary. Diffserv re-marking=20
> was not intended=20
> to be fed back to the source.
>      The intent of ECN re-marking is to reduce the load at=20
> source through=20
> feedback. ECN re-marking was specifically not intended to alter the=20
> downstream forwarding behaviour of re-marked packets.
>=20
> That's the idealistic view. In practice, it can be convenient=20
> to break=20
> architecture. But architecture is there to warn you to think=20
> long and hard=20
> when you depart from it, so you are aware of what you might=20
> break in the=20
> future.
>=20

I agree that this would be an idealistic picture. Note that you would =
like to use ECN for Admission Control. Diffserv is used also for =
admission control so there is an overlap between ECN and Diffserv. In =
the meantime ECN was defined for end-to-end congestion control of =
elastic traffic type that makes things complicate. While there is no =
such limitation to use remaining Diffserv codepoints for congestion =
notification edge-to-edge.

> 1.2/ Was ECN at the IP layer intended to have end-to-end semantics?
> -------------------------------------------------------------------
> RFC3168 was written so that the ECN semantics in IP could be=20
> separated from=20
> the end-to-end ECN semantics of TCP when other ECN transports=20
> were defined.
>=20
> [According to Sally Floyd at the time, the main reason for=20
> specifying ECN=20
> for TCP & IP together in the same RFC was to encourage the first=20
> experiments with ECN to be in TCP implementations which tend=20
> to be written=20
> with a lot more care by a few kernel experts.]
>=20
> Indeed, Jon Crowcroft and I wrote an I-D reviewing the ECN=20
> I-D before it=20
> became RFC3168. In section 12, we proposed text on ECN semantics for=20
> proxies (edge-to-edge), asking that it be added to the ECN RFC:
> <http://www.cs.ucl.ac.uk/staff/B.Briscoe/pubs.html#ECN-IP> (Expired)
>=20
> Sally Floyd's response (off-line) at the time is quoted here:
>=20
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> /\/\/\/\/\/\/\/
> At 11:35 21/02/01 -0800, Sally Floyd wrote:
>  >Feedback on Section 12, proposing rules for allowing proxies in the
>  >network to change ECN codepoints:
>  >
>  >I think that this is complicated, and has to be dealt with in a
>  >separate document, in context.  That is, when people have specific
>  >proposals for intermediate nodes to modify the ECN field,
>  >then I think they have to be addressed at that time.  My own opinion
>  >is that making general rules ahead of time, in the abstract,
>  >such as "we will now propose rules for changing the ECN
>  >capability of a packet at intermediate nodes", never gets it right.
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> /\/\/\/\/\/\/\/
>=20
> <draft-briscoe-tsvwg-cl-architecture-01.txt> is exactly that.=20
> A separate=20
> document about the semantics of ECN proxies, in this case with a flow=20
> signalling transport like RSVP (or NSIS).
>=20
> The idea of RMD and of=20
> <draft-briscoe-tsvwg-cl-architecture-01.txt> is for=20
> the node at the end of a long signalling 'hop' (a whole=20
> Diffserv region) to=20
> see how much congestion has accumulated since the start of=20
> the region.=20
> Potentially there may be other signalling 'hops' further=20
> downstream using=20
> the same technique again. So the egress of one signalling hop=20
> must tidy=20
> things up by folding any re-marked packets back in to the=20
> same marking as=20
> un-re-marked packets, to avoid confusing further region(s)=20
> downstream if=20
> they are using the same technique.
>=20
> [For instance, you are thinking of RMD being used for=20
> admission control=20
> across a radio access network. But there may be another RAN=20
> at the other=20
> end of the network using the same technique. So you must ensure any=20
> re-marked DSCPs are folded back into the same DSCP as=20
> non-re-marked packets=20
> at the RMD egress. ]
>=20

Yes, I agree that Egress edge should restore the orig. DSCP, otherwise =
there can be multiple actions for the same event. It may not be restored =
if there is agreement between domains that a downsteram domain handles =
the problem.=20

> 1.3/ Summary of architectural concerns
> --------------------------------------
> To indicate the need for admission control, it is certainly=20
> more convenient=20
> to do Diffserv re-marking as RMD does, but I believe it is more=20
> architecturally consistent to use ECN re-marking, as we do.
>=20
> However, architecture is like religion. You can break it, if=20
> it becomes too=20
> inconvenient, and if you can convince enough people you have=20
> a good excuse.
>=20
> 2. Practical issues
> -------------------
> I don't think we need to break the architecture in this case=20
> (which is why=20
> we use ECN), but using ECN re-marking edge-edge does raise=20
> the following=20
> issue...
>=20
> 2.1/ Edge-to-edge ECN conflicts with end-to-end ECN
> ---------------------------------------------------
> We fully understand that use of ECN re-marking to trigger=20
> admission control=20
> within Diffserv regions would conflict with end-to-end ECN congestion=20
> control for the *same* flow. But we deliberately chose to=20
> specify the end=20
> to end service we were providing as "controlled load=20
> [RFC2211]" to try to=20
> preclude such cases.
>=20
> RFC 2211 says:
>=20
> "  ...
> 2. End-to-End Behavior
>     ...                              Should the client's traffic
>     generation properties fall outside of the region described by the
>     TSpec parameters, the QoS provided to the client may exhibit
>     characteristics indicative of overload, including large numbers of
>     delayed or dropped packets.
>=20
>     ...
>=20
> 7. Policing
>     ...                                  the network element=20
> MUST attempt
>       to forward the excess traffic on a best-effort basis if=20
> sufficient
>       resources are available
>=20
>     ...
>=20
>     Beyond requirements 2 and 3 above, the controlled-load=20
> service does
>     not define the QoS behavior delivered to flows with non-conformant
>     arriving traffic.  Specifically, it is permissible either=20
> to degrade
>     the service delivered to all of the flow's packets equally, or to
>     sort the flow's packets into a conformant set and a=20
> nonconformant set
>     and deliver different levels of service to the two sets.
>=20
>     ...
>=20
> 9. Guidelines for Implementors
>=20
>     ...
> If most controlled-load traffic arises from rate-adaptive
>     realtime or elastic applications attempting to establish a bounded
>     minimum level of service, the use of separate resource=20
> classes might
>     be preferable.
>=20
> "
> I won't paste everything RF2211 says on with advice for=20
> implementors on=20
> scheduling elastic flows with a bounded minimum, as there's=20
> rather a lot.=20
> But basically, you get unavoidably bad re-ordering and other=20
> complications=20
> that make it hard. Even though this seems a desirable service, it's=20
> unlikely to work well in practice.
>=20
> 2.2/ End-to-end ECN conflicts with edge-to-edge admission control
> -----------------------------------------------------------------
> The congestion-based admission control mechanism used in RMD=20
> and in our=20
> <draft-briscoe-tsvwg-cl-architecture-01.txt> would break if a=20
> significant=20
> proportion of admitted traffic were adaptive. If congestion=20
> on an interior=20
> path were close to the threshold where admission control was needed,=20
> adaptive traffic might temporarily drop well below its=20
> minimum bound. More=20
> flows might then be accepted, then the adaptive traffic could=20
> grow again,=20
> destroying the controlled load service for all flows through=20
> that path.
>=20
> [Note: Variable bit rate (VBR) like video traffic would=20
> superfically seem=20
> to break a measurement-based admission control system in the=20
> same way as=20
> adaptive traffic. But unlike with adaptive traffic, troughs=20
> in VBR load are=20
> not correlated with congestion. Our analyses of how the=20
> effective bandwidth=20
> of VBR (and silence-suppressed voice) aggregates has shown that our=20
> solution works OK for VBR, given specific conditions on the amount of=20
> aggregation and provided VBR traffic sources are not=20
> correlated. We are=20
> currently preparing this analysis for publication.]
>=20

That study sounds interesting. I do not think that the congestion-based =
admission control is good enough for all networks. Meas. based methods =
certainly have limitations, especially in access network, as you also =
mention in your draft. In RMD edge nodes are statefull nodes. I think =
that unit-based aggregated reservation in core combined with per-flow =
schedulers in edges can provide an Intserv-like service in the domain as =
well.

> 2.3/ Summary of end/edge conflicts
> ----------------------------------
> So, we prefer to say that a different service would have to=20
> be requested to=20
> cater for your hybrid requirement. Hence my preference for explicitly=20
> requesting "adaptive rate control with a bounded minimum" in the=20
> signalling, as a different QoS service. In NSIS terms, this=20
> is would be in=20
> the QSPEC, I believe.
>

I think this traffic should use controlled load service. Or define a new =
QoS model.

> 2.4/ Codepoint space
> --------------------
> Real-estate in the IP header is at a premium. Treating the=20
> 6-bit Diffserv=20
> field and the 2-bit ECN field separately leads to 2^6 + 2^2 =3D 68=20
> codepoints. Treating them together leads to 2^8 =3D 256=20
> codepoints. In the=20
> MPLS EXP field, real-estate is a far greater headache.
>=20
> If ECN marking is orthogonal to Diffserv marking for most Diffserv=20
> codepoints, it makes sense to treate the field as 6-bit and 2-bit=20
> sub-fields. But I don't believe we should be averse to=20
> bending the rules to=20
> save codepoint space across both fields.
>=20
> For instance both our approach and RMD need another marking=20
> state for a=20
> router in the Diffserv interior to indicate the need for flow=20
> pre-emption=20
> (eg. after re-routes). Pre-emption represents severe=20
> congestion and needs=20
> to be fed back upstream. So by my arguments above pre-emption=20
> should be=20
> re-marked using the ECN field. But in our current pre-emption=20
> solution, if=20
> two or more nodes in a path require some flows to be=20
> pre-empted, packets=20
> that have already been re-marked once to indicate pre-emption=20
> need to be=20
> treated differently by downstream nodes. So by my arguments above=20
> pre-emption should also be re-marked using the DSCP.
>=20
> Well, it would be silly to waste two codepoints for one=20
> state. And there=20
> aren't enough ECN codepoints anyway. So, IMHO, you have to be=20
> pragmatic and=20
> be willing to re-mark the Diffserv codepoint for pre-emption=20
> (CAVEAT: the=20
> authors of <draft-briscoe-tsvwg-cl-architecture-01.txt> still haven't=20
> reached consensus on marking - that's why=20
> <draft-briscoe-tsvwg-cl-phb-00.txt> hasn't been updated yet).

We think that both DSCP and ECN remarking could be used for congestion =
notification admission control and severe congestion [pre-emption] with =
limitation.=20

>=20
> 7/ Consistent meaning of an ECN marking
> ---------------------------------------
> I hope I have answered your question about why we use ECN not=20
> Diffserv=20
> re-marking. We are not completely inflexible about using ECN,=20
> but I do have=20
> further reasons for preferring ECN re-marking---to do with=20
> the economic=20
> interpretation of congestion marking across different=20
> classes. It would=20
> take too long to go into that here, but you can read a recent paper I=20
> published on the subject if interested.
>=20
> Commercial Models for IP Quality of Service Interconnect, Bob=20
> Briscoe &=20
> Steve Rudkin (BT), in BTTJ Special Edition on IP Quality of=20
> Service, 23(2)=20
> (Apr 2005)
> <http://www.cs.ucl.ac.uk/staff/B.Briscoe/pubs.html#ixqos>
>=20
> I have also given responses inline...
>=20
> At 09:28 24/11/2005, Georgios Karagiannis wrote:
> >----- Original Message ----- From: <philip.eardley@bt.com>
> >To: <philip.eardley@bt.com>; <karagian@cs.utwente.nl>
> >Cc: <tsvwg@ietf.org>; <nsis@ietf.org>
> >Sent: Thursday, November 24, 2005 1:23 AM
> >Subject: RE: [Tsvwg] why use edge-to-edge ECN re-marking when DSCP=20
> >re-markingcan do it
> >
> >
> >>>>[GK] What is the technical reason of using ECN for edge-toedge=20
> >>>>congestion control?
> >>[PE] The use of Ecn seems natural to me, since we wnat the=20
> network to=20
> >>indicate incipient congestion and that's what ECN is=20
> supposed to do. Note=20
> >>that the semantics are the same as rfc3168 (ECN) - ie same=20
> codepoints of=20
> >>ECN field and CE codepoint indicates incipient congestion.=20
> I also think=20
> >>it can help with migration to a fully ecn world. As operators get=20
> >>experience of using ecn, whilst not requiring all nws / end=20
> hosts to be=20
> >>using it.
> >
> >Georgios: yes I understand but the ECN semantics apply=20
> end-to-end, not=20
> >edge-toedge,
> >please see the previous discussions on this issue!
>=20
> [BB] ECN semantics were originally defined for an end-to-end protocol=20
> (TCP). That does not imply they were only intended to ever be=20
> end-to-end.=20
> RFC3168 did not preclude edge-to-edge. And at least one of=20
> the authors=20
> believed edge-to-edge semantics could be a valid thing to=20
> define later (see=20
> quote from Sally Floyd above).
>=20
>=20
>=20
> >>[PE] Second, using DSCP re-marking seems to need a lot of DSCPs.=20
> >>According to your draft, admission control implies 2 per=20
> traffic class=20
> >>(one for re-marked pkts, one for other pkts passing thru the same=20
> >>router). Plus another for the severe congestion indication.=20
> In addition,=20
> >>in the core network an interesting future extension is to use the=20
> >>mechanisms in a network with MPLS-TE (see our framework=20
> draft for brief=20
> >>discussion) - there isnt sufficient space in the label for=20
> these extra dscps.
> >
> >Georgios: regarding the number of DSCP's you are right, but=20
> there are ways
> >of reducing this number, please see the RMD draft.
> >Please also note that the streaming aplication example that has been=20
> >discussed in
> >the tsvwg and nsis mailing lists shows that it is usefull to use
> >end-to-end ECN based congestion control for reserved traffic.
> >This streaming application example can very efficiently use=20
> RSVP and the
> >DCCP protocol (which uses the end-to-end ECN concept).
>=20
> [BB] No-one on the list has said it would be efficient. In fact the=20
> opposite has been said (by Louise Burness) and no-one has=20
> disagreed. I=20
> believe this hybrid service should be set aside for someone=20
> else to define=20
> a mechanism for later. Intserv couldn't even do it very well,=20
> even though=20
> it had a per-flow scheduler.
>=20
>=20
> >[GK] Please also note that the support of this type of this type of=20
> >streaming application that
> >combines the end to end ECN semantics
> >with reserved minimum bandwidth is needed not only
> >in the backbone network but also in the wireless network as well.
> >Therefore the rate-adaptation function of ECN (DCCP functionality)
> >combined with minimum bandwidth reservation can be very important.
>=20
> [BB] Yes, an adaptive application with a minimum rate would=20
> be a desirable=20
> service. But it's not the one we are defining. And you will=20
> find it doesn't=20
> work with RMD's congestion-based admission scheme either.
>=20
> [BB] We are trying to do Controlled Load to scale to the=20
> Internet. We don't=20
> know how to implement this hybrid at Internet scale. We have=20
> had to limit=20
> our scope to avoid this hybrid problem. And you will find that such a=20
> hybrid service wouldn't work with the mechanism you have=20
> defined for RMD=20
> either.
>=20
> [BB] So I need to turn your question back on you: how would=20
> you prevent=20
> adaptive applications using your RMD congestion mechanism,=20
> and breaking the=20
> admission control system?
>=20
> [BB] The solution I have proposed is to require the=20
> application to signal=20
> this hybrid requirement and if it is not signalled, to drop=20
> any excess=20
> traffic at the region ingress in order to disincentivise any adaptive=20
> application trying to use the wrong service for its needs.
>=20
>=20
> >>Third, (as bob has pointed out) that it's easy to overcome=20
> the end-to-end=20
> >>vs edge-to-edge
> >marking issue (if that's really needed, which I'm inclined=20
> to think it isnt)
> >
> >Georgios: regarding this point I am not sure if it is easy!=20
> It depends on the
> >imposed additional complexity.
>=20
> [BB] If a request for this hybrid were signalled (and an=20
> operator chose to=20
> support the hybrid service), with the current state of=20
> knowledge, I would=20
> say that this hybrid traffic would have to be dealt with by a=20
> less scalable=20
> means, such as Intserv per-flow schedulers on every node, or=20
> your hop by=20
> hop reservation method in RMD.
>=20
>=20
> Bob
>=20
> >Best regards,
> >Georgios
> >
> >
> >>
> >>________________________________
> >>
> >>From: tsvwg-bounces@ietf.org on behalf of philip.eardley@bt.com
> >>Sent: Wed 23/11/2005 23:48
> >>To: karagian@cs.utwente.nl
> >>Cc: tsvwg@ietf.org; nsis@ietf.org
> >>Subject: Re: [Tsvwg] why use edge-to-edge ECN re-marking when DSCP=20
> >>re-markingcan do it
> >>
> >>
> >>
> >>some comments below.
> >>
> >>best wishes, phil
> >>
> >>________________________________
> >>
> >>*       To: <rbriscoe at jungle.bt.co.uk=20
<mailto:rbriscoe@DOMAIN.HIDDEN> >
>>*       Subject: [Tsvwg] why use edge-to-edge ECN re-marking when DSCP =

>>re-marking can do it
>>*       From: "Georgios Karagiannis" <karagian at cs.utwente.nl=20
>><mailto:karagian@DOMAIN.HIDDEN> >
>>*       Date: Mon, 21 Nov 2005 10:52:22 +0100
>>*       Cc: tsvwg at ietf.org <mailto:tsvwg@DOMAIN.HIDDEN> , nsis at=20
>>ietf.org <mailto:nsis@DOMAIN.HIDDEN>
>>
>>Hi Bob
>>
>>In addition to the previous discussion I would like to
>>discuss and ask you the following.
>>
>>[chop]
>>What is the technical reason of using ECN for edge-toedge congestion =
control,
>>when the same solution (on providing admission control
>>based on congestion notification and severe
>>congestion [pre-emption]) can be provided by using DSCP re-marking?
>>
>>
>>
>>
>>_______________________________________________
>>tsvwg mailing list
>>tsvwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/tsvwg
>>
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis

_________________________________________________________________________=
___
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT =
Research
B54/130 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.   +44 1473 =
645196 =20



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 08 11:59:01 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkP6j-00067Q-4B; Thu, 08 Dec 2005 11:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EkP6h-00062G-Fn
	for nsis@megatron.ietf.org; Thu, 08 Dec 2005 11:58:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10225
	for <nsis@ietf.org>; Thu, 8 Dec 2005 11:57:58 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX1/+j8qPqA4SX5KfLe/HydvkLi2cACt0xq8=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkP6Y-0008Ai-RQ
	for nsis@ietf.org; Thu, 08 Dec 2005 11:58:53 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1EkP6F-0008UW-TR; Thu, 08 Dec 2005 17:58:42 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id ABAADB3CD;
	Thu,  8 Dec 2005 17:58:31 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1EkP6F-0002fx-9a; Thu, 08 Dec 2005 17:58:31 +0100
Message-ID: <43986636.2050508@tm.uka.de>
Date: Thu, 08 Dec 2005 17:58:30 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] Update on the QoS NSLP work
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
In-Reply-To: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.2 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.2 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Jukka MJ Manner schrieb:
> Hi all,
> 
> Georgios, Andrew and I have worked on the QoS NSLP since the Vancouver
> meeting. The document is close to being finalized. The main issue left is
> a sanity check on whether and how mobility really works with the QoS NSLP.
> Apart from that, we should be done.

We slightly disagree here ;-)

> A diff of the current version against -08 is available at:
> 
> http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html
> 
> All feedback is always appreciated.
Thanks for the new version, but I guess we have still some more
open issues:
----------------------------------
5.4.1.  RESERVE Messages
   ....

   When a QNE receives a RESERVE message with an unknown SESSION_ID, it
   MAY send a NOTIFY message to its upstream peer, indicating the
   unknown SESSION_ID. If the message was meant as a refresh, the reply
   indicates a downstream route change to the upstream peer.  The
   upstream peer SHOULD send a complete RESERVE on the new path (new
   SII).  It identifies the old signalling association (old SII) and MAY
   start sending complete RESERVE messages for other SESSION_IDs linked
   to this association.


We find this paragraph a little bit strange:
- the paragraph contradicts with sec 5.4.4:
  NOTIFY message do do not directly cause other messages to
  be sent. NOTIFY messages are sent asynchronously, rather than in
  response to other messages.
- the purpose of this mechanism is not getting totally clear:
  if it's only for the case of reduced refreshes along a
  new path (i.e. QSPEC is missing) then we would propose
  to sent rather a RESPONSE with an appropriate error code
  in order to trigger resending a RESERVE with a full QSPEC
  (this would be more consistent with the NOTIFY definition
  in 5.4.4).
  Are there other useful benefits of this proposed NOTIFY?
  Otherwise even every intial RESERVE would cause such a
  NOTIFY to be sent by all QNEs.
- How far should one forward the NOTIFY message?
  Only one hop? (this is generally not very clear)
  What about the use of the scoping flag (currently not used)?
- "If the message was meant as a refresh, the reply..."
  What reply? do you mean the NOTIFY?

------------------------------------------

5.4.1
   If the SCOPING flag is set, or if the QNE is the last QNE on the path
   to the destination, the QNE MUST send a RESPONSE message.

- "is the last QNE on the path to the destination" (isn't this the QNR?)
- if neither ACK nor SCOPING are set and no RII is present
  why MUST (only?) the last QNE generate a RESPONSE?
- we think that a RESPONSE is either triggered by an
  ACK or an RII or an error.

---------------------------------------------

PACKET_CLASSIFIER:
- is it really necessary to specify the PACKET_CLASSIFIER
  even for reduced refreshes?
- Is the value of the MRM exactly the same as in GISTs MRI?
  What should be done in case of a mismatch?

-----------------------------------------------
5.4.3.  RESPONSE Messages
   .....

   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
   flag is set or when an error occurs while processing a received
   message.  If the received message contains an RII object, this object
   MUST be put in the RESPONSE, as described above.

- We think that the last sentence should only be true in case
  of an error, but not when an ACK flag is set. In this case
  a RESPONSE should not include the RII (this RESPONSE will usually
  follow from the last QNE later) but the RSN.

That's it for now, possibly more issues later...

P.S.: would be nice if you could include also Markus Ott in the
      Acknowledgments :-)

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 04:53:11 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkewB-0007Vj-2O; Fri, 09 Dec 2005 04:53:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekew8-0007Tj-Uv
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 04:53:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09416
	for <nsis@ietf.org>; Fri, 9 Dec 2005 04:52:12 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkewD-0004eT-Kz
	for nsis@ietf.org; Fri, 09 Dec 2005 04:53:16 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB99pmWA027847;
	Fri, 9 Dec 2005 09:51:48 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no stack
	configuration data, which holds MA_HOLD_TIME)
Date: Fri, 9 Dec 2005 09:51:48 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5423E11@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no
	stack configuration data, which holds MA_HOLD_TIME)
Thread-Index: AcX2lstnDH4OKiKfQuihiMp7REaTcAGDhZWQ
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Roland Bless" <bless@tm.uka.de>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi roland, all,

well, i checked to see whether the description of this point in the GIST
spec could be improved, and found that there was no description at all
:-(
i'm pretty sure something was there in previous versions, but it seems
to have got lost at some stage...

so i added a new sub-section in the security considerations. hopefully
it
is now a bit less compact.

r.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

8.6.  Security Protocol Selection Policy

   This specification defines a single mandatory-to-implement security
   protocol (TLS, Section 5.7.3).  However, it is possible to define
   additional security protocols in the future, for example to allow re-
   use with other types of credentials, or migrate towards protocols
   with stronger security properties.  In addition, use of any security
   protocol for a messaging association is optional.  Security protocol
   selection is carried out as part of the GIST handshake mechanism
   (Section 4.4.1).

   The selection process may be vulnerable to downgrade attacks, where a
   man in the middle modifies the capabilities offered in the Query or
   Response to mislead the peers into accepting a lower level of
   protection than is achievable.  There is a two part defence against
   such attacks (the following is based the same concepts as [21]):

   1.  The Response does not depend on the Stack-Proposal in the Query
       (see Section 5.7.1).  Therefore, tampering with the Query message
       has no effect on the resulting messaging association
       configuration.

   2.  The Responding node's Stack-Proposal is echoed in the Confirm.
       The Responding node checks this to validate that the proposal it
       made in the Response is the same as the one received by the
       Querying node.  (Note that as a consequence of the previous
       point, the Responding node does not have to remember the proposal
       explicitly, since it is a static function of local policy.)

   The validity of the second part depends on the strength of the
   security protection provided for the Confirm message.  If the
   Querying node is prepared to create messaging associations with null
   security properties (e.g.  TCP only), the defence is ineffective,
   since the man in the middle can re-insert the original Responder's
   Stack-Proposal, and the Responding node will assume that the minimal
   protection is a consequence of Querying node limitations.  However,
   if the messaging association provides at least integrity protection
   that cannot be broken in real-time, the Confirm cannot be modified in
   this way.  Therefore, provided that the Querying node applies a
   security policy on the messaging association protocols it will create
   that ensures at least this minimal level of protection is met, it can
   be assured that the capability discovery process will result in the
   setup of a messaging association with the correct security properties
   as appropriate for the two peers involved.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-----Original Message-----
From: Roland Bless [mailto:bless@tm.uka.de]=20
Sent: 01 December 2005 16:46
To: Hancock, Robert
Cc: nsis@ietf.org
Subject: Re: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no
stack configuration data, which holds MA_HOLD_TIME)


Hi Robert,

> [changed the subject line to attract new readers ;-) ]
:-)

> apologies for the belated reply. i never find this topic easy to=20
> analyse.

No problem.

> If this is as far as it goes, the MITM has succeeded: A
> was available to both parties, but they didn't use it; instead, there=20
> is a security association in place but which doesn't protect the=20
> signaling data from interception (in real-time, for B1, or off-line=20
> decryption, B2).
>=20
> However, if we echo the R-node proposal in the Confirm,
> we have
>=20
> Confirm: Q --> (B1, B2, C) --> MITM --> (B1, B2, C) --> R (the MITM=20
> can't break the integrity protection provided by B1 or brute-force the

> key used in B2 within a single RTT)

Ok, right. I guess the sentence in parentheses is exactly what I was
missing. In my scenario the MITM was able to re-establish the original
proposal:
Confirm: Q --> (B1, B2, C) --> MITM --> (A, B1, B2, C) --> R This would
be possible if B1,..,C are too weak. So I think it is an important point
and must be mentioned.

> et voila: R will detect the downgrade attack and call the police.
:-D

> so this is the combination of (type of attack, security
> policy) that we are trying to prevent. a way of stating this would be:
>=20
> "without the echo of the R-node proposal in the Confirm, an MITM can=20
> bid the level of security protection down to the weakest policy that=20
> the Q-node accepts. with the echo of the R-node proposal in the=20
> Confirm, the Q-node only needs to enforce a minimal security policy=20
> [require integrity protection that cannot be broken in real-time] to=20
> ensure that the optimal level of MA security protection supported by=20
> both nodes is actually used."
>=20
> is this correct?

Yep. But it's written rather compact. I'm not sure whether it's getting
clear that the essential point is the integrity protection of the
Confirm by the MA that prevents modification of the echoed proposal.

Regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 05:43:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ekfij-0000Kr-Eg; Fri, 09 Dec 2005 05:43:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekfii-0000Km-8m
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 05:43:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15252
	for <nsis@ietf.org>; Fri, 9 Dec 2005 05:42:26 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX1+0sEfZ+Q4Nh/T+DHNNy1c4VCSIMYtCzYk=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekfir-0006NA-J7
	for nsis@ietf.org; Fri, 09 Dec 2005 05:43:31 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1EkfiX-0006fP-Tq; Fri, 09 Dec 2005 11:43:17 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 945ACB482;
	Fri,  9 Dec 2005 11:43:09 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1EkfiX-00048y-AU; Fri, 09 Dec 2005 11:43:09 +0100
Message-ID: <43995FBC.9000602@tm.uka.de>
Date: Fri, 09 Dec 2005 11:43:08 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
Subject: Re: Downgrade attacks (was: RE: [NSIS] GIST Confirm contains no stack
	configuration data, which holds MA_HOLD_TIME)
References: <A632AD91CF90F24A87C42F6B96ADE5C5423E11@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <A632AD91CF90F24A87C42F6B96ADE5C5423E11@rsys005a.comm.ad.roke.co.uk>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.2 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.2 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Robert,

> well, i checked to see whether the description of this point in the GIST
> spec could be improved, and found that there was no description at all
> :-(

Right, that's why I was asking for more details.

> i'm pretty sure something was there in previous versions, but it seems
> to have got lost at some stage...

That's a pity.

> so i added a new sub-section in the security considerations. hopefully
> it
> is now a bit less compact.

> r.
> 
> ======================================================================
> 
> 8.6.  Security Protocol Selection Policy
> 
>    This specification defines a single mandatory-to-implement security
>    protocol (TLS, Section 5.7.3).  However, it is possible to define
>    additional security protocols in the future, for example to allow re-
>    use with other types of credentials, or migrate towards protocols
>    with stronger security properties.  In addition, use of any security
>    protocol for a messaging association is optional.  Security protocol
>    selection is carried out as part of the GIST handshake mechanism
>    (Section 4.4.1).
> 
>    The selection process may be vulnerable to downgrade attacks, where a
>    man in the middle modifies the capabilities offered in the Query or
>    Response to mislead the peers into accepting a lower level of
>    protection than is achievable.  There is a two part defence against
>    such attacks (the following is based the same concepts as [21]):
> 
>    1.  The Response does not depend on the Stack-Proposal in the Query
>        (see Section 5.7.1).  Therefore, tampering with the Query message
>        has no effect on the resulting messaging association
>        configuration.
> 
>    2.  The Responding node's Stack-Proposal is echoed in the Confirm.
>        The Responding node checks this to validate that the proposal it
>        made in the Response is the same as the one received by the
>        Querying node.  (Note that as a consequence of the previous
>        point, the Responding node does not have to remember the proposal
>        explicitly, since it is a static function of local policy.)
> 
>    The validity of the second part depends on the strength of the
>    security protection provided for the Confirm message.  If the
>    Querying node is prepared to create messaging associations with null
>    security properties (e.g.  TCP only), the defence is ineffective,
>    since the man in the middle can re-insert the original Responder's
>    Stack-Proposal, and the Responding node will assume that the minimal
>    protection is a consequence of Querying node limitations.  However,
>    if the messaging association provides at least integrity protection
>    that cannot be broken in real-time, the Confirm cannot be modified in
>    this way.  Therefore, provided that the Querying node applies a
>    security policy on the messaging association protocols it will create
>    that ensures at least this minimal level of protection is met, it can
>    be assured that the capability discovery process will result in the
>    setup of a messaging association with the correct security properties
>    as appropriate for the two peers involved.

That sounds quite good and clear to me.

Cheers,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 06:19:01 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkgHF-0001ck-Cc; Fri, 09 Dec 2005 06:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EkgHD-0001aP-Sg
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 06:18:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19146
	for <nsis@ietf.org>; Fri, 9 Dec 2005 06:17:16 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkgGZ-0007RC-8P
	for nsis@ietf.org; Fri, 09 Dec 2005 06:18:22 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB9BHfWA019147;
	Fri, 9 Dec 2005 11:17:42 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 9 Dec 2005 11:17:43 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5423E16@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: GIST Late State Insallation: Does Responding NSLP wait for
	NetworkNotification?
Thread-Index: AcXx50JSwziPmb/nRCyGmw6+Vw42HQKxTmXw
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [NSIS] RE: GIST Late State Insallation: Does Responding NSLP wait
	for NetworkNotification?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi thomas,

there are two points here:

*) i think the idea of indicating that routing state has been
created via a NetworkNotification is a good clarification, which
can be added to the API description. (will be in -09.)

*) however, on the initial point you raise, about how to handle
an NSLP which has data to send 'against the flow', I would handle
the NSLP/GIST interaction differently.

- if there is a 'one-shot' response at the NSLP level, that can
be generated synchronously and piggybacked in the Response message
(as previously discussed).

- if the NSLP has some more significant data to send to that flow,
then there actually is no need to constrain the GIST level to=20
carry out late state installation at all. the point of the late
state installation is to avoid a state exhaustion attack on GIST
by creating half-complete routing state for large numbers of flows.
however, if there is already state in the NSLP, either we know that
this is a 'useful' flow for which it makes sense to keep state
early, or we know that the NSLP itself is vulnerable to a state
exhaustion attack, which GIST cannot defend it from. In this case,
it makes sense for GIST to handle the Query by going to the=20
"Awaiting Confirm" state (see case (2) in section 6.2). In that
state, the NSLP can generate Data messages which will be queued
in GIST until the routing state is set up.

(in theory, the selection of which state GIST should go into=20
could be indicated via the return values from the RecvMessage
API call. however, i feel that is going too deep into implementation
aspects for the GIST spec itself.)

cheers,

robert h.

> -----Original Message-----
> From: Thomas Herzog [mailto:thomas.herzog@gmx.li]=20
> Sent: 25 November 2005 17:35
> To: nsis@ietf.org; Hancock, Robert
> Subject: GIST Late State Insallation: Does Responding NSLP=20
> wait for NetworkNotification?
>=20
>=20
> Hi all,=20
>=20
> I am currently in the phase of testing and validating our=20
> GIST implementation,=20
> for which I am able to use the GistPing tool of the folks=20
> from Goettingen=20
> which currently proves to work just fine as a lightweight=20
> testing NSLP.
>=20
> So far, I am now facing the task of validating our Late State=20
> Installation=20
> mechanism, so a thought occured to me:
>=20
> Does the Responding Node's NSLP have to wait for a=20
> NetworkNotification after=20
> having told GIST to establish backwards routing state until=20
> it sends back=20
> messages itself?
>=20
> I see the problem in using Late State Installation in the=20
> case, the RN NSLP=20
> wants to directly answer to a received incoming Message.
>=20
> GIST discards any information about the Flow after having=20
> sent the response,=20
> thus a SendMessage from the Responding NSLP prior to the=20
> final State Setup=20
> would lead to an upstream Query to be sent.
>=20
> This would be a severe problem. So I think the Responding=20
> Node's NSLP should=20
> wait after receiving/answering the initial RecvMessage for the=20
> NetworkNotification which tells it that state is set up!
>=20
> Has this been covered in the NSLP draft?
>=20
> Currently (draft-08), we are signaling "Route changed, status=20
> XY" and "Last=20
> Node" via NetworkNotifications. I think, this should be=20
> extended by "Route=20
> initially set up", because in this case, there is no Route=20
> changed and the=20
> information that the messaging path is available should be=20
> also vital to a=20
> NSLP?
>=20
> Can someone clarify this?
>=20
> Cheers, Thomas
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 10:16:51 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkjzP-0004Sj-6T; Fri, 09 Dec 2005 10:16:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EkjzK-0004RB-EO
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 10:16:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18129
	for <nsis@ietf.org>; Fri, 9 Dec 2005 10:15:42 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkjzM-0007Rg-5T
	for nsis@ietf.org; Fri, 09 Dec 2005 10:16:49 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB9FFgWA021950;
	Fri, 9 Dec 2005 15:15:42 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RE: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
Date: Fri, 9 Dec 2005 15:16:05 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5423E34@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] RE: GIST API: Adding SessionID to NetworkNotification,
	SetStateLifetime, InvalidateRoutingState?
Thread-Index: AcX3UgmrCpdda8F5RCKmfO5WHaZL4gFgKaVw
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: quoted-printable
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi thomas,

it's a reasonable question; in parallel to the discussion,
i have also updated the API text for NetworkNotification
to clarify that it gets delivered to a particular NSLP,
i.e. that the NSLPID is part of the notified information.

(Routing state genuinely is NSLP dependent, not only=20
because peering state depends on which NSLPs are implemented
in which nodes, but also because there are discussions that
in some cases, NSLPs may decide to change which flows they
are interested in. This is potentially the case with the
metering NSLP, for example.)

The routing state then has to be re-established for each NSLP
independently. The signalling applications have to operate
in parallel with each other from this point of view.

cheers,

r.

> -----Original Message-----
> From: Thomas Herzog [mailto:thomas.herzog@gmx.li]=20
> Sent: 02 December 2005 15:05
> To: Hancock, Robert
> Cc: nsis@ietf.org
> Subject: RE: [NSIS] RE: GIST API: Adding SessionID to=20
> NetworkNotification, SetStateLifetime, InvalidateRoutingState?
>=20
>=20
> Hi, thanks, this sounds OK, but I have one small point to argue:
>=20
> Assume 2 GIST signaling paths for the same MRI but 2=20
> different Sessions.
>=20
> Assume that one signaling path has another GIST next hop.
>=20
> This link may break, but it may happen that the second path=20
> via another GIST next hop is not influenced.
>=20
> This scenario may happen if one would implement e.g.=20
> Aggregation and a specific GIST has been told by it's NSLP to=20
> drop out of the path for one Session, but stay in the path=20
> for another Session.
>=20
> In this case, GIST would signal "this Flow in this direction=20
> is broken", but it would only be the case for one of its Sessions.
>=20
> What about this case?
>=20
> e.g.:
>=20
> A --- B --- C --- D  breaks because of something happening to B
>=20
> A --------- C --- D  stays intact, as B is irrelevant
>=20
> Of course, the Flow itself may also be broken for the second=20
> path, but this cannot be decided by the GIST on node A. It=20
> could also happen that the flow stays intact, simply=20
> rerouting around B and converging back in C.
>=20
>=20
> Cheers, Thomas
>=20
>=20
> > --- Urspr=FCngliche Nachricht ---
> > Von: "Hancock, Robert" <robert.hancock@roke.co.uk>
> > An: "Thomas Herzog" <thomas.herzog@gmx.li>
> > Kopie: <bless@tm.uka.de>, <nsis@ietf.org>
> > Betreff: RE: [NSIS] RE: GIST API: Adding SessionID to
> > NetworkNotification,	SetStateLifetime,=20
> InvalidateRoutingState?
> > Datum: Fri, 2 Dec 2005 11:14:02 -0000
> >=20
> > hi thomas,
> >=20
> > i think the question here is how one sees the relationship between
> > - the GIST routing state table
> > - API events
> > - the 'external' network events (e.g. IP-level re-routing)
> >=20
> > if you regard the NetworkNotification API as a signal that=20
> there has=20
> > been a change in the GIST routing state table, it is also=20
> logical to=20
> > that it should include the session ID.
> >=20
> > however, if you regard the NetworkNotification API as a
> > signal to signalling applications that something has changed
> > in the network, it probably doesn't - since the network=20
> > level changes are detected (in general) with session ID
> > independent means (e.g. a forwarding table change is SID
> > independent).
> >=20
> > i tend to see the second as more fundamental; NSLPs should
> > not care about the GIST routing table structure, but do care
> > about the more fundamental re-routing (and other) events. so
> > i see GIST as manipulating the routing state table and=20
> > issuing API events as logically independent activities, both
> > of them triggered by events in the network.
> >=20
> > robert h.
> >=20
> > > -----Original Message-----
> > > From: Thomas Herzog [mailto:thomas.herzog@gmx.li]
> > > Sent: 01 December 2005 15:45
> > > To: Hancock, Robert
> > > Cc: bless@tm.uka.de; nsis@ietf.org
> > > Subject: Re: [NSIS] RE: GIST API: Adding SessionID to=20
> > > NetworkNotification, SetStateLifetime, InvalidateRoutingState?
> > >=20
> > >=20
> > > Hi, see inline!
> > >=20
> > > > i assume the motivation is that you don't want the NSLP=20
> to have to=20
> > > > maintain an index of its state by MRI but only by SID? i am not=20
> > > > sure whether it is possible to eliminate this=20
> functionality from=20
> > > > the average NSLP.
> > >=20
> > > The motivation was, that GIST maintains state per-MRI,=20
> per-SID and=20
> > > per-NSLPID.
> > >=20
> > > It is logically inconsistent, to signal the state of one
> > > specific entry via
> > > a primitive which refers to SEVERAL entries (all SIDs of a flow).
> > >=20
> > > This does only apply to the NetworkNotification=20
> primitive, the other=20
> > > primitives are directed from NSLP to GIST and it is=20
> feasible to not=20
> > > discern between SIDs in this direction.
> > >=20
> > > The NSLP is of course free to discard the SessionID
> > > information, but from
> > > GISTs perspective, it should include the SessionID?
> > >=20
> > > Cheers,
> > > Thomas
> > >=20
> > > --
> > > 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
> > > +++ GMX - die erste Adresse f=FCr Mail, Message, More +++
> > >=20
> >=20
>=20
> --=20
> Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne=20
> Risiko! Satte Provisionen f=FCr GMX Partner:=20
> http://www.gmx.net/de/go/partner
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 10:37:34 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EkkJS-0003GZ-Eb; Fri, 09 Dec 2005 10:37:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EkkJQ-00037F-AP
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 10:37:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20286
	for <nsis@ietf.org>; Fri, 9 Dec 2005 10:36:33 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkkJX-0008A6-GB
	for nsis@ietf.org; Fri, 09 Dec 2005 10:37:40 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jB9Fb8WA027953;
	Fri, 9 Dec 2005 15:37:08 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] End node detection in GIST for Messages relayed on behalf
	ofthe NSLP?
Date: Fri, 9 Dec 2005 15:37:34 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C5423E35@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] End node detection in GIST for Messages relayed on behalf
	ofthe NSLP?
Thread-Index: AcXms79MFYGL2RegSF2dn3N1R6ZjiwWIePzg
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi all,

my personal view is that it is the responsibility of the
NSLP (or other implementation support code) to detect that
there is no point in invoking GIST to send a message=20
because the destination for the message is known to be inside=20
the same node as the origin. there are actually several=20
circumstances where it makes sense to be able to do this,
but i'd rather focus the GIST specification on the node
external aspects.

robert h.

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Thomas Herzog
> Sent: 11 November 2005 11:27
> To: nsis@ietf.org
> Subject: [NSIS] End node detection in GIST for Messages=20
> relayed on behalf ofthe NSLP?
>=20
>=20
> Hi, together,
>=20
> as a result of having implemented the GIST level relaying on=20
> behalf of the=20
> NSLP, it occured to me, that if we are on the End Node of the=20
> flow and NSLP=20
> would indicate to "relay", the message would basically=20
> "cycle", i.e. the NSLP=20
> would get it delivered again and again. (if it is the actual=20
> flow endpoint,=20
> if it is the last GIST hop and the flow endpoint is not=20
> GIST-aware, it would=20
> simply be lost)
>=20
> Is a NSLP supposed to do no such nonsense (it should know it=20
> is the end node),=20
> or is GIST supposed to do End Node detection in this case=20
> also (as it does=20
> for pure GIST relaying if there is no NSLP for the message)?
>=20
> GIST could do End Node detection and provide a MessageStatus=20
> for the message,=20
> but there is no status code defined yet for such an event.
>=20
> Or GIST could deliver the message again (being relayed to=20
> itself, it will come=20
> back) and NSLP could then detect that it is the actual End=20
> Node by the fact=20
> of receiving a already relayed Message?
>=20
> Cheers, Thomas
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 09 13:49:57 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EknJd-0004Kf-9o; Fri, 09 Dec 2005 13:49:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EknJb-0004Ic-GA
	for nsis@megatron.ietf.org; Fri, 09 Dec 2005 13:49:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14245
	for <nsis@ietf.org>; Fri, 9 Dec 2005 13:48:59 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EknJn-0006od-U2
	for nsis@ietf.org; Fri, 09 Dec 2005 13:50:09 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jB9InPlW024409 for <nsis@ietf.org>; Fri, 9 Dec 2005 20:49:26 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 9 Dec 2005 20:49:46 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 9 Dec 2005 20:49:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5FCF1.5332EA32"
Date: Fri, 9 Dec 2005 20:49:46 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEBBE@esebe100.NOE.Nokia.com>
X-MS-Has-Attach: yes
Thread-Topic: nsis meeting minutes
Thread-Index: AcX2tjJB0l72kT5UT9O/JLrs9/M8FAGOxH3Q
To: <nsis@ietf.org>
X-OriginalArrivalTime: 09 Dec 2005 18:49:47.0372 (UTC)
	FILETIME=[53D51AC0:01C5FCF1]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 025f8c5000216988bfe31585db759250
Subject: [NSIS] FW: nsis meeting minutes
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5FCF1.5332EA32
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

Minutes are attached, send comments & corrections.

John

------_=_NextPart_001_01C5FCF1.5332EA32
Content-Type: text/plain;
	name="IETF "
Content-Description: IETF 
Content-Disposition: inline;
	filename="IETF "
Content-Transfer-Encoding: base64

V0VETkVTREFZLCBOb3ZlbWJlciA5LCAyMDA1DQowOTAwLTExMzAgTW9ybmluZyBTZXNzaW9uIEkN
ClRTViAgICAgbnNpcyAgICAgIE5leHQgU3RlcHMgaW4gU2lnbmFsaW5nIFdHDQoNCk1lZXRpbmcg
TWludXRlIFRha2VyOg0KIC0gQW5kcmV3IE1jRG9uYWxkDQogLSBBbmRyZWFzIFBhc2hhbGlkaXMN
CiBDb21waWxlZCBieSBIYW5uZXMgVHNjaG9mZW5pZw0KDQpBZ2VuZGEgYmFzaGluZyAtIGNoYWly
IC0gMTAgbWluDQotLS0tLS0tLS0tLS0tLQ0KDQpTbGlkZXMgYXJlIGF2YWlsYWJsZSBhdDoNCmh0
dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRlcy9uc2lzLTAucHB0DQoN
Ck5BVEZXIE5TTFAgLSBNYXJ0aW4gU3RpZW1lcmxpbmcgLSAyMCBtaW4NCmh0dHA6Ly93d3cuaWV0
Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbnNpcy1uc2xwLW5hdGZ3LTA4LnR4dA0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxlIGF0OiANCmh0dHA6Ly93d3czLmll
dGYub3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRlcy9uc2lzLTEucHB0DQoNCi0gUTogd2hhdCBp
ZiB0d28gcG9ydHMgbmVlZCB0byBvcGVuLCBlZy4gUlRQPyBhIHByb2JsZW0gd2l0aCBkb2luZyB0
d28NCiAgaXMgdGhhdCB5b3UgbWlnaHQgbm90IGdldCBzdWJzZXF1ZW50IG51bWJlcnMuIElmIHRo
ZXJlIGlzIGEgbW9yZQ0KICBnZW5lcmljIG5lZWQsIHRoZW4gdGhpcyBtaWdodCBtZSBjb25zaWRl
cmVkIHRvIGJlIGFkZGVkLg0KDQqTTm90aWZpY2F0aW9uIHN0b3JtlCBpc3N1ZTogDQoNCkpvaG4g
aXMgaW4gZmF2b3VyIG9mIJNhZ2dyZWdhdGVklCBub3RpZmllcy4gDQoNClJvYmVydDogaG93IGRv
IHlvdSByb3V0ZSB0aGlzIG1lc3NhZ2U/IA0KDQpNYXJ0aW46IGdvb2QgcXVlc3Rpb247IG5leHQg
bm9kZSBtYXkgbmVlZCB0byBmb3J3YXJkIHRoZSBub3RpZnkgZGVwZW5kaW5nIG9uIHdoZXJlIHRo
aW5ncyBtYXkgYmUgYWZmZWN0ZWQuIA0KDQpIYW5uZXM6IHdlIG5lZWQgbW9yZSB0aW1lIHRvIHN0
dWR5IHRoaXMgaXNzdWUuDQoNCkhhbm5lcyAmIEpvaG46IGEgbGlnaHR3ZWlnaHQgdmVyc2lvbiBv
ZiB0aGUgTkFURlcgTlNMUCBzZWVtcyB0byBiZSBiZXR0ZXIsIG5vdyB0aGF0IHdlIGRvbpJ0IGtu
b3cgeWV0IHdoYXQgd2UgYXJlIGdvaW5nIHRvIG5lZWQgd2l0aCBleHBlcmllbmNlLg0KDQpNYXJ0
aW46IEJ5IEZlYnJ1YXJ5IDA2LCB3ZSBhcmUgbGlrZWx5IHRvIGJlIHJlYWR5IGZvciBMQy4NCg0K
DQpOQVRGVyBOU0xQIEltcGxlbWVudGF0aW9uIFN0YXR1cyAtIEhhbm5lcyBUc2Nob2ZlbmlnIC0g
NSBtaW4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQpTbGlkZXMgYXJlIGF2YWlsYWJsZSBhdDoNCmh0dHA6Ly93d3czLmlldGYu
b3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRlcy9uc2lzLTIucHB0DQoNCkpvaG46IFdpbGwgdGhl
IHNvdXJjZSBjb2RlIGJlIG1hZGUgYXZhaWxhYmxlPyANCg0KSGFubmVzIGhvcGVzIFhpYW9taW5n
IEZ1IHdpbGwgcmVsZWFzZSB0aGUNCmNvZGUuIChubyBkYXRlIGdpdmVuKQ0KDQoNCk1vYmlsaXR5
IEFwcGxpY2FiaWxpdHkgU3RhdGVtZW50IGZvciBOU0lTIC0gU3VuZy1IeXVjayBMZWUgLSAxMCBt
aW4NCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbnNpcy1h
cHBsaWNhYmlsaXR5LW1vYmlsaXR5LXNpZ25hbGluZy0wMy50eHQNCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3
dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xpZGVzL25zaXMtMy5wcHQNCg0KLSBIYW5u
ZXM6IHdpdGggcmVnYXJkIHRvIE1JUCBBUEksIHdoZXRoZXIgd2UgY291bGQgbGV2ZXJhZ2Ugc29t
ZSB3b3JrDQogIGZyb20gb3RoZXIgV0dzPyBIYXMgc29tZW9uZSBsb29rZWQgYXQgdGhvc2U/IEVn
LiB0aGUgUEZLRVkgaW50ZXJmYWNlIHRoYXQgd2FzIHVzZWQgaW4gdGhlIGNvbnRleHQgb2YgTU9C
SUtFPyANCg0KLSBObyBvdGhlciBjb21tZW50cw0KDQpKb2huOiBpdCBpcyBnb29kIGlmIHBlb3Bs
ZSBjYW4gZ28gYW5kIHJlYWQgdGhlIG9wZW4gaXNzdWVzIGFuZCBtYWtlIGNvbW1lbnRzLg0KDQoN
Cg0KR0lTVCAtIFJvYmVydCBIYW5jb2NrIC0gMjAgbWlucyANCmh0dHA6Ly93d3cuaWV0Zi5vcmcv
aW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbnNpcy1udGxwLTA4LnR4dA0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNs
aWRlcyBhcmUgYXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3Mv
MDVub3Yvc2xpZGVzL25zaXMtNC5wcHQNCg0KUm9iZXJ0IHByZXNlbnRzIHdoYXQgaXMgZ29pbmcg
b24gaW4gY3JlYXRpbmcgdmVyc2lvbiAwOSBiYXNlZCBvbiBXR0xDDQoNCg0KTWFydGluOiCTaXQg
aXMgaW1wb3J0YW50IHRvIGZpbmlzaCBHSVNUOyB0aHVzIGhhdmUgaXQgd2l0aCBiYXNpYyBUTFMg
bm93LCBhbmQgYWRkIGFkdmFuY2VkIFRMUyBsYXRlcpQuDQoNCkpvaG46IJN0aGUgc2VjdXJpdHkg
YXJlYSB3aWxsIGxvb2sgY2xvc2VseSBvbiBob3cgd2UgdXNlIFRMUzsgc28gZW5vdWdoIGluZm9y
bWF0aW9uIHNob3VsZCBiZSBpbiBHSVNUIHNvIHRoYXQgdGhlIHNlY3VyaXR5IGFyZWEgaXMgc2F0
aXNmaWVklC4NCg0KSGFubmVzOiBJdCBpcyBnb29kIHRvIHRoaW5rIG5vdyBhYm91dCBleHRlbnNp
YmlsaXR5IGFuZCBob3cgdG8gZXh0ZW5kIHVzYWdlIHNjZW5hcmlvcy4gSSB0aGluayB3ZSBuZWVk
IG1vcmUgdGhpbmtpbmcgYWJvdXQgaG93IHRvIHByb2NlZWQgYmVzdC4NCg0KSm9objogUkZDIDIw
MjYuIG1heWJlIHdlIHNob3VsZCBhZGQgc29tZSCTTVVTVJQgd2l0aCBhIJNNQVmUIHRoYXQgd291
bGQgYWxsb3cgb3RoZXIgdXNhZ2VzIG9mIFRMUw0KDQpIYW5uZXM6IJNiYXNpYyBzdHVmZiB3b3Jr
cywgYnV0IG90aGVyIG1lY2hhbmlzbXMgdGhhdCBhcmUgbW9yZSBzdWl0YWJsZSBmb3IgY2VydGFp
biBkZXBsb3ltZW50cyBtYXkgbmVlZCB0byBleGNoYW5nZSBhZGRpdGlvbmFsIGluZm9ybWF0aW9u
lA0KDQpSb2JlcnQ6IJNpdCBpcyBpbXBvcnRhbnQgdG8gZ2V0IHRoZSBvdGhlciB1c2VzIG9mIFRM
Uy4gSW4gcmVhbGl0eSBpdCBpcyBpbXBvcnRhbnQgdG8gZ2V0IHRoZXNlIGluLiANClF1ZXN0aW9u
IGlzOiBkbyB3ZSB3YW50IHRoaXMgYXMgYW4gZXh0ZW5zaW9uIG9yIG5vPw0KDQpYaWFvbWluZzog
k3RoZSBNQVkgYXBwcm9hY2ggc2VlbXMgdXNlZnVsIHRvIG1lOyBpdCBkb2VzIG5vdCBodXJ0OyB0
aGVuIGV4dGVuc2lvbnMgY2FuIGJlIGRvbmUgd2hlbiB0aGV5knJlIG5lZWRlZJQNCg0KSGVubmlu
ZzogbmVlZCB0byBoYXZlIGEgc2luZ2xlIHBsYWNlIHdoZXJlIHRoZSB0ZXh0IHRhbGtzIGFib3V0
DQp0aW1lcnMsIGhvdyB0byBzZXQgdGhlbSB1cCwgd2hhdCBhcmUgdGhlIGlzc3VlcywgaG93IHRv
IGF2b2lkIG5ldHdvcmsNCnN5bmNocm9uaXphdGlvbiwgZXRjLg0KDQpKb2huOiCTYWJvdXQgZG93
bmdyYWRpbmcgYXR0YWNrczogdGhlIHNlY3VyaXR5IEFEIHdpbGwgc3BvdCB0aGlzIGFuZCBwb2lu
dCBvdXQgcHJvYmxlbXMsIGlmIHRoZXJlIGFyZSBhbnmULiBBYm91dCBpbnRlcm5hbCB0aW1lciBv
cGVyYXRpb24gYW5kIHNldHRpbmcNCg0KSGVubmluZzogk3RoaXMgaXMgYSBwcm9ibGVtIHRoYXQg
YXJpc2VzIGluIG90aGVyIHByb3RvY29scy4gSXQgc2VlbXMgcmVhc29uYWJsZSwgdG8gaGF2ZSBh
IHBhcmFncmFwaCBzb21ld2hlcmUgYmVjYXVzZSB0aGlzIHN0dWZmIGlzIHJlYWxseSB1c2VmdWwg
Zm9yIGltcGxlbWVudGVycy4gVGhlcmUgaXMgYSBmaXJzdCBvcmRlciBjb25jZXJuLCBlLmcuIHlv
dSBkb26SdCB3YW50IHRvIHdhaXQgdW50aWwgdGhlIGxhc3QgbWlsbGlzZWNvbmQgYmVmb3JlIHlv
dSByZWZyZXNoLpQNCg0KUm9iZXJ0OiCTd2lsbCBhZGQgdGV4dJQuDQoNCkpvaG46IJN0aGVyZSBh
cmUgYSBudW1iZXIgb2YgR0lTVCBpbXBsZW1lbnRhdGlvbiB1bmRlciBHUEwgZXRjLiB0aGVyZSBp
cyB0aGVyZWZvcmUgcnVubmluZyBjb2RlIGF2YWlsYWJsZSBmb3IgcGVvcGxlIHdobyB3b3VsZCBs
aWtlIHRvIGV4cGVyaW1lbnQgd2l0aCBpdIWUDQoNCkFuYWx5c2lzIG9mIE9wdGlvbnMgZm9yIFNl
Y3VyaW5nIEdJU1QgLSBIYW5uZXMgVHNjaG9mZW5pZw0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRl
cm5ldC1kcmFmdHMvZHJhZnQtdHNjaG9mZW5pZy1uc2lzLWdpc3Qtc2VjdXJpdHktMDAudHh0DQot
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRwOi8v
d3d3My5pZXRmLm9yZy9wcm9jZWVkaW5ncy8wNW5vdi9zbGlkZXMvbnNpcy01LnBwdA0KDQoNCkpv
aG46IJN0aGlzIGlzIGZ1dHVyZSBvcmllbnRlZCBzY2VuYXJpb3M7IGdvb2QgdG8gZ2V0IGZlZWRi
YWNrIGZyb20gZGVwbG95ZXJzOyBkbyBhbnkgb2YgdGhlc2UgdGhhdCBIYW5uZXMgbGlzdGVuIGFy
ZSByZWxldmFudCB0byBwZW9wbGUgd2hvIHdhbnQgdG8gZGVwbG95IHRoaXMgc3R1ZmY/lA0KDQpI
YW5uZXM6IJNpdCBtaWdodCBiZSBnb29kIHRvIGhhdmUgYSCTc3RvcnmUIGFib3V0IGhvdyB0byBp
bnRlZ3JhdGUgb3RoZXIgc2VjdXJpdHkgbWVjaGFuaXNtcyB3aXRoaW4gR0lTVJQNCg0KDQpQYXRo
IHR5cGUgc3VwcG9ydCBmb3IgTlNJUyBzaWduYWxpbmcgLSBUYWtha28gU2FuZGEgLSAxNSBtaW4N
Cmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXNhbmRhLW5zaXMtcGF0
aC10eXBlLTAzLnR4dA0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxlIGF0Og0K
aHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xpZGVzL25zaXMtNi5wcHQN
Cg0KTm8gY29tbWVudHMgZnJvbSB0aGUgYXVkaWVuY2UNCg0KSm9objogk3dlIG5lZWQgZmVlZGJh
Y2sgdG8gc2VlIGlmIHRoaXMgaXMgbmVlZGVkIGluIE5TSVOUDQoNCg0KDQpOU0lTIEZsb3cgSUQg
YW5kIHBhY2tldCBjbGFzc2lmaWNhdGlvbiBJc3N1ZXMgLSBDaGVuZyBIb25nIC0gMTUgbWluDQpo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jaGVuZy1uc2lzLWZsb3dp
ZC1pc3N1ZXMtMDIudHh0DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxl
IGF0Og0KaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xpZGVzL25zaXMt
Ny5wcHQNCg0Kk2FsbCBpbmZvcm1hdGlvbiBpcyBzdGlsbCBkZXJpdmVkIGZyb20gdGhlIE1SSZQu
DQoNCkpvaG46IJNzb21lIG9mIHRoaXMgaXMgZ29pbmcgdG8gYmUgZGlzY3Vzc2VkIHRvbW9ycm93
LiBIb3QgdG9waWMgd2l0aCByZXNwZWN0IHRvIFFvUyBOU0xQlC4NCg0KWGlhb21pbmc/OiCTcTE6
IGlkZWEgaXMgdG8gY2xhc3NpZnkgYW55dGhpbmcgdGhhdCBpcyBub3QgaW4gdGhlIE1SSS4gV2hl
cmUgeW91IHNwZWNpZnkgdGhlIG5lZWRlZCBvYmplY3Q/IFEyOiCTaXMgdGhpcyByZWFsbHkgbmVl
ZGVkIHJpZ2h0IG5vdz8gV2UgY2FuIGFsd2F5cyBhZGQgbmV3IG9iamVjdHMgaW4gdGhlIGZ1dHVy
ZSwgd2hlbiB0aGVyZSBpcyByZWFsIG5lZWSULg0KDQpDaGVuZzogd2UgYXJlIG5vdCBnb2luZyB0
byBkZWZpbmUgYW55dGhpbmcuIFdlIHRoaW5rIHRoYXQgaXQgaXMgbmVlZGVkIG5vdyBiZWNhdXNl
IGluIFFvUyB5b3Ugd2FudCB0byBzaWduYWwgcG9ydCByYW5nZXMuDQoNClJvYmVydDogk2lmIHlv
dSBoYXZlIGEgY2xhc3NpZmllciB3aXRoIG11bHRpcGxlIGFkZHJlc3NlcywgaG93IHdvdWxkIHlv
dSByb3V0ZSB0aGlzIHRvPyAoaWYgeW91IGhhdmUgbXVsdGlwbGUgZGVzdGluYXRpb24gYWRkcmVz
c2VzKS4gQW5vdGhlciBxIGFib3V0IHBvcnQgcmFuZ2VzOiBob3cgY29tbW9uIGlzIGl0IHRvIGNh
cnJ5IGlkZW50aWNhbCBzaWduYWxpbmcgZGF0YSBvdmVyIG11bHRpcGxlIHBvcnRzP5QNCg0KTWFy
dGluOiCTSSBoYXZlIHByb2JsZW1zIHdpdGggc2F5aW5nIHRvIHB1dCBzb21ldGhpbmcgaW4gdGhl
IE5TTFAgbGF5ZXIgdGhhdCByZXBsYWNlcyBzb21ldGhpbmcgaW1wb3J0YW50LiBJcyB0aGlzIHRo
ZSBzYW1lIHNpZ25hbGluZyBmbG93IHlvdSBhcmUgc2lnbmFsaW5nIGZvcj8gWW91IGNhbiBleHRl
bmQgdGhlIE1SSSwgYnV0IG5vdCBjb21wbGV0ZWx5IHJlcGxhY2UgaXSFlCANCg0KQ2hlbmc6IJNz
aWduYWxpbmcgaXMgc3RpbGwgYmFzZWQgb24gTVJJLiBUaGVyZSBhcmUgc29tZSBjYXNlcyB0aGF0
IG1heSByZXN1bHQgaW4gYSBkaWZmZXJlbnQgTVJJOyBleGFtcGxlOiB0dW5uZWxpbmcgY2FzZS4g
VGhlcmUgYXJlIHNvbWUgcmVhbCB1c2UgY2FzZXMgZm9yIG11bHRpcGxlIHBvcnRzlA0KDQoNCg0K
R0lTVCBvdmVyIFNDVFAgLSBYaWFvbWluZyBGdSAtIDUgbWluDQpodHRwOi8vd3d3LmlldGYub3Jn
L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1mdS1uc2lzLW50bHAtc2N0cC0wMC50eHQNCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoN
Cg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3My5pZXRmLm9yZy9wcm9jZWVk
aW5ncy8wNW5vdi9zbGlkZXMvbnNpcy04LnBwdA0KDQpYaWFvbWluZyBtZW50aW9ucyB0aGF0IHBl
cmZvcm1hbmNlIHRlc3RzIHJlZ2FyZGluZyB0aGUgTGludXggU0NUUCB2ZXJzaW9uIGRvIG5vdCBv
ZmZlcg0KdGhlIGJlc3QgcGVyZm9ybWFuY2UuIFhpYW9taW5nIHRoaW5rcyB0aGF0IHRoZSBTQ1RQ
IGltcGxlbWVudGlvbiBjb3VsZCBiZSBpbXByb3ZlZC4gDQoNCkpvaG46IJN0aGUgbGludXggU0NU
UCBoYXMgbm8gb3B0aW1pemF0aW9uIGluIGl0LpQNCg0KSm9objogk2hvdyBtdWNoIGRvZXMgdGhp
cyBhZmZlY3QgdGhlIGN1cnJlbnQgR0lTVD+UDQoNClJvYmVydDogk3doZW4gdGhpcyBjYW1lIG91
dCwgSSBzYWlkIJN0aGlzIGRyYWZ0IGlzIHJlYWxseSBzaG9ydJSXd2hpY2ggaXMgYSBnb29kIHRo
aW5nLiBJIHRoaW5rIHRoaXMgc2hvdWxkIGJlIGRvbmUgc2VwYXJhdGVseS6UDQoNCkpvaG46IJNt
YXkgaXQgaXMgYmV0dGVyIHRvIG1vdmUgd2l0aCB0aGlzIGZvcndhcmQgc2VwYXJhdGVseS4gVGhp
cyBpcyBsaWtlbHkgdG8gYmVjb21lIFdHIGl0ZW0sIGJ1dCBmaXJzdCBsZXSScyBoYXZlIEFEIHJl
dmlldyBmb3IgdGhlIGJhc2UgR0lTVIWUDQoNCg0KDQoNCk5TSVMgT3BlcmF0aW9uIE92ZXIgSVAg
VHVubmVscyAtIEhlbm5pbmcgU2NodWx6cmlubmUgLSAxMCBtaW4JDQpodHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1zaGVuLW5zaXMtdHVubmVsLTAxLnR4dCANCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3My5pZXRmLm9yZy9wcm9j
ZWVkaW5ncy8wNW5vdi9zbGlkZXMvbnNpcy05LnBwdA0KDQoNClJvYmVydDogdHVubmVsIG5lZWRz
IHRvIGRvIE5TTFAtcmVsYXRlZCBwcm9jZXNzaW5nLCByaWdodD8gSXQgc2VlbXMgdGhpcw0KaXMg
YWJvdmUgR0lTVA0KDQpNYXJ0aW46IG1pZ2h0IG5vdCBiZSBuZWVkZWQgd2l0aCB0aGUgTkFUL0ZX
DQoNCkVsd3luIERhdmlzOiBwcm9iYWJseSB3ZSBkb24ndCBjYXJlIG9mIGl0Lg0KDQpSb2JlcnQ6
IE1ldGVyaW5nIHNob3VsZCB0aGluayBhYm91dCB0aGlzPw0KDQpUaGUgcm9vbSBzaG93ZWQgc3Vw
cG9ydCBmb3IgdGhpcy4NCg0KSm9obiB3aWxsIG1ha2UgdGhpcyBhIHByb3Zpc2lvbmFsIFdHIGl0
ZW0sIGxhdGVyDQooeWV0LCB0aGUgcHJvcG9zZWQgZXh0ZW5zaW9uIHRvIHRoZSBCT1VORF9TRVNT
SU9OX0lEIG9iamVjdCBpbiBRb1MNCk5TTFAgd2lsbCBiZSBhY2NlcHRlZCkNCg0KDQoNCkFBQSBz
dXBwb3J0IGZvciBRb1Mgc2lnbmFsaW5nIC0gSGFubmVzIFRzY2hvZmVuaWcgLSAxMCBtaW4NCmh0
dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWFsZmFuby1hYWEtcW9zcHJv
dC0wNS50eHQNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LXRzY2hv
ZmVuaWctcmFkZXh0LXFvcy0wMi50eHQgIA0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpTbGlkZXMgYXJlIGF2
YWlsYWJsZSBhdDoNCmh0dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRl
cy9uc2lzLTEwLnBwdA0KDQoNCkhhbm5lcyBtZW50aW9uZWQgdGhlIHByZXZpb3VzIGRlcGVuZGVu
Y3kgb24gdGhlIHVzYWdlIG9mIGFjY291bnRpbmcgbWVzc2FnZXMuIA0KQmFzZWQgb24gY29tbWVu
dHMgdGhpcyBkZXBlbmRlbmN5IHdhcyByZWxheGVkLiANCiAgICAgICANCkpvaG4gbWVudGlvbnMg
dGhhdCB0aGUgZHJhZnQgbmVlZHMgdG8gYmUgdmVyeSBmbGV4aWJsZSB0byBzdXBwb3J0IHRoZSBm
dWxsIHJhbmdlIA0Kb2YgdXNhZ2Ugc2NlbmFyaW9zLiANCg0KTWFydGluOiB3b3VsZCBOQVQvRlcg
bmVlZCB0aGlzLCB0b28/IA0KDQoNCk1ldGVyaW5nIE5TTFAgLSBKdXJnZW4gUXVpdHRlay0gMTAg
bWluDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1mZXNzaS1uc2lz
LW0tbnNscC1mcmFtZXdvcmstMDIudHh0DQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1kcmVzc2xlci1uc2lzLW1ldGVyaW5nLW5zbHAtMDMudHh0DQotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dzMuaWV0Zi5v
cmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xpZGVzL25zaXMtMTEucHB0DQogDQoNCkpvaG46IElQRklY
IGFuZCBQU0FNUDogaG93IG11Y2ggYXJlIHRoZXkgbG9va2luZyBmb3J3YXJkIHRvIHRoaXM/DQoN
Ckp1ZXJnZW46IGRvbid0IGtub3csIHlldA0KDQoNCkRlc2lnbiBPcHRpb25zIG9mIE5TSVMgRGlh
Z25vc3RpY3MgTlNMUCAtIFhpYW9taW5nIEZ1IC0gMTAgbWluDQpodHRwOi8vdXNlci5pbmZvcm1h
dGlrLnVuaS1nb2V0dGluZ2VuLmRlL35mdS9uc2lzL2RpYWdub3N0aWNzL2RyYWZ0LWZ1LW5zaXMt
ZGlhZ25vc3RpY3MtbnNscC0wMC50eHQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQpTbGlkZXMgYXJlIGF2YWlsYWJsZSBhdDoNCmh0dHA6Ly93d3czLmlldGYu
b3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRlcy9uc2lzLTEyLnBwdA0KDQpSb2JlcnQ6IGlzIHRo
aXMgbmV0d29yayBtYW5hZ2VtZW50IChpZS4gcmVhZGluZyBNSUJzKSBvciBkaWFnbm9zdGljcz8g
aG93IGlzIHRoaXMgZGlmZmVyZW50IGZyb20gbmV0d29yayBtYW5hZ2VtZW50IHdpdGgsIGUuZy4g
U05NUCBhbmQgbmV0d29yayBtYW5hZ2VtZW50IHRvb2xzDQoNCkpvaG46IJNJIGFtIG5vdCBzdXJl
IGlmIEkgd2FudCBHSVNUL05TTFAgdG8gYmVjb21lIJN5ZXQgYW5vdGhlciBuZXR3b3JrIG1hbmFn
ZW1lbnQgdG9vbJQuDQoNCkhhbm5lczogdGhpcyBpcyBmaW5lIGxpbmUsIG5lZWQgdG8gdGhpbmsg
aG93IGZhciB5b3Ugd291bGQgbGlrZSB0byBnbw0KICBpbiB0aGlzLCBzb21lIHNjZW5hcmlvcyBj
b3VsZCBmZWVsIG1vcmUgbGlrZSBuZXR3b3JrIG1hbmFnZW1lbnQuIG9uZSBvZiB0aGUgcXVlc3Rp
b24gaXMgYWJvdXQgaG93IGZhciB5b3Ugd2FudCB0byBnby4NCg0KRWx3eW4gRGF2aXM6IG1vdGl2
YXRpb24gdG8gZ28gZm9yIGNvbXBsaWNhdGVkIGZ1bmN0aW9ucyB3YXMgdGhlIG5lZWQgdG8NCmZp
bmQgbm9kZXMgaW52b2x2ZWQsIHRoZW4geW91IGNhbiByZWFkIE1JQnMgdG8gZmluZCBvdXQgbW9y
ZSBpbmZvcm1hdGlvbi4uLg0KDQpYaWFvbWluZzogk29uZSBvZiB0aGUgb3B0aW9ucyBpcyB0byBk
ZWZpbmUgYSBNSUIgZm9yIEdJU1QgYW5kIHRoZSBOU0xQcy6UDQoNClJvYmVydDogk3lvdSBoYXZl
IHRvIGRlY2lkZSBvbiB3aGljaCBOU0xQIElEIHlvdSBzZW50IHRoZSBsaXN0IG9mIHN1cHBvcnRl
ZCBOU0xQIElEcy6UDQoNClhpYW9taW5nOiCTdGhpcyB3b3VsZCBydW4gb24gdGhlIEdJU1QgbGF5
ZXIsIGhvd2V2ZXIsIEdJU1QgZG9lcyBub3Qgc3VwcG9ydCBlbmQtdG8tZW5kIHNlbWFudGljc5Qu
DQoNClJvYmVydDogk4UgaXQgc2VlbXMgdGhpcyB3aWxsIGJlIGEgbmV3IE5TTFAgd2l0aCBhIG5l
dyBOU0xQIElELpQNCg0KSm9objogk3Blb3BsZSBwcm9iYWJseSBoYXZlIG5vdCByZWFkIGl0OyBv
bmNlIHRoZXkgZG8sIGNvbW1lbnQgb24gdGhlIG1haWxpbmcgbGlzdC6UDQoNCg0KVEhVUlNEQVks
IE5vdmVtYmVyIDEwLCAyMDA1DQoxNTEwLTE2MTAgQWZ0ZXJub29uIFNlc3Npb24gSUkNClRTViAg
ICAgbnNpcyAgICAgIE5leHQgU3RlcHMgaW4gU2lnbmFsaW5nIFdHDQoNClFvUy1OU0xQIC0gSnVr
a2EgTWFubmVyIC0gMTUgbWluDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1pZXRmLW5zaXMtcW9zLW5zbHAtMDgudHh0DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUg
YXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xp
ZGVzL25zaXMtMTMucHB0DQoNClJlZ2FyZGluZyB0aGUgcG9saWN5IGRhdGEgb2JqZWN0IEhhbm5l
cyBtZW50aW9ucyB0aGUgZGlmZmljdWx0eSBkZXNjcmliaW5nIHRoZSBpbnRlcmFjdGlvbiANCmJl
dHdlZW4gdGhlIGludm9sdmVkIHByb3RvY29scyBpbiBhbGwgc2NlbmFyaW9zLiBIZSB3b3JrZWQg
b24gYSBkb2N1bWVudCB0aGF0IHdpbGwgYmUgcHVibGlzaGVkDQpzb29uLiANCg0KSm9objogZG9l
cyBpdCBtYWtlcyBzZW5zZSB0byBob2xkIHVwIHRoaXMgZG9jdW1lbnQ/DQoNCkp1a2thOiBJIHBy
b3Bvc2Ugd2hhdCB0aGUgUlNWUCBzcGVjIHNheXMuIFBvbGljeSBvYmplY3QgY2FuIGJlIGRlZmlu
ZWQgaW4gbmV3IGRyYWZ0Lg0KDQpKb2huOiBpcyB0aGlzIGdvb2Qgb3IgYmFkPw0KDQpIYW5uZXM6
IHVzYWdlIG9mIHRoZSB0b2tlbiBpcyBmaW5lLiBPbiB0aGUgbG93ZXIgbGF5ZXIgd2UgaGF2ZSB0
aGUgaW5mb3JtYXRpb24gYWJvdXQgYXV0aGVudGljYXRlZCBpZGVudGl0aWVzhSB0aGVyZSBpcyBz
b21ldGhpbmcgbWlzc2luZywgSSB0aGluayBob3dldmVyIGl0IHNob3VsZCBub3Qgc3RvcCB0aGUg
cHJvZ3Jlc3Mgb2YgdGhpcyBkb2N1bWVudC4gSXQgaGFzIHRvIGRvIHdpdGggdGhlIGF1dGhlbnRp
Y2F0aW9uIG9mIHRoZSBxb3MgcmVxdWVzdCB0byBhIHRoaXJkIHBhcnR5Lg0KDQpKb2huOiBJIHN1
Z2dlc3QgdGhlbiB3ZSBkbyB3aGF0IHJzdnAgZG9lcyBhbmQgY2xvc2UgdGhpcyBpc3N1ZS4NCg0K
Um9iZXJ0IGFib3V0IHBhY2tldCBjbGFzc2lmaWVyczogSSB3b3VsZCBsaWtlIG9uZSBjbGFzc2lm
aWVyIGFjcm9zcyBOU0xQcy4gSSBkb26SdCB0aGluayB0aGF0IHlvdSBuZWVkIGFueXRoaW5nIG1v
cmUuDQoNCkp1a2thknMgcHJvcG9zYWw6IGRvIG5vdGhpbmcgZm9yIHRoZSB0aW1lIGJlaW5nLg0K
DQoNClFTUEVDIEktRCAtIEplcnJ5IEFzaCAtIDEwIG1pbg0KaHR0cDovL3d3dy5pZXRmLm9yZy9p
bnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1uc2lzLXFzcGVjLTA3LnR4dA0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpT
bGlkZXMgYXJlIGF2YWlsYWJsZSBhdDoNCmh0dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdz
LzA1bm92L3NsaWRlcy9uc2lzLTE0LnBwdA0KDQpubyBjb21tZW50cw0KDQpZLjE1NDEtUU9TTSBJ
LUQgLSBKZXJyeSBBc2ggLSA1IG1pbg0KaHR0cDovL2lldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1pZXRmLW5zaXMteTE1NDEtcW9zbS0wMC50eHQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUg
YXZhaWxhYmxlIGF0Og0KaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xp
ZGVzL25zaXMtMTUucHB0DQoNCm5vIGNvbW1lbnRzDQoNClVzZXIgQXBwbGljYXRpb24tdG8tVXNl
ciBQbGFuZSBWZXJ0aWNhbCBJbnRlcmZhY2UgLSBKZXJyeSBBc2ggLSA1IG1pbg0KaHR0cDovL2ll
dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1hc2gtbnNpcy12ZXJ0aWNhbC1pbnRlcmZhY2Ut
MDEudHh0DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRw
Oi8vd3d3My5pZXRmLm9yZy9wcm9jZWVkaW5ncy8wNW5vdi9zbGlkZXMvbnNpcy0xNi5wcHQNCg0K
QWxzbyBwcmVzZW50cyB1c2VyIGFwcGxjYWl0aW9uIHRvIHVzZXIgcGxhbmUgdmVydGljYWwgaW50
ZXJmYWNlDQoNClByb3Bvc2FsIHRvIGJlY29tZSBXRyBkb2N1bWVudC4NCg0KVGF5bG9yOiBpcyB0
aGlzIHdoYXQgb3RoZXIgcGVvcGxlIHdvdWxkIGNsYXNzaWZ5IGFzIHRoZSBHcSBpbnRlcmZhY2U/
DQoNCkhhbm5lczogdGhhdJJzIGFuIGludGVyZXN0aW5nIHF1ZXN0aW9uLg0KDQpIYW5uZXM6IGl0
IHNob3VsZCBub3QgYmVjb21lIGEgV0cgaXRlbTsgaWYgaXQgZG9lcywgSSB0b3RhbGx5IG1pc3Vu
ZGVyc3Rvb2QgdGhlIGRvY3VtZW50LiANCg0KSm9obiBlbmNvdXJhZ2VzIHBlb3BsZSB0byByZWFk
IHRoZSBkcmFmdCBhZ2FpbiB0byBtYWtlIHN1cmUgZXZlcnlvbmUgYWdyZWVzIGFib3V0IHdoYXQg
dGhlIHB1cnBvc2Ugb2YgdGhlIGRvY3VtZW50IGlzLg0KDQoNCg0KDQpSTUQtUU9TTSAtIEF0dGls
YSBCYWRlciAtIDEwIG1pbg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtaWV0Zi1uc2lzLXJtZC0wNC50eHQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClNsaWRlcyBhcmUgYXZhaWxhYmxlIGF0
Og0KaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDVub3Yvc2xpZGVzL25zaXMtMTcu
cHB0DQoNCm5vIGNvbW1lbnRzDQoNCkF0dGlsYSBtZW50aW9ucyB0aGF0IHRoZSBkb2N1bWVudCBj
YW4gZ28gaW50byBsYXN0IGNhbGwgZWFybHkgbmV4dCB5ZWFyLiANCg0KM0dQUC1RT1NNIC0gMTAg
bWluDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9uZy1uc2lz
LTNncHAtcW9zbS0wMi50eHQNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpTbGlkZXMgYXJlIGF2YWlsYWJsZSBh
dDoNCmh0dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdzLzA1bm92L3NsaWRlcy9uc2lzLTE4
LnBwdA0KDQpubyBjb21tZW50cw0KDQpKb2huOiB3aGF0IGFib3V0IHRoZSCTb3RoZXIgd2lyZWxl
c3MgbmV0d29ya3OUPyBtYXliZSB3ZSBjYW4gaGF2ZSBzdHVmZiAocGFyYW1ldGVycykgdGhhdCBy
ZWxhdGVzIHRvIHRob3NlIGluIGEgc2VwYXJhdGUgZG9jdW1lbnQuDQoNCkpvaG46IGNvbW1lbnQg
ZnJvbSBwYXJpczogZ3NtYSBoYXMgdGFrZW4gb3ZlciBzb21lIHJlc3BvbnNpYmlsaXR5IGZvciBt
YXBwaW5nIHFvcyBwYXJhbWV0ZXJzIHRvIGRpZmZzZXJ2IHN0dWZmLiANCg0KSm9objogaXMgM2dw
cCBpcyBkb2luZyBhbnl0aGluZyB3aXRoIHRoaXMgYXQgdGhlIG1vbWVudC4NCg0KU3BlYWtlcjog
aW50ZXJ3b3JraW5nIGlzIGFuIGlzc3VlLiBJdCBpcyBpbnRlcmVzdGluZyB0byBuc2lzIHBlb3Bs
ZS4gM2dwcCBhcmUgd2FpdGluZyBmb3IgbnNpcyBwcm9ncmVzcy4NCg0KDQpBIFFvUyBNb2RlbCBm
b3IgU2lnbmFsaW5nIEludFNlcnYgQ29udHJvbGxlZC1Mb2FkIFNlcnZpY2UgLSBYLiBGdSAtIDUg
bWluDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1rYXBwbGVyLW5z
aXMtcW9zbW9kZWwtY29udHJvbGxlZGxvYWQtMDMgDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3My5pZXRmLm9yZy9wcm9jZWVk
aW5ncy8wNW5vdi9zbGlkZXMvbnNpcy0xOS5wcHQNCg0Kbm8gY29tbWVudHMNCg0KDQpOQVQgdHJh
dmVyc2FsIGZvciBHSVNUDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvd2cvbnNpcy9kcmFmdC1wYXNo
YWxpZGlzLW5zaXMtZ2ltcHMtbmF0dHJhdmVyc2FsLTAxLnR4dA0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCg0KU2xpZGVzIGFyZSBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3My5pZXRmLm9yZy9wcm9j
ZWVkaW5ncy8wNW5vdi9zbGlkZXMvbnNpcy0yMC5wcHQNCg0KUm9iZXJ0OiBJdCB3b3VsZCBiZSBn
b29kIHRvIGV2YWx1YXRlIGhvdyBNSURDT00gcHJvdG9jb2xzIChTVFVOLCBldGMpIHJlbGF0ZSB0
byB0aGUgYXBwcm9hY2gsIGFuZCBhbHNvIHdoYXQgc29ydCBvZiBwb2xpY3kgZGVjaXNpb25zIGFy
ZSBpbnZvbHZlZCB3aGVuIE5BVHMgYWxsb2NhdGUgTkFUIGJpbmRpbmdzIGZvciBkYXRhIHRyYWZm
aWMuDQoNCg0KDQoNCg==

------_=_NextPart_001_01C5FCF1.5332EA32
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

------_=_NextPart_001_01C5FCF1.5332EA32--




From nsis-bounces@ietf.org Mon Dec 12 05:42:32 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ell8a-0004uJ-Fa; Mon, 12 Dec 2005 05:42:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ell8Z-0004tS-9Y
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 05:42:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01898
	for <nsis@ietf.org>; Mon, 12 Dec 2005 05:41:24 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ell9A-0006SF-Qy
	for nsis@ietf.org; Mon, 12 Dec 2005 05:43:10 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	7BD275B8B0 for <nsis@ietf.org>; Mon, 12 Dec 2005 11:42:11 +0100 (CET)
Received: from [134.76.81.226] (p5484BEDA.dip0.t-ipconnect.de [84.132.190.218])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP
	for <nsis@ietf.org>; Mon, 12 Dec 2005 11:42:11 +0100 (CET)
Message-ID: <439D53F6.5050401@cs.uni-goettingen.de>
Date: Mon, 12 Dec 2005 11:41:58 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [NSIS] QoS-NSLP Message format
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

I've got a question about the QSPEC field in a RESERVE, QUERY, RESPONSE and NOTIFY 
message. It has the form '*2QSPEC'. Does this mean that a message can contain two 
QSPEC objects at the most, e.g. end-to-end and local QSPEC?

Thanks,
Bernd

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 05:50:47 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EllGZ-0007Bc-Qo; Mon, 12 Dec 2005 05:50:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EllGY-00079q-Mb
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 05:50:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03123
	for <nsis@ietf.org>; Mon, 12 Dec 2005 05:49:49 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EllHH-0006oC-S6
	for nsis@ietf.org; Mon, 12 Dec 2005 05:51:35 -0500
Received: from wrl-40.cs.helsinki.fi (wrl-40.cs.helsinki.fi [128.214.166.160])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Mon, 12 Dec 2005 12:50:38 +0200
	id 00070241.439D55FE.000020EA
Date: Mon, 12 Dec 2005 12:50:38 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
Subject: Re: [NSIS] QoS-NSLP Message format
In-Reply-To: <439D53F6.5050401@cs.uni-goettingen.de>
Message-ID: <Pine.LNX.4.58.0512121250090.11659@wrl-40.cs.helsinki.fi>
References: <439D53F6.5050401@cs.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi Bernd,

Quick answer: Yes.

Cheers,
Jukka

On Mon, 12 Dec 2005, Bernd Schloer wrote:

> Hi,
> 
> I've got a question about the QSPEC field in a RESERVE, QUERY, RESPONSE and
> NOTIFY message. It has the form '*2QSPEC'. Does this mean that a message can
> contain two QSPEC objects at the most, e.g. end-to-end and local QSPEC?
> 
> Thanks,
> Bernd
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 07:35:38 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Elmu2-0001z8-H8; Mon, 12 Dec 2005 07:35:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Elmtv-0001vV-9P; Mon, 12 Dec 2005 07:35:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15258;
	Mon, 12 Dec 2005 07:34:25 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ElmuW-0001zJ-Tv; Mon, 12 Dec 2005 07:36:10 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBCCVaoS000377; Mon, 12 Dec 2005 14:31:37 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 14:35:09 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 14:35:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN re-markingwhen
	DSCPre-markingcan do it
Date: Mon, 12 Dec 2005 14:35:08 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEBF8@esebe100.NOE.Nokia.com>
In-Reply-To: <F005CD411D18D3119C8F00508B087480139F4A2B@ehubunt100.eth.ericsson.se>
Thread-Topic: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN re-markingwhen
	DSCPre-markingcan do it
Thread-Index: AcXxV5l9yovCkXiBT8qKRKPVyhRjUAJxQmbwAP7bX5A=
To: <attila.bader@ericsson.com>, <rbriscoe@jungle.bt.co.uk>
X-OriginalArrivalTime: 12 Dec 2005 12:35:09.0782 (UTC)
	FILETIME=[7D624F60:01C5FF18]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ca81a19b939ce054f98c8f830c2d7742
Content-Transfer-Encoding: quoted-printable
Cc: philip.eardley@bt.com, karagian@cs.utwente.nl, nsis@ietf.org,
	tsvwg@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Bob (& by extension the TSVWG WG),

I'm still left feeling like we don't have consensus around the issues =
out-lined
in your mail in the tsvwg community, even outside of RMD issues. =20

I'm wondering if we should start trying to find somethings that we could =
get
consensus on and then see what to do about the other issues.  Many of =
the points
are still experimental (in the TSVWG sense of experimental), so I'm =
wondering
what the next steps should be.

thanks,
John

>-----Original Message-----
>From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
>Behalf Of ext Attila B=E1der (IJ/ETH)
>Sent: 08 December, 2005 16:02
>To: Bob Briscoe
>Cc: philip.eardley@bt.com; Georgios Karagiannis;=20
>tsvwg@ietf.org; nsis@ietf.org
>Subject: RE: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN=20
>re-markingwhen DSCPre-markingcan do it
>
>Hi Bob, Thank you for your answer, please see my comments below.
>
>Best regards, Attila
>
>> -----Original Message-----
>> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org]
>> Sent: Thursday, November 24, 2005 6:41 PM
>> To: Georgios Karagiannis
>> Cc: philip.eardley@bt.com; tsvwg@ietf.org; nsis@ietf.org
>> Subject: Re: [NSIS] Re: [Tsvwg] why use edge-to-edge ECN=20
>> re-markingwhen DSCP re-markingcan do it
>>=20
>>=20
>> Georgios,
>>=20
>> (long e-mail)
>>=20
>> We thought long and hard about which re-marking to use. My primary=20
>> concern was to keep the Internet architecture consistent,=20
>which leads=20
>> to the arguments below.
>>=20
>> 1/ Intended semantics of the Internet Architecture=20
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>>=20
>> 1.1/ Intended re-marking semantics of Diffserv & ECN
>> --------------------------------------------------
>> Diffserv re-marking was defined for two reasons:
>>      i) To allow the ingress of a Diffserv domain to prevent traffic=20
>> in excess of the contracted rate/burstiness from being given=20
>> favourable treatment at downstream routers if they became congested=20
>> themselves.
>>      ii) To allow a border router to map the DSCP used for a per-hop=20
>> behaviour in the upstream domain to that used for the same=20
>PHB in the=20
>> downstream domain.
>>=20
>> ECN re-marking is used by a node to indicate that the node itself is=20
>> approaching congestion. The intent is to reduce the load from the=20
>> source, but marking is forwarded downstream in the=20
>expectation that it=20
>> will be fed back to the source.
>>=20
>>      Thus, the intent of Diffserv re-marking is to alter the=20
>> downstream per hop forwarding behaviour if necessary. Diffserv=20
>> re-marking was not intended to be fed back to the source.
>>      The intent of ECN re-marking is to reduce the load at source=20
>> through feedback. ECN re-marking was specifically not intended to=20
>> alter the downstream forwarding behaviour of re-marked packets.
>>=20
>> That's the idealistic view. In practice, it can be convenient to =
break=20
>> architecture. But architecture is there to warn you to think long and =

>> hard when you depart from it, so you are aware of what you=20
>might break=20
>> in the future.
>>=20
>
>I agree that this would be an idealistic picture. Note that=20
>you would like to use ECN for Admission Control. Diffserv is=20
>used also for admission control so there is an overlap between=20
>ECN and Diffserv. In the meantime ECN was defined for=20
>end-to-end congestion control of elastic traffic type that=20
>makes things complicate. While there is no such limitation to=20
>use remaining Diffserv codepoints for congestion notification=20
>edge-to-edge.
>
>> 1.2/ Was ECN at the IP layer intended to have end-to-end semantics?
>> -------------------------------------------------------------------
>> RFC3168 was written so that the ECN semantics in IP could be =
separated=20
>> from the end-to-end ECN semantics of TCP when other ECN transports=20
>> were defined.
>>=20
>> [According to Sally Floyd at the time, the main reason for specifying =

>> ECN for TCP & IP together in the same RFC was to encourage the first=20
>> experiments with ECN to be in TCP implementations which tend to be=20
>> written with a lot more care by a few kernel experts.]
>>=20
>> Indeed, Jon Crowcroft and I wrote an I-D reviewing the ECN I-D before =

>> it became RFC3168. In section 12, we proposed text on ECN semantics=20
>> for proxies (edge-to-edge), asking that it be added to the ECN RFC:
>> <http://www.cs.ucl.ac.uk/staff/B.Briscoe/pubs.html#ECN-IP> (Expired)
>>=20
>> Sally Floyd's response (off-line) at the time is quoted here:
>>=20
>> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>> /\/\/\/\/\/\/\/
>> At 11:35 21/02/01 -0800, Sally Floyd wrote:
>>  >Feedback on Section 12, proposing rules for allowing proxies in the =
=20
>> >network to change ECN codepoints:
>>  >
>>  >I think that this is complicated, and has to be dealt with in a =20
>> >separate document, in context.  That is, when people have specific =20
>> >proposals for intermediate nodes to modify the ECN field,  >then I=20
>> think they have to be addressed at that time.  My own opinion  >is=20
>> that making general rules ahead of time, in the abstract,  >such as=20
>> "we will now propose rules for changing the ECN  >capability of a=20
>> packet at intermediate nodes", never gets it right.
>> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>> /\/\/\/\/\/\/\/
>>=20
>> <draft-briscoe-tsvwg-cl-architecture-01.txt> is exactly that. A =
separate
>> document about the semantics of ECN proxies, in this case with a flow =

>> signalling transport like RSVP (or NSIS).
>>=20
>> The idea of RMD and of
>> <draft-briscoe-tsvwg-cl-architecture-01.txt> is for the node at the=20
>> end of a long signalling 'hop' (a whole Diffserv region) to see how=20
>> much congestion has accumulated since the start of the region.
>> Potentially there may be other signalling 'hops' further downstream=20
>> using the same technique again. So the egress of one signalling hop=20
>> must tidy things up by folding any re-marked packets back in to the=20
>> same marking as un-re-marked packets, to avoid confusing further=20
>> region(s) downstream if they are using the same technique.
>>=20
>> [For instance, you are thinking of RMD being used for admission=20
>> control across a radio access network. But there may be another RAN =
at=20
>> the other end of the network using the same technique. So you must=20
>> ensure any re-marked DSCPs are folded back into the same DSCP as=20
>> non-re-marked packets at the RMD egress. ]
>>=20
>
>Yes, I agree that Egress edge should restore the orig. DSCP,=20
>otherwise there can be multiple actions for the same event. It=20
>may not be restored if there is agreement between domains that=20
>a downsteram domain handles the problem.=20
>
>> 1.3/ Summary of architectural concerns
>> --------------------------------------
>> To indicate the need for admission control, it is certainly more=20
>> convenient to do Diffserv re-marking as RMD does, but I believe it is =

>> more architecturally consistent to use ECN re-marking, as we do.
>>=20
>> However, architecture is like religion. You can break it, if it=20
>> becomes too inconvenient, and if you can convince enough people you=20
>> have a good excuse.
>>=20
>> 2. Practical issues
>> -------------------
>> I don't think we need to break the architecture in this case=20
>(which is=20
>> why we use ECN), but using ECN re-marking edge-edge does raise the=20
>> following issue...
>>=20
>> 2.1/ Edge-to-edge ECN conflicts with end-to-end ECN
>> ---------------------------------------------------
>> We fully understand that use of ECN re-marking to trigger admission=20
>> control within Diffserv regions would conflict with end-to-end ECN=20
>> congestion control for the *same* flow. But we deliberately chose to=20
>> specify the end to end service we were providing as "controlled load=20
>> [RFC2211]" to try to preclude such cases.
>>=20
>> RFC 2211 says:
>>=20
>> "  ...
>> 2. End-to-End Behavior
>>     ...                              Should the client's traffic
>>     generation properties fall outside of the region described by the
>>     TSpec parameters, the QoS provided to the client may exhibit
>>     characteristics indicative of overload, including large=20
>numbers of
>>     delayed or dropped packets.
>>=20
>>     ...
>>=20
>> 7. Policing
>>     ...                                  the network element=20
>> MUST attempt
>>       to forward the excess traffic on a best-effort basis if=20
>> sufficient
>>       resources are available
>>=20
>>     ...
>>=20
>>     Beyond requirements 2 and 3 above, the controlled-load service=20
>> does
>>     not define the QoS behavior delivered to flows with=20
>non-conformant
>>     arriving traffic.  Specifically, it is permissible either to=20
>> degrade
>>     the service delivered to all of the flow's packets equally, or to
>>     sort the flow's packets into a conformant set and a=20
>nonconformant=20
>> set
>>     and deliver different levels of service to the two sets.
>>=20
>>     ...
>>=20
>> 9. Guidelines for Implementors
>>=20
>>     ...
>> If most controlled-load traffic arises from rate-adaptive
>>     realtime or elastic applications attempting to establish=20
>a bounded
>>     minimum level of service, the use of separate resource classes=20
>> might
>>     be preferable.
>>=20
>> "
>> I won't paste everything RF2211 says on with advice for implementors=20
>> on scheduling elastic flows with a bounded minimum, as=20
>there's rather=20
>> a lot.
>> But basically, you get unavoidably bad re-ordering and other=20
>> complications that make it hard. Even though this seems a desirable=20
>> service, it's unlikely to work well in practice.
>>=20
>> 2.2/ End-to-end ECN conflicts with edge-to-edge admission control
>> -----------------------------------------------------------------
>> The congestion-based admission control mechanism used in RMD and in=20
>> our <draft-briscoe-tsvwg-cl-architecture-01.txt> would break if a=20
>> significant proportion of admitted traffic were adaptive. If=20
>> congestion on an interior path were close to the threshold where=20
>> admission control was needed, adaptive traffic might=20
>temporarily drop=20
>> well below its minimum bound. More flows might then be=20
>accepted, then=20
>> the adaptive traffic could grow again, destroying the=20
>controlled load=20
>> service for all flows through that path.
>>=20
>> [Note: Variable bit rate (VBR) like video traffic would superfically=20
>> seem to break a measurement-based admission control system=20
>in the same=20
>> way as adaptive traffic. But unlike with adaptive traffic,=20
>troughs in=20
>> VBR load are not correlated with congestion. Our analyses of how the=20
>> effective bandwidth of VBR (and silence-suppressed voice) aggregates=20
>> has shown that our solution works OK for VBR, given specific=20
>> conditions on the amount of aggregation and provided VBR traffic=20
>> sources are not correlated. We are currently preparing this analysis=20
>> for publication.]
>>=20
>
>That study sounds interesting. I do not think that the=20
>congestion-based admission control is good enough for all=20
>networks. Meas. based methods certainly have limitations,=20
>especially in access network, as you also mention in your=20
>draft. In RMD edge nodes are statefull nodes. I think that=20
>unit-based aggregated reservation in core combined with=20
>per-flow schedulers in edges can provide an Intserv-like=20
>service in the domain as well.
>
>> 2.3/ Summary of end/edge conflicts
>> ----------------------------------
>> So, we prefer to say that a different service would have to be=20
>> requested to cater for your hybrid requirement. Hence my preference=20
>> for explicitly requesting "adaptive rate control with a bounded=20
>> minimum" in the signalling, as a different QoS service. In=20
>NSIS terms,=20
>> this is would be in the QSPEC, I believe.
>>
>
>I think this traffic should use controlled load service. Or=20
>define a new QoS model.
>
>> 2.4/ Codepoint space
>> --------------------
>> Real-estate in the IP header is at a premium. Treating the 6-bit=20
>> Diffserv field and the 2-bit ECN field separately leads to=20
>2^6 + 2^2 =3D=20
>> 68 codepoints. Treating them together leads to 2^8 =3D 256 =
codepoints.=20
>> In the MPLS EXP field, real-estate is a far greater headache.
>>=20
>> If ECN marking is orthogonal to Diffserv marking for most Diffserv=20
>> codepoints, it makes sense to treate the field as 6-bit and 2-bit=20
>> sub-fields. But I don't believe we should be averse to bending the=20
>> rules to save codepoint space across both fields.
>>=20
>> For instance both our approach and RMD need another marking=20
>state for=20
>> a router in the Diffserv interior to indicate the need for flow=20
>> pre-emption (eg. after re-routes). Pre-emption represents severe=20
>> congestion and needs to be fed back upstream. So by my=20
>arguments above=20
>> pre-emption should be re-marked using the ECN field. But in our=20
>> current pre-emption solution, if two or more nodes in a path require=20
>> some flows to be pre-empted, packets that have already been=20
>re-marked=20
>> once to indicate pre-emption need to be treated differently by=20
>> downstream nodes. So by my arguments above pre-emption=20
>should also be=20
>> re-marked using the DSCP.
>>=20
>> Well, it would be silly to waste two codepoints for one state. And=20
>> there aren't enough ECN codepoints anyway. So, IMHO, you have to be=20
>> pragmatic and be willing to re-mark the Diffserv codepoint for=20
>> pre-emption
>> (CAVEAT: the
>> authors of <draft-briscoe-tsvwg-cl-architecture-01.txt>=20
>still haven't=20
>> reached consensus on marking - that's why=20
>> <draft-briscoe-tsvwg-cl-phb-00.txt> hasn't been updated yet).
>
>We think that both DSCP and ECN remarking could be used for=20
>congestion notification admission control and severe=20
>congestion [pre-emption] with limitation.=20
>
>>=20
>> 7/ Consistent meaning of an ECN marking
>> ---------------------------------------
>> I hope I have answered your question about why we use ECN=20
>not Diffserv=20
>> re-marking. We are not completely inflexible about using=20
>ECN, but I do=20
>> have further reasons for preferring ECN re-marking---to do with the=20
>> economic interpretation of congestion marking across different=20
>> classes. It would take too long to go into that here, but=20
>you can read=20
>> a recent paper I published on the subject if interested.
>>=20
>> Commercial Models for IP Quality of Service Interconnect,=20
>Bob Briscoe=20
>> & Steve Rudkin (BT), in BTTJ Special Edition on IP Quality=20
>of Service,=20
>> 23(2) (Apr 2005)=20
>> <http://www.cs.ucl.ac.uk/staff/B.Briscoe/pubs.html#ixqos>
>>=20
>> I have also given responses inline...
>>=20
>> At 09:28 24/11/2005, Georgios Karagiannis wrote:
>> >----- Original Message ----- From: <philip.eardley@bt.com>
>> >To: <philip.eardley@bt.com>; <karagian@cs.utwente.nl>
>> >Cc: <tsvwg@ietf.org>; <nsis@ietf.org>
>> >Sent: Thursday, November 24, 2005 1:23 AM
>> >Subject: RE: [Tsvwg] why use edge-to-edge ECN re-marking when DSCP=20
>> >re-markingcan do it
>> >
>> >
>> >>>>[GK] What is the technical reason of using ECN for edge-toedge=20
>> >>>>congestion control?
>> >>[PE] The use of Ecn seems natural to me, since we wnat the
>> network to
>> >>indicate incipient congestion and that's what ECN is
>> supposed to do. Note
>> >>that the semantics are the same as rfc3168 (ECN) - ie same
>> codepoints of
>> >>ECN field and CE codepoint indicates incipient congestion.=20
>> I also think
>> >>it can help with migration to a fully ecn world. As operators get=20
>> >>experience of using ecn, whilst not requiring all nws / end
>> hosts to be
>> >>using it.
>> >
>> >Georgios: yes I understand but the ECN semantics apply
>> end-to-end, not
>> >edge-toedge,
>> >please see the previous discussions on this issue!
>>=20
>> [BB] ECN semantics were originally defined for an end-to-end=20
>protocol=20
>> (TCP). That does not imply they were only intended to ever be=20
>> end-to-end.
>> RFC3168 did not preclude edge-to-edge. And at least one of=20
>the authors=20
>> believed edge-to-edge semantics could be a valid thing to=20
>define later=20
>> (see quote from Sally Floyd above).
>>=20
>>=20
>>=20
>> >>[PE] Second, using DSCP re-marking seems to need a lot of DSCPs.=20
>> >>According to your draft, admission control implies 2 per
>> traffic class
>> >>(one for re-marked pkts, one for other pkts passing thru the same=20
>> >>router). Plus another for the severe congestion indication.
>> In addition,
>> >>in the core network an interesting future extension is to use the=20
>> >>mechanisms in a network with MPLS-TE (see our framework
>> draft for brief
>> >>discussion) - there isnt sufficient space in the label for
>> these extra dscps.
>> >
>> >Georgios: regarding the number of DSCP's you are right, but
>> there are ways
>> >of reducing this number, please see the RMD draft.
>> >Please also note that the streaming aplication example that=20
>has been=20
>> >discussed in the tsvwg and nsis mailing lists shows that it is=20
>> >usefull to use end-to-end ECN based congestion control for reserved=20
>> >traffic.
>> >This streaming application example can very efficiently use
>> RSVP and the
>> >DCCP protocol (which uses the end-to-end ECN concept).
>>=20
>> [BB] No-one on the list has said it would be efficient. In fact the=20
>> opposite has been said (by Louise Burness) and no-one has=20
>disagreed. I=20
>> believe this hybrid service should be set aside for someone else to=20
>> define a mechanism for later. Intserv couldn't even do it very well,=20
>> even though it had a per-flow scheduler.
>>=20
>>=20
>> >[GK] Please also note that the support of this type of this type of=20
>> >streaming application that combines the end to end ECN=20
>semantics with=20
>> >reserved minimum bandwidth is needed not only in the=20
>backbone network=20
>> >but also in the wireless network as well.
>> >Therefore the rate-adaptation function of ECN (DCCP functionality)=20
>> >combined with minimum bandwidth reservation can be very important.
>>=20
>> [BB] Yes, an adaptive application with a minimum rate would be a=20
>> desirable service. But it's not the one we are defining. And=20
>you will=20
>> find it doesn't work with RMD's congestion-based admission scheme=20
>> either.
>>=20
>> [BB] We are trying to do Controlled Load to scale to the=20
>Internet. We=20
>> don't know how to implement this hybrid at Internet scale.=20
>We have had=20
>> to limit our scope to avoid this hybrid problem. And you will find=20
>> that such a hybrid service wouldn't work with the mechanism you have=20
>> defined for RMD either.
>>=20
>> [BB] So I need to turn your question back on you: how would you=20
>> prevent adaptive applications using your RMD congestion=20
>mechanism, and=20
>> breaking the admission control system?
>>=20
>> [BB] The solution I have proposed is to require the application to=20
>> signal this hybrid requirement and if it is not signalled,=20
>to drop any=20
>> excess traffic at the region ingress in order to disincentivise any=20
>> adaptive application trying to use the wrong service for its needs.
>>=20
>>=20
>> >>Third, (as bob has pointed out) that it's easy to overcome
>> the end-to-end
>> >>vs edge-to-edge
>> >marking issue (if that's really needed, which I'm inclined
>> to think it isnt)
>> >
>> >Georgios: regarding this point I am not sure if it is easy!=20
>> It depends on the
>> >imposed additional complexity.
>>=20
>> [BB] If a request for this hybrid were signalled (and an operator=20
>> chose to support the hybrid service), with the current state of=20
>> knowledge, I would say that this hybrid traffic would have=20
>to be dealt=20
>> with by a less scalable means, such as Intserv per-flow=20
>schedulers on=20
>> every node, or your hop by hop reservation method in RMD.
>>=20
>>=20
>> Bob
>>=20
>> >Best regards,
>> >Georgios
>> >
>> >
>> >>
>> >>________________________________
>> >>
>> >>From: tsvwg-bounces@ietf.org on behalf of philip.eardley@bt.com
>> >>Sent: Wed 23/11/2005 23:48
>> >>To: karagian@cs.utwente.nl
>> >>Cc: tsvwg@ietf.org; nsis@ietf.org
>> >>Subject: Re: [Tsvwg] why use edge-to-edge ECN re-marking when DSCP=20
>> >>re-markingcan do it
>> >>
>> >>
>> >>
>> >>some comments below.
>> >>
>> >>best wishes, phil
>> >>
>> >>________________________________
>> >>
>> >>*       To: <rbriscoe at jungle.bt.co.uk=20
><mailto:rbriscoe@DOMAIN.HIDDEN> >
>>>*       Subject: [Tsvwg] why use edge-to-edge ECN re-marking=20
>when DSCP=20
>>>re-marking can do it
>>>*       From: "Georgios Karagiannis" <karagian at cs.utwente.nl=20
>>><mailto:karagian@DOMAIN.HIDDEN> >
>>>*       Date: Mon, 21 Nov 2005 10:52:22 +0100
>>>*       Cc: tsvwg at ietf.org <mailto:tsvwg@DOMAIN.HIDDEN> , nsis at=20
>>>ietf.org <mailto:nsis@DOMAIN.HIDDEN>
>>>
>>>Hi Bob
>>>
>>>In addition to the previous discussion I would like to=20
>discuss and ask=20
>>>you the following.
>>>
>>>[chop]
>>>What is the technical reason of using ECN for edge-toedge congestion=20
>>>control, when the same solution (on providing admission=20
>control based=20
>>>on congestion notification and severe congestion=20
>[pre-emption]) can be=20
>>>provided by using DSCP re-marking?
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>tsvwg mailing list
>>>tsvwg@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/tsvwg
>>>
>>
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>
>_______________________________________________________________
>_____________
>Bob Briscoe, <bob.briscoe@bt.com>      Networks Research=20
>Centre, BT Research
>B54/130 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.  =20
>+44 1473 645196 =20
>
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis
>

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 07:40:03 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElmyJ-0002Me-G3; Mon, 12 Dec 2005 07:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElmyF-0002Hz-Nf
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 07:40:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15963
	for <nsis@ietf.org>; Mon, 12 Dec 2005 07:38:55 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Elmyt-00029j-7I
	for nsis@ietf.org; Mon, 12 Dec 2005 07:40:40 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBCCdEBJ006202; Mon, 12 Dec 2005 14:39:15 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 14:39:39 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 14:39:39 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Update on the QoS NSLP work
Date: Mon, 12 Dec 2005 14:39:39 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEBFB@esebe100.NOE.Nokia.com>
In-Reply-To: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
Thread-Topic: [NSIS] Update on the QoS NSLP work
Thread-Index: AcX7XWe5AKUsRvxhSfiUh9b1xW8TUQDu5rhg
To: <jmanner@cs.Helsinki.FI>, <nsis@ietf.org>
X-OriginalArrivalTime: 12 Dec 2005 12:39:39.0771 (UTC)
	FILETIME=[1E4F5CB0:01C5FF19]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Jukka,

There's been quite a few comments on this current draft. I was thinking
that
a quick rev then a WGLC on this & the QSPEC draft in the new year might
be
a good way to start 2006.

Thoughts?
John=20

>-----Original Message-----
>From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
>Behalf Of ext Jukka MJ Manner
>Sent: 07 December, 2005 20:34
>To: nsis@ietf.org
>Subject: [NSIS] Update on the QoS NSLP work
>
>
>Hi all,
>
>Georgios, Andrew and I have worked on the QoS NSLP since the=20
>Vancouver meeting. The document is close to being finalized.=20
>The main issue left is a sanity check on whether and how=20
>mobility really works with the QoS NSLP.
>Apart from that, we should be done.
>
>A diff of the current version against -08 is available at:
>
>http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html
>
>All feedback is always appreciated.
>
>Regards,
>Jukka
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis
>

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:02:48 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElnKK-00083g-H2; Mon, 12 Dec 2005 08:02:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElnKH-000818-GC
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 08:02:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18661
	for <nsis@ietf.org>; Mon, 12 Dec 2005 08:01:49 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElnL4-00038H-CS
	for nsis@ietf.org; Mon, 12 Dec 2005 08:03:34 -0500
Received: from wrl-40.cs.helsinki.fi (wrl-40.cs.helsinki.fi [128.214.166.160])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Mon, 12 Dec 2005 15:02:42 +0200
	id 0007022C.439D74F2.00003F9E
Date: Mon, 12 Dec 2005 15:02:42 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: john.loughney@nokia.com
Subject: RE: [NSIS] Update on the QoS NSLP work
In-Reply-To: <1AA39B75171A7144A73216AED1D7478D6CEBFB@esebe100.NOE.Nokia.com>
Message-ID: <Pine.LNX.4.58.0512121457040.11659@wrl-40.cs.helsinki.fi>
References: <1AA39B75171A7144A73216AED1D7478D6CEBFB@esebe100.NOE.Nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi,

The comments from Roland are being dealt with as we speak, and Jerry had a
few simple comments about references. Has there been other comments?

I would like people to comment now on my current editor's version. I
could, e.g., submit an official new version next week, or after Christmas,
and we could start a WGLC in early January, sure.

Regards,
Jukka

On Mon, 12 Dec 2005 john.loughney@nokia.com wrote:

> Jukka,
> 
> There's been quite a few comments on this current draft. I was thinking
> that
> a quick rev then a WGLC on this & the QSPEC draft in the new year might
> be
> a good way to start 2006.
> 
> Thoughts?
> John 
> 
> >-----Original Message-----
> >From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
> >Behalf Of ext Jukka MJ Manner
> >Sent: 07 December, 2005 20:34
> >To: nsis@ietf.org
> >Subject: [NSIS] Update on the QoS NSLP work
> >
> >
> >Hi all,
> >
> >Georgios, Andrew and I have worked on the QoS NSLP since the 
> >Vancouver meeting. The document is close to being finalized. 
> >The main issue left is a sanity check on whether and how 
> >mobility really works with the QoS NSLP.
> >Apart from that, we should be done.
> >
> >A diff of the current version against -08 is available at:
> >
> >http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html
> >
> >All feedback is always appreciated.
> >
> >Regards,
> >Jukka
> >
> >_______________________________________________
> >nsis mailing list
> >nsis@ietf.org
> >https://www1.ietf.org/mailman/listinfo/nsis
> >
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:05:02 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElnMT-0008PI-Nv; Mon, 12 Dec 2005 08:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElYBY-0004G9-GD
	for nsis@megatron.ietf.org; Sun, 11 Dec 2005 15:52:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06522
	for <nsis@ietf.org>; Sun, 11 Dec 2005 15:51:37 -0500 (EST)
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElYC1-00047m-Gd
	for nsis@ietf.org; Sun, 11 Dec 2005 15:53:14 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Sun, 11 Dec 2005 15:52:19 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2005121115521203506 ; Sun, 11 Dec 2005 15:52:17 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <XLDBYP91>; Sun, 11 Dec 2005 15:52:09 -0500
Message-Id: <84E5D7F15F52D34DA84C9C90ACE6554F623383@0591-its-exmp01.us.saic.com>
From: "Roy, Radhika R." <royrr@us.saic.com>
To: john.loughney@nokia.com
Subject: RE: [NSIS] FW: nsis meeting minutes
Date: Sun, 11 Dec 2005 15:51:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-Mailman-Approved-At: Mon, 12 Dec 2005 08:05:00 -0500
Cc: gash@att.com, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi, John and all:
 
Minutes show no comments on the following draft: Y.1541-QOSM I-D - Jerry Ash
- 5 min
http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt
-----------------------------------------------------------------
"no comments"
 
However, we have comments on this as follows:

1.	

	This draft is INCOMPLETE with respect to extensions of QOSM
parameters for using Y.1541. For example, some extensions of QOSM parameters
for Y.1541 have been done in the QOSM draft and some extensions of QOSM
parameters have been done in this (Y.1541-QOSM I-D) draft. Why is it so?
2.	

	It is inconsistent that the generalized QOSM draft contains some
INCOMPLETE extensions for Y.1541-specific draft. Why is it so?
3.	

	Why does this draft (Y.1541-QOSM I-D) not contain all
Y.1541-specific extensions of QOSM parameters and make it complete per item
1? Is there any reason for not doing so?

Best regards,

Radhika



  _____  

From: nsis-bounces@ietf.org on behalf of john.loughney@nokia.com
Sent: Fri 12/9/2005 1:49 PM
To: nsis@ietf.org
Subject: [NSIS] FW: nsis meeting minutes



Hi all,

Minutes are attached, send comments & corrections.

John



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:06:56 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElnOK-0000Mx-C0; Mon, 12 Dec 2005 08:06:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElnOJ-0000Kf-4j
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 08:06:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19455
	for <nsis@ietf.org>; Mon, 12 Dec 2005 08:05:51 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElnOx-0003Lm-8M
	for nsis@ietf.org; Mon, 12 Dec 2005 08:07:36 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBCD6dZo013743; Mon, 12 Dec 2005 15:06:43 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 15:06:42 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 15:06:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Update on the QoS NSLP work
Date: Mon, 12 Dec 2005 15:06:20 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEC02@esebe100.NOE.Nokia.com>
In-Reply-To: <Pine.LNX.4.58.0512121457040.11659@wrl-40.cs.helsinki.fi>
Thread-Topic: [NSIS] Update on the QoS NSLP work
Thread-Index: AcX/HGDpXvy86PTOSdCFdYUzcL4mcAAAFOFg
To: <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 12 Dec 2005 13:06:42.0280 (UTC)
	FILETIME=[E5669680:01C5FF1C]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Jukka,

>The comments from Roland are being dealt with as we speak, and=20
>Jerry had a few simple comments about references. Has there=20
>been other comments?
>
>I would like people to comment now on my current editor's=20
>version. I could, e.g., submit an official new version next=20
>week, or after Christmas, and we could start a WGLC in early=20
>January, sure.

Sorry, drop the 'quite' and leave 'a few comments.' Anyhow,
if folks could send in comments, so that Jukka could do
an update in early January for WGLC.

thanks,
JOhn

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:17:02 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElnY6-0003p6-SQ; Mon, 12 Dec 2005 08:17:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElnY4-0003oK-La
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 08:17:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20702
	for <nsis@ietf.org>; Mon, 12 Dec 2005 08:15:57 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElnYj-0003jP-LN
	for nsis@ietf.org; Mon, 12 Dec 2005 08:17:43 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBCDDBFd011470; Mon, 12 Dec 2005 15:13:11 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 15:16:36 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 15:16:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] FW: nsis meeting minutes
Date: Mon, 12 Dec 2005 15:16:19 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CEC03@esebe100.NOE.Nokia.com>
In-Reply-To: <84E5D7F15F52D34DA84C9C90ACE6554F623383@0591-its-exmp01.us.saic.com>
Thread-Topic: [NSIS] FW: nsis meeting minutes
Thread-Index: AcX/HUhBXmarQzBcQd+GT2cNg51gwAAACgRQ
To: <royrr@us.saic.com>
X-OriginalArrivalTime: 12 Dec 2005 13:16:35.0755 (UTC)
	FILETIME=[4723AFB0:01C5FF1E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: quoted-printable
Cc: gash@att.com, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Radhika,

>Hi, John and all:
>=20
>Minutes show no comments on the following draft: Y.1541-QOSM I-D -
Jerry Ash
>- 5 min
>http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt
>-----------------------------------------------------------------
>"no comments"

At least I don't remember making any comments to this draft at the
meeting.

John=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:22:42 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Elnda-0005EX-JB; Mon, 12 Dec 2005 08:22:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ElndZ-0005EM-LX
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 08:22:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21252
	for <nsis@ietf.org>; Mon, 12 Dec 2005 08:21:37 -0500 (EST)
Received: from mail121.messagelabs.com ([216.82.241.195])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ElneA-0003vP-EN
	for nsis@ietf.org; Mon, 12 Dec 2005 08:23:23 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-8.tower-121.messagelabs.com!1134393721!8938856!9
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 2778 invoked from network); 12 Dec 2005 13:22:18 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-8.tower-121.messagelabs.com with SMTP;
	12 Dec 2005 13:22:18 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh3i.attrh.att.com (7.2.052)
	id 4389E74D001C8A59; Mon, 12 Dec 2005 08:22:17 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [NSIS] nsis meeting minutes
Date: Mon, 12 Dec 2005 07:22:16 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA977C@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: [NSIS] nsis meeting minutes
Thread-Index: AcX/HUhBXmarQzBcQd+GT2cNg51gwAAACgRQAAA/VEA=
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <john.loughney@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

John,

> > Minutes show no comments on the following draft: Y.1541-QOSM I-D -
> > Jerry Ash
> > - 5 min
> > http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt
> > -----------------------------------------------------------------
> > "no comments"

> At least I don't remember making any comments to this draft at the
> meeting.

You're right, there were no comments.  There was a brief discussion that
the I-D should go to WGLC after the QoS/NSLP & QSPEC WGLC.

Jerry

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 08:49:01 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Elo33-0003mo-Fa; Mon, 12 Dec 2005 08:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Elo31-0003mc-Ob
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 08:48:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24313
	for <nsis@ietf.org>; Mon, 12 Dec 2005 08:48:03 -0500 (EST)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Elo3o-0004yX-2h
	for nsis@ietf.org; Mon, 12 Dec 2005 08:49:49 -0500
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D51A27B3
	for <nsis@ietf.org>; Mon, 12 Dec 2005 14:48:49 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Dec 2005 14:48:49 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Mon, 12 Dec 2005 14:48:48 +0100
Message-ID: <F005CD411D18D3119C8F00508B08748014547324@ehubunt100.eth.ericsson.se>
Thread-Topic: Rmd-qos-nslp statemachine issues
Thread-Index: AcX/IsdDE912ZxH8Qba/jJT6XNwkNg==
From: =?iso-8859-1?Q?Ferenc_Pint=E9r_=28IJ/ETH=29?=
	<ferenc.pinter@ericsson.com>
To: <nsis@ietf.org>
X-OriginalArrivalTime: 12 Dec 2005 13:48:49.0543 (UTC)
	FILETIME=[C7C45170:01C5FF22]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 4863a9796402a44fdb52482f353618fe
Subject: [NSIS] Rmd-qos-nslp statemachine issues
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0671330997=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


This is a multi-part message in MIME format.

--===============0671330997==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5FF22.C758BE60"


This is a multi-part message in MIME format.

------_=_NextPart_001_01C5FF22.C758BE60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all!

I am a hungarian student implementing the QoS-NSLP and its RMD extension =
with help of Attila Bader at Ericsson.
I've found some problematic parts while creating a new statemachine for =
the RMD-extended QoS-NSLP.
This was:


"As I read the original QoS-Statemachine draft =
/draft-fu-nsis-qos-nslp-statemachine-02.txt/
and the .pdf version, I've found that if a QNE in IDLE state receives a =
normal reservation
request without RII it cannot admit - (rx_RESERVE)&&(!RII)&&(RMF=3D"NOT =
AVAIL") - ,=20
sends a response - tx_RESPONSE(RSN,E_SPEC=3D"0x04?") - to its upstream =
peer.
If the upstream peer (or any QNE) in QoS_INSTALLED state receives that =
type of response,
indicating reservation failure, it sends a notify - =
tx_NOTIFY(RSN,E_SPEC=3D"0x04?") -=20
upstream.
The question is: why does the upstream node translate the response =
message to a notify,
however notify is only used in special error conditions?
Is this a typo in the statemachine draft?

I've re-read the newest qos-nslp draft as well, and found in section =
5.4.3 Response Messages:


"On receipt of a RESPONSE message containing an RSN object, the QNE
MUST compare the RSN to that of the appropriate signalling session.
If the match succeeds then the INFO_SPEC MUST be processed. The
RESPONSE message MUST NOT be forwarded further along the path whether
or not the match succeeds."

Is this why the statemachine uses notify for this case?

This problem also does not help with the following:

	- What if Egress receives a downstream peer sent response/notify =
indicating
	  reservation failure downstream of the stateless domain and Egress?
	  What type of message shall be sent to Ingress to ignite an =
intra-domain teardown?
	 =20
		-	A marked response(PDR,E_SPEC=3D"0x04?") with restoring a pre-saved
			hop-count in PDR_Reservation_Report to help Ingress create the=20
			intra-domain teardown reserve?

		-	Do not save any values in Egress after successful intra-domain
			reservation, rather insert a BIG value into Response's Admitted_Hops =
count
			when this failure occurs?

		-	Use a Notify(PDR) with S or M or both bits set and let the edge
			nodes figure out this is not the severe congestion case, by for. ex.
			using PDR_Reservation_Report instead of default =
PDR_Congestion_Report?

		-	Or, as the last option, use a simple QoS-NSLP Notify, and program
			Ingress to issue an intra-domain teardown somehow (and only for =
specific notifies),
			and Egress to filter it out?

Attila suggested using simple QoS-NSLP Notify() when Egress receives a=20
Notify(RSN,E_SPEC=3D"0x04?") from its downstream peer - just sending it =
through Egress - ,
and using a Response(PDR)  with either storing the hop count of the =
domain after the=20
reservation, or adding a BIG hop count to it before sending to Ingress, =
after Egress
received a Response(RSN,E_SPEC=3D"0x04?").Either way, if Egress receives =
a Response()
indicating failure, with a CheckRII=3DNOT_LOCAL RII inside it, it will =
just send a=20
Reponse(PDR) to Ingress."


As Georgios proposed, I've read the related paragraphs /5.4.3, 5.3.5.4/ =
in http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html, they say =
RESPONSE must be, and NOTIFY may be sent by QNE receiving a response =
indicating downstream reservation failure.=20
So after all, I am convinced that I shall not send a NOTIFY, although =
that is written in - draft-fu-nsis-qos-nslp-statemachine-02.txt /and in =
the pdf version as well/ - which seems to be the newest QoS-NSLP =
statemachine draft around.=20
I will use at every QNE (in QoS installed state) :=20
rx_RESPONSE(RSN, E_SPEC=3D"0x04?") 	Delete QoS state IDLE 	=
tx_RESPONSE(RSN, E_SPEC=3D"0x04?")=20
and do not care about what if QNE receives notify.=20
instead of what is written is the QoS-NSLP statemachine draft:=20
rx_RESPONSE(RSN, 		|Delete QoS state 		|IDLE 	|
	E_SPEC=3D"0x04?") 	|tx_NOTIFY(RSN, 	|	|
				| E_SPEC=3D"0x04?") 	|	|
and=20

rx_NOTIFY(RSN, 			|Delete QoS state 		|IDLE 	|
	E_SPEC=3D"0x04?") 	|rx_NOTIFY(RSN, 	| 	|
				| E_SPEC=3D"0x04?") 	| 	|

And QNI will receive RESPONSE(failure) with RSN, not NOTIFY(failure) =
with RSN. /I do not know why they used NOTIFY for this in the QoS-NSLP =
statemachine draft in the first place./=20
This might lead to the following in RMD-QoS-NSLP:=20
When Egress receives this failure response, it simply sends a =
RESPONSE(PDR,E_SPEC=3D"0x04?") to Ingress to signal the error. Egress =
will include an Admitted_Hops value in this RESPONSE /as =
Max_Admitted_Hops/, which was saved previously when it received the =
intra-domain RESERVE(PHR). /or, for simpler Egress operation, it could =
just use a BIG value as well instead of this Admitted_Hops count, =
because when Ingress will issue an intra-domain teardown, the interior =
nodes will forward the teardown RESERVE as well, it will just reach =
Egress where it will be filtered out by the way/=20
Using Admitted_Hops is more precise though.=20
Since Egress will never receive a NOTIFY(RSN,E_SPEC=3D"0x04?") instead =
of RESPONSE(RSN,E_SPEC=3D"0x04?"), I will not include this in the RMD =
Statemachine draft. / how Egress and Ingress handles other NOTIFY =
messages received from downstream is policy dependent, so I will skip =
these as well/.

Ferenc

------_=_NextPart_001_01C5FF22.C758BE60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7232.84">
<TITLE>Rmd-qos-nslp statemachine issues</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi all!</FONT>
</P>

<P><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE">I am a hungarian =
student implementing the QoS-NSLP and its RMD extension with help of =
Attila Bader at Ericsson.</FONT></SPAN>

<BR><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE">I've found some =
problematic parts while creating a new statemachine for the RMD-extended =
QoS-NSLP.</FONT></SPAN>

<BR><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE">This =
was:</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial =
CE">&quot;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">As I read the original QoS-Statemachine draft =
/draft-fu-nsis-qos-nslp-statemachine-02.txt/</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and the .pdf =
version, I've found that if a QNE in IDLE state receives a normal =
reservation</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">request without =
RII it cannot admit - =
(rx_RESERVE)&amp;&amp;(!RII)&amp;&amp;(RMF=3D&quot;NOT AVAIL&quot;) - , =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">sends a response =
- tx_RESPONSE(RSN,E_SPEC=3D&quot;0x04?&quot;) - to its upstream =
peer.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If the upstream =
peer (or any QNE) in QoS_INSTALLED state receives that type of =
response,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">indicating =
reservation failure, it sends a notify - =
tx_NOTIFY(RSN,E_SPEC=3D&quot;0x04?&quot;) - </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">upstream.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The question is: =
why does the upstream node translate the response message to a =
notify,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">however notify is =
only used in special error conditions?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Is this a typo in =
the statemachine draft?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I've re-read the =
newest qos-nslp draft as well, and found in section 5.4.3 Response =
Messages:</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&quot;On receipt =
of a RESPONSE message containing an RSN object, the QNE</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">MUST compare the =
RSN to that of the appropriate signalling session.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If the match =
succeeds then the INFO_SPEC MUST be processed. The</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">RESPONSE message =
MUST NOT be forwarded further along the path whether</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">or not the match =
succeeds.&quot;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Is this why the =
statemachine uses notify for this case?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This problem also =
does not help with the following:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2 FACE=3D"Arial">- What if Egress receive</FONT></SPAN><SPAN =
LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE">s</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> a downstream peer sent =
response/notify indicating</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Arial">&nbsp; reservation failure downstream of =
the stateless domain and Egre</FONT></SPAN><SPAN LANG=3D"hu"><FONT =
SIZE=3D2 FACE=3D"Arial CE">ss</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Arial">&nbsp; What type of message shall be sent =
to Ingress to ignite an intra-domain teardown?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Arial">&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A marked =
response(PDR,E_SPEC=3D&quot;0x04?&quot;) with restoring a =
pre-saved</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">hop-count in PDR_Reservation_Report to help Ingress =
create the </FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">intra-domain teardown reserve?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do not save any =
values in Egress after successful intra-domain</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">reservation, rather insert a BIG value into Response's =
Admitted_Hops</FONT></SPAN><SPAN LANG=3D"hu"><FONT SIZE=3D2 =
FACE=3D"Arial CE"> count</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">when this failure occurs?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Use a Notify(PDR) =
with S or M or both bits set and let the edge</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">nodes figure out this is not the severe congestion case, =
by for. ex.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">using PDR_Reservation_Report instead of default =
PDR_Congestion_Report?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Or, as the last =
option, use a simple QoS-NSLP Notify, and program</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Ingress to issue an intra-domain teardown =
somehow</FONT></SPAN><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE"> =
(and only for specific notifies)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">,</FONT></SPAN>

<BR><SPAN LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">and Egress to</FONT></SPAN><SPAN LANG=3D"hu"><FONT =
SIZE=3D2 FACE=3D"Arial CE"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">filter it out?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Attila suggested =
using simple QoS-NSLP Notify() when Egress receives a </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Notify(RSN,E_SPEC=3D&quot;0x04?&quot;) from its =
downstream peer - just sending it through Egress - ,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and using a =
Response(PDR)&nbsp; with either storing the hop count of the domain =
after the </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">reservation, or =
adding a BIG hop count to it before sending to Ingress, after =
Egress</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">received a =
Response(RSN,E_SPEC=3D&quot;0x04?&quot;).Either way, if Egress receives =
a Response()</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">indicating =
failure, with a CheckRII=3DNOT_LOCAL RII inside it, it will just send a =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Reponse(PDR) to =
Ingress.</FONT></SPAN><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial =
CE">&quot;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"hu"><FONT SIZE=3D2 FACE=3D"Arial CE">As Georgios =
proposed</FONT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial CE">, =
I</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">'ve read the related paragraphs /5.4.3, 5.3.5.4/ =
in</FONT> </SPAN><A =
HREF=3D"http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html"><SPA=
N LANG=3D"en-us"><U></U><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.htm=
l</FONT></U></SPAN></A><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" =
SIZE=3D2 FACE=3D"Arial">, they say RESPONSE must be</FONT></SPAN><SPAN =
LANG=3D"hu"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial =
CE">,</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial"> and NOTIFY</FONT><FONT COLOR=3D"#000000" FACE=3D"Times =
New Roman"></FONT> <FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">may =
be sent by QNE receiving a response indicating downstream reservation =
failure.</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"> =
</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">So after all, I am convinced that I shall not send a =
NOTIFY, although that is written in - =
draft-fu-nsis-qos-nslp-statemachine-02.txt /and in the pdf version as =
well/ - which seems to be the newest QoS-NSLP statemachine draft =
around.</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"> =
</FONT></SPAN></P>

<P><SPAN LANG=3D"hu"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial =
CE">I</FONT></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial"> will use at every QNE (in QoS installed state) =
:</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"> </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Times =
New Roman">rx_RESPONSE(RSN, =
E_SPEC=3D&quot;0x04?&quot;)</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000000" =
SIZE=3D2 FACE=3D"Times New Roman">Delete QoS state =
IDLE</FONT></SPAN><SPAN LANG=3D"hu"> &nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#000000" SIZE=3D2 FACE=3D"Times New Roman">tx_RESPONSE(RSN, =
E_SPEC=3D&quot;0x04?&quot;)</FONT><FONT COLOR=3D"#000000" FACE=3D"Times =
New Roman"></FONT> </SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">and do not care about what if QNE receives =
notify.</FONT><FONT SIZE=3D2 FACE=3D"Arial"> </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">instead of</FONT></SPAN><SPAN LANG=3D"hu"><FONT =
COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial CE"> what is written is the =
QoS-NSLP statemachine draft</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">:</FONT><FONT =
COLOR=3D"#000000" FACE=3D"Times New Roman"> </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">rx_RESPONSE(RSN,</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|Delete QoS state</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|IDLE</FONT></SPAN><SPAN LANG=3D"hu"> &nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|<BR>
</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">E_SPEC=3D&quot;0x04?&quot;)</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|tx_NOTIFY(RSN,</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|<BR>
</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">| E_SPEC=3D&quot;0x04?&quot;)</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN LANG=3D"hu"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times New =
Roman">|</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN>
<BR>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">rx_NOTIFY(RSN,</FONT></SPAN><SPAN LANG=3D"hu">&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|Delete QoS state</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|IDLE</FONT></SPAN><SPAN LANG=3D"hu"> &nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|<BR>
</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">E_SPEC=3D&quot;0x04?&quot;)</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|rx_NOTIFY(RSN,</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">|</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN LANG=3D"hu"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times New Roman">|<BR>
</FONT></SPAN><SPAN =
LANG=3D"hu">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN =
LANG=3D"hu"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times =
New Roman">| E_SPEC=3D&quot;0x04?&quot;)</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN LANG=3D"hu"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times New =
Roman">|</FONT></SPAN><SPAN LANG=3D"hu"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN LANG=3D"hu"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Times New Roman">|</FONT><BR>
</SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">And QNI will receive RESPONSE(failure) with RSN, not =
NOTIFY(failure) with RSN.</FONT><FONT COLOR=3D"#000000" FACE=3D"Times =
New Roman"></FONT> <FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">/I do =
not know why they used NOTIFY for this in the QoS-NSLP statemachine =
draft in the first place./</FONT><FONT COLOR=3D"#000000" FACE=3D"Times =
New Roman"> </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">This might lead to the following in =
RMD-QoS-NSLP:</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"> =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">When Egress receives this failure response, it simply =
sends a RESPONSE(PDR,E_SPEC=3D&quot;0x04?&quot;) to Ingress to =
signal</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"></FONT> =
<FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">the error. Egress will =
include an Admitted_Hops value in this RESPONSE /as Max_Admitted_Hops/, =
which was saved previously when it received the intra-domain =
RESERVE(PHR). /or, for simpler Egress operation, it could just use a BIG =
value as well instead of this Admitted_Hops count, because when Ingress =
will issue an intra-domain teardown, the</FONT><FONT COLOR=3D"#000000" =
FACE=3D"Times New Roman"></FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">interior nodes will forward the teardown RESERVE as well, =
it will just reach Egress where it will be filtered out by the =
way/</FONT><FONT COLOR=3D"#000000" FACE=3D"Times New Roman"> =
</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">Using Admitted_Hops is more precise though.</FONT><FONT =
COLOR=3D"#000000" FACE=3D"Times New Roman"> </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">Since Egress will never receive a =
NOTIFY(RSN,E_SPEC=3D&quot;0x04?&quot;) instead of =
RESPONSE(RSN,E_SPEC=3D&quot;0x04?&quot;),</FONT><FONT COLOR=3D"#000000" =
FACE=3D"Times New Roman"></FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">I will not include this in the RMD Statemachine draft. / =
how Egress and Ingress handles other NOTIFY messages received from =
downstream is policy dependent, so I will skip these as =
well/.</FONT></SPAN></P>

<P><SPAN LANG=3D"hu"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial =
CE">Ferenc</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C5FF22.C758BE60--


--===============0671330997==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--===============0671330997==--




From nsis-bounces@ietf.org Mon Dec 12 12:18:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElrI6-0007rS-9Q; Mon, 12 Dec 2005 12:16:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElrI3-0007pz-98; Mon, 12 Dec 2005 12:16:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19322;
	Mon, 12 Dec 2005 12:15:39 -0500 (EST)
Received: from smtp.ci.uc.pt ([193.136.200.62] helo=smtp-1-relay.ci.uc.pt)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ElrIR-0003tU-5u; Mon, 12 Dec 2005 12:17:28 -0500
Received: from smtp-1.ci.uc.pt (localhost [127.0.0.1])
	by smtp-1-relay.ci.uc.pt (Postfix) with ESMTP
	id CFFB62A9669; Mon, 12 Dec 2005 17:16:00 +0000 (WET)
Received: from teste-d.ci.uc.pt (sendmail.uc.pt [193.136.200.162])
	by smtp-1.ci.uc.pt (Postfix) with ESMTP
	id B67D01728C8; Mon, 12 Dec 2005 17:16:00 +0000 (WET)
Received: from [193.136.207.63] (unknown [193.136.207.63])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by teste-d.ci.uc.pt (Postfix) with ESMTP id 902434A80DF;
	Mon, 12 Dec 2005 17:16:00 +0000 (WET)
Message-ID: <439D4B26.3010906@dei.uc.pt>
Date: Mon, 12 Dec 2005 10:04:22 +0000
From: =?ISO-8859-1?Q?Lu=EDs_Cordeiro?= <cordeiro@dei.uc.pt>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: nsis@ietf.org, nsis-imp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [NSIS] NSIS interop meeting
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi all,

Since most of the NSIS implementation groups showed interest in the=20
creation of a new interop meeting in January, the University of Coimbra=20
- Portugal (http://www.dei.uc.pt) is glad to host a new NSIS=20
interoperability meeting.

We propose 30 and 31 of January of 2006 for this meeting.

If you want to participate in this interop meeting please send me an=20
email indicating which application you want to interop so we are able to =

create a list of possible interoperability tests. I would appreciate the =

replies by 15 of January of 2006 in order to do all the arrangements.


Best regards,
Lu=EDs Cordeiro



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 16:32:32 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElvHc-0005JM-0r; Mon, 12 Dec 2005 16:32:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ElvHW-0005IH-QD; Mon, 12 Dec 2005 16:32:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00685;
	Mon, 12 Dec 2005 16:31:19 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX1+ls4gdjSOfxIE6s1B9FIZNeTqLojLphOc=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ElvID-0007it-UC; Mon, 12 Dec 2005 16:33:11 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1ElvH9-0006J5-5a; Mon, 12 Dec 2005 22:32:09 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id E50C6B511;
	Mon, 12 Dec 2005 22:32:02 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1ElvH8-0002Eo-LY; Mon, 12 Dec 2005 22:32:02 +0100
Message-ID: <439DEC51.4070109@tm.uka.de>
Date: Mon, 12 Dec 2005 22:32:01 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Lu=EDs_Cordeiro?= <cordeiro@dei.uc.pt>
References: <439D4B26.3010906@dei.uc.pt>
In-Reply-To: <439D4B26.3010906@dei.uc.pt>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -4.2 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.2 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA00685
Cc: nsis-imp@ietf.org, nsis@ietf.org
Subject: [NSIS] Re: [Nsis-imp] NSIS interop meeting
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Luis,

Lu=EDs Cordeiro schrieb:
> Since most of the NSIS implementation groups showed interest in the
> creation of a new interop meeting in January, the University of Coimbra
> - Portugal (http://www.dei.uc.pt) is glad to host a new NSIS
> interoperability meeting.
>=20
> We propose 30 and 31 of January of 2006 for this meeting.
>=20
> If you want to participate in this interop meeting please send me an
> email indicating which application you want to interop so we are able t=
o
> create a list of possible interoperability tests. I would appreciate th=
e
> replies by 15 of January of 2006 in order to do all the arrangements.

We express our interest to participate.
Presumably we would like to test:
- GIST draft-08 or later
- QoS-NSLP draft-08 or later
- QSPEC-Template draft-07 or later
"or later" means that our current implementations
may be updated to newer versions if available
and as time permits.

Best regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 12 17:57:22 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Elwbi-0007tJ-Cp; Mon, 12 Dec 2005 17:57:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Elwbe-0007st-K5
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 17:57:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10140
	for <nsis@ietf.org>; Mon, 12 Dec 2005 17:56:10 -0500 (EST)
Received: from mailrelay2.lrz-muenchen.de ([129.187.254.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ElwcM-0001uI-0A
	for nsis@ietf.org; Mon, 12 Dec 2005 17:58:03 -0500
Received: from mars.ze.tum.de (mars.ze.tum.de [129.187.39.17]) by
	mailout.lrz-muenchen.de with ESMTP; Mon, 12 Dec 2005 23:56:52 +0100
To: ferenc.pinter@ericsson.com, <nsis@ietf.org>
From: Tseno Tsenov <tseno.tsenov@mytum.de>
Subject: =?iso-8859-1?q?Re=3A_=5BNSIS=5D_Rmd-qos-nslp_statemachine_issues?=
Date: Mon, 12 Dec 2005 23:56:51 +0100
Mime-version: 1.0
Content-type: Multipart/mixed; boundary="===============0581494023=="
Message-Id: <iss.bb8178fe.2518.439e0034.b6630.e5@mailout.lrz-muenchen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

You will not see this in a MIME-aware mail reader.
--===============0581494023==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


Hi Ferenc,

Thanks a lot for reviewing the statemachine draft.
Pls. see inline:


Original Message:

>Hi all!
>
>I am a hungarian student implementing the QoS-NSLP and its RMD extension w=
ith help of Attila Bader >at Ericsson.
>I've found some problematic parts while creating a new statemachine for th=
e RMD-extended QoS-NSLP.
>This was:
>"As I read the original QoS-Statemachine draft /draft-fu-nsis-qos-nslp-sta=
temachine-02.txt/
>and the .pdf version, I've found that if a QNE in IDLE state receives a no=
rmal reservation
>request without RII it cannot admit - (rx_RESERVE)&&(!RII)&&(RMF=3D"NOT AV=
AIL") - , =

>sends a response - tx_RESPONSE(RSN,E_SPEC=3D"0x04?") - to its upstream pee=
r.
>If the upstream peer (or any QNE) in QoS_INSTALLED state receives that typ=
e of response,
>indicating reservation failure, it sends a notify - tx_NOTIFY(RSN,E_SPEC=
=3D"0x04?") - =

>upstream.
>The question is: why does the upstream node translate the response message=
 to a notify,
>however notify is only used in special error conditions?
>Is this a typo in the statemachine draft?
>
>
>I've re-read the newest qos-nslp draft as well, and found in section 5.4.3=
 Response Messages:
>
>"On receipt of a RESPONSE message containing an RSN object, the QNE
>MUST compare the RSN to that of the appropriate signalling session.
>If the match succeeds then the INFO_SPEC MUST be processed. The
>RESPONSE message MUST NOT be forwarded further along the path whether
>or not the match succeeds."
>
>Is this why the statemachine uses notify for this case?
>

Yes, this statement is the reason why a NOTIFY message appears in such case.
Pls. note that the statemachine draft is based on v-07 of the qos-nslp draf=
t and at that time we identified this as an open issue and used NOTIFY for =
signaling of unsuccessful reservation. AFAIR, in October before the IETF me=
eting, Roland Bless spotted this issue in the mailing list, too.

Unfortunately, recently I dont follow the nsis work in details and don't kn=
ow whether this issue is solved in the latest qos-nslp work. If you say tha=
t this statement is still in the newest qos-nslp draft then maybe additiona=
l clarifying text has been added or just these scenario and issue are class=
ified as infeasible?

Greetings,
Tseno_


>This problem also does not help with the following:
>
>[SNIP]
>
>Ferenc

--===============0581494023==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--===============0581494023==--




From nsis-bounces@ietf.org Tue Dec 13 08:12:01 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Em9wn-0001vb-Qw; Tue, 13 Dec 2005 08:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Elowp-0000UB-Jc
	for nsis@megatron.ietf.org; Mon, 12 Dec 2005 09:46:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01191
	for <nsis@ietf.org>; Mon, 12 Dec 2005 09:45:34 -0500 (EST)
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EloxV-0006w3-JU
	for nsis@ietf.org; Mon, 12 Dec 2005 09:47:21 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com; Mon, 12 Dec 2005 09:46:08 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
	by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2005121209460624330 ; Mon, 12 Dec 2005 09:46:07 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <XLDB5073>; Mon, 12 Dec 2005 09:46:05 -0500
Message-Id: <84E5D7F15F52D34DA84C9C90ACE6554F622BD7@0591-its-exmp01.us.saic.com>
From: "Roy, Radhika R." <royrr@us.saic.com>
To: john.loughney@nokia.com
Subject: RE: [NSIS] FW: nsis meeting minutes
Date: Mon, 12 Dec 2005 09:45:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
X-Mailman-Approved-At: Tue, 13 Dec 2005 08:11:59 -0500
Cc: gash@att.com, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0349299755=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0349299755==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5FF2A.ACD55D78"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C5FF2A.ACD55D78
Content-Type: text/plain;
	charset="iso-8859-1"

John:

OK, let us now discuss about the following comments. Kindly help us as to
resolve the following:

1.      This draft is INCOMPLETE with respect to extensions of QOSM
parameters for using Y.1541. For example, some extensions of QOSM parameters
for Y.1541 have been done in the QOSM draft and some extensions of QOSM
parameters have been done in this (Y.1541-QOSM I-D) draft. Why is it so?

2.      It is inconsistent that the generalized QOSM draft contains some
INCOMPLETE extensions for Y.1541-specific draft. Why is it so?

3.      Why does this draft (Y.1541-QOSM I-D) not contain all
Y.1541-specific extensions of QOSM parameters and make it complete per item
1? Is there any reason for not doing so?

Best regards,

Radhika


-----Original Message-----
From: john.loughney@nokia.com [mailto:john.loughney@nokia.com
<mailto:john.loughney@nokia.com> ]
Sent: Monday, December 12, 2005 8:16 AM
To: Roy, Radhika R.
Cc: gash@att.com; nsis@ietf.org
Subject: RE: [NSIS] FW: nsis meeting minutes

Radhika,

>Hi, John and all:

> 

>Minutes show no comments on the following draft: Y.1541-QOSM I-D -

Jerry Ash

>- 5 min

>http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt
<http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt> 

>-----------------------------------------------------------------

>"no comments"

At least I don't remember making any comments to this draft at the

meeting.

John 


------_=_NextPart_001_01C5FF2A.ACD55D78
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7233.28">
<TITLE>RE: [NSIS] FW: nsis meeting minutes</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">Jo</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">hn:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">OK, let us now discuss about the following comments. Kindly help =
us as</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman"> to resolve =
the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Times New Roman"> follow</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times =
New Roman">ing</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">:</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2>This draft&nbsp;is INCOMPLETE with respect to extensions =
of QOSM parameters for using Y.1541. For example, some extensions of =
QOSM parameters for Y.1541 have been done in the QOSM draft and some =
extensions of QOSM parameters have been done in this (Y.1541-QOSM I-D) =
draft. Why is it so?</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2>It is inconsistent that the generalized =
QOSM draft contains some INCOMPLETE extensions for Y.1541-specific =
draft. Why is it so?</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2>Why&nbsp;does this draft (Y.1541-QOSM =
I-D) not contain all Y.1541-specific extensions of QOSM parameters and =
make it complete per item 1? Is there any reason for not doing =
so?</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2>Best =
regards,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2>Radhika</FONT></SPAN></P>
<BR>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">-----Original Message-----<BR>
From: john.loughney@nokia.com [<A =
HREF=3D"mailto:john.loughney@nokia.com">mailto:john.loughney@nokia.com</=
A>]<BR>
Sent: Monday, December 12, 2005 8:16 AM<BR>
To: Roy, Radhika R.<BR>
Cc: gash@att.com; nsis@ietf.org<BR>
Subject: RE: [NSIS] FW: nsis meeting minutes</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">Radhika,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;Hi, John and all:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt; </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;Minutes show no comments on the following draft: Y.1541-QOSM =
I-D -</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">Jerry Ash</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;- 5 min</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;<A =
HREF=3D"http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.tx=
t">http://ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-00.txt</A>=
</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;-------------------------------------------------------------=
----</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">&gt;&quot;no comments&quot;</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">At least I don't remember making any comments to this draft at =
the</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">meeting.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">John</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C5FF2A.ACD55D78--


--===============0349299755==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--===============0349299755==--




From nsis-bounces@ietf.org Wed Dec 14 09:03:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmXE1-0005vP-0a; Wed, 14 Dec 2005 09:03:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXDv-0005v4-DU
	for nsis@megatron.ietf.org; Wed, 14 Dec 2005 09:03:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28308
	for <nsis@ietf.org>; Wed, 14 Dec 2005 09:02:07 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmXEw-0007zb-Vn
	for nsis@ietf.org; Wed, 14 Dec 2005 09:04:20 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id jBEE2pdZ022155; 
	Wed, 14 Dec 2005 15:02:51 +0100 (MET)
Message-ID: <00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "Roland Bless" <bless@tm.uka.de>,
	"Jukka MJ Manner" <jmanner@cs.Helsinki.FI>
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
Date: Wed, 14 Dec 2005 15:02:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -5.628 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Wed, 14 Dec 2005 15:02:53 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Roland

I will provide some observations only on the latter four of your
comments. We will provide observations on the first comment later on!


-//-  snip

> ------------------------------------------
>
> 5.4.1
>   If the SCOPING flag is set, or if the QNE is the last QNE on the path
>   to the destination, the QNE MUST send a RESPONSE message.
>
> - "is the last QNE on the path to the destination" (isn't this the QNR?)
> - if neither ACK nor SCOPING are set and no RII is present
>  why MUST (only?) the last QNE generate a RESPONSE?
> - we think that a RESPONSE is either triggered by an
>  ACK or an RII or an error.

Georgios:
I think that here, the last node can be either the QNR, but it could also be
a node that is configured to be the last node, which is not the QNR, e.g., a
boundary of a
domain. I think that only this last node SHOULD send the RESPONSE,
due to the fact that we are also using scoping by configuration, where the
SCOPING flag does
not have to be set!



> ---------------------------------------------
>
> PACKET_CLASSIFIER:
> - is it really necessary to specify the PACKET_CLASSIFIER
>  even for reduced refreshes?
> - Is the value of the MRM exactly the same as in GISTs MRI?
>  What should be done in case of a mismatch?
>
> -----------------------------------------------

Georgios:
About using the PACKET_CLASSIFIER for reduced refreshes, why should we not 
use it?
Regarding the MRM, I think taht it should be exactly the same as the GIST 
MRI, since the
QOS-NSLP processing must use the GIST MRI at each node.
However, if this is not the same, then the additional paramaters have to be 
included in
the PACKET_CLASSIFIER object.


> 5.4.3.  RESPONSE Messages
>   .....
>
>   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
>   flag is set or when an error occurs while processing a received
>   message.  If the received message contains an RII object, this object
>   MUST be put in the RESPONSE, as described above.
>
> - We think that the last sentence should only be true in case
>  of an error, but not when an ACK flag is set. In this case
>  a RESPONSE should not include the RII (this RESPONSE will usually
>  follow from the last QNE later) but the RSN.

Georgios:
I think that I agree with your proposal!
Other thoughts?

> That's it for now, possibly more issues later...
>
> P.S.: would be nice if you could include also Markus Ott in the
>      Acknowledgments :-)

Georgios: It think that it will be good to do that!

Best regards,
Georgios



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 14 09:21:46 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmXVq-000146-B3; Wed, 14 Dec 2005 09:21:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXVp-00013X-C7
	for nsis@megatron.ietf.org; Wed, 14 Dec 2005 09:21:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00858
	for <nsis@ietf.org>; Wed, 14 Dec 2005 09:20:40 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmXWt-0000KG-JS
	for nsis@ietf.org; Wed, 14 Dec 2005 09:22:53 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id jBEELU7P023201; 
	Wed, 14 Dec 2005 15:21:30 +0100 (MET)
Message-ID: <010f01c600b9$ae091b60$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "Roland Bless" <bless@tm.uka.de>,
	"Jukka MJ Manner" <jmanner@cs.Helsinki.FI>
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
Date: Wed, 14 Dec 2005 15:21:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -5.627 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Wed, 14 Dec 2005 15:21:32 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Roland

I will provide some observations only on the latter four of your
comments. We will provide observations on the first comment later on!


-//-  snip

> ------------------------------------------
>
> 5.4.1
>   If the SCOPING flag is set, or if the QNE is the last QNE on the path
>   to the destination, the QNE MUST send a RESPONSE message.
>
> - "is the last QNE on the path to the destination" (isn't this the QNR?)
> - if neither ACK nor SCOPING are set and no RII is present
>  why MUST (only?) the last QNE generate a RESPONSE?
> - we think that a RESPONSE is either triggered by an
>  ACK or an RII or an error.

Georgios:
I think that here, the last node can be either the QNR, but it could also be
a node that is configured to be the last node, which is not the QNR, e.g., a
boundary of a
domain. I think that only this last node SHOULD send the RESPONSE,
due to the fact that we are also using scoping by configuration, where the
SCOPING flag does
not have to be set!



> ---------------------------------------------
>
> PACKET_CLASSIFIER:
> - is it really necessary to specify the PACKET_CLASSIFIER
>  even for reduced refreshes?
> - Is the value of the MRM exactly the same as in GISTs MRI?
>  What should be done in case of a mismatch?
>
> -----------------------------------------------

Georgios:
About using the PACKET_CLASSIFIER for reduced refreshes, why should we not 
use it?
Regarding the MRM, I think taht it should be exactly the same as the GIST 
MRI, since the
QOS-NSLP processing must use the GIST MRI at each node.
However, if this is not the same, then the additional paramaters have to be 
included in
the PACKET_CLASSIFIER object.


> 5.4.3.  RESPONSE Messages
>   .....
>
>   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
>   flag is set or when an error occurs while processing a received
>   message.  If the received message contains an RII object, this object
>   MUST be put in the RESPONSE, as described above.
>
> - We think that the last sentence should only be true in case
>  of an error, but not when an ACK flag is set. In this case
>  a RESPONSE should not include the RII (this RESPONSE will usually
>  follow from the last QNE later) but the RSN.

Georgios:
I think that I agree with your proposal!
Other thoughts?

> That's it for now, possibly more issues later...
>
> P.S.: would be nice if you could include also Markus Ott in the
>      Acknowledgments :-)

Georgios: It think that it will be good to do that!

Best regards,
Georgios



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 14 10:11:47 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmYIF-0000t1-89; Wed, 14 Dec 2005 10:11:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmYIE-0000sA-4m
	for nsis@megatron.ietf.org; Wed, 14 Dec 2005 10:11:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07723
	for <nsis@ietf.org>; Wed, 14 Dec 2005 10:10:47 -0500 (EST)
Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmYJL-0002Od-20
	for nsis@ietf.org; Wed, 14 Dec 2005 10:13:01 -0500
Received: from unknown (unknown [192.168.9.180])
	by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id
	D19051800283
	for <nsis@ietf.org>; Wed, 14 Dec 2005 15:11:27 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.49)
	by wfilter.us4.outblaze.com; 14 Dec 2005 15:11:27 -0000
Received: by ws1-1.us4.outblaze.com (Postfix, from userid 1001)
	id A0ECB83C0E; Wed, 14 Dec 2005 15:11:27 +0000 (GMT)
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
From: "Markus Ott" <markus@minister.com>
To: nsis@ietf.org
Date: Wed, 14 Dec 2005 10:11:27 -0500
Received: from [141.3.70.162] by ws1-1.us4.outblaze.com with http for
	markus@minister.com; Wed, 14 Dec 2005 10:11:27 -0500
X-Originating-Ip: 141.3.70.162
X-Originating-Server: ws1-1.us4.outblaze.com
Message-Id: <20051214151127.A0ECB83C0E@ws1-1.us4.outblaze.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
Subject: [NSIS] NOTIFY after tearing down the state?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

 Hi all,
 my name is Markus Ott and I am implementing QoS NSLP at university of Karl=
sruhe(with help of Roland Bless).
 I have almost finished my implementation. Now I am integrating NOTIFY mess=
ages in my implementation. I found a part in the internet draft that is not=
 clear to me. Could anyone say what exactly meant there?=20
=20
 In 3.1.2.  Protocol messages:
=20
 ....
 NOTIFY:  NOTIFY messages are used to convey information to a QNE.
      They differ from RESPONSE messages in that they are sent
      asynchronously and need not refer to any particular state or
      previously received message.  The information conveyed by a NOTIFY
      message is typically related to error conditions.  Examples would
      be notification to an upstream peer about state being torn down or
      to indicate when a reservation has been pre-empted.
....
The sentence "Examples would be notification to an upstream peer about stat=
e being torn down or..." is not clear to me.=20
Take for instance following example:


                 /-\     /-\
              /--|B|-----|E|---\=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
             /   \-/     \-/    \=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
          /-\                    /-\=20=20=20=20=20=20=20=20=20=20=20=20
      ----|A|                    |D|--------
          \-/                    \-/=20=20=20=20=20=20=20=20=20=20=20=20
             \   /-\            /=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
              \--|C|-----------/=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
                 \-/
=20=20=20=20=20
All the nodes are QNEs. The flow is going from A to D. The old flow was goi=
ng through A-B-E-D. Then because of rerouting the new flow is going now thr=
ough A-C-D. The A sends a RESERVE with the TEAR_DOWN bit set to B. B tears =
down its state and forwards the RESERVE with TEAR_DOWN bit set to E. If the=
 node B notifies node A with NOTIFY message about its state being torn down=
 - there will be no problem. But if the next node E after tearing down its =
state will send a NOTIFY message to B, then what will happen? Will the node=
 B just forward this message because it will not find the appropriate SESSI=
ON_ID or just drop it? If it will just drop it, then there is no sense to s=
end this NOTIFY message at all. If the node B will forward this message to =
A, then what can A do with this NOTIFY message? There can be 10-20 nodes be=
tween A and D on the old path. What will node A do in this case with 10-20 =
NOTIFY messages?

What other cases of tearing down the state could be there, after that a NOT=
IFY message could be sent? I think soft state expiration is other issue.

Just one more question: how far are NOTIFY messages being forwarded? One ho=
p or till QNI?

Regards,

Markus Ott.

--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 14 11:14:37 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmZH3-00049E-Tw; Wed, 14 Dec 2005 11:14:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmZH2-00047u-Es
	for nsis@megatron.ietf.org; Wed, 14 Dec 2005 11:14:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17115
	for <nsis@ietf.org>; Wed, 14 Dec 2005 11:13:14 -0500 (EST)
Received: from webmail-outgoing2.us4.outblaze.com ([205.158.62.67]
	helo=webmail-outgoing.us4.outblaze.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmZHr-0005P4-N1
	for nsis@ietf.org; Wed, 14 Dec 2005 11:15:29 -0500
Received: from unknown (unknown [192.168.9.180])
	by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id
	EC81B180035F
	for <nsis@ietf.org>; Wed, 14 Dec 2005 16:13:59 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.55)
	by wfilter.us4.outblaze.com; 14 Dec 2005 16:13:59 -0000
Received: by ws1-3.us4.outblaze.com (Postfix, from userid 1001)
	id 83CFB101D9; Wed, 14 Dec 2005 16:13:59 +0000 (GMT)
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
From: "Markus Ott" <markus@minister.com>
To: nsis@ietf.org
Date: Wed, 14 Dec 2005 11:13:59 -0500
Received: from [141.3.70.162] by ws1-3.us4.outblaze.com with http for
	markus@minister.com; Wed, 14 Dec 2005 11:13:59 -0500
X-Originating-Ip: 141.3.70.162
X-Originating-Server: ws1-3.us4.outblaze.com
Message-Id: <20051214161359.83CFB101D9@ws1-3.us4.outblaze.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Subject: [NSIS] How to request a RESERVE with full QSPEC?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi all,

I've got one more question relating to the internet draft of QoS NSLP:

it relates to the part=20

"5.4.1.  RESERVE Messages".

-------------
.......
When a QNE receives a RESERVE message with an unknown SESSION_ID, it
   MAY send a NOTIFY message to its upstream peer, indicating the
   unknown SESSION_ID. If the message was meant as a refresh, the reply
   indicates a downstream route change to the upstream peer.  The
   upstream peer SHOULD send a complete RESERVE on the new path (new
   SII).  It identifies the old signalling association (old SII) and MAY
   start sending complete RESERVE messages for other SESSION_IDs linked
   to this association.
-------------
The questions to this paragraph were already sent by Roland Bless.
Just one more issue:
In the sentence "If the message was meant as a refresh, the reply
   indicates a downstream route change to the upstream peer.": how=20
   is the indication of a route change done? Is it done with help=20
   of INFO_SPEC? If so then in the list with error values of all error=20
   classes there is no appropriate error value to signal this=20
   information. The only one (not very suitable for this) is the=20
   protocol error with code 0x04: "Mandatory object missing: an=20
   object required in a message of this type was missing." But I=20
   think we need in this case a special code to notify this. Or what=20
   a node must state in this case? Empty message - because the detection of=
=20
   route change is done with help of SII handle?
   Or is this done in another way? Which one?
=20=20=20
Regards,

Markus Ott.

--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 14 13:33:53 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmbRp-0007Ly-Sb; Wed, 14 Dec 2005 13:33:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmbRm-0007Ja-Mu
	for nsis@megatron.ietf.org; Wed, 14 Dec 2005 13:33:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06736
	for <nsis@ietf.org>; Wed, 14 Dec 2005 13:32:42 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmbSp-00039o-NY
	for nsis@ietf.org; Wed, 14 Dec 2005 13:34:58 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBEIWdUA028801;
	Wed, 14 Dec 2005 18:32:40 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] TLS in the GIST draft
Date: Wed, 14 Dec 2005 18:32:50 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCEA@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] TLS in the GIST draft
Thread-Index: AcXTbmmrzpaKZGvORFOnk1y3buFk+AQcsdvABz7U8jA=
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: <Pasi.Eronen@nokia.com>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi pasi, all,

after a certain amount of agonising about this issue, i
have the following proposal (proposed text at the end).

I believe that it is necessary to add text on mandatory ciphersuites. It
also
seems to be important in the long term to allow the more flexible uses
of TLS,
and that some of these require more information than just the TLS usage
selection in the first place. However, some of the options for TLS usage
are
currently somewhat speculative, and there is a case for implementing the
basic
certificate TLS usage first while leaving the way open for more advanced
uses.

The following text is proposed for section 5.7.3:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D

5.7.3.  Protocol Definition: Transport Layer Security

   This defines the use of transport layer security as a basic channel
   security mechanism.  Support for this protocol is mandatory;
   associations using it can carry messages with the transfer attribute
   Secure=3DTrue.  For use with TCP, implementation of TLS1.0 [6] is
   REQUIRED and implementation of TLS1.1 [8] is RECOMMENDED.  (If an
   unreliable transport such as DCCP or UDP is defined for GIST in the
   future, TLS would be implemented with it using DTLS [36].)  GIST
   nodes supporting TLS1.0 or TLS1.1 MUST be able to negotiate the
   following TLS ciphersuites:

   o  TLS_RSA_WITH_RC4_128_MD5

   o  TLS_RSA_WITH_RC4_128_SHA

   o  TLS_RSA_WITH_3DES_EDE_CBC_SHA

   and SHOULD be able to negotiate the following TLS ciphersuite:

   o  TLS_RSA_WITH_AES_128_CBC_SHA

   The default mode of TLS authentication (which applies in particular
   to the above ciphersuites) is server-only or mutual authentication
   using certificates.  The Querying node acts as a TLS client, and the
   Responding node acts as a TLS server.  Where one of the above
   ciphersuites is negotiated, the GIST node acting as a server MUST
   provide its own certificate, and MUST request one from the GIST node
   acting as a TLS client.

   GIST nodes MAY negotiate other TLS ciphersuites.  In some cases, the
   negotiation of alternative ciphersuites is used to trigger
   alternative authentication procedures (for example, the use of pre-
   shared keys).  Where the operation of the procedure depends on the
   prior knowledge of identity hints about the peer, these SHOULD be
   derived from the Peer-Identity provided in the NLI object of Query
   and Response messages.

   No higher-layer-addressing data is defined for TLS.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D

views?

robert h.

ps. in the tracker at
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue103

> -----Original Message-----
> From: Pasi.Eronen@nokia.com [mailto:Pasi.Eronen@nokia.com]=20
> Sent: 07 November 2005 21:22
> To: Hancock, Robert; nsis@ietf.org
> Subject: RE: [NSIS] TLS in the GIST draft
>=20
>=20
> Robert Hancock wrote:
>=20
> > hi pasi, john, all,
> >=20
> > [warning: long, dense mail]
> >
> > i've had time to think about this a little. in terms of=20
> what one could=20
> > specific about TLS, there seem to be 4 (related) issues,=20
> all of one it=20
> > would be good to see some more discussion on.
> >
> > 1. TLS version. The draft currently says MUST 1.0, SHOULD=20
> 1.1. Given=20
> > that GIST will be built from TLS libraries (rather than already=20
> > deployed TLS code), maybe we could be more prescriptive=20
> about wanting=20
> > 1.1; would that be a good or bad thing?
>=20
> Many existing TLS libraries don't support 1.1 yet, and since=20
> the improvements in 1.1 are really minor, I don't see why we=20
> should require it.
>=20
> > 2. Cipher suites (raised earlier in this thread). AFAICT=20
> from reading=20
> > them, the TLS documents specify a single (mandatory to
> > implement) cipher suite, so TLS compliance is enough to provide=20
> > interoperability from that point of view. Is there a need=20
> to be more=20
> > prescriptive here? (Why did Diameter do so?)
>=20
> The mandatory-to-implement ciphersuite specified in RFC 2246=20
> is TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA. This can't be used in=20
> many situations because it requires certificates containing=20
> DSS public keys (most certs are RSA).
>=20
> TLS 1.1 changes this to TLS_RSA_WITH_3DES_EDE_CBC_SHA, which=20
> is slightly better. But IMHO it is still worthwhile to clarify=20
> this explicitly in the NSIS specs, especially if we do not=20
> mandate 1.1.
>=20
> > 3. What authentication methods (certificates, EAP, SRP, etc.  etc.)=20
> > should be implemented. (Sometimes the authentication method=20
> seems to=20
> > be implied by offering a certain special ciphersuite, as in the PSK=20
> > case in particular.)
>=20
> The ciphersuite does imply something about the=20
> authentication, but not necessarily everything that's needed.=20
> But if we copy the Diameter text, it pretty unambiguously=20
> talks about mutual authentication using certificates.
>=20
> > 4. How to decide which identity is to be asserted and authenticated=20
> > (of querying and responding node
> >
> <snip>
> >
> > Even if we do stick with the NLI, there may still be a need=20
> to write=20
> > something about operational issues. That could be to encourage some=20
> > uniformity in the selection of authentication techniques, and also
> > (maybe) proposing a structure for the PI field in the NLI=20
> (if only to=20
> > make it human-readable).  That might be for the GIST spec=20
> itself, or=20
> > (more likely?)  for some separate BCP-like thing.
>=20
> If it's required for actual interoperability, then it IMHO=20
> needs to be in the GIST spec (or if it's a separate document,=20
> the GIST spec will need a normative reference to it)... but I=20
> guess it depends on the ambition level. It seems that for=20
> certificates, this isn't really an issue, so copying the=20
> Diameter text would be fine.
>=20
> Best regards,
> Pasi
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 15 06:20:44 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmrAC-0001KC-Gs; Thu, 15 Dec 2005 06:20:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmrAB-0001J1-EP
	for nsis@megatron.ietf.org; Thu, 15 Dec 2005 06:20:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20917
	for <nsis@ietf.org>; Thu, 15 Dec 2005 06:19:27 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmrBG-0005Vo-0n
	for nsis@ietf.org; Thu, 15 Dec 2005 06:21:52 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBFBGvUA000686;
	Thu, 15 Dec 2005 11:16:57 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] GIST Refresh Mechanism eventually breaks upstream path
	onCrossover Router
Date: Thu, 15 Dec 2005 11:16:59 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCF2@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] GIST Refresh Mechanism eventually breaks upstream path
	onCrossover Router
Thread-Index: AcX0Y9mT+B0hYkfUQbeisDjr5xUlAwM8/lXg
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

hi thomas,

this is a good question.

I think the general issue here is that we can have a scenario
where two nodes (P1, P2) think they are the upstream peer=20
of a crossover node CN2, and their routing state management=20
messages confuse the crossover node.

there are two classes of solution:
1) prevent the 'wrong' upstream peer (P1) issuing refreshes
2) prevent the crossover accepting them

      /--P1--\           (old path)
--CN1-        -CN2--  flow direction ------->
      \--P2--/           (new path)

the local repair approach concentrates on the first method. in
the general scheme of things, local repair must have been=20
iniated from the upstream crossover node CN1, which must=20
therefore have unique downstream state through the path with
P2. CN1 will not be refreshing state through the P1 path, which
will eventually cause all the state on that path to time out
(including preventing P1 from generating refreshes).

One point to clarify in the draft is that P1 should stop=20
refreshing routing state if its upstream state times out.=20
I suspect this should be enforced at the GIST level. (We
can't stop a signaling application at P1 from generating a new
NSLP message and starting the process over again, but at=20
least we can prevent GIST keeping stuff around in the
background.)

As you point out, stale state on the old path can still
lead to P1 issuing refreshes (I think the time for which this
can take place is bounded by the RSV time at CN1, but I'm
not totally sure about this). The solution here is explicit
tear along the path at the NSLP level followed by indication
to GIST that routing state is no longer needed. I don't think
it's unreasonable to depend on NSLP operation here; the basic
point is that we left explicit teardown out of GIST for
authorisation reasons, so part of the overall signalling
functionality is deferred to the NSLP anyway. It corresponds
to the fact that GIST depends on the NSLP to decide to send
messages in the first place. To put it another way, we cannot
actually solve the explicit tear problem entirely at the
GIST level since state in the signalling applications can
cause GIST to come back to life anyway. But we should also
update section 7 to point out this aspect of the GIST/NSLP
interaction.

So much for approach (1). Option (2) which you suggest has some
attractions, and could for example be added as a backwards=20
compatible extension at some stage (there are spare bits in
the common header, one of which could be defined as a hint
'ignore me if you have state from someone else'). However, I'd
be uncomfortable to make that change in this version. Partly
it's because we would effectively have two different sorts of
Query message with the processing depending on degree of state
synchronisation between Q and R node, and there are several new
cases to analyse (e.g. what if the Q node thinks something is=20
a refresh but the R node does not; this would arise when route
changes were detected as part of the normal soft state mechanism).
Also, route flaps really do take place, so it might well be that
the flow returned to the 'old' path, but P1 was never able to
re-establish the state. We'd need another error message to=20
indicate that a Query was rejected, and so on. I'm not saying
these issues are insoluble, but I think there is a case for
a more leisurely analysis. In the meantime, the clarifications/
refinements in section 7 will be included.

cheers,

r.



> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Thomas Herzog
> Sent: 28 November 2005 21:29
> To: nsis@ietf.org
> Subject: Re: [NSIS] GIST Refresh Mechanism eventually breaks=20
> upstream path onCrossover Router
>=20
>=20
> Hi, all,
>=20
> of course, there could also be other possibilities to fix=20
> this issue. I think,=20
> in general,  a Responding Node should be able to detect=20
> whether an incoming=20
> GIST Query is part of a state setup or of a refresh requence.
>=20
> This could also be implemented by adding a flag *somewhere*=20
> to a Query. So a=20
> Responding Node could drop a Query if it comes in from=20
> another peer than the=20
> currently installed peer and is part of a Refresh.
>=20
>=20
> Cheers, Thomas
>=20
>=20
> Am Montag, 28. November 2005 19:12 schrieb Thomas Herzog:
> > Having thought about this issue, I would like to propose discussion=20
> > about a
> > new GIST Query-type Message, say "GIST Refresh" with the following=20
> semantics:
> >=20
> > GIST Refresh:
> > - may refresh established Routing State
> > - may lead to establishment of new Routing State
> >=20
> > GIST Query:
> > - may replace established Routing State
> > - may lead to establishment of new Routing State
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 15 08:33:53 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EmtF3-0003xZ-07; Thu, 15 Dec 2005 08:33:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EmtF1-0003vu-S2
	for nsis@megatron.ietf.org; Thu, 15 Dec 2005 08:33:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06420
	for <nsis@ietf.org>; Thu, 15 Dec 2005 08:32:52 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmtGP-0001pr-Sy
	for nsis@ietf.org; Thu, 15 Dec 2005 08:35:19 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBFDWkUA032213;
	Thu, 15 Dec 2005 13:32:46 GMT
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <200511071414.41803.thomas.herzog@gmx.li>
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
X-OlkEid: E3A4D92541902090A7C075468713348B4FB35BA9
Content-class: urn:content-classes:message
Subject: RE: [NSIS] GIST API: InvalidateRoutingstate setting state
	to"Tentative" - what use would it have?
Date: Thu, 15 Dec 2005 13:32:48 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBCF3@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] GIST API: InvalidateRoutingstate setting state
	to"Tentative" - what use would it have?
Thread-Index: AcYBfAiF9qTmvMKCQKKqCFelNctwBA==
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Thomas Herzog" <thomas.herzog@gmx.li>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Thomas,

[written in vancouver but i obviously forget to send it...]

No doubt it is a subtle subject. There's one simple point and
one complex one.

1. [Could just be a clarification:] You say below "Currently,=20
I set the state to "TENTATIVE", when entering a Refresh cycle".
Just to be clear: *if* you set the routing quality to tentative,
*then* you must enter awaiting refresh/response; however, the
converse is not true. In other words, *if* you enter awaiting
refresh because of normal routing state timer behaviour, you
should *not* automatically change routing quality to tentative.

2. [Your main question:] If the NSLP sets the routing state to
tentative, the state machine may transition to either awaiting
response or awaiting refresh. Which to do is a matter of local
policy. The protocol will work correctly in either case. A=20
reasonable policy would be always to move to awaiting refresh,=20
but I can think of several other reasonable policies; it really=20
has to be left open as implementation freedom.

In either case, at some subsequent stage the handshake *must*
take place (see the first sentence after the list of options in
section 7.1.3); if the transition is marked urgent this *must* be
done immediately, otherwise the GIST layer is free to schedule=20
it as it sees fit.

I think your main question is: what is the point of the NSLP
setting the state to 'tentative' if you do not immediately try=20
to refresh it (i.e. do not set the urgent flag). I think the=20
basic answer to this is that it is a way for the NSLP to be=20
notified when the state is confirmed as Good, without disrupting=20
on-going signalling or triggering a storm of Query updates.=20
(How much NSLPs would use this functionality I cannot say, but
it seems unwise to rule it out.)

Hope this helps,

robert h.

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Thomas Herzog
> Sent: 07 November 2005 05:15
> To: nsis@ietf.org
> Subject: [NSIS] GIST API: InvalidateRoutingstate setting=20
> state to"Tentative" - what use would it have?
>=20
>=20
> Hi, I am currently implementing the InvalidateRoutingstate and=20
> SetStateLifetime API calls und stumbled about one thing:
>=20
> According to the I-D, NSLP may invalidate Routing State to "BAD" and=20
> "TENTATIVE" and also supply a "urgency" Flag, as to whether=20
> GIST should=20
> reestablish the Route instantly or if it can delay this until=20
> the next=20
> SendMessage call.
>=20
> In my eyes, setting state to "BAD" would be killing Routing=20
> State, so that=20
> only the SII-Handle may be used to contact the peer after=20
> that call, and the=20
> "urgency" flag would tell GIST to do a new handshake and=20
> install new Routing=20
> State for all the (MRI/SID/NSLPID) tuples the=20
> InvalidateRoutingState API call=20
> applied to.
>=20
> But what would the case of NSLP setting the state to=20
> "TENTATIVE" cause GIST to=20
> do? Would it cause a Routing State REFRESH, if the urgency=20
> flag is set?
>=20
> What happens, if the NSLP sets the state to "TENTATIVE" and=20
> not set the=20
> "urgency" flag? GIST would then only know "this routing state=20
> can be wrong"=20
> when the next SendMessage arrives, I can see no use for this=20
> case at all, can=20
> someone enlighten me? Should GIST then start a refresh on the next=20
> SendMessage call? (it would in the meantime also do Refreshes=20
> due to periodic=20
> probing...)
>=20
> Currently, I set the state to "TENTATIVE", when entering a=20
> Refresh cycle and=20
> to "BAD" when the state times out. "GOOD" I use when the=20
> state machine enters=20
> the "established" states.
>=20
> So, it would be helpful, if someone could clearify what=20
> exactly GIST is=20
> supposed to do when:
>=20
> - NSLP sets the state to "tentative" and provides urgency flag
> - NSLP sets the state to "tentative" and does not provide urgency flag
>=20
> Thanks in advance,
> Thomas
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 15 17:13:14 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En1Ld-0005og-FZ; Thu, 15 Dec 2005 17:13:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En1Lb-0005oS-Q6
	for nsis@megatron.ietf.org; Thu, 15 Dec 2005 17:13:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23377
	for <nsis@ietf.org>; Thu, 15 Dec 2005 17:12:13 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En1N4-0008Ug-TX
	for nsis@ietf.org; Thu, 15 Dec 2005 17:14:44 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	6F1375B8B0 for <nsis@ietf.org>; Thu, 15 Dec 2005 23:13:02 +0100 (CET)
Received: from [134.76.81.226] (p5484B166.dip0.t-ipconnect.de [84.132.177.102])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP
	for <nsis@ietf.org>; Thu, 15 Dec 2005 23:13:02 +0100 (CET)
Message-ID: <43A1EA7C.5070307@cs.uni-goettingen.de>
Date: Thu, 15 Dec 2005 23:13:16 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: [NSIS] RAO value
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

each NSLP-ID correspondents to a unique RAO value. draft-rmd-04 mentions that there 
are predefined values to bypass end-to-end RESPONSE messages at QNE Interior nodes. 
Are these NSLP-IDs and RAO values somewhere defined?

There's also mentioned that QNE Interior nodes are configured to handle only certain 
levels of RAO values. Are these RAO values processed at NTLP level or are they passed 
to the NSLP and handled there?

Thanks,
Bernd

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 15 18:01:28 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En26K-0003fb-OC; Thu, 15 Dec 2005 18:01:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En26I-0003c7-VH
	for nsis@megatron.ietf.org; Thu, 15 Dec 2005 18:01:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28719
	for <nsis@ietf.org>; Thu, 15 Dec 2005 18:00:28 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En27m-00021v-DS
	for nsis@ietf.org; Thu, 15 Dec 2005 18:02:59 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	56C855B8B0 for <nsis@ietf.org>; Fri, 16 Dec 2005 00:01:21 +0100 (CET)
Received: from [134.76.81.226] (p5484B166.dip0.t-ipconnect.de [84.132.177.102])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP
	for <nsis@ietf.org>; Fri, 16 Dec 2005 00:01:20 +0100 (CET)
Message-ID: <43A1F5CE.4000207@cs.uni-goettingen.de>
Date: Fri, 16 Dec 2005 00:01:34 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [NSIS] wrong error code in INFO_SPEC object?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

in draft-qos-nslp-08, paragraph 3.1.3.6 INFO_SPEC the error code for 'Permanent 
RMF-related error' is 0x05000005. This is a 32-bit value and does not fit into the 
12-bit error code field. Should this be 0x05 ?

Thanks,
Bernd

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 16 01:14:43 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1En8rb-0000l8-GG; Fri, 16 Dec 2005 01:14:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1En8ra-0000l3-24
	for nsis@megatron.ietf.org; Fri, 16 Dec 2005 01:14:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08602
	for <nsis@ietf.org>; Fri, 16 Dec 2005 01:13:42 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1En8t7-0000hs-Ah
	for nsis@ietf.org; Fri, 16 Dec 2005 01:16:18 -0500
Received: from wrl-40.cs.helsinki.fi (wrl-40.cs.helsinki.fi [128.214.166.160])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Fri, 16 Dec 2005 08:14:38 +0200
	id 00070119.43A25B4E.00001875
Date: Fri, 16 Dec 2005 08:14:37 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
Subject: Re: [NSIS] wrong error code in INFO_SPEC object?
In-Reply-To: <43A1F5CE.4000207@cs.uni-goettingen.de>
Message-ID: <Pine.LNX.4.58.0512160814150.19154@wrl-40.cs.helsinki.fi>
References: <43A1F5CE.4000207@cs.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi,
Yes it should. :)

Jukka

On Fri, 16 Dec 2005, Bernd Schloer wrote:

> Hi,
> 
> in draft-qos-nslp-08, paragraph 3.1.3.6 INFO_SPEC the error code for
> 'Permanent RMF-related error' is 0x05000005. This is a 32-bit value and does
> not fit into the 12-bit error code field. Should this be 0x05 ?
> 
> Thanks,
> Bernd
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 16 08:54:30 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EnG2Y-0005JU-Iy; Fri, 16 Dec 2005 08:54:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EnG2X-0005JM-3K
	for nsis@megatron.ietf.org; Fri, 16 Dec 2005 08:54:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20718
	for <nsis@ietf.org>; Fri, 16 Dec 2005 08:53:28 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EnG46-0007pz-K0
	for nsis@ietf.org; Fri, 16 Dec 2005 08:56:09 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBGDrBUA017613;
	Fri, 16 Dec 2005 13:53:11 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] RAO value
Date: Fri, 16 Dec 2005 13:53:11 -0000
Message-ID: <A632AD91CF90F24A87C42F6B96ADE5C57EBD01@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] RAO value
Thread-Index: AcYBxS4tuEzhF0otQ8+ip73KkvcgpQAgIHxQ
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Bernd Schloer" <bschloer@cs.uni-goettingen.de>, <nsis@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Bernd,

for your first question, AFAIK there are no concrete values=20
defined. they would be defined as part of the registration
process for a new NSLPID (see the IANA considerations section
in the GIST spec) - at least, that's how I assume it would be
done.

On the second question, I suspect that the RMD document is
not strictly correct; it should be phrased in terms of NSLPID
values rather than RAO values (the semantics of which message
should be processed where are defined by the NSLPID values; the
RAO value is selected to make interception of messages with
particular NSLPID values as efficient as possible, but doesn't
have semantic significance). And then it is simple: it is a
GIST issue to pull out messages with the right NSLPID by=20
configuring the IP layer to look for certain RAO values (or
by any other means), but the only information element visible
at the NSLP level is the NSLPID.

hope this helps,

robert h.

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Bernd Schloer
> Sent: 15 December 2005 22:13
> To: nsis@ietf.org
> Subject: [NSIS] RAO value
>=20
>=20
> Hi,
>=20
> each NSLP-ID correspondents to a unique RAO value.=20
> draft-rmd-04 mentions that there=20
> are predefined values to bypass end-to-end RESPONSE messages=20
> at QNE Interior nodes.=20
> Are these NSLP-IDs and RAO values somewhere defined?
>=20
> There's also mentioned that QNE Interior nodes are configured=20
> to handle only certain=20
> levels of RAO values. Are these RAO values processed at NTLP=20
> level or are they passed=20
> to the NSLP and handled there?
>=20
> Thanks,
> Bernd
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
>=20

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 16 16:19:44 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EnMyc-0001ld-Ce; Fri, 16 Dec 2005 16:18:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EnMyb-0001lN-7R
	for nsis@megatron.ietf.org; Fri, 16 Dec 2005 16:18:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19827
	for <nsis@ietf.org>; Fri, 16 Dec 2005 16:17:52 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EnN0G-0000mp-Ei
	for nsis@ietf.org; Fri, 16 Dec 2005 16:20:37 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	55E605B8B0; Fri, 16 Dec 2005 22:18:50 +0100 (CET)
Received: from [134.76.81.226] (p5484B264.dip0.t-ipconnect.de [84.132.178.100])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP;
	Fri, 16 Dec 2005 22:18:49 +0100 (CET)
Message-ID: <43A32F44.1070405@cs.uni-goettingen.de>
Date: Fri, 16 Dec 2005 22:19:00 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
Subject: Re: [NSIS] RAO value
References: <A632AD91CF90F24A87C42F6B96ADE5C57EBD01@rsys005a.comm.ad.roke.co.uk>
In-Reply-To: <A632AD91CF90F24A87C42F6B96ADE5C57EBD01@rsys005a.comm.ad.roke.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Robert,

yes, this helped a lot. I just got a litte confused when I read the paragraph in the 
RMD document. Things are much clearer now!

Bernd

Hancock, Robert wrote:
> Hi Bernd,
> 
> for your first question, AFAIK there are no concrete values 
> defined. they would be defined as part of the registration
> process for a new NSLPID (see the IANA considerations section
> in the GIST spec) - at least, that's how I assume it would be
> done.
> 
> On the second question, I suspect that the RMD document is
> not strictly correct; it should be phrased in terms of NSLPID
> values rather than RAO values (the semantics of which message
> should be processed where are defined by the NSLPID values; the
> RAO value is selected to make interception of messages with
> particular NSLPID values as efficient as possible, but doesn't
> have semantic significance). And then it is simple: it is a
> GIST issue to pull out messages with the right NSLPID by 
> configuring the IP layer to look for certain RAO values (or
> by any other means), but the only information element visible
> at the NSLP level is the NSLPID.
> 
> hope this helps,
> 
> robert h.
> 
> 
>>-----Original Message-----
>>From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
>>Behalf Of Bernd Schloer
>>Sent: 15 December 2005 22:13
>>To: nsis@ietf.org
>>Subject: [NSIS] RAO value
>>
>>
>>Hi,
>>
>>each NSLP-ID correspondents to a unique RAO value. 
>>draft-rmd-04 mentions that there 
>>are predefined values to bypass end-to-end RESPONSE messages 
>>at QNE Interior nodes. 
>>Are these NSLP-IDs and RAO values somewhere defined?
>>
>>There's also mentioned that QNE Interior nodes are configured 
>>to handle only certain 
>>levels of RAO values. Are these RAO values processed at NTLP 
>>level or are they passed 
>>to the NSLP and handled there?
>>
>>Thanks,
>>Bernd
>>
>>_______________________________________________
>>nsis mailing list
>>nsis@ietf.org
>>https://www1.ietf.org/mailman/listinfo/nsis
>>

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 19 02:46:39 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoFjD-0007yh-FH; Mon, 19 Dec 2005 02:46:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoFjB-0007xo-OS
	for nsis@megatron.ietf.org; Mon, 19 Dec 2005 02:46:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01005
	for <nsis@ietf.org>; Mon, 19 Dec 2005 02:45:34 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoFlL-00018j-4h
	for nsis@ietf.org; Mon, 19 Dec 2005 02:48:52 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	9E11B5B8B0 for <nsis@ietf.org>; Mon, 19 Dec 2005 08:46:27 +0100 (CET)
Received: from [134.76.81.226] (p548487E7.dip0.t-ipconnect.de [84.132.135.231])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP
	for <nsis@ietf.org>; Mon, 19 Dec 2005 08:46:27 +0100 (CET)
Message-ID: <43A6655B.7040201@cs.uni-goettingen.de>
Date: Mon, 19 Dec 2005 08:46:35 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: [NSIS] Typo in QSPEC Parameters ?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

in the qspec-draft, section 9. IANA Considerations the 'Excess Treatment' Parameter is
listed with a size of 8 bits. However in section 7.2.2 this field and the 'NON QOSM
Hop' field (7.2.1) both have a size of 7 bits. Is that a typo ?

In Section 7.2 Parameter Coding the example with the Bandwidth Parameter points to
section 7.2.2. It's in section 7.2.3.

Bernd



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 19 06:08:14 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoIsI-00022L-SK; Mon, 19 Dec 2005 06:08:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoIsH-00021l-NW
	for nsis@megatron.ietf.org; Mon, 19 Dec 2005 06:08:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26504
	for <nsis@ietf.org>; Mon, 19 Dec 2005 06:07:11 -0500 (EST)
Received: from mail126.messagelabs.com ([216.82.254.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EoIuM-0008Vy-St
	for nsis@ietf.org; Mon, 19 Dec 2005 06:10:30 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-14.tower-126.messagelabs.com!1134990427!10990125!10
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 10887 invoked from network); 19 Dec 2005 11:07:54 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-14.tower-126.messagelabs.com with SMTP;
	19 Dec 2005 11:07:54 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh3i.attrh.att.com (7.2.052)
	id 43A3035900027219; Mon, 19 Dec 2005 06:07:50 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] Typo in QSPEC Parameters ?
Date: Mon, 19 Dec 2005 05:07:50 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA97D6@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: [NSIS] Typo in QSPEC Parameters ?
Thread-Index: AcYEcKhQkdw16RWUS8iOkTohMZ/MKgAGwglg
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: "Bernd Schloer" <bschloer@cs.uni-goettingen.de>, <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
	"Attila Bader \(ETH\)" <Attila.Bader@ericsson.com>, "Kappler,
	Cornelia" <cornelia.kappler@siemens.com>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Bernd,

Thanks a lot for your careful review of the QSPEC document.

> in the qspec-draft, section 9. IANA Considerations the
> 'Excess Treatment' Parameter is listed with a size of 8 bits.
> However in section 7.2.2 this field and the 'NON QOSM Hop'
> field (7.2.1) both have a size of 7 bits. Is that a typo?

Yes, they should both be 8 bits.  We'll fix in the next revision.

> In Section 7.2 Parameter Coding the example with the Bandwidth
> Parameter points to section 7.2.2. It's in section 7.2.3.

Yes, right you are.  We'll fix in the next Revision.

Thanks,
Regards,
Jerry

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Dec 19 17:28:19 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoTUQ-0001G6-VY; Mon, 19 Dec 2005 17:28:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoTUP-0001Fi-Ut
	for nsis@megatron.ietf.org; Mon, 19 Dec 2005 17:28:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27100
	for <nsis@ietf.org>; Mon, 19 Dec 2005 17:27:15 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX1+HVmuRCrf4GY7nZxdqDNOPKQoMLYSq53U=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoTWh-0000vh-5I
	for nsis@ietf.org; Mon, 19 Dec 2005 17:30:40 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1EoTUB-00065n-Vp; Mon, 19 Dec 2005 23:28:06 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 9F75BB4ED;
	Mon, 19 Dec 2005 23:27:57 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1EoTU5-0006im-4F; Mon, 19 Dec 2005 23:27:57 +0100
Message-ID: <43A7340A.9080101@tm.uka.de>
Date: Mon, 19 Dec 2005 23:28:26 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
Subject: Re: [NSIS] Update on the QoS NSLP work
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
	<00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
In-Reply-To: <00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.1 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.3 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Georgios,
>> ------------------------------------------
>>
>> 5.4.1
>>   If the SCOPING flag is set, or if the QNE is the last QNE on the path
>>   to the destination, the QNE MUST send a RESPONSE message.
>>
>> - "is the last QNE on the path to the destination" (isn't this the QNR?)
>> - if neither ACK nor SCOPING are set and no RII is present
>>  why MUST (only?) the last QNE generate a RESPONSE?
>> - we think that a RESPONSE is either triggered by an
>>  ACK or an RII or an error.
> 
> 
> Georgios:
> I think that here, the last node can be either the QNR, but it could
> also be
> a node that is configured to be the last node, which is not the QNR,
> e.g., a
> boundary of a
> domain. I think that only this last node SHOULD send the RESPONSE,
> due to the fact that we are also using scoping by configuration, where the
> SCOPING flag does
> not have to be set!

Hmm. this sounds like a special configuration that you have in mind.
Your proposed behavior would IMHO contradict with the default behavior
when an RII is set... Nevertheless this paragraph needs clarification.

>> PACKET_CLASSIFIER:
>> - is it really necessary to specify the PACKET_CLASSIFIER
>>  even for reduced refreshes?
>> - Is the value of the MRM exactly the same as in GISTs MRI?
>>  What should be done in case of a mismatch?
>>
>> -----------------------------------------------
> 
> 
> Georgios:
> About using the PACKET_CLASSIFIER for reduced refreshes, why should we
> not use it?

Because it will not change and is thus redundant.

> Regarding the MRM, I think taht it should be exactly the same as the
> GIST MRI, since the
> QOS-NSLP processing must use the GIST MRI at each node.
> However, if this is not the same, then the additional paramaters have to
> be included in
> the PACKET_CLASSIFIER object.

Does this really make sense? Any examples or other opinions?

>> 5.4.3.  RESPONSE Messages
>>   .....
>>
>>   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
>>   flag is set or when an error occurs while processing a received
>>   message.  If the received message contains an RII object, this object
>>   MUST be put in the RESPONSE, as described above.
>>
>> - We think that the last sentence should only be true in case
>>  of an error, but not when an ACK flag is set. In this case
>>  a RESPONSE should not include the RII (this RESPONSE will usually
>>  follow from the last QNE later) but the RSN.
> 
> Georgios:
> I think that I agree with your proposal!
> Other thoughts?

Yep, more input?

Regards,
 Roland.

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 03:28:39 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EocrP-00040A-DM; Tue, 20 Dec 2005 03:28:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EocrO-0003ym-AP
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 03:28:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26914
	for <nsis@ietf.org>; Tue, 20 Dec 2005 03:27:34 -0500 (EST)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eoctj-0002eb-JG
	for nsis@ietf.org; Tue, 20 Dec 2005 03:31:06 -0500
Received: from localhost (localhost [127.0.0.1])
	by s4.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	BFD185B8C6 for <nsis@ietf.org>; Tue, 20 Dec 2005 09:28:26 +0100 (CET)
Received: from [134.76.81.226] (p5484B067.dip0.t-ipconnect.de [84.132.176.103])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP
	for <nsis@ietf.org>; Tue, 20 Dec 2005 09:28:26 +0100 (CET)
Message-ID: <43A7C0B2.9060607@cs.uni-goettingen.de>
Date: Tue, 20 Dec 2005 09:28:34 +0100
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [NSIS] Wrong Parameter ID in QSPEC Objects?
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

both the Bandwidth Parameter (7.2.3) and the Slack Term Parameter (7.2.4) have the 
same ID #3. Shouldn't the Bandwidth Parameter have the ID #2 ?

In 7.2.5 the Token Bucket #1 Parameter has ID #5 and the Token Bucket #2 Parameter has 
ID #6. Shouldn't this be ID #4 and ID #5 as in the packet format description ?

Thanks,
Bernd


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 04:06:59 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EodSV-0003cE-10; Tue, 20 Dec 2005 04:06:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EodST-0003bX-8v
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 04:06:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00135
	for <nsis@ietf.org>; Tue, 20 Dec 2005 04:05:53 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EodUq-0003vS-Tc
	for nsis@ietf.org; Tue, 20 Dec 2005 04:09:25 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id jBK96dYm003102; 
	Tue, 20 Dec 2005 10:06:39 +0100 (MET)
Message-ID: <006f01c60544$b066a5f0$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "Roland Bless" <bless@tm.uka.de>
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi><43986636.2050508@tm.uka.de><00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
	<43A7340A.9080101@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
Date: Tue, 20 Dec 2005 10:06:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -5.637 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Tue, 20 Dec 2005 10:06:40 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Roland

----- Original Message ----- 
From: "Roland Bless" <bless@tm.uka.de>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Cc: "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>; <nsis@ietf.org>
Sent: Monday, December 19, 2005 11:28 PM
Subject: Re: [NSIS] Update on the QoS NSLP work


> Hi Georgios,
>>> ------------------------------------------
>>>
>>> 5.4.1
>>>   If the SCOPING flag is set, or if the QNE is the last QNE on the path
>>>   to the destination, the QNE MUST send a RESPONSE message.
>>>
>>> - "is the last QNE on the path to the destination" (isn't this the QNR?)
>>> - if neither ACK nor SCOPING are set and no RII is present
>>>  why MUST (only?) the last QNE generate a RESPONSE?
>>> - we think that a RESPONSE is either triggered by an
>>>  ACK or an RII or an error.
>>
>>
>> Georgios:
>> I think that here, the last node can be either the QNR, but it could
>> also be
>> a node that is configured to be the last node, which is not the QNR,
>> e.g., a
>> boundary of a
>> domain. I think that only this last node SHOULD send the RESPONSE,
>> due to the fact that we are also using scoping by configuration, where 
>> the
>> SCOPING flag does
>> not have to be set!
>
> Hmm. this sounds like a special configuration that you have in mind.
> Your proposed behavior would IMHO contradict with the default behavior
> when an RII is set... Nevertheless this paragraph needs clarification.

Georgios: Thanks, we will do that!

>>> PACKET_CLASSIFIER:
>>> - is it really necessary to specify the PACKET_CLASSIFIER
>>>  even for reduced refreshes?
>>> - Is the value of the MRM exactly the same as in GISTs MRI?
>>>  What should be done in case of a mismatch?
>>>
>>> -----------------------------------------------
>>
>>
>> Georgios:
>> About using the PACKET_CLASSIFIER for reduced refreshes, why should we
>> not use it?
>
> Roland: Because it will not change and is thus redundant.

Georgios: I think that you are right!
Other thoughts


>
>> Regarding the MRM, I think taht it should be exactly the same as the
>> GIST MRI, since the
>> QOS-NSLP processing must use the GIST MRI at each node.
>> However, if this is not the same, then the additional paramaters have to
>> be included in
>> the PACKET_CLASSIFIER object.
>
> Does this really make sense? Any examples or other opinions?
Georgios: Othre thoughts?

>
>>> 5.4.3.  RESPONSE Messages
>>>   .....
>>>
>>>   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
>>>   flag is set or when an error occurs while processing a received
>>>   message.  If the received message contains an RII object, this object
>>>   MUST be put in the RESPONSE, as described above.
>>>
>>> - We think that the last sentence should only be true in case
>>>  of an error, but not when an ACK flag is set. In this case
>>>  a RESPONSE should not include the RII (this RESPONSE will usually
>>>  follow from the last QNE later) but the RSN.
>>
>> Georgios:
>> I think that I agree with your proposal!
>> Other thoughts?
>
> Yep, more input?

Georgios: Other thoughts?
> Regards,
> Roland.
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 04:22:53 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eodht-0007Nu-Bk; Tue, 20 Dec 2005 04:22:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eodhr-0007Nk-8p
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 04:22:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01634
	for <nsis@ietf.org>; Tue, 20 Dec 2005 04:21:47 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EodkE-0004Qo-Fr
	for nsis@ietf.org; Tue, 20 Dec 2005 04:25:19 -0500
Received: from wrl-40.cs.helsinki.fi (wrl-40.cs.helsinki.fi [128.214.166.160])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Tue, 20 Dec 2005 11:22:43 +0200
	id 0006FC82.43A7CD63.0000605E
Date: Tue, 20 Dec 2005 11:22:42 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
In-Reply-To: <43A7340A.9080101@tm.uka.de>
Message-ID: <Pine.LNX.4.58.0512201116410.32205@wrl-40.cs.helsinki.fi>
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
	<00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
	<43A7340A.9080101@tm.uka.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit
Cc: Georgios Karagiannis <karagian@cs.utwente.nl>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi boys,

two comments:

a) Roland, if you think the paragraph in 5.4.1 needs to be more clear, 
would you send us the proposed text, eg. "switch paragraph X with the 
following".

b) I couldn't find the text where it says that a reduced refresh must
include the PACKET_CLASSIFIER. At least I have not added such text
explicitly, as to me leaving out the PACKET_CLASSIFIER, or at least, leave
it as optional in reduced refreshes, is the way to go.

In general, I would really appreciate that if people send 
comments/questions about unclear/wierd parts of basically any I-D, they 
would also send the proposed text that fixes the problem. Thanks.

Cheers,
Jukka

On Mon, 19 Dec 2005, Roland Bless wrote:

> Hi Georgios,
> >> ------------------------------------------
> >>
> >> 5.4.1
> >>   If the SCOPING flag is set, or if the QNE is the last QNE on the path
> >>   to the destination, the QNE MUST send a RESPONSE message.
> >>
> >> - "is the last QNE on the path to the destination" (isn't this the QNR?)
> >> - if neither ACK nor SCOPING are set and no RII is present
> >>  why MUST (only?) the last QNE generate a RESPONSE?
> >> - we think that a RESPONSE is either triggered by an
> >>  ACK or an RII or an error.
> > 
> > 
> > Georgios:
> > I think that here, the last node can be either the QNR, but it could
> > also be
> > a node that is configured to be the last node, which is not the QNR,
> > e.g., a
> > boundary of a
> > domain. I think that only this last node SHOULD send the RESPONSE,
> > due to the fact that we are also using scoping by configuration, where the
> > SCOPING flag does
> > not have to be set!
> 
> Hmm. this sounds like a special configuration that you have in mind.
> Your proposed behavior would IMHO contradict with the default behavior
> when an RII is set... Nevertheless this paragraph needs clarification.
> 
> >> PACKET_CLASSIFIER:
> >> - is it really necessary to specify the PACKET_CLASSIFIER
> >>  even for reduced refreshes?
> >> - Is the value of the MRM exactly the same as in GISTs MRI?
> >>  What should be done in case of a mismatch?
> >>
> >> -----------------------------------------------
> > 
> > 
> > Georgios:
> > About using the PACKET_CLASSIFIER for reduced refreshes, why should we
> > not use it?
> 
> Because it will not change and is thus redundant.
> 
> > Regarding the MRM, I think taht it should be exactly the same as the
> > GIST MRI, since the
> > QOS-NSLP processing must use the GIST MRI at each node.
> > However, if this is not the same, then the additional paramaters have to
> > be included in
> > the PACKET_CLASSIFIER object.
> 
> Does this really make sense? Any examples or other opinions?
> 
> >> 5.4.3.  RESPONSE Messages
> >>   .....
> >>
> >>   In addition, a RESPONSE message MUST be sent when the ACKNOWLEDGE
> >>   flag is set or when an error occurs while processing a received
> >>   message.  If the received message contains an RII object, this object
> >>   MUST be put in the RESPONSE, as described above.
> >>
> >> - We think that the last sentence should only be true in case
> >>  of an error, but not when an ACK flag is set. In this case
> >>  a RESPONSE should not include the RII (this RESPONSE will usually
> >>  follow from the last QNE later) but the RSN.
> > 
> > Georgios:
> > I think that I agree with your proposal!
> > Other thoughts?
> 
> Yep, more input?
> 
> Regards,
>  Roland.
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 05:01:45 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoeJV-00079C-3R; Tue, 20 Dec 2005 05:01:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoeJU-00078u-63
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 05:01:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04904
	for <nsis@ietf.org>; Tue, 20 Dec 2005 05:00:41 -0500 (EST)
Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoeLo-0005VS-5H
	for nsis@ietf.org; Tue, 20 Dec 2005 05:04:12 -0500
Received: from unknown (unknown [192.168.9.180])
	by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id
	BCB8D180022C
	for <nsis@ietf.org>; Tue, 20 Dec 2005 10:01:24 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.49)
	by wfilter.us4.outblaze.com; 20 Dec 2005 10:01:24 -0000
Received: by ws1-1.us4.outblaze.com (Postfix, from userid 1001)
	id 4C90B83C08; Tue, 20 Dec 2005 10:01:24 +0000 (GMT)
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
From: "Markus Ott" <markus@minister.com>
To: nsis@ietf.org
Date: Tue, 20 Dec 2005 05:01:23 -0500
Subject: Re: [NSIS] How to request a RESERVE with full QSPEC?
Received: from [141.3.70.162] by ws1-1.us4.outblaze.com with http for
	markus@minister.com; Tue, 20 Dec 2005 05:01:23 -0500
X-Originating-Ip: 141.3.70.162
X-Originating-Server: ws1-1.us4.outblaze.com
Message-Id: <20051220100124.4C90B83C08@ws1-1.us4.outblaze.com>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi all,
Because I have not received any answers or proposals to my questions until =
now I'm asking myself:
"Are my questions too complicated or are they outside of the scope of this =
discussion?".
As Jukka proposed "In general, I would really appreciate that if people send
comments/questions about unclear/wierd parts of basically any I-D, they
would also send the proposed text that fixes the problem. Thanks." I'm send=
ing now my proposal to the solution of my question:
Instead of=20

> .......
> When a QNE receives a RESERVE message with an unknown SESSION_ID, it
>     MAY send a NOTIFY message to its upstream peer, indicating the
>     unknown SESSION_ID. If the message was meant as a refresh, the reply
>     indicates a downstream route change to the upstream peer.  The
>     upstream peer SHOULD send a complete RESERVE on the new path (new
>     SII).  It identifies the old signalling association (old SII) and MAY
>     start sending complete RESERVE messages for other SESSION_IDs linked
>     to this association.
> -------------

I would propose the following:

"When a QNE receives a RESERVE message with an unknown SESSION_ID and=20
this message contains no QSPEC because it was meant as a refresh then the
node MUST send a RESPONSE message with an INFO_SPEC that indicates a=20
downstream route change to the upstream peer. The upstream peer SHOULD=20
send a complete RESERVE on the new path (new SII).  It identifies the old=
=20
signalling association (old SII) and MAY start sending complete RESERVE=20
messages for other SESSION_IDs linked to this association."

Of course there must be an appropriate error code added in the draft.
The sending of RESPONSE message instead of NOTIFY is more consistent with t=
he
draft because the following part says:

5.4.4.  NOTIFY Messages
..........................

NOTIFY messages are sent asynchronously, rather than in
response to other messages.

.........................

In my proposal the phrase "...the node MUST send a RESPONSE message..." can
be replaced with "...the node MAY send a RESPONSE message..." if we take in=
to=20
consideration that the upstream node will receive a NetworkNotification (wi=
th the new SII handle)=20
from GIST after sending the RESERVE message and so it will detect the route=
 change before=20
receiving the RESPONSE message.

Regards,
=20
Markus Ott.




----- Original Message -----
From: "Markus Ott" <markus@minister.com>
To: nsis@ietf.org
Subject: [NSIS] How to request a RESERVE with full QSPEC?
Date: Wed, 14 Dec 2005 11:13:59 -0500

>=20
> Hi all,
>=20
> I've got one more question relating to the internet draft of QoS NSLP:
>=20
> it relates to the part
>=20
> "5.4.1.  RESERVE Messages".
>=20
> -------------
> .......
> When a QNE receives a RESERVE message with an unknown SESSION_ID, it
>     MAY send a NOTIFY message to its upstream peer, indicating the
>     unknown SESSION_ID. If the message was meant as a refresh, the reply
>     indicates a downstream route change to the upstream peer.  The
>     upstream peer SHOULD send a complete RESERVE on the new path (new
>     SII).  It identifies the old signalling association (old SII) and MAY
>     start sending complete RESERVE messages for other SESSION_IDs linked
>     to this association.
> -------------
> The questions to this paragraph were already sent by Roland Bless.
> Just one more issue:
> In the sentence "If the message was meant as a refresh, the reply
>     indicates a downstream route change to the upstream peer.": how
>     is the indication of a route change done? Is it done with help
>     of INFO_SPEC? If so then in the list with error values of all error
>     classes there is no appropriate error value to signal this
>     information. The only one (not very suitable for this) is the
>     protocol error with code 0x04: "Mandatory object missing: an
>     object required in a message of this type was missing." But I
>     think we need in this case a special code to notify this. Or what
>     a node must state in this case? Empty message - because the detection=
 of
>     route change is done with help of SII handle?
>     Or is this done in another way? Which one?
>=20
> Regards,
>=20
> Markus Ott.
>=20
> --
> ___________________________________________________
> Play 100s of games for FREE! http://games.mail.com/
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis


--=20
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 05:13:57 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoeVJ-0001Cj-6t; Tue, 20 Dec 2005 05:13:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoeVG-0001B9-W7
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 05:13:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06110
	for <nsis@ietf.org>; Tue, 20 Dec 2005 05:12:52 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoeXa-0005vr-Uc
	for nsis@ietf.org; Tue, 20 Dec 2005 05:16:23 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBKADHUA015478;
	Tue, 20 Dec 2005 10:13:17 GMT
Received: from [193.118.197.110] ([193.118.197.110]) by
	rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Dec 2005 10:13:17 +0000
Message-ID: <43A7D93D.1040505@roke.co.uk>
Date: Tue, 20 Dec 2005 10:13:17 +0000
From: Andrew McDonald <andrew.mcdonald@roke.co.uk>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
In-Reply-To: <43986636.2050508@tm.uka.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2005 10:13:17.0322 (UTC)
	FILETIME=[FEDDFEA0:01C6054D]
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: andrew.mcdonald@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: Jukka MJ Manner <jmanner@cs.Helsinki.FI>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Roland,

Roland Bless wrote:
> ----------------------------------
> 5.4.1.  RESERVE Messages
>    ....
> 
>    When a QNE receives a RESERVE message with an unknown SESSION_ID, it
>    MAY send a NOTIFY message to its upstream peer, indicating the
>    unknown SESSION_ID. If the message was meant as a refresh, the reply
>    indicates a downstream route change to the upstream peer.  The
>    upstream peer SHOULD send a complete RESERVE on the new path (new
>    SII).  It identifies the old signalling association (old SII) and MAY
>    start sending complete RESERVE messages for other SESSION_IDs linked
>    to this association.
> 
> 
> We find this paragraph a little bit strange:
> - the paragraph contradicts with sec 5.4.4:
>   NOTIFY message do do not directly cause other messages to
>   be sent. NOTIFY messages are sent asynchronously, rather than in
>   response to other messages.
> - the purpose of this mechanism is not getting totally clear:
>   if it's only for the case of reduced refreshes along a
>   new path (i.e. QSPEC is missing) then we would propose
>   to sent rather a RESPONSE with an appropriate error code
>   in order to trigger resending a RESERVE with a full QSPEC
>   (this would be more consistent with the NOTIFY definition
>   in 5.4.4).
>   Are there other useful benefits of this proposed NOTIFY?
>   Otherwise even every intial RESERVE would cause such a
>   NOTIFY to be sent by all QNEs.
> - How far should one forward the NOTIFY message?
>   Only one hop? (this is generally not very clear)
>   What about the use of the scoping flag (currently not used)?
> - "If the message was meant as a refresh, the reply..."
>   What reply? do you mean the NOTIFY?
> 
> ------------------------------------------

There may have been some logic to this when it was written, but I can't 
work out what it might have been. Changing this to a RESPONSE message 
seems reasonable to me.

I'm not sure whether it might also be worth noting that the NSLP may 
notify the GIST layer using the InvalidateRoutingState, though this is a 
node-internal action.

regards,

Andrew

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 05:14:54 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EoeWE-0001N8-0y; Tue, 20 Dec 2005 05:14:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EoeWC-0001N1-CK
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 05:14:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06277
	for <nsis@ietf.org>; Tue, 20 Dec 2005 05:13:49 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoeYX-0005zK-LR
	for nsis@ietf.org; Tue, 20 Dec 2005 05:17:21 -0500
Received: from wrl-40.cs.helsinki.fi (wrl-40.cs.helsinki.fi [128.214.166.160])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Tue, 20 Dec 2005 12:14:44 +0200
	id 000700B7.43A7D994.0000369E
Date: Tue, 20 Dec 2005 12:14:44 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Markus Ott <markus@minister.com>
Subject: Re: [NSIS] How to request a RESERVE with full QSPEC?
In-Reply-To: <20051220100124.4C90B83C08@ws1-1.us4.outblaze.com>
Message-ID: <Pine.LNX.4.58.0512201213230.32205@wrl-40.cs.helsinki.fi>
References: <20051220100124.4C90B83C08@ws1-1.us4.outblaze.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi Markus,

Your suggestions sounds pretty good to me. What error code would you like 
to see? Could you send that suggestion too, thanks.

Regards,
Jukka

On Tue, 20 Dec 2005, Markus Ott wrote:

> Hi all,
> Because I have not received any answers or proposals to my questions until now I'm asking myself:
> "Are my questions too complicated or are they outside of the scope of this discussion?".
> As Jukka proposed "In general, I would really appreciate that if people send
> comments/questions about unclear/wierd parts of basically any I-D, they
> would also send the proposed text that fixes the problem. Thanks." I'm sending now my proposal to the solution of my question:
> Instead of 
> 
> > .......
> > When a QNE receives a RESERVE message with an unknown SESSION_ID, it
> >     MAY send a NOTIFY message to its upstream peer, indicating the
> >     unknown SESSION_ID. If the message was meant as a refresh, the reply
> >     indicates a downstream route change to the upstream peer.  The
> >     upstream peer SHOULD send a complete RESERVE on the new path (new
> >     SII).  It identifies the old signalling association (old SII) and MAY
> >     start sending complete RESERVE messages for other SESSION_IDs linked
> >     to this association.
> > -------------
> 
> I would propose the following:
> 
> "When a QNE receives a RESERVE message with an unknown SESSION_ID and 
> this message contains no QSPEC because it was meant as a refresh then the
> node MUST send a RESPONSE message with an INFO_SPEC that indicates a 
> downstream route change to the upstream peer. The upstream peer SHOULD 
> send a complete RESERVE on the new path (new SII).  It identifies the old 
> signalling association (old SII) and MAY start sending complete RESERVE 
> messages for other SESSION_IDs linked to this association."
> 
> Of course there must be an appropriate error code added in the draft.
> The sending of RESPONSE message instead of NOTIFY is more consistent with the
> draft because the following part says:
> 
> 5.4.4.  NOTIFY Messages
> ..........................
> 
> NOTIFY messages are sent asynchronously, rather than in
> response to other messages.
> 
> .........................
> 
> In my proposal the phrase "...the node MUST send a RESPONSE message..." can
> be replaced with "...the node MAY send a RESPONSE message..." if we take into 
> consideration that the upstream node will receive a NetworkNotification (with the new SII handle) 
> from GIST after sending the RESERVE message and so it will detect the route change before 
> receiving the RESPONSE message.
> 
> Regards,
>  
> Markus Ott.
> 
> 
> 
> 
> ----- Original Message -----
> From: "Markus Ott" <markus@minister.com>
> To: nsis@ietf.org
> Subject: [NSIS] How to request a RESERVE with full QSPEC?
> Date: Wed, 14 Dec 2005 11:13:59 -0500
> 
> > 
> > Hi all,
> > 
> > I've got one more question relating to the internet draft of QoS NSLP:
> > 
> > it relates to the part
> > 
> > "5.4.1.  RESERVE Messages".
> > 
> > -------------
> > .......
> > When a QNE receives a RESERVE message with an unknown SESSION_ID, it
> >     MAY send a NOTIFY message to its upstream peer, indicating the
> >     unknown SESSION_ID. If the message was meant as a refresh, the reply
> >     indicates a downstream route change to the upstream peer.  The
> >     upstream peer SHOULD send a complete RESERVE on the new path (new
> >     SII).  It identifies the old signalling association (old SII) and MAY
> >     start sending complete RESERVE messages for other SESSION_IDs linked
> >     to this association.
> > -------------
> > The questions to this paragraph were already sent by Roland Bless.
> > Just one more issue:
> > In the sentence "If the message was meant as a refresh, the reply
> >     indicates a downstream route change to the upstream peer.": how
> >     is the indication of a route change done? Is it done with help
> >     of INFO_SPEC? If so then in the list with error values of all error
> >     classes there is no appropriate error value to signal this
> >     information. The only one (not very suitable for this) is the
> >     protocol error with code 0x04: "Mandatory object missing: an
> >     object required in a message of this type was missing." But I
> >     think we need in this case a special code to notify this. Or what
> >     a node must state in this case? Empty message - because the detection of
> >     route change is done with help of SII handle?
> >     Or is this done in another way? Which one?
> > 
> > Regards,
> > 
> > Markus Ott.
> > 
> > --
> > ___________________________________________________
> > Play 100s of games for FREE! http://games.mail.com/
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> 
> 
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 05:36:31 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eoer9-0006QF-0A; Tue, 20 Dec 2005 05:36:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eoer7-0006Q2-F8
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 05:36:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08317
	for <nsis@ietf.org>; Tue, 20 Dec 2005 05:35:26 -0500 (EST)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoetU-0006ka-Ov
	for nsis@ietf.org; Tue, 20 Dec 2005 05:38:58 -0500
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id jBKAZpUA021540;
	Tue, 20 Dec 2005 10:35:51 GMT
Received: from [193.118.197.110] ([193.118.197.110]) by
	rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 20 Dec 2005 10:35:50 +0000
Message-ID: <43A7DE86.9030906@roke.co.uk>
Date: Tue, 20 Dec 2005 10:35:50 +0000
From: Andrew McDonald <andrew.mcdonald@roke.co.uk>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
Subject: Re: [NSIS] Update on the QoS NSLP work
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi><43986636.2050508@tm.uka.de>
	<00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
In-Reply-To: <00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2005 10:35:50.0928 (UTC)
	FILETIME=[25ADE100:01C60551]
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: andrew.mcdonald@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: Roland Bless <bless@tm.uka.de>, Jukka MJ Manner <jmanner@cs.Helsinki.FI>,
	nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Georgios Karagiannis wrote:
>  > ------------------------------------------
>  >
>  > 5.4.1
>  >   If the SCOPING flag is set, or if the QNE is the last QNE on the path
>  >   to the destination, the QNE MUST send a RESPONSE message.
>  >
>  > - "is the last QNE on the path to the destination" (isn't this the QNR?)
>  > - if neither ACK nor SCOPING are set and no RII is present
>  >  why MUST (only?) the last QNE generate a RESPONSE?
>  > - we think that a RESPONSE is either triggered by an
>  >  ACK or an RII or an error.
> 
> Georgios:
> I think that here, the last node can be either the QNR, but it could also be
> a node that is configured to be the last node, which is not the QNR, e.g., a
> boundary of a
> domain. I think that only this last node SHOULD send the RESPONSE,
> due to the fact that we are also using scoping by configuration, where the
> SCOPING flag does
> not have to be set!

I find that statement a bit confusing. The last node (signalling 
endpoint) is the QNR by definition, but the QNR is not necessarily the 
flow endpoint (receiver/sender). See definitions in section 2, and fig 2 
in particular.

Andrew

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 12:06:04 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eokw8-0003Nr-Jv; Tue, 20 Dec 2005 12:06:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eokw6-0003Nc-I5
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 12:06:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01097
	for <nsis@ietf.org>; Tue, 20 Dec 2005 12:04:59 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX183syGLv9A+1TQGbMj4EqdoF2tvRRSlTuY=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EokyX-0005E7-Oj
	for nsis@ietf.org; Tue, 20 Dec 2005 12:08:35 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1Eokvs-0007pk-VW; Tue, 20 Dec 2005 18:05:55 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id B13BAB4D3;
	Tue, 20 Dec 2005 18:05:48 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1Eokvs-00084z-6M; Tue, 20 Dec 2005 18:05:48 +0100
Message-ID: <43A839EB.2090800@tm.uka.de>
Date: Tue, 20 Dec 2005 18:05:47 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] How to request a RESERVE with full QSPEC?
References: <20051220100124.4C90B83C08@ws1-1.us4.outblaze.com>
	<Pine.LNX.4.58.0512201213230.32205@wrl-40.cs.helsinki.fi>
In-Reply-To: <Pine.LNX.4.58.0512201213230.32205@wrl-40.cs.helsinki.fi>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.1 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.3 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Jukka,

Jukka MJ Manner wrote:

> Your suggestions sounds pretty good to me. What error code would you like 
> to see? Could you send that suggestion too, thanks.

We would propose to use something like
Transient (0x04) and within that class (0x11): "Full QSPEC required"
(or "Re-send RESERVE with full QSPEC"?)
BTW: is it intentional that the code is increased like 0x08, 0x09, 0x10
instead of 0x08, 0x09, 0x0A, 0x0B, and so on?


> On Tue, 20 Dec 2005, Markus Ott wrote:

>>"When a QNE receives a RESERVE message with an unknown SESSION_ID and 
>>this message contains no QSPEC because it was meant as a refresh then the
>>node MUST send a RESPONSE message with an INFO_SPEC that indicates a 
>>downstream route change to the upstream peer. The upstream peer SHOULD 
>>send a complete RESERVE on the new path (new SII).  It identifies the old 
>>signalling association (old SII) and MAY start sending complete RESERVE 
>>messages for other SESSION_IDs linked to this association."

New proposal:
"When a QNE receives a RESERVE message with an unknown SESSION_ID and
this message contains no QSPEC because it was meant as a refresh then
the node MUST send a RESPONSE message with an INFO_SPEC that indicates a
missing QSPEC to the upstream peer ("Full QSPEC required"). The upstream
peer SHOULD send a complete RESERVE (i.e. one containing a QSPEC) on the
new path (new SII)."

I'm not sure about the correctness of the following approach:
"It identifies the old signalling association (old
SII) and MAY start sending complete RESERVE messages for other
SESSION_IDs linked to this association."

So I'm not sure about the applicability of this statement, because
a rerouting event may only affect a particular flow, thus
it is not guaranteed that other sessions are also re-routed
along the new association?

Regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Dec 20 15:56:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EooWz-0000tr-6V; Tue, 20 Dec 2005 15:56:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EooWx-0000tk-Mt
	for nsis@megatron.ietf.org; Tue, 20 Dec 2005 15:56:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06149
	for <nsis@ietf.org>; Tue, 20 Dec 2005 15:55:15 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EooZQ-00068m-Op
	for nsis@ietf.org; Tue, 20 Dec 2005 15:58:54 -0500
Received: from sbz-30.cs.helsinki.fi (sbz-30.cs.helsinki.fi [128.214.9.98])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Tue, 20 Dec 2005 22:56:16 +0200
	id 00070148.43A86FF0.00007F50
Date: Tue, 20 Dec 2005 22:56:16 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] How to request a RESERVE with full QSPEC?
In-Reply-To: <43A839EB.2090800@tm.uka.de>
Message-ID: <Pine.LNX.4.58.0512202253050.8376@sbz-30.cs.Helsinki.FI>
References: <20051220100124.4C90B83C08@ws1-1.us4.outblaze.com>
	<Pine.LNX.4.58.0512201213230.32205@wrl-40.cs.helsinki.fi>
	<43A839EB.2090800@tm.uka.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi Roland, Markus,

Your suggestions sound, yet again, good to me. The statement about other
flows may follow the new route sounds like a "possible" optimization, but
I don't think we want to imply that within this spec - as you said, flows
should be independent by default. The only case I can see where the
session relation could happen is when you have used the BOUND_SESSION_ID
object. But I'm happy leaving that statement out.

Cheers,
Jukka

On Tue, 20 Dec 2005, Roland Bless wrote:

> Hi Jukka,
> 
> Jukka MJ Manner wrote:
> 
> > Your suggestions sounds pretty good to me. What error code would you like 
> > to see? Could you send that suggestion too, thanks.
> 
> We would propose to use something like
> Transient (0x04) and within that class (0x11): "Full QSPEC required"
> (or "Re-send RESERVE with full QSPEC"?)
> BTW: is it intentional that the code is increased like 0x08, 0x09, 0x10
> instead of 0x08, 0x09, 0x0A, 0x0B, and so on?
> 
> 
> > On Tue, 20 Dec 2005, Markus Ott wrote:
> 
> >>"When a QNE receives a RESERVE message with an unknown SESSION_ID and 
> >>this message contains no QSPEC because it was meant as a refresh then the
> >>node MUST send a RESPONSE message with an INFO_SPEC that indicates a 
> >>downstream route change to the upstream peer. The upstream peer SHOULD 
> >>send a complete RESERVE on the new path (new SII).  It identifies the old 
> >>signalling association (old SII) and MAY start sending complete RESERVE 
> >>messages for other SESSION_IDs linked to this association."
> 
> New proposal:
> "When a QNE receives a RESERVE message with an unknown SESSION_ID and
> this message contains no QSPEC because it was meant as a refresh then
> the node MUST send a RESPONSE message with an INFO_SPEC that indicates a
> missing QSPEC to the upstream peer ("Full QSPEC required"). The upstream
> peer SHOULD send a complete RESERVE (i.e. one containing a QSPEC) on the
> new path (new SII)."
> 
> I'm not sure about the correctness of the following approach:
> "It identifies the old signalling association (old
> SII) and MAY start sending complete RESERVE messages for other
> SESSION_IDs linked to this association."
> 
> So I'm not sure about the applicability of this statement, because
> a rerouting event may only affect a particular flow, thus
> it is not guaranteed that other sessions are also re-routed
> along the new association?
> 
> Regards,
>  Roland
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 21 05:39:56 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep1O0-0001If-54; Wed, 21 Dec 2005 05:39:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep1Ny-0001IN-Cr
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 05:39:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21956
	for <nsis@ietf.org>; Wed, 21 Dec 2005 05:38:49 -0500 (EST)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep1QY-0006w6-BN
	for nsis@ietf.org; Wed, 21 Dec 2005 05:42:35 -0500
Received: from mail3.siemens.de (localhost [127.0.0.1])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id jBLAdkqR032303;
	Wed, 21 Dec 2005 11:39:46 +0100
Received: from mhpahx0c.ww002.siemens.net (mhpahx0c.ww002.siemens.net
	[139.25.165.42])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id jBLAdkZg022538;
	Wed, 21 Dec 2005 11:39:46 +0100
Received: from blns00fa.ww002.siemens.net ([147.54.45.102]) by
	mhpahx0c.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Dec 2005 11:39:46 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 Dec 2005 11:39:45 +0100
Message-ID: <391E6FBF5E786940B9E2F7CA6376C708DE469C@blns00fa.ww002.siemens.net>
Thread-Topic: QOSM IANA Status / NSIS Extensibility Doc on QOSMs
Thread-Index: AcYGGtu4bcmLfQvLSgugBRwOwZdaRQ==
From: "Kappler, Cornelia" <cornelia.kappler@siemens.com>
To: <john.loughney@nokia.com>
X-OriginalArrivalTime: 21 Dec 2005 10:39:46.0247 (UTC)
	FILETIME=[DC5A7570:01C6061A]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>, nsis@ietf.org,
	"Attila Bader \(ETH\)" <Attila.Bader@ericsson.com>
Subject: [NSIS] QOSM IANA Status / NSIS Extensibility Doc on QOSMs
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1342464099=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1342464099==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6061A.DBD429CE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6061A.DBD429CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi John,=20

when studying the NSIS Ext. ID I noticed the text in Sec. 5 needs to be
updated. It is too unprecise currently.=20

It says: "New QSPECs require IETF action which defines the elements
within the QSPEC".=20

(i) it probably should be "QoS Models" rather than QSPECs. One could go
on and say how new QSPEC parameters (elements???) are defined but this
is detailed in the QSPEC ID so it should suffice to provide a pointer.=20

(ii) "IETF Action" what exactly is that? I've recently been studying the
IANA RFC 2434 and this is not defined there. Or is this vague on purpose
/ defined elsewhere?

Along the same lines, when updating the QSPEC IANA section we were
wondering what kind of IETF action is required for defining new QOSMs /
QOSM IDs: Will the QOSM IDs be informational RFCs (=3D> "specification
required" or "IETF Consensus" in IANA language !?) or standards track
(=3D> "standards action" in IANA language)? We are currently assuming it
is just "specification required" and updated the QSPEC ID accordingly.
Note this implies that new  _optional_ QSPEC parameters will receive
this same IANA treatment because they can be defined by QOSMs. (New
_mandatory_ QSPEC parameters would require standards action, because
they "MUST be interpreted" by all QNEs)

My proposal for new text in the NSIS Ext ID is "New QoS Models can be
defined by providing a specification. A new QoS Model would define the
QoS parameters to be carried in the QSPEC. For details see [QSPEC ID]".=20

Best regards, Cornelia

------_=_NextPart_001_01C6061A.DBD429CE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7232.55">
<TITLE>QOSM IANA Status / NSIS Extensibility Doc on QOSMs</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Hi John, =
</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">when studying the =
NSIS Ext. ID I noticed the text in Sec. 5 needs to be updated. It is too =
unprecise currently. </FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">It says: &quot;New =
QSPECs require IETF action which defines the elements within the =
QSPEC&quot;. </FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">(i) it probably =
should be &quot;QoS Models&quot; rather than QSPECs. One could go on and =
say how new QSPEC parameters (elements???) are defined but this is =
detailed in the QSPEC ID so it should suffice to provide a pointer. =
</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">(ii) &quot;IETF =
Action&quot; what exactly is that? I've recently been studying the IANA =
RFC 2434 and this is not defined there. Or is this vague on purpose / =
defined elsewhere?</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Along the same lines, =
when updating the QSPEC IANA section we were wondering what kind of IETF =
action is required for defining new QOSMs / QOSM IDs: Will the QOSM IDs =
be informational RFCs (=3D&gt; &quot;specification required&quot; or =
&quot;IETF Consensus&quot; in IANA language !?) or standards track =
(=3D&gt; &quot;standards action&quot; in IANA language)? We are =
currently assuming it is just &quot;specification required&quot; and =
updated the QSPEC ID accordingly. Note this implies that new&nbsp; =
_optional_ QSPEC parameters will receive this same IANA treatment =
because they can be defined by QOSMs. (New _mandatory_ QSPEC parameters =
would require standards action, because they &quot;MUST be =
interpreted&quot; by all QNEs)</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">My proposal for new =
text in the NSIS Ext ID is &quot;New QoS Models can be defined by =
providing a specification. A new QoS Model would define the QoS =
parameters to be carried in the QSPEC. For details see [QSPEC ID]&quot;. =
</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Best regards, =
Cornelia</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C6061A.DBD429CE--


--===============1342464099==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--===============1342464099==--




From nsis-bounces@ietf.org Wed Dec 21 09:15:36 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep4ki-0002Nv-B9; Wed, 21 Dec 2005 09:15:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep4kg-0002Ng-Vy
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 09:15:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17844
	for <nsis@ietf.org>; Wed, 21 Dec 2005 09:14:30 -0500 (EST)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX18ue8Rwc53TzVt2HeNYdo1LiDCYHR4DswY=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep4nJ-0006Jq-DH
	for nsis@ietf.org; Wed, 21 Dec 2005 09:18:18 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1Ep2zn-0000IZ-Hl; Wed, 21 Dec 2005 13:23:10 +0100
Received: from vorta.ipv6.tm.uni-karlsruhe.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:207:e9ff:fe0c:5e44])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 6C3BFB4ED;
	Wed, 21 Dec 2005 13:23:03 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by vorta.ipv6.tm.uni-karlsruhe.de with esmtp (Exim 4.44)
	id 1Ep2zn-0002yy-7E; Wed, 21 Dec 2005 13:23:03 +0100
Message-ID: <43A94926.6080301@tm.uka.de>
Date: Wed, 21 Dec 2005 13:23:02 +0100
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Subject: Re: [NSIS] Update on the QoS NSLP work
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
	<00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
	<43A7340A.9080101@tm.uka.de>
	<Pine.LNX.4.58.0512201116410.32205@wrl-40.cs.helsinki.fi>
In-Reply-To: <Pine.LNX.4.58.0512201116410.32205@wrl-40.cs.helsinki.fi>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.1 (----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	0.3 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: Georgios Karagiannis <karagian@cs.utwente.nl>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Jukka
> two comments:
> 
> a) Roland, if you think the paragraph in 5.4.1 needs to be more clear, 
> would you send us the proposed text, eg. "switch paragraph X with the 
> following".

I thought it would be good to hear the reasons why the text was
included. Georgious gave some hints.

> b) I couldn't find the text where it says that a reduced refresh must
> include the PACKET_CLASSIFIER. At least I have not added such text
> explicitly, as to me leaving out the PACKET_CLASSIFIER, or at least, leave
> it as optional in reduced refreshes, is the way to go.

I gues that there is no such text, but:
it stems from the inconsistency between the definition
of RESERVE messages in 5.1.2.1. and 5.4.1. In the latter section
PACKET_CLASSIFIER is not optional so one cannot leave it out for
refreshes.

5.1.2.1.  RESERVE

   The format of a RESERVE message is as follows:


   RESERVE = COMMON_HEADER
             RSN [ RII ] [ REFRESH_PERIOD ] [ BOUND_SESSION_ID ]
             [ POLICY_DATA ] *2QSPEC




5.4.1

   RESERVE = COMMON_HEADER
             RSN PACKET_CLASSIFIER [ RII ]
             [ REFRESH_PERIOD ] [ BOUND_SESSION_ID ]
             [ POLICY_DATA ] *2QSPEC

I suggest to check the other copies of the format in section 5.4 as
well.

> In general, I would really appreciate that if people send 
> comments/questions about unclear/wierd parts of basically any I-D, they 
> would also send the proposed text that fixes the problem. Thanks.

We'll do that. However, we thought it would be good to hear
any reasons why certain features are included instead of simply
omitting things.

Regards,
 Roland

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 21 12:01:57 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep7Lh-0008SQ-OI; Wed, 21 Dec 2005 12:01:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep7Lf-0008SE-Sy
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 12:01:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15572
	for <nsis@ietf.org>; Wed, 21 Dec 2005 12:00:50 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep7OI-0005JQ-L4
	for nsis@ietf.org; Wed, 21 Dec 2005 12:04:41 -0500
Received: from sbz-30.cs.helsinki.fi (sbz-30.cs.helsinki.fi [128.214.9.98])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 21 Dec 2005 19:01:48 +0200
	id 000701E6.43A98A7C.00002507
Date: Wed, 21 Dec 2005 19:01:48 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] Update on the QoS NSLP work
In-Reply-To: <43A94926.6080301@tm.uka.de>
Message-ID: <Pine.LNX.4.58.0512211900360.6102@sbz-30.cs.Helsinki.FI>
References: <Pine.LNX.4.58.0512071156480.22244@wrl-40.cs.helsinki.fi>
	<43986636.2050508@tm.uka.de>
	<00ee01c600b7$13107a60$4c0d5982@dynamic.ewi.utwente.nl>
	<43A7340A.9080101@tm.uka.de>
	<Pine.LNX.4.58.0512201116410.32205@wrl-40.cs.helsinki.fi>
	<43A94926.6080301@tm.uka.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: Georgios Karagiannis <karagian@cs.utwente.nl>, nsis@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi boys,

I'll try to fix the question b. I'll let Georgios think about the question
a.

Cheers,
Jukka

On Wed, 21 Dec 2005, Roland Bless wrote:

> Hi Jukka
> > two comments:
> > 
> > a) Roland, if you think the paragraph in 5.4.1 needs to be more clear, 
> > would you send us the proposed text, eg. "switch paragraph X with the 
> > following".
> 
> I thought it would be good to hear the reasons why the text was
> included. Georgious gave some hints.
> 
> > b) I couldn't find the text where it says that a reduced refresh must
> > include the PACKET_CLASSIFIER. At least I have not added such text
> > explicitly, as to me leaving out the PACKET_CLASSIFIER, or at least, leave
> > it as optional in reduced refreshes, is the way to go.
> 
> I gues that there is no such text, but:
> it stems from the inconsistency between the definition
> of RESERVE messages in 5.1.2.1. and 5.4.1. In the latter section
> PACKET_CLASSIFIER is not optional so one cannot leave it out for
> refreshes.
> 
> 5.1.2.1.  RESERVE
> 
>    The format of a RESERVE message is as follows:
> 
> 
>    RESERVE = COMMON_HEADER
>              RSN [ RII ] [ REFRESH_PERIOD ] [ BOUND_SESSION_ID ]
>              [ POLICY_DATA ] *2QSPEC
> 
> 
> 
> 
> 5.4.1
> 
>    RESERVE = COMMON_HEADER
>              RSN PACKET_CLASSIFIER [ RII ]
>              [ REFRESH_PERIOD ] [ BOUND_SESSION_ID ]
>              [ POLICY_DATA ] *2QSPEC
> 
> I suggest to check the other copies of the format in section 5.4 as
> well.
> 
> > In general, I would really appreciate that if people send 
> > comments/questions about unclear/wierd parts of basically any I-D, they 
> > would also send the proposed text that fixes the problem. Thanks.
> 
> We'll do that. However, we thought it would be good to hear
> any reasons why certain features are included instead of simply
> omitting things.
> 
> Regards,
>  Roland
> 

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 21 13:24:21 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep8dR-0002aI-J7; Wed, 21 Dec 2005 13:24:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep8dQ-0002Zu-46
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 13:24:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27166
	for <nsis@ietf.org>; Wed, 21 Dec 2005 13:23:16 -0500 (EST)
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep8g3-0008MR-H4
	for nsis@ietf.org; Wed, 21 Dec 2005 13:27:05 -0500
Received: from sbz-30.cs.helsinki.fi (sbz-30.cs.helsinki.fi [128.214.9.98])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 21 Dec 2005 20:24:15 +0200
	id 000700D6.43A99DCF.000001EE
Date: Wed, 21 Dec 2005 20:24:15 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: nsis@ietf.org
Message-ID: <Pine.LNX.4.58.0512211910330.6595@sbz-30.cs.Helsinki.FI>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Subject: [NSIS] New diff of QoS NSLP
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


Hi all,
 
I've made a new diff of the QoS NSLP. It is available from:
 
http://www.cs.helsinki.fi/u/jmanner/diff-qosnslp-08-09.html

(Note: htmlwdiff gets mixed up around section 5.1.3.7...)
 
This version includes fixes due to comments from Roland and Markus Ott,
Xiaoming, Jerry, Georgios, Andrew, and Bernd Schloer.

The most notable changes include allowing multiple BOUND_SESSION_ID
objects in a message, and fixes&clarfications to the INFO_SPEC object.
I've added new stuff into the INFO_SPEC specification, as it was missing
the description of how a QNE can include additional information into the
INFO_SPEC, eg., tell which object was erroneous (this was copied from 
GIST and modified to fit the QoS NSLP).

I've also tried to clarify which objects are mandatory, and which optional
in certain cases.


I'll be having my Christmas holidays from now on, which includes no email
access. :)

I'll check my emails next week. If you have questions, hopefully someone 
else answers, yet, if you have suggestions for clarfications, please 
provide the new text, too. Thanks.

If there are no complex and difficult comments, we'll try to go for WGLC 
right after new year.


Cheers and have relaxing holidays,
Jukka

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 21 14:07:01 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep9Ij-0001PI-Da; Wed, 21 Dec 2005 14:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ep9Ii-0001Nr-4y; Wed, 21 Dec 2005 14:07:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01909;
	Wed, 21 Dec 2005 14:05:56 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ep9LO-0001Lt-2t; Wed, 21 Dec 2005 14:09:46 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jBLJ6Lw29065;
	Wed, 21 Dec 2005 11:06:21 -0800 (PST)
Message-Id: <200512211906.jBLJ6Lw29065@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 21 Dec 2005 11:06:21 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
Subject: [NSIS] RFC 4230 on RSVP Security Properties
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 4230

        Title:      RSVP Security Properties
        Author(s):  H. Tschofenig, R. Graveman
        Status:     Informational
        Date:       December 2005
        Mailbox:    Hannes.Tschofenig@siemens.com, rfg@acm.org
        Pages:      48
        Characters: 121030
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nsis-rsvp-sec-properties-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4230.txt


This document summarizes the security properties of RSVP.  The goal
of this analysis is to benefit from previous work done on RSVP and to
capture knowledge about past activities.

This document is a product of the Next Steps in Signaling Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <051221110432.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4230

--OtherAccess
Content-Type: Message/External-body; name="rfc4230.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <051221110432.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--NextPart--




From nsis-bounces@ietf.org Wed Dec 21 15:51:41 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpAw1-00072Y-Jl; Wed, 21 Dec 2005 15:51:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpAuc-0006QE-6z; Wed, 21 Dec 2005 15:50:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19548;
	Wed, 21 Dec 2005 15:49:09 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EpAx9-0006gN-1X; Wed, 21 Dec 2005 15:52:52 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EpAuR-0005Zi-1a; Wed, 21 Dec 2005 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EpAuR-0005Zi-1a@newodin.ietf.org>
Date: Wed, 21 Dec 2005 15:50:03 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-08.txt 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Steps in Signaling Working Group of the IETF.

	Title		: QoS-NSLP QSPEC Template
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-nsis-qspec-08.txt
	Pages		: 47
	Date		: 2005-12-21
	
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This draft defines a template for
   the QSPEC, which contains both the QoS description and QSPEC control
   information. The QSPEC format is defined, as are a number of QSPEC
   parameters.  The QSPEC parameters provide a common language to be
   re-used in several QOSMs.  To a certain extent QSPEC parameters
   ensure interoperability of QOSMs.  Optional QSPEC parameters aim to
   ensure the extensibility of QoS NSLP to other QOSMs in the future.
   The node initiating the NSIS signaling adds an Initiator QSPEC that
   must not be removed, thereby ensuring the intention of the NSIS
   initiator is preserved along the signaling path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-nsis-qspec-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-qspec-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-12-21151226.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-qspec-08.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-nsis-qspec-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-12-21151226.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--NextPart--




From nsis-bounces@ietf.org Wed Dec 21 16:21:41 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpBP3-0006Q3-Ba; Wed, 21 Dec 2005 16:21:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpBP1-0006PG-UR
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 16:21:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03483
	for <nsis@ietf.org>; Wed, 21 Dec 2005 16:20:32 -0500 (EST)
Received: from mail120.messagelabs.com ([216.82.255.211])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EpBRb-00030t-UG
	for nsis@ietf.org; Wed, 21 Dec 2005 16:24:24 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-5.tower-120.messagelabs.com!1135200073!9014352!5
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 14840 invoked from network); 21 Dec 2005 21:21:21 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4)
	by server-5.tower-120.messagelabs.com with SMTP;
	21 Dec 2005 21:21:21 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by
	attrh3i.attrh.att.com (7.2.052)
	id 43A3035900092638 for nsis@ietf.org; Wed, 21 Dec 2005 16:21:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Dec 2005 15:21:20 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA980C@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-nsis-qspec-08.txt 
Thread-Index: AcYGcWKyaxn5Q8jlS567RUEemN+1cAAAe+9A
From: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
To: <nsis@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Subject: [NSIS] RE: I-D ACTION:draft-ietf-nsis-qspec-08.txt 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi All,

Please review and comment on the updated 'QoS-NSLP QSPEC Template' I-D
at http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-08.txt.

The updates include the following:

1. update to 'RSVP-style' reservation in Section 6.1.2 to mirror what is
done in RSVP
2. modified text (from David Black) on DiffServ QSPEC example in Section
6.2
3. update to general QSPEC parameter formats in Section 7.1 (length
restrictions, etc.)
4. re-numbered QSPEC parameter IDs in Section 7.2
5. modified <Excess Treatment> parameter values in Section 7.2.2
6. update to reservation priority Section 7.2.7
7. specify the 3 "STATS" in the <Path Jitter> parameter, Section 7.2.9.4
8. minor updates to IANA Considerations Section 9

There are no open issues currently identified.

Please review and comment.

Thanks,
Regards,
Jerry

-----Original Message-----
From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Wednesday, December 21, 2005 3:50 PM
To: i-d-announce@ietf.org
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-08.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Next Steps in Signaling Working Group
of the IETF.

	Title		: QoS-NSLP QSPEC Template
	Author(s)	: J. Ash, et al.
	Filename	: draft-ietf-nsis-qspec-08.txt
	Pages		: 47
	Date		: 2005-12-21
=09
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This draft defines a template for
   the QSPEC, which contains both the QoS description and QSPEC control
   information. The QSPEC format is defined, as are a number of QSPEC
   parameters.  The QSPEC parameters provide a common language to be
   re-used in several QOSMs.  To a certain extent QSPEC parameters
   ensure interoperability of QOSMs.  Optional QSPEC parameters aim to
   ensure the extensibility of QoS NSLP to other QOSMs in the future.
   The node initiating the NSIS signaling adds an Initiator QSPEC that
   must not be removed, thereby ensuring the intention of the NSIS
   initiator is preserved along the signaling path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-08.txt

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Dec 21 21:54:54 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpGbW-0000p9-TM; Wed, 21 Dec 2005 21:54:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpGbV-0000of-Os
	for nsis@megatron.ietf.org; Wed, 21 Dec 2005 21:54:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15834
	for <nsis@ietf.org>; Wed, 21 Dec 2005 21:53:46 -0500 (EST)
Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.24] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpGeA-0000ko-7C
	for nsis@ietf.org; Wed, 21 Dec 2005 21:57:41 -0500
Received: From wagner With LocalMail ; Thu, 22 Dec 2005 13:54:40 +1100 
From: Muhammad Ali Malik <mamalik@cse.unsw.edu.au>
To: nsis@ietf.org
Date: Thu, 22 Dec 2005 13:54:40 +1100 (EST)
X-X-Sender: mamalik@wagner.orchestra.cse.unsw.EDU.AU
Message-ID: <Pine.LNX.4.61.0512221353590.23770@wagner.orchestra.cse.unsw.EDU.AU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [NSIS] scalability problem by trigger messages
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

There are lot of extension of RSVP and other signaling protocol to reduce
the frequency of refresh messages, but is it also necessary to reduce the
frequency of TRIGGER messages ? The trigger messages are those which have
reuested for new or update reservation, while refresh messages are those
which do not change the reservation.

Do the trigger messages impose processing and signaling overheads on 
routers
and links. Can anybody state the situation where there is scalability
problem by the trigger messages. Any document discussing the problem by
tigger messages are much appreciate. How can we reduce the frequency by
trigger messages, any thought.

Regards,
=Malik

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Thu Dec 22 03:48:11 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpM7P-0003WR-7F; Thu, 22 Dec 2005 03:48:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpM7N-0003Vo-1S
	for nsis@megatron.ietf.org; Thu, 22 Dec 2005 03:48:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15093
	for <nsis@ietf.org>; Thu, 22 Dec 2005 03:47:04 -0500 (EST)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpMA9-00024t-7C
	for nsis@ietf.org; Thu, 22 Dec 2005 03:51:02 -0500
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id jBM8lsPq017023
	for <nsis@ietf.org>; Thu, 22 Dec 2005 09:47:54 +0100 (MET)
Message-ID: <00b701c606d4$6794db80$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <nsis@ietf.org>
References: <Pine.LNX.4.58.0512211910330.6595@sbz-30.cs.Helsinki.FI>
Date: Thu, 22 Dec 2005 09:47:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -5.638 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0b5
	(denhaag.ewi.utwente.nl [130.89.10.11]);
	Thu, 22 Dec 2005 09:47:55 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Subject: [NSIS] happy new year
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Dear all

I wish to you and to your families 
 very nice Christmas holidays and a 

Happy New Year!

Best Regards,
Georgios

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 23 00:00:04 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Epf2C-00048C-BH; Fri, 23 Dec 2005 00:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Epf2A-00047h-Nz
	for nsis@megatron.ietf.org; Fri, 23 Dec 2005 00:00:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24806
	for <nsis@ietf.org>; Thu, 22 Dec 2005 23:58:54 -0500 (EST)
Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.24] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Epf55-0002du-JB
	for nsis@ietf.org; Fri, 23 Dec 2005 00:03:04 -0500
Received: From mustafa ([129.94.172.200] == mustafa.cse.unsw.EDU.AU)
	(for <nsis@ietf.org>) By note With Smtp ;
	Fri, 23 Dec 2005 15:59:53 +1100 
From: "Muhammad Ali Malik" <mamalik@cse.unsw.edu.au>
To: <nsis@ietf.org>
Date: Fri, 23 Dec 2005 15:59:47 +1100
Message-ID: <002101c6077d$b3769f80$c8ac5e81@mustafa>
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Subject: [NSIS] scaling problem by trigger messages ...
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1782031919=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1782031919==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001E_01C607D9.E5CDB840"

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C607D9.E5CDB840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

The RFC states that: " On the other hand, in many of the new =
applications for which a
   signaling protocol is required, the user session duration can be
   relatively short.  The dynamics of adding/dropping user sessions
   could introduce a large number of "triggered" messages in the
   network.  This can clearly introduce a substantial amount of
   processing overhead to the routers.  This is one area where a new
   signaling protocol may be needed to reduce the processing complexity
   in the resource reservation process."

Can anybody please elaborate the situation where there is overheads =
because of trigger messages and not by the refresh message. Apart from =
processing overheads, the trigger messages also exhibit signaling =
overheads. But i hardly seen any documents addressing the issues by =
trigger messages only and not by the refresh messages. How does NSIS =
address the issue of overheads due to trigger messages.

Regards,

=3DMalik
------=_NextPart_000_001E_01C607D9.E5CDB840
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The RFC states that: "<!--StartFragment =
--><FONT=20
face=3D"Times New Roman" size=3D3> </FONT><TT><FONT size=3D3>On the =
other hand, in=20
many of the new applications for which a<BR>&nbsp;&nbsp; signaling =
protocol is=20
required, the user session duration can be<BR>&nbsp;&nbsp; relatively=20
short.&nbsp; The dynamics of adding/dropping user =
sessions<BR>&nbsp;&nbsp; could=20
introduce a large number of "triggered" messages in the<BR>&nbsp;&nbsp;=20
network.&nbsp; This can clearly introduce a substantial amount=20
of<BR>&nbsp;&nbsp; processing overhead to the routers.&nbsp; This is one =
area=20
where a new<BR>&nbsp;&nbsp; signaling protocol may be needed to reduce =
the=20
processing complexity<BR>&nbsp;&nbsp; in the resource reservation=20
process."</FONT></TT></FONT></DIV>
<DIV><FONT face=3DArial size=3D3><TT></TT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D3><TT>Can anybody please elaborate the =
situation=20
where there is overheads because of trigger messages and not by the =
refresh=20
message. Apart from processing overheads, the trigger messages also =
exhibit=20
signaling overheads. But i hardly seen any documents addressing the =
issues by=20
trigger messages only and not by the refresh messages. How does NSIS =
address the=20
issue of overheads due to trigger messages.</TT></FONT></DIV>
<DIV><FONT face=3DArial size=3D3><TT></TT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D3><TT>Regards,</TT></FONT></DIV>
<DIV><FONT face=3DArial size=3D3><TT></TT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D3><TT>=3DMalik</TT></FONT></DIV></BODY></HTML>

------=_NextPart_000_001E_01C607D9.E5CDB840--



--===============1782031919==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

--===============1782031919==--





From nsis-bounces@ietf.org Fri Dec 23 02:14:45 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eph8W-0001GV-RC; Fri, 23 Dec 2005 02:14:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eph8V-0001Fb-0A
	for nsis@megatron.ietf.org; Fri, 23 Dec 2005 02:14:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05953
	for <nsis@ietf.org>; Fri, 23 Dec 2005 02:13:34 -0500 (EST)
From: john.loughney@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EphBQ-0006eu-ON
	for nsis@ietf.org; Fri, 23 Dec 2005 02:17:46 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBN7ER6G016533; Fri, 23 Dec 2005 09:14:32 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Dec 2005 09:13:25 +0200
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Dec 2005 09:13:26 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] scaling problem by trigger messages ...
Date: Fri, 23 Dec 2005 09:13:25 +0200
Message-ID: <1AA39B75171A7144A73216AED1D7478D6CED5D@esebe100.NOE.Nokia.com>
Thread-Topic: [NSIS] scaling problem by trigger messages ...
Thread-Index: AcYHfjOsnu+l3Q2+Rnupv71E3BiC3AAEiJNA
To: <mamalik@cse.unsw.edu.au>, <nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2005 07:13:26.0510 (UTC)
	FILETIME=[5E4800E0:01C60790]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Malik,
=20
Which RFC are you refering to?
=20
John


________________________________

	From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On
Behalf Of ext Muhammad Ali Malik
	Sent: 23 December, 2005 07:00
	To: nsis@ietf.org
	Subject: [NSIS] scaling problem by trigger messages ...
=09
=09
	Hi,
	=20
	The RFC states that: " On the other hand, in many of the new
applications for which a
	   signaling protocol is required, the user session duration can
be
	   relatively short.  The dynamics of adding/dropping user
sessions
	   could introduce a large number of "triggered" messages in the
	   network.  This can clearly introduce a substantial amount of
	   processing overhead to the routers.  This is one area where a
new
	   signaling protocol may be needed to reduce the processing
complexity
	   in the resource reservation process."
	=20
	Can anybody please elaborate the situation where there is
overheads because of trigger messages and not by the refresh message.
Apart from processing overheads, the trigger messages also exhibit
signaling overheads. But i hardly seen any documents addressing the
issues by trigger messages only and not by the refresh messages. How
does NSIS address the issue of overheads due to trigger messages.
	=20
	Regards,
	=20
	=3DMalik


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 23 04:47:39 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpjWU-000290-VW; Fri, 23 Dec 2005 04:47:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpjWT-00028r-J5
	for nsis@megatron.ietf.org; Fri, 23 Dec 2005 04:47:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19466
	for <nsis@ietf.org>; Fri, 23 Dec 2005 04:46:31 -0500 (EST)
From: Pasi.Eronen@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpjZS-0002uY-8I
	for nsis@ietf.org; Fri, 23 Dec 2005 04:50:43 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	jBN9kQIE013825; Fri, 23 Dec 2005 11:46:30 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Dec 2005 11:46:30 +0200
Received: from esebe105.NOE.Nokia.com ([172.21.143.53]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 23 Dec 2005 11:46:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] TLS in the GIST draft
Date: Fri, 23 Dec 2005 11:46:29 +0200
Message-ID: <B356D8F434D20B40A8CEDAEC305A1F2401FDB95A@esebe105.NOE.Nokia.com>
In-Reply-To: <A632AD91CF90F24A87C42F6B96ADE5C57EBCEA@rsys005a.comm.ad.roke.co.uk>
Thread-Topic: [NSIS] TLS in the GIST draft
Thread-Index: AcXTbmmrzpaKZGvORFOnk1y3buFk+AQcsdvABz7U8jABsZtZ4A==
To: <robert.hancock@roke.co.uk>, <nsis@ietf.org>
X-OriginalArrivalTime: 23 Dec 2005 09:46:29.0990 (UTC)
	FILETIME=[C00FD860:01C607A5]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Robert,

A couple of comments:

- I don't think we need to make the RC4-based ciphersuites
mandatory; 3DES and AES will do just fine.

- Using TLS with server-only (Responding node only) authentication
sounds quite strange in this situation. To me it looks like
authenticating the querying node would be much more important... =20
so the default mandatory-to-implement mechanism should do mutual
authentication.

- The requirement ".. identity hints about the peer, these SHOULD be
derived from the Peer-Identity provided..." is a bit strange. =20

The spec says that the Peer-Identity is just an opaque octet string,
and nodes are free to choose it however they want, as long as it has
a "high probability of uniqueness". E.g. a sufficiently long and
properly generated random number would do. But clearly this text
assumes that Peer-Identity is something else than an opaque unique
string, since that would be quite useless in this case...

Also, to get interoperable implementations for e.g. using RFC2712
for GIST, it's not sufficient to say it's somehow derived from
Peer-Identity; some specification needs to say _how_ it's derived.

My recommendation would be to just define a MA-Protocol-ID=20
for TLS-with-Certificates, and leave other kinds of TLS uses
beyond the scope of the specification (with the understanding
that they probably require a different MA-Protocol-ID).

Best regards,
Pasi=20

> -----Original Message-----
> From: ext Hancock, Robert [mailto:robert.hancock@roke.co.uk]=20
> Sent: 14 December, 2005 20:33
> To: Eronen Pasi (Nokia-NRC/Helsinki); nsis@ietf.org
> Subject: RE: [NSIS] TLS in the GIST draft
>=20
> hi pasi, all,
>=20
> after a certain amount of agonising about this issue, i have the
> following proposal (proposed text at the end).
>=20
> I believe that it is necessary to add text on mandatory
> ciphersuites. It also seems to be important in the long term to
> allow the more flexible uses of TLS, and that some of these
> require more information than just the TLS usage selection in the
> first place. However, some of the options for TLS usage are
> currently somewhat speculative, and there is a case for
> implementing the basic certificate TLS usage first while leaving
> the way open for more advanced uses.
>=20
> The following text is proposed for section 5.7.3:
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> 5.7.3.  Protocol Definition: Transport Layer Security
>=20
>    This defines the use of transport layer security as a basic
>    channel security mechanism.  Support for this protocol is
>    mandatory; associations using it can carry messages with the
>    transfer attribute Secure=3DTrue.  For use with TCP,
>    implementation of TLS1.0 [6] is REQUIRED and implementation of
>    TLS1.1 [8] is RECOMMENDED.  (If an unreliable transport such as
>    DCCP or UDP is defined for GIST in the future, TLS would be
>    implemented with it using DTLS [36].)  GIST nodes supporting
>    TLS1.0 or TLS1.1 MUST be able to negotiate the following TLS
>    ciphersuites:
>=20
>    o  TLS_RSA_WITH_RC4_128_MD5
>=20
>    o  TLS_RSA_WITH_RC4_128_SHA
>=20
>    o  TLS_RSA_WITH_3DES_EDE_CBC_SHA
>=20
>    and SHOULD be able to negotiate the following TLS ciphersuite:
>=20
>    o  TLS_RSA_WITH_AES_128_CBC_SHA
>=20
>    The default mode of TLS authentication (which applies in
>    particular to the above ciphersuites) is server-only or mutual
>    authentication using certificates.  The Querying node acts as a
>    TLS client, and the Responding node acts as a TLS server.  Where
>    one of the above ciphersuites is negotiated, the GIST node acting
>    as a server MUST provide its own certificate, and MUST request one
>    from the GIST node acting as a TLS client.
>=20
>    GIST nodes MAY negotiate other TLS ciphersuites.  In some
>    cases, the negotiation of alternative ciphersuites is used to
>    trigger alternative authentication procedures (for example, the
>    use of pre- shared keys).  Where the operation of the procedure
>    depends on the prior knowledge of identity hints about the
>    peer, these SHOULD be derived from the Peer-Identity provided
>    in the NLI object of Query and Response messages.
>=20
>    No higher-layer-addressing data is defined for TLS.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> views?
>=20
> robert h.
>=20
> ps. in the tracker at
> http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue103

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 23 06:38:43 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EplFy-0007v6-Vh; Fri, 23 Dec 2005 06:38:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EplFx-0007uy-UQ
	for nsis@megatron.ietf.org; Fri, 23 Dec 2005 06:38:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29786
	for <nsis@ietf.org>; Fri, 23 Dec 2005 06:37:35 -0500 (EST)
Received: from mail21.syd.optusnet.com.au ([211.29.133.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EplIx-0006DM-Po
	for nsis@ietf.org; Fri, 23 Dec 2005 06:41:49 -0500
Received: from 3m1 (d220-236-76-9.dsl.nsw.optusnet.com.au [220.236.76.9])
	by mail21.syd.optusnet.com.au (8.12.11/8.12.11) with SMTP id
	jBNBcM4q004388; Fri, 23 Dec 2005 22:38:24 +1100
Message-ID: <005f01c607b5$6ad3ac90$0501010a@3m1>
From: "Muhammad Ali Malik" <mamalik@cse.unsw.edu.au>
To: <john.loughney@nokia.com>, <nsis@ietf.org>
References: <1AA39B75171A7144A73216AED1D7478D6CED5D@esebe100.NOE.Nokia.com>
Subject: Re: [NSIS] scaling problem by trigger messages ...
Date: Fri, 23 Dec 2005 22:38:37 +1100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi John,

I am refering to RFC 4094: "Analysis of Existing Quality-of-Service 
Signaling Protocols". Sorry for not mentioning the RFC in my last e-mail.

Regards,

Malik

----- Original Message ----- 
From: <john.loughney@nokia.com>
To: <mamalik@cse.unsw.edu.au>; <nsis@ietf.org>
Sent: Friday, December 23, 2005 6:13 PM
Subject: RE: [NSIS] scaling problem by trigger messages ...


Hi Malik,

Which RFC are you refering to?

John


________________________________

From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On
Behalf Of ext Muhammad Ali Malik
Sent: 23 December, 2005 07:00
To: nsis@ietf.org
Subject: [NSIS] scaling problem by trigger messages ...


Hi,

The RFC states that: " On the other hand, in many of the new
applications for which a
   signaling protocol is required, the user session duration can
be
   relatively short.  The dynamics of adding/dropping user
sessions
   could introduce a large number of "triggered" messages in the
   network.  This can clearly introduce a substantial amount of
   processing overhead to the routers.  This is one area where a
new
   signaling protocol may be needed to reduce the processing
complexity
   in the resource reservation process."

Can anybody please elaborate the situation where there is
overheads because of trigger messages and not by the refresh message.
Apart from processing overheads, the trigger messages also exhibit
signaling overheads. But i hardly seen any documents addressing the
issues by trigger messages only and not by the refresh messages. How
does NSIS address the issue of overheads due to trigger messages.

Regards,

=Malik



_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Fri Dec 23 08:03:27 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpmZz-0007YZ-Nt; Fri, 23 Dec 2005 08:03:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EpmZy-0007Xx-0b; Fri, 23 Dec 2005 08:03:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08364;
	Fri, 23 Dec 2005 08:02:19 -0500 (EST)
Received: from s2.ifi.informatik.uni-goettingen.de ([134.76.81.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Epmcz-0000Yk-05; Fri, 23 Dec 2005 08:06:34 -0500
Received: from localhost (localhost [127.0.0.1])
	by s2.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP id
	821269C008; Fri, 23 Dec 2005 14:03:16 +0100 (CET)
Received: from [172.22.0.51] (tmg51.tmg.loc [172.22.0.51])
	by s2.ifi.informatik.uni-goettingen.de (Postfix) with ESMTP;
	Fri, 23 Dec 2005 14:03:16 +0100 (CET)
Message-ID: <43ABF58E.1070909@cs.uni-goettingen.de>
Date: Fri, 23 Dec 2005 14:03:10 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nsis-imp@ietf.org, nsis@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by sophie+clamav (Debian) at informatik.uni-goettingen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: Christian Dickmann <nsis@christian-dickmann.de>, "Tschofenig,
	Hannes" <hannes.tschofenig@siemens.com>
Subject: [NSIS] new nsis release available
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi all,

Just a quick update of our NSIS implementation: we are glad to release 
0.3.0 which includes support for QoS NSLP and NAT/FW NSLP. The team 
would appreciate your feedbacks and reviews:
http://user.informatik.uni-goettingen.de/~nsis/

Wish all a Merry Christmas and happy New Year!

Cheers,
Xiaoming

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



