<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR>
<STYLE>P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: navy; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: navy; TEXT-DECORATION: underline
}
P.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle18 {
COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.EmailStyle19 {
FONT-FAMILY: Arial
}
SPAN.EmailStyle20 {
COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=EN-US dir=ltr vLink=navy link=blue bgColor=#ffffff>
<DIV><FONT face=Arial>> Malik, I vote for MENOG. It'll be great if we can
make it, </FONT></DIV>
<DIV><FONT face=Arial>> of course it'll need a lot of discussion regarding
where will </FONT></DIV>
<DIV><FONT face=Arial>> it based, rules, who will operate it's
website, who could be </FONT></DIV>
<DIV><FONT face=Arial>> a member & how,...etc.</FONT></DIV>
<DIV><FONT face=Arial><FONT size=2></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2>
<DIV><FONT face=Arial>Here is a suggestion with respect MENOG based on
experience with the original NANOG:</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>"Keep it organizationally lightweight with the clear and
simple goal of technical information exchanges for techies by techies".
</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>All policy issues, excepts for the very important
understanding the technical implications of such policies, should be handled by
different groups (e.g. <FONT size=2>ARISPA, others). The reason to keep
non-technical policy issues explicitly out of its mandates is, while
important, the commercial/national politics behind the scene can be
overwhelming and beyond the scope of the people MENOG should be serving.
</FONT></FONT></DIV>
<DIV> </DIV>
<DIV>While policy is outside the mandate of MENOG, it can serve as a technical
advisory entity to approrpiate policy making groups.</DIV>
<DIV> </DIV>
<DIV>Best regards,</DIV>
<DIV>John Leong</DIV>
<DIV> </DIV>
<DIV> </DIV></FONT></FONT></DIV></BODY></HTML>