[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipsec
Subject:    Re: [IPsec] Query regarding Qos with IKE
From:       Paul Simon <paulsimon.c () gmail ! com>
Date:       2013-11-07 9:35:57
Message-ID: CANRC3+5zY9qj6wk2geqsi0j=YHx6V5vrXj7zM-d5XJ3seK9o0A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


ok thank you. I will try notification.


On Thu, Nov 7, 2013 at 12:28 AM, Black, David <david.black@emc.com> wrote:

> > Correct.
> > you'd have to write an ID on a new Notify type.
>
> Or on a new Configuration Attribute if that's more appropriate -
> see section 3.15.1 of RFC 5996.
>
> Thanks,
> --David
>
>
> > -----Original Message-----
> > From: ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf
> Of
> > Michael Richardson
> > Sent: Wednesday, November 06, 2013 12:18 PM
> > To: Paul Simon
> > Cc: <ipsec@ietf.org>; Tero Kivinen
> > Subject: Re: [IPsec] Query regarding Qos with IKE
> >
> >
> > Paul Simon <paulsimon.c@gmail.com> wrote:
> >     > Yes now it is clear that IKE is not supposed to do DSCP negotiation
> >     > Thanks for the explanations.
> >
> > *negotiation* is the key word.
> > negotiation != notification
> >
> >     > [PAUL] I have gone through RFC 5996 section 3.10.1 notify message
> types.
> >     > But could not find a suitable message type to convey dscp
> information.
> >     > Can you suggest which notification message should be used here ?
> >
> > Correct.
> > you'd have to write an ID on a new Notify type.
> >
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >
>
>

[Attachment #5 (text/html)]

<div dir="ltr">ok thank you. I will try notification.</div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 12:28 AM, \
Black, David <span dir="ltr">&lt;<a href="mailto:david.black@emc.com" \
target="_blank">david.black@emc.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">&gt; Correct.<br> &gt; you&#39;d have to \
write an ID on a new Notify type.<br> <br>
</div>Or on a new Configuration Attribute if that&#39;s more appropriate -<br>
see section 3.15.1 of RFC 5996.<br>
<br>
Thanks,<br>
--David<br>
<div class="im HOEnZb"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href="mailto:ipsec-bounces@ietf.org">ipsec-bounces@ietf.org</a> \
[mailto:<a href="mailto:ipsec-bounces@ietf.org">ipsec-bounces@ietf.org</a>] On Behalf \
Of<br> </div><div class="im HOEnZb">&gt; Michael Richardson<br>
&gt; Sent: Wednesday, November 06, 2013 12:18 PM<br>
&gt; To: Paul Simon<br>
&gt; Cc: &lt;<a href="mailto:ipsec@ietf.org">ipsec@ietf.org</a>&gt;; Tero Kivinen<br>
&gt; Subject: Re: [IPsec] Query regarding Qos with IKE<br>
&gt;<br>
&gt;<br>
</div><div class="HOEnZb"><div class="h5">&gt; Paul Simon &lt;<a \
href="mailto:paulsimon.c@gmail.com">paulsimon.c@gmail.com</a>&gt; wrote:<br> &gt;     \
&gt; Yes now it is clear that IKE is not supposed to do DSCP negotiation<br> &gt;     \
&gt; Thanks for the explanations.<br> &gt;<br>
&gt; *negotiation* is the key word.<br>
&gt; negotiation != notification<br>
&gt;<br>
&gt;     &gt; [PAUL] I have gone through RFC 5996 section 3.10.1 notify message \
types.<br> &gt;     &gt; But could not find a suitable message type to convey dscp \
information.<br> &gt;     &gt; Can you suggest which notification message should be \
used here ?<br> &gt;<br>
&gt; Correct.<br>
&gt; you&#39;d have to write an ID on a new Notify type.<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Michael Richardson &lt;<a \
href="mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@sandelman.ca</a>&gt;, Sandelman \
Software Works<br> &gt;<br>
<br>
</div></div></blockquote></div><br></div>



_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec


[prev in list] [next in list] [prev in thread] [next in thread]