<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=text/html;charset=iso-8859-1 http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.7600.16700"></HEAD> <BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px" id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true" name="Compose message area"> <DIV><FONT face=Calibri>My suggestion was to develop a best practice for consumer CPE specifications based on existing IETF standards/drafts. </FONT></DIV> <DIV><FONT face=Calibri></FONT> </DIV> <DIV><FONT face=Calibri>Regards,</FONT></DIV> <DIV><FONT face=Calibri>-Ahmed</FONT></DIV> <DIV><FONT face=Calibri></FONT> </DIV> <DIV style="FONT: 10pt Tahoma"> <DIV><BR></DIV> <DIV style="BACKGROUND: #f5f5f5"> <DIV style="font-color: black"><B>From:</B> <A title=marcoh@marcoh.net href="mailto:marcoh@marcoh.net">Marco Hogewoning</A> </DIV> <DIV><B>Sent:</B> Sunday, January 09, 2011 1:22 PM</DIV> <DIV><B>To:</B> <A title=ahmed@tamkien.com href="mailto:ahmed@tamkien.com">Ahmed Abu-Abed</A> </DIV> <DIV><B>Cc:</B> <A title=kzorba@otenet.gr href="mailto:kzorba@otenet.gr">kzorba@otenet.gr</A> ; <A title=ipv6-wg@ripe.net href="mailto:ipv6-wg@ripe.net">ipv6-wg@ripe.net</A> </DIV> <DIV><B>Subject:</B> Re: [ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment</DIV></DIV></DIV> <DIV><BR></DIV><BR>On 9 jan 2011, at 05:40, Ahmed Abu-Abed wrote:<BR><BR>> Good point, and having a Consumer CPE spec as a RIPE standard would help for last mile access requirements. RIPE-501 only aimed for government and enterprise deployments.<BR><BR>My personal preference would be to keep pointing to the work done in the IETF. The problem with standards is, there usually are too many. Adding another one will only lead to more confusion, let alone the time it will take to get consensus.<BR><BR>Grtx,<BR><BR>MarcoH<BR><BR>-- <BR>"Good tests kill flawed theories; we remain alive to guess again"<BR></BODY></HTML>