RE: [NSIS] state management and the nsis framework

Hi

What is the actual benefit of mixing the two protocols like this? Generally,
its best to keep the interface and meaning between the two elements as
simple as possible? Efficincy gains must be minimal? Is it guarenteed that
beacuse the NTLP/ transport is still alive  the NSLP still is?

Louise

-----Original Message-----
From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
Sent: 13 May 2003 14:22
To: Hancock, Robert
Cc: nsis@ietf.org
Subject: Re: [NSIS] state management and the nsis framework

Hi Robert

[reh]
> > in terms of what is being discussed below, could you clarify
> > if you see
> > any difference in overall NSIS functionality between our two
> > descriptions
> > (and what this difference is).
> >
> > if there is no overall difference, could you explain why you
> > prefer your
> > split of responsibility between NSLP/NTLP. what you propose
> > seems to me
> > to assume a closer customisation of NTLP functionality to
> > support one specific
> > signalling application that I feel we should be aiming for.
>                          ^^^^
> should be:              "than"
>

[GK]
The main difference is the following:
* In my proposed text, the NTLP is used to provide NTLP soft state
management,
   meaning that NTLP refresh messages are used. The NSLP is using this
procedure
   for NSLP soft state management. If a NTLP state is not refreshed, then
the NSLP instance
   is informed about it. Moreover, for inter-domain signaling no NSLP
refresh
   messages are needed. Please note that a NSLP might choose to not use the
NTLP soft
   state management.

* If  I understood you correctly, in your proposed text you are in favour of
using
   the NSLP protocol to provide the NSLP and NTLP soft state manegement.
Meaning that
   each NSLP will have to use its own refresh messages for providing NSLP
and NTLP soft state
   management.

In my opinion my proposed text is presenting a NTLP/NSLP soft state
management concept that is not specific
for one signaling application, but that is general and can be used for all
types of signaling applications.
Please note that this soft state management concept is similar to the soft
state manegement concept presented
in the Bob Braden's draft, see:
http://www.ietf.org/internet-drafts/draft-braden-2level-signal-arch-01.txt

However, please note that these two proposals could be combined. The NSLP
that does not use the NTLP
soft state management concpet could provide its own by using NSLP refresh
messages.

Best regards,
Georgios

_______________________________________________
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