Dear Med,
OK, that answers my concern.

Thank you,
Tina

On Jan 22, 2013, at 12:47 AM, "mohamed.boucad...@orange.com" 
<mohamed.boucad...@orange.com> wrote:

> Dear Tina,
> 
> Thank you for reviewing the draft and for your support. 
> 
> The draft does only extend the definition of already reserved bits to be also 
> treated as flags. In addition, the draft provides some clarifications for the 
> use of flag bits (including both the old and the extended ones). The 
> recommendation sketched in the draft applies for all flag bits (including the 
> newly defined ones). As such, we don't see the need to use a different name 
> to refer to the newly defined flag bits. 
> 
> Please let me know if this answers to your concern about the name. 
> 
> Cheers,
> Med  
> 
>> -----Message d'origine-----
>> De : Tina TSOU [mailto:tina.tsou.zout...@huawei.com] 
>> Envoyé : jeudi 17 janvier 2013 23:43
>> À : BOUCADAIR Mohamed OLNC/OLN; ipv6@ietf.org
>> Cc : Stig Venaas
>> Objet : RE: draft-boucadair-6man-multicast-addr-arch-update-00
>> 
>> Dear Med and Stig,
>> I technically support this draft.
>> The newly defined flgs field has the same field name in old 
>> Addressing Architecture. I would suggest renaming newly 
>> defined flgs field.
>> 
>> Thank you,
>> Tina
>> 
>> 
>>> -----Original Message-----
>>> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] 
>> On Behalf Of
>>> mohamed.boucad...@orange.com
>>> Sent: 2013年1月16日 6:54
>>> To: ipv6@ietf.org
>>> Cc: Brian Haberman; Stig Venaas
>>> Subject: draft-boucadair-6man-multicast-addr-arch-update-00
>>> 
>>> Dear all,
>>> 
>>> We submitted this short draft to update some existing IPv6 
>> multicast RFCs;
>>> especially to extend the definition of some reserved bits.
>>> 
>>> Comments are more than welcome.
>>> 
>>> Cheers,
>>> Med
>>> 
>>> -----Message d'origine-----
>>> De : i-d-announce-boun...@ietf.org 
>> [mailto:i-d-announce-boun...@ietf.org]
>>> De la part de internet-dra...@ietf.org Envoyé : mercredi 16 
>> janvier 2013
>>> 13:13 À : i-d-annou...@ietf.org Objet : I-D Action: 
>> draft-boucadair-6man-
>>> multicast-addr-arch-update-00.txt
>>> 
>>> 
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> 
>>> 
>>>    Title           : Updates to the IPv6 Multicast Addressing
>>> Architecture
>>>    Author(s)       : Mohamed Boucadair
>>>                          Stig Venaas
>>>    Filename        : 
>> draft-boucadair-6man-multicast-addr-arch-update-
>>> 00.txt
>>>    Pages           : 5
>>>    Date            : 2013-01-16
>>> 
>>> Abstract:
>>>   This document updates the IPv6 multicast addressing 
>> architecture by
>>>   defining the 17-20 reserved bits as generic flag bits.  
>> The document
>>>   provides also some clarifications related to the use of these flag
>>>   bits.
>>> 
>>>   This document updates RFC 3956, RFC 3306, RFC 4607 and RFC 4291.
>>> 
>>> 
>>> 
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-boucadair-6man-multicast-addr-
>>> arch-update
>>> 
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-boucadair-6man-multicast-addr-arch-
>>> update-00
>>> 
>>> 
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>> 
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> i-d-annou...@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html or
>>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to