Re: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments

[Christer Holmberg <[e-mail]>]

Hi,

When taking a closer look, I actually think there is something technically wrong with the syntax in Section 5 of draft-ietf-soc-overload-rate-control.

draft-ietf-soc-overload-control  defines the oc parameter as:

oc          = "oc" [EQUAL oc-num]


Now, it seems like draft-ietf-soc-overload-rate-control actually re-defines the same parameter. In addition, it’s done in a backward compatible manner, e.g. because the parameter can now contain a non-numeric value (see the bullet list below what can go wrong):

oc          = "oc" EQUAL oc-value


The following can happen:


1.       If an entity that supports draft-ietf-soc-overload-control  receives “oc=NaN” it will reject it, as it expects a numeric value.

2.       If an entity that supports draft-ietf-soc-overload-rate-control receives “oc” it will reject it, as it expects an oc-value. But, in draft-ietf-soc-overload-control  the usage of oc-value is optional.


One way to fix this could be to define oc-value as a separate Via header field parameter (similar to oc-validity, oc-seq etc), instead of a value of the oc parameter. But, then you would have oc-num

Another way is to change the syntax in draft-ietf-soc-overload-control , in order to allow what you want to do in draft-ietf-soc-overload-rate-control.

Regards,

Christer




Lähettäjä: Janet P Gunn [mailto:[e-mail]]
Lähetetty: 27. kesäkuuta 2013 22:04
Vastaanottaja: Christer Holmberg
Kopio: [e-mail]; [e-mail]; [e-mail]
Aihe: Re: VS: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments

Christer

 draft-ietf-soc-overload-control  says
" 8.  Syntax

   This specification extends the existing definition of the Via header
   field parameters of [RFC3261] as follows:

       via-params  =  via-ttl / via-maddr
                      / via-received / via-branch
                      / oc / oc-validity
                      / oc-seq / oc-algo / via-extension


       oc          = "oc" [EQUAL oc-num]
       oc-num      = 1*DIGIT
       oc-validity = "oc-validity" [EQUAL delta-ms]
       oc-seq      = "oc-seq" EQUAL 1*12DIGIT "." 1*5DIGIT
       oc-algo     = "oc-algo" EQUAL DQUOTE algo-list *(COMMA algo-list)
                     DQUOTE
       algo-list   = "loss" / *(other-algo)
       other-algo  = %x41-5A / %x61-7A / %x30-39
       delta-ms    = 1*DIGIT"
and
"11.  IANA Considerations

   This specification defines four new Via header parameters as detailed
   below in the "Header Field Parameter and Parameter Values" sub-
   registry as per the registry created by [RFC3968].  The required
   information is:

       Header Field  Parameter Name  Predefined Values  Reference
       __________________________________________________________
       Via           oc                 Yes             RFCXXXX
       Via           oc-validity        Yes             RFCXXXX
       Via           oc-seq             Yes             RFCXXXX
       Via           oc-algo            Yes             RFCXXXX

       RFC XXXX [NOTE TO RFC-EDITOR: Please replace with final RFC
       number of this specification.]"

The text of draft-ietf-soc-overload-control refers to both "loss" and "rate"  as values for  oc-algo.

The text of draft-ietf-soc-overload-control  section 5.3 refers to the use of oc for either rate or loss

"As an example, a value of "oc=10" when the loss-based algorithm is
   used implies that 10% of the total number of SIP requests (dialog
   forming as well as in-dialogue) are subject to reduction at the
   client.  Analogously, a value of "oc=10" when the rate-based
   algorithm [I-D.ietf-soc-overload-rate-control] is used indicates that
   the client should send SIP requests at a rate of 10 SIP requests or
   fewer per second."

What are you suggesting would go in the "IANA Considerations" section of  draft-ietf-soc-overload-rate-control ?  Does it just need a reference to the IANA Considerations in draft-ietf-soc-overload-control?

Janet






This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.



From:        Christer Holmberg <[e-mail]<mailto:[e-mail]>>
To:        Janet P Gunn/USA/CSC@CSC
Cc:        "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date:        06/27/2013 12:54 PM
Subject:        VS: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control -        Christer's comments
________________________________



Hi,

>The IANA considerations section of  draft-ietf-soc-overload-control registers the new Via header field parameters.
>
>Is it needed here as well?

The draft (Section 5) does extend the oc parameter, doesn’t it? I would assume that needs to go to IANA.

Regards,

Christer


[e-mail]<mailto:[e-mail]> wrote on 06/27/2013 06:05:41 AM:

> From: Christer Holmberg <[e-mail]<mailto:[e-mail]>>
> To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
> Cc: "[e-mail]<mailto:[e-mail]>"
> <[e-mail]<mailto:[e-mail]>>
> Date: 06/27/2013 06:05 AM
> Subject: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control -
> Christer's comments
> Sent by: [e-mail]<mailto:[e-mail]>
>
> Hi,
>
> I have read draft-ietf-soc-overload-rate-control-04.txt as part of the WGLC.
>
...
> Q7: In Section 7 you say that there are no IANA considerations. But,
> don’t you need to request IANA to register the new Via header field
> parameters?
>
> Regards,
>
> Christer
>
>
>
>
>  _______________________________________________
> sip-overload mailing list
> [e-mail]<mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/sip-overload