Re: [Dime] Application-id reuse

[Ankit Kumar Sharma <ankit.sharma at aricent.com>]

Hi Biplab,
-----Original Message-----
From: dime-bounces at ietf.org [mailto:dime-bounces at ietf.org] On Behalf Of Sarkar, Biplab
Sent: Monday, September 15, 2008 10:27 AM
To: Jacob Martin; jouni.korhonen at iki.fi
Cc: dime at ietf.org
Subject: Re: [Dime] Application-id reuse

Hi all,

I was thinking of the consequences of allowing AVP's to have the liberty to either set or un-set the M-bit.
The sender may decide to set it depending upon its judgement about the version of the peer.

< I hope you are referring to section 4.1 of RFC 3588.
" A configuration option may be provided on a system wide, per
         peer, or per realm basis that would allow/prevent particular
         Mandatory AVPs to be sent.  Thus an administrator could change
         the configuration to avoid interoperability problem ">

- Will this give added help for extendability?
<Yes it would add to the extendibility/flexibility>
- Is it really required to mandate the presence of M-bit for AVPs? Won't it be better to allow the sender to decide?

< To define any specification, there should be mandate on some of the basic AVPs which helps in core functioning. For proprietary extensions, vendors are allowed to define custom AVPs to meet their requirements>

Some comments on this please.

Thanks & Regards,
Biplab


-----Original Message-----
From: dime-bounces at ietf.org on behalf of Jacob Martin
Sent: Mon 9/15/2008 10:17 AM
To: jouni.korhonen at iki.fi
Cc: dime at ietf.org
Subject: Re: [Dime] Application-id reuse

On 9/15/08, Jouni <ron.kehno at kolumbus.fi> wrote:
> Jacob Martin kirjoitti:
>>
>>> Now that M-bit settings are wrong is just n error in TS29.234
>>>
>> I did not get you on this. could you please explain this again?
> Wm has some new AVPs with M-bit set, as you also pointed out. This goes
> against the rule for "when to create a new application" as no new
> application is
> created. These are just errors in the current TS 29.234.
ok... Thanks for the clarification.
>
> Jouni
>
>
>
>
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME at ietf.org
https://www.ietf.org/mailman/listinfo/dime

Thanks,
Ankit

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www.ietf.org/mailman/listinfo/dime