Re: documenting OCP parameters

Alex,

I am changing parameter definitions to TDM. This is what I have so far:

  am-part: extends atom;
  am-parts: extends list am-part;

  HTTP-Profile: extends Feature with {
  [Aux-Parts: am-parts];
  [Wont-Use-Body: size];
  [Pause-At-Body: size];
  [Content-Encodings: codings];
  };

Is this correct?

In order to define which tokens are defined as the am-part atoms, may I
still write:
  am-part = "request-header"
          / "request-body"
          / "request-trailer"
          / "response-header"
          / "response-body"
          / "response-trailer"
in addition to the above?

And what is codings now?
Is it actually a list of tokens, as we used it so far or a list of
quoted-values?
Or is it just a list of atoms and implementations decide whether bare-values
work here?

Regards
Martin


----- Original Message ----- 
From: "Alex Rousskov" <rousskov(_at_)measurement-factory(_dot_)com>
To: "OPES WG" <ietf-openproxy(_at_)imc(_dot_)org>
Sent: Saturday, October 25, 2003 3:58 PM
Subject: RE: documenting OCP parameters


> On Sat, 25 Oct 2003, Martin Stecher wrote:
>
> > > Profile: extends Service with {
> > > [Aux-Parts: Am-Parts];
> > > [Skip-Parts: Am-Parts];
> > > };
> > I think, this last option is easiest to understand.
> Agreed, documented, and pushed to the web site.
>
> Alex.
>
> ------------------------------------------------------------
> This mail has been scanned by debian3-smtp
> (WebWasher 4.4.1 Build 688)
> ------------------------------------------------------------