RE: FW: [Diffserv] Informal WG last call for draft-ietf-diffserv-new-terms-06.txt

Focusing on #4.

The text says ... "Therefore, the relationship between an SLS and a service
provisioning policy is that the latter is, in part, the set of rules that
define the parameters and range of values that may be in the former."

<Dan> My inclination at this point is to leave it as it is, unless Andrea
can come
up with a concise sentence or two that can be dropped in.  I think that
policy
aware readers will understand that we don't intend to be restrictive, and
non-policy aware readers won't be confused.

Can we say "the set of rules that IMPLEMENT the parameters and range of
values ..."?  My problem is with the word DEFINES.

Andrea

-----Original Message-----
From: Andrea Westerinen [mailto:andreaw@cisco.com]
Sent: Wednesday, November 14, 2001 1:53 PM
To: Dan Grossman
Cc: Diffserv@Ietf. Org; Policy@Ietf. Org; Bert Wijnen (Bert)
Subject: RE: FW: [Diffserv] Informal WG last call for
draft-ietf-diffserv-new-terms-06.txt

Pulling everything up here.  It looks like #4 needs a bit more discussion -
however, it is not a major issue for me.

1. PolTerm supports SLAs as contractual - Agreed to document this alignment.
2. Dan said, "I'd be hesitant to alter the Diffserv definition, since this
was subject of a great deal of working group debate.  However, some words to
the effect that
you suggest would be appropriate."
	- This is all that I was suggesting.  I totally understand how painful
these things can be - and I think that the definitions are aligned.  PolTerm
is just broader and this was intentional.
3. Normative reference to PolTerm - OK.
4. Service provisioning policy "defines and manages to parameters and range
of values" in an SLS.  Dan asked how rules can manage to parameters and
ranges.
	- This really depends on your rules.  For static "preconfiguration" rules,
then all that you are doing is defining what you want, and making it so.  In
the more general case of provisioning rules, you might have
"preconfiguration" rules, and other "runtime" rules that are invoked "if
<something happens>."  If/when something happens, then the actions of the
other rules might manipulate the environment to maintain (ie, "manage to")
the parameters and ranges, or switch to new parameters, or ignore
parameters/ranges, etc.  I was asking about whether we should generalize
what a "provisioning rule" might do.
5-7. Nits and typos - Will be cleaned up.

Andrea

_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www2.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html