Re: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-08.txt]

"Rajeev Koodli (rkoodli)" <rkoodli@cisco.com> Tue, 22 October 2013 05:22 UTC

From: "Rajeev Koodli (rkoodli)" <rkoodli@cisco.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, "netext@ietf.org" <netext@ietf.org>
Thread-Topic: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-08.txt]
Thread-Index: AQHOzqxG8NtGw8kbX0CbFNziK3IPz5n/m2kAgACCWID///DNgA==
Date: Tue, 22 Oct 2013 05:22:38 +0000
Message-ID: <7C52FDEBC843C44DBAF2CA6A30662C6D01621F8F@xmb-aln-x04.cisco.com>
In-Reply-To: <24C0F3E22276D9438D6F366EB89FAEA81DCBF601@xmb-aln-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2EC4E522705F024D909AFB2AB8B61155@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [netext] [Fwd: I-D Action: draft-ietf-netext-pmipv6-flowmob-08.txt]
Precedence: list

Right, we needed to discuss this before putting text - especially I saw no
response to my email about this after the last IETF meeting.

In particular, I am not sure about having to implement the UPN spec for
one to do FM. Let's discuss what this means; may be I don't fully follow..
Perhaps Carlos could spend some time at Vancouver on this.

It would help me if the following is shown with some text for the ID.
I don't see what the text duplication is. If the text is there for UPN, we
can re-use it.

Thanks.

-Rajeev


On 10/21/13 4:16 PM, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
wrote:

>Hi Carlos/Rajeev:
>
>I agree, we did not resolve this issue one way or the other.
>
>How about the following ?
>
>We can still the keep the FMI message, its use and the text in the spec.
>No changes are needed.  But, under the wrappers, FMI message can be a UPN
>message with a NR code of "FMI". So, in the format section, we point to
>the UPN message.
>
>Otherwise, we have to add all the considerations around security, IPSec
>PAD entries, IPv4 transport, ..etc and that is not there currently in the
>spec. May end up duplicating lot of text. Even for implementation, its
>additional bit of text dealing with a new message type.
>
>This has least impact on the existing text. Else, we need to revert to the
>prev version.
>
>Is this a reasonable way-forward ?
>
>
>
>
>Regards
>Sri
>
>
>
>
>On 10/21/13 3:30 PM, "Rajeev Koodli (rkoodli)" <rkoodli@cisco.com> wrote:
>
>>
>>Hi Carlos,
>>
>>
>>On 10/21/13 3:24 PM, "Carlos Jesús Bernardos Cano" <cjbc@it.uc3m.es>
>>wrote:
>>
>>>Hi,
>>>
>>>Following the discussion during the last meeting, I've updated the
>>>draft. As requested by the WG, it now uses the Update Notifications for
>>>Proxy Mobile IPv6.
>>
>>Hmm? I don't recall any discussion on this..Perhaps I missed the
>>response(s) to my email.
>>We need to discuss this :)
>>
>>-Rajeev
>>
>>
>>
>>>
>>>Comments are welcome. I'd like to ask people that submitted an issue to
>>>the tracker to see if you are happy with the revision (and close the
>>>issue if that is the case).
>>>
>>>Thanks,
>>>
>>>Carlos
>>
>>_______________________________________________
>>netext mailing list
>>netext@ietf.org
>>https://www.ietf.org/mailman/listinfo/netext
>

[netext] I-D Action: draft-ietf-netext-pmipv6-flo… internet-drafts
[netext] [Fwd: I-D Action: draft-ietf-netext-pmip… Carlos Jesús Bernardos Cano
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Rajeev Koodli (rkoodli)
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Sri Gundavelli (sgundave)
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Rajeev Koodli (rkoodli)
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Carlos Jesús Bernardos Cano
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Carlos Jesús Bernardos Cano
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Rajeev Koodli (rkoodli)
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Behcet Sarikaya
Re: [netext] [Fwd: I-D Action: draft-ietf-netext-… Carlos Jesús Bernardos Cano