Re: [XCON] Partial notifications for the XCON event package
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [XCON] Partial notifications for the XCON event package
True, I didn't remember the new state elements defined in the event
packages... So, if we define them, we need a new MIME type.
Oscar
On Wed, 2008-01-30 at 18:59 +0200, Gonzalo Camarillo wrote:
> Hi,
>
> the current event package draft has a whole section explaining why a new
> MIME type is needed. The reason it gives is the presence of state
> attributes in new elements. However, if we do not define new state
> attributes by use xml patch operations instead, we could reuse the old
> MIME type, as you suggest. Of course, we would need to define a new one
> for partial notifications based on xml patch operations.
>
> Does anybody else have an opinion on this issue?
>
> Cheers,
>
> Gonzalo
>
>
> Oscar Novo wrote:
> > Yes, I believe we should use the same MIME type as in RFC4575 and a
> > different MIME type for the 'xml patch operation' option.
> >
> > Oscar
> >
> >> what do you exactly mean by "100% backward compatible"? Do you mean that
> >> we should be using the same MIME type as in RFC 4575?
> >>
> >> Cheers,
> >>
> >> Gonzalo
> >>
> >
>
_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.