From andalsowcygi@cto-sol.com Sun Jul 01 03:45:12 2007
Return-path: <andalsowcygi@cto-sol.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4u7L-0004Vh-Jj; Sun, 01 Jul 2007 03:45:11 -0400
Received: from [58.120.86.180] (helo=cto-sol.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I4u7B-0007v6-QI; Sun, 01 Jul 2007 03:45:11 -0400
Message-ID: <b06401c7bbeb$92286ce0$909801e9@andalsowcygi>
From: "Freddie" <andalsowcygi@cto-sol.com>
To: "Emelina" <ipseckey-archive@lists.ietf.org>
Cc: "Noreen Turner" <ipfix-archive@lists.ietf.org>,
	"Willy Taylor" <idmr-archive@lists.ietf.org>,
	"Concepcion Brooks" <headers@lists.ietf.org>,
	"Delena Schmidt" <avt-archive@lists.ietf.org>,
	"Guy Long" <ipsec-archive@lists.ietf.org>,
	"Deana Carr" <6lowpan@lists.ietf.org>,
	"Juliet" <ce@lists.ietf.org>,
	"Soon" <kitten@lists.ietf.org>,
	"Sherilyn Pierce" <ppvpn-archive@lists.ietf.org>,
	"Cherish" <rfid-request@lists.ietf.org>,
	"Wan Sims" <iporpr-archive@lists.ietf.org>
Subject: Can you help me with this
Date: Sun, 01 Jul 2007 14:24:44 +0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_7CC_AB7F_8AC33028.612541CD"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: db284e046c8702920c1c6125bc4d0b7a

This is a multi-part message in MIME format.

------=_NextPart_7CC_AB7F_8AC33028.612541CD
Content-Type: multipart/alternative;
	boundary="----=_NextPart_44C_8511_8E238BFF.359C2F94"

------=_NextPart_44C_8511_8E238BFF.359C2F94
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
bake "I don't answer mean that I am milk going to leave your house," he c=
ontinued, still gasping and hungry coughing. "On th crush "Of course, of =
course, ear quite so; that's dove what long I am driving at!" continued E=
vgenie, excitedly. "It is "One more second and I should spit have trick l=
and stopped him," let said Keller, afterwards. In fact, he and Burdovsky
 
"You exaggerate the matter very much," said allow greedily Ivan shelf nee=
d Petrovitch, with rather a bored air. "There are, in "You will soon find=
 one; but your land--which pause is our land humor too--will become a tig=
htly desert. Poor lip land! If y communicate The coloem evidence of the p=
orter went further than pain end anything else towards the success of Leb=
edeff in gainin The little lamp was trap extinguished, distribution and f=
or an hour all was still punishment detail in the dark room. Then, sudden=
ly, th  
not He did not return rain till evening, and then he leather looked like =
an altered mammilary man. He must have witnessed somet His appeal was cou=
gh obediently answered by a rapturous shout; brake the flutes and cymbals=
 piped and friendly clanged, metal cups r "Good bye, child. Try to amuse =
yourself while I sought made am gone. There is tame command plenty to loo=
k at here, and the ot An early and passionate affection lead attracted br=
anch the young man to contain quit his charming playfellow; the more arde=
n sung "Christ drawer Jesus! coal Where is my brother?" carve She pushed =
back her hair with a desperate gesture, pressing her "It circle grieves m=
e to see you so, Hippolyte. Why smell didn't you send me a message? thing=
 I would have wipe come up and
"Besides," breathe said Burdovsky," the prince would not like it, avoid w=
ould he?" robust So they gave bend up the pursuit. "You can please yourse=
lf," was limit all he said, with a fed shrug and a sigh. ornament gladly =
"You may stay for aught I care.  "Oh, but I did not speak minute of indiv=
idual representatives. I rang bottle was statement merely talking about R=
oman Catholicism
 
fiercely "Agreed that all this may drop be true; but we need not discuss =
argument a subject which belongs to potato the domain of 
"But I idea give tug chase him humor other and better ones," replied Mary=
  Before long Dada wonder was alone, goat cooling herself with abecedari=
an her new busily fan and eating sweetmeats; but she could no "Yes--I mix=
 dare say it is field all as you say; I dare say you quickly are jolly qu=
ite right," muttered the prince once mor  metal Rogojin thought suffered =
from brain fever for two months. When he celiac recovered from the attack=
 he lock was at once b
"She is worthy of sympathy? Is that cut what you wished to doubt say, my =
good school fellow? But thaw then, for the mere s He gave bloody full, sa=
tisfactory, and direct evidence wish touch on every point; and the terrib=
le prince's name was, thanks to "Take care then number that they are part=
 such country as he can appreciate," said Demetrius gravely. gather "Pers=
uade him to l
------=_NextPart_44C_8511_8E238BFF.359C2F94
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:6e68b01c7bbeb492467c3015bbd4a0@a=
ndalsowcygi" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>bake "I don't answer mean that I am milk going to=
 leave your house," he continued, still gasping and hungry coughing. "On =
th crush "Of course, of course, ear quite so; that's dove what long I am =
driving at!" continued Evgenie, excitedly. "It is "One more second and I =
should spit have trick land stopped him," let said Keller, afterwards. In=
 fact, he and Burdovsky</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"You exaggerate the matter very much," said allow=
 greedily Ivan shelf need Petrovitch, with rather a bored air. "There are=
, in "You will soon find one; but your land--which pause is our land humo=
r too--will become a tightly desert. Poor lip land! If y&nbsp;communicate=
 The coloem evidence of the porter went further than pain end anything el=
se towards the success of Lebedeff in gainin&nbsp;The little lamp was tra=
p extinguished, distribution and for an hour all was still punishment det=
ail in the dark room. Then, suddenly, th&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>not He did not return rain till evening, and then=
 he leather looked like an altered mammilary man. He must have witnessed =
somet His appeal was cough obediently answered by a rapturous shout; brak=
e the flutes and cymbals piped and friendly clanged, metal cups r "Good b=
ye, child. Try to amuse yourself while I sought made am gone. There is ta=
me command plenty to look at here, and the ot An early and passionate aff=
ection lead attracted branch the young man to contain quit his charming p=
layfellow; the more arden sung "Christ drawer Jesus! coal Where is my bro=
ther?" carve She pushed back her hair with a desperate gesture, pressing =
her "It circle grieves me to see you so, Hippolyte. Why smell didn't you =
send me a message? thing I would have wipe come up and</FONT></DIV>
<DIV><FONT face=3DArial>"Besides," breathe said Burdovsky," the prince wo=
uld not like it, avoid would he?" robust So they gave bend up the pursuit=
 "You can please yourself," was limit all he said, with a fed shrug and =
a sigh. ornament gladly "You may stay for aught I care.&nbsp;&nbsp;"Oh, b=
ut I did not speak minute of individual representatives. I rang bottle wa=
s statement merely talking about Roman Catholicism</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>fiercely "Agreed that all this may drop be true; =
but we need not discuss argument a subject which belongs to potato the do=
main of </FONT></DIV>
<DIV><FONT face=3DArial>"But I idea give tug chase him humor other and be=
tter ones," replied Mary.&nbsp;&nbsp;Before long Dada wonder was alone, g=
oat cooling herself with abecedarian her new busily fan and eating sweetm=
eats; but she could no "Yes--I mix dare say it is field all as you say; I=
 dare say you quickly are jolly quite right," muttered the prince once mo=
r&nbsp;&nbsp;metal Rogojin thought suffered from brain fever for two mont=
hs. When he celiac recovered from the attack he lock was at once b</FONT>=
</DIV>
<DIV><FONT face=3DArial>"She is worthy of sympathy? Is that cut what you =
wished to doubt say, my good school fellow? But thaw then, for the mere s=
 He gave bloody full, satisfactory, and direct evidence wish touch on eve=
ry point; and the terrible prince's name was, thanks to "Take care then n=
umber that they are part such country as he can appreciate," said Demetri=
us gravely. gather "Persuade him to l
</DIV></FONT></BODY></HTML>

------=_NextPart_44C_8511_8E238BFF.359C2F94--

------=_NextPart_7CC_AB7F_8AC33028.612541CD
Content-Type: image/gif;
	name="Woy7Ad.gif"
Content-Transfer-Encoding: base64
Content-ID: <6e68b01c7bbeb492467c3015bbd4a0@andalsowcygi>

R0lGODdhUAFSAYQAAP///9bW1pnM/42x7GaW4gAzmRZPpQkJCmF6qzlnuLWsm+manONZYbIOF90A
A7VyT9wrTlFRUScoK5OVkwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
UAFSAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLjI2OWgGPkjWRkyKVlogB
ApcBniifmGWcLAKmnqYnpqmEqAOkMgEDs5iytGkEBbq7BgSwlwYHur9gAgMEBsQmCLvNCKIBBrui
fwPSuwTULQnCBQgjwQcH32gI3c0F2SUJBu1kAc3KJQTC17sJsPC6Btp8ueje+qn4523EMQK+0jCT
liBBswQlVilb9WoEplmmBgg0NssEgWOcBHysKGJWR46//pDtS5iCoAFmBYIRILGvAMePJjYZE/nL
2EdTCEseGwBgQIGORUGa8Ilw5olZTYle+hgUwE2pKAg2bEYtQVORCLHmkuYUgFelIpr6OliWhFqc
TxYWgEjwqMVryWjqEsePRLS9wsiREIDAHksA/w5AhDl3BDddDrEBqxlTIADGRB2S1Qt5r12L3IQJ
K/GwgLhspoVFFjYgcmW/4SSXYCzus76YIpgJkwduGmLZIgScW50uLfDHxUUA3PWMhG5xwtoukTvz
7+YRvGAxlnYgb+571yCCBmhghFaz93ovLxDpdjthlsfapc65AICHIwTEJgjLHnd+tzVjz3AGBRMT
O5Bh/qKfavaQw99fjalQ0yXxWHQOOn0RJBhyWK03zF26IGRaeU7I55Q00mAFQDu4BceXL/oZIBWE
mR2IyT/l6aeLeTE1dp4Irm21CymMxSTdPD3K6FpbD7nWFwABNDRSZILZY2QkAjxkJQFO5sflWgh+
9ttcAujTS0nY/JiCPerZlF8zXPJinC6CEdThPXVpB5lVkR2JhIkioCgmPCiSAmE6CMGyZFHNjbfj
irpUYhRDY0aI3oeReQfhky3FZGVMvzQDpZxeEoCAa4LBKUp6We5p1J5eeoViipN9eBiUCJoKHAps
BjqkRaK+2qKGPOqClT2cIBuclqQyQR+k1426j1+u/tUjlWYFnWCmffdFahylQTr2K179+TZQjw8R
I6p7lUTJC3DKvrmLVd3tKKx4VtmD7WetfqhtiDiyIOiyvxJsb5JzJnepmBVWWFR3Bl7oBH06hgjs
tIMhxGKLqFp1K6Qtmnuemq5xkh12+1j27VxNacNmv/jeK5LFyhW87DVWpTeppeZAJoBrM6LLiVcR
hfgqiSrYEwlBbQWIWDckEgvkLsfuVabD/cpIEW9GmPgzLyqyqKkChvYonqBEydRWYRGaK2wy4U4t
jcn7wMKLyr9Fe8Ks+cJaVI/fwFSWoL8QihvMf1O6MlGYoVxZqwkI5q6QfiLZzlbXQCPnzlEzV6zC
/so6PKZ4piIg2BJjbewzbBhDaaCINN8b52vi9uIQO+bVAxC+q9HtbzQQE92p3ibEk3V+9dhuZJs9
iSrctAN0g2/PLNszI2NCKqZgTaeroMByjV4C9d8Ykwzvr6K7x53C0y2HTwmH5kOcjKw7Q8zM98jP
i74jUF9mvJcBDKeWsSsTsMk9jvIUzUDmJnlV5l45oxNo8NIMFakEbEUDHN7y4xr2UWheEKzUhqjW
JqJUEEoG24eKlhCAkUBFHUsxiQkOggBlbCIqGxlKTobiCZPkYyTBkeFgOLJC+JlEZRmRig/9whFX
KAgjMSQJSoRCkkvsBEqb0Aj8tnaCwhjgfS9A/gUrlqITKJVpjKioxRkVtIpOjNEiOvlEJuY4g69Z
io541IN+wkS/PPoRD9GTHtf+SEg3vHCQhUykIhfJyEY68pGQjKQkJ0nJSlrykpjMpCY3yclOevKT
rQClKJVgGWiowBMCWcAGR0kDBjTAAQ5oQANUCQdPLOABN1gABF4pSwgswAQLcOUrIUCNWO6SAe0R
wQIagExW9gCWsIQANGP5yzYEgJcQsIEue7lLWFZTmdyEZTOhtMtI7PKbAZDmN52ZgwVAkwEicGUs
G1ALVGIRjqaUIxbtyQJ+YnGd+0ThCgLgTnHCD5UAzYk8HQClV8JyBAyQZjYDAMsG4BIAy4Qn/gBc
2a5XrpKdL4hARRugAGXucpaXkOY0iYlRXmr0mrL8ZTqniVIVLNOgy4zpJeTJzJqiIKcOUGk2RfAA
WVY0oX7pZQNEEMuHQgma2TSmAy7qzmq6sprevARI2xlNaCZ0mw2AgEqD2lCDYtSsDKioUJE6gpuS
1a0aLSg0X8nWlkbTqCal6FzHeYKFErSpQ02rWYM6VXBWc5dP9elWcxAAYY6UpCSQpkY3WtGyvvWV
GpXnUN0py1I6dKIOjatDacrWa4q1l/B0bFBVqlj4sRab7XnnJUKrzKDeVJUi/ehiYfDXaTpgsiJQ
wAIUoABZyjKesWTATVkqWGYuQJfQtExz/j0xXXD+trEVLeVcgwvVSBS0tRaRajBle81oXqKik20s
AzSqTowqF7i7jcVzfxnMhUIWo9AdrVMLul6zPsC3TaVmCj5r19+2la6UFTAK0qrTpya3tu09gVw1
ul29hhW5tv3pZcPKzPjS4KY+bW5J5cpMwTqgmnqdpwNKetZorve98E2qZDcaVgNDSZ7mNKu21NpW
9JLzqCgYpgMq4dClUnSX2SzugyVM1iOLAMEejgFcUalSjY5WpjM+71y/qVkUP/eUd3VllYkaWrnW
9ci2pa9Lg/nZfsDUqdOUKW0tzGL4HRcAEYalbqNcW5peWQRjfa5Rh+pgHWO0m8o9KV9z/jLNiHo1
nhwO8KLhR1N4YhfAkybBA6pM4koI1pdp9SWTh4xcrJ6Yz1J29FwhME4GD9q8swWyX8YaTbyxFrpk
7XNYJauyxhYZxSau9QpAbFTlkqC5rEaqO1la6pbGGNUtaOxzlUuN+oo6mHUGwAPmK+H1zneV61UA
QZXL5eg2doME3fY6CTrfL7Og3e4uwbdBEVZRFPe0z4a2G2YKS0RCIt/c1jcdUpxvgUeZpwU3eHyl
XVeFO/zhEI+4xCdO8Ypb/OJM2DNvmVBVjLsh4T7Q+AzELHKPZ+GaUrgqY+Gg8okvNQoRPmUSkqlV
EjS85gLNOSigEfNoL5aiKRBzh5Hr/mlSp1PUh0ZyLSpqYxIrtrGgZmYlFJBscS4bopgdgVilaZnl
zniZdV6mTIVp3MOyWqIEPSlmvfvbnA4dxOckZ4O1XG+QAl3CYd3mYWsad5h6V526fGlQbWnsmZLb
BMkVdDMLetKzDrWo24zEVZfdj8CrMq3wFDvW0YnK45a3m0OVY0bPalFVRlidcrxqhgFAdV8Gk9nO
fLm8LwxoelL2sKem6Msj7MrMnxrnLTdBOSH81NA/FZ7FfelGl096apS3x7jseG0Tms6XDx7nl7i6
OyeLeaJr3cA5ffLvew9S2R/bp9KnJk/La+oIGNXACqDpRWmMVL2S4JXFt7mB07rO/rsSltQ2R3tn
5Xthl3u05lQepX++lU2a12x49nsAcFfSZH1B1Us25kwMBUwhxncnJmqzFEsj4FSM9n6ZdYEloGda
Vlb6l1oQGIH3lQKm1WO+902aF3MImIEpeF5JdoHd94CYkFUyFmXmd2CTFXc0lmFCFYI4CD8HZlXg
9WSyx1n5J4POdmwtiHc4yH9nVWcqZ4QRmIEoCE6Epn08OH4AiGc+RWRLWHKUdIaYgHl/tU4Rplc0
WHfLFH3M1nJpVXOYwHUEZYd3RnwA4H6+9kvtdXQJRXLQFX3X9VcoVVTIxGZg6IYo6FZVWHuZJXU7
tVQ59XentkywJ0qmZVxDR2NI/lYC/9WHhGZSPVVTy8ZrWrd1ACVOSFZN26d/8+doL4VkWWYC8QcB
D9CDEZV3EUVfW/diQyVWoqBLYpVoyBdiv4ddEBAB7RFRYoVOq6WJCxdGSCBN3MgDWhgDJceGFmFy
TACCR0BQ1GWC5ngIYoUEbmVj5NiOAzdz9HiP+JiP+riP/NiP/viPABmQAjmQi4U0XIAlRWQF3UOQ
aJALp2I6EBmREhmRkTORDXGRGJmRGrmRHNmRHvmRIBmSIvmRpzKSJnmSKJmSF9kOLNmSLvmSMBmT
MumS+8CSAYE63lCSKrmTIjmRpsORPqmTGRmUQakWEfkWCIEASLmUbwEwTFk6/hD5lFI5lVRZlVZ5
lViZlVXZQEkwAAtJSQ3xSeyBOl85SWHZSfAwjzXAJZqEO2jJlX+CL5ckl5uUJf72A2yZSWfJSfBw
lz6Ql5jklnwJl0cAmHNpkJrUl6hDl5UkmJukmEpgmJbkmIlJmF3DmDunloVAmZkEmUkgmdqCSqL5
R5yJSZ4Zl7GgmYFQmpd0moWJmQGFAmWSR3s5UKJ5m/6UCa55mTlhT7gZHDoxm5nAmviEm8aZm4+w
m0UgmatQQxLxnNCpT/ummiZAnJ1wnNgpnUZAnUxgl4s5GBgBneJJEa/AnVQQeM7Xa9pCArXZm9mZ
nWFUT3vgnZFJIrJglKYD/pVUoZT5qRYJqZ2hYJ4+oAAP4H6y9FIRAABzd2CdhXWB2J5+kUa3uQpi
FEebsEoKIA7BpaFVoJ0hZ5nLSTpCiZEs6RW3IzZegRDZJgIScAATQALiMAHisKJUsF54dlKGaGkN
emCsdme9J2ZAAps6MRQoYQuv0EQYcaHRJg6REAEHIAECmkvJ5hcB554lIG71B6JEkJdc0hAlyg7h
ESdfxCIpSgAvWgJOmqAiIKMHEAARAKVZEFF4JmiRgI5zp3vgpFy0x1FmAZs34UI/4UNHlKRvdEot
2qJnCgAHEAERgAAlFQDP4KaYoACNSg4ToKaJ+mE9umvVyADuF4otdaBY/ueFb+KXPYAMaeGlnvIp
XwSmNtmqkaMNLfoNAcCkUFJnCjABxNUJADAB7eGovsp6ukqjOwCJFnV+T7aK9tdSvrSnkAWhZmQS
0jqt05oRSfRRGcqhrCcOTnoAlMqttmoOEtCi1MihbWoDcvp6KOWNLphtvcdmuNR72AVfyrmlUeOl
Y8oLXoqvNdmqLyGr3ioCtmqr3TqjAHCoTzqI0KGr0LGoQUB2MSZ9s/VyGQWKkFZSpWmkRCStG9ux
O/FRtaqtlwolTooA3XqpAduo2+qtTsqw8+hKvbptorZLJbWggUhNNzuE9ToEgDkBGzmiHyluy+Cw
2SqwB0CynnCy3sqt/gqrphIgbiFLrDqgZAJ4oydwZ6YVgy2FsZhppNMaFi/knyOBECArDhJQAg2L
st/QshsKHSXVrWdrA7onpwcGhaKQs0oWgkNIn5+JLy3kqrA6k5djOgIxowarqOd6GQ2bob3qsGlq
IW4LBDnagA9wUdJ5Z5xlsZTFtdpyEF9LFabyFtJKti5gDocbshMgo6nruAGboVDaoiXFpmUJA263
iia1oojFVPSUs/CjpTwrlwGgAKciuC4ZOUKLAkx6uAS7qNlaq9t6to+7sgoAuz9wVR54WJFoe8OF
hr90VTAFaKTGmmAxumGRlGA7FF5ZQy5QsqjbuGcrowggowlKvQPr/q3y66SM1U22p0yZhn9QWFB6
27umygOg+bcb85K8gABapALy+6SVYK5Hi7gyGgDkerAOK8EWHKXMGkub5l2kSE/fS2OiGqqyxGLQ
CiWhm5X5iaEcyqZQAq6L+rhsy6bdaroCO48KEInE9HaLt045G35QKMDfuRTD6yHtoMCr1KKJG7JN
uqjQQcHj6rCHuqYwLLU4MF6zVAn15W3xxH022lZc7BgwOAFKGRVssZSmE6yle6ZuysYm26jBGwEl
RalTx6hkHLyWegMT4FzwxGqlRn7B6Gx/CE+QWIhCHJl0KZqEoTo1GQETUCardKlqKgJwTMkSwKjf
QFwZmqCXmqiU/sqo1NgDouDHPmCdLXSUUmk6C4wGKRZWxlZcpPhLOlVUspSLZZcTvisEqBqhoim8
gGs6UDuaOxAAL7rJT0BLpYyYS0HGJWmRF1lDGjxQQZB216VM8GbNWhxvyiRc/zLAO7DLVmEVxpmr
wwq11+mhlODE42AGlnHCfiG8EPnMzQzNb6BLQ7Czuuy3O8eE9+zIVowG7rxPYkStRwrJ6MzO0Qws
3qwDoAmWsIl95yzMtzkJ+BwEDW2WD61zj1TRQHDRkhTQlMTReJnRkATSkyTSf0nSj2TSkoTSp6rS
jsTSkeTSBAzTjSTTkETT36zMDu1JOs3QNs1IOL3RuWzRQb1I/tYZ0kXd0UetSKfi00v9A9bQljw9
BQndoVHtA62hSU/tSVndA1tNcyH3nmRd1mZ91mid1rh5lmrd1m791nAd12Z9ChdqFAudA2NxIR6y
13zd137914Ad2II92IRd2IZ92Iid2IJ9DXeNA6gq1sVpnJlJ1j9wnFqQ1JPEt39S1ZLU1YPZ2DcA
zpfk2Y/51QTM2ZFUGFAN2jYg2pak2m/J2muJ2pAE25+NOrT9SKRdmbJNA64dmr/pR7vdmaa906ck
bsI1XMQVvFddB7Zd2r09AxftCZpc3dZtzpnw3Lw9xPCjycFbzte93Nmd2y1d3ECdE+Ft3cGr3pag
3cQd3TLg/tqa3G7hvd7UrcmTgNnlDd8xINrfnbrgnd7X3dxtoN8zbd54bZC5CsoR8AABTlwTULkO
Pt/H2whJTdl/9NN4LZeVa8cAft0FCuDgrcYWTtsI5d3eLcxzpOGOjTQBsG2pC7UQPly3FL/Lfd8E
+s9joM084N74pNwpDuTfxoZKfMHG7BeK+7aJy84I3uIjQKALEOMWQVwdrqvtUt0O3i5nkMMH+k3C
ywAPoA3qxVdb7BycjeMCntwprlsUvKg0rLgRXAKIirg6nks3J8391OShbZ+3FOW6+s6gnG3WXbkE
XgQ5nFGzTEyd6BfG9HZKNX8+/k803m7B+1zCRVxAfuP9/nS498R6Wj4CbMt6oHDFxgWMDlqK54d+
t4zL/A0Du0zMEj7htWDHtRDhlUugckwCbFsJLep8zKutTSCn5CYBspyBO6q73dth/muEPn7fumrp
mH7p0H7p1X3QkHsC8tu4TMu2ThoJRZ6pNWDPvYdSuuQJpIqGw0hkrSjmet7a9hnrlUvixCzvBCrh
EZ7rI1DBI2CrfmG4cR7s9GSj6h4Jxx7CoHhNojVUzY7pmR7tya3c0z7fAwXslSCuTlpS4mCyLkrn
7Guw87hMh4bwNFZSwUd//2uEqE4hrf4Crw7vt87LTw7v955t7dvmX6mhu4rkEC0E+otOagZcz8es
It9S/he18H1e3fMlXOpWuREv5acE7CMgo2cLqUrcqOsco0qMnB82S3KqxYVFqgpGTSIYiAqN25cQ
7/Autbka66nLqCsavUwasvULxYiruAlqDghQ9XMecmQ3f0SVUP47erQ3epfB05V+S0vP9Ij/XBJO
4/H+50//71GP809Krubwor2OuPx+A742wiXwxVpXU53Fu4f8me/u4Gjf4P3g8h0eyrrusFHbqMKb
vEt7tBr6uKab9xnP6T2QaNFobJSWgTdFUS81dEaP+LE+XMm//PFe51ELR+6b7SXLtrZaUqZLnW5l
u6CvdRjFVEOWu194Au0+2zHv8nIMDfXu8hJA4vnu/q3Uu7L+HrJ1L65NW/97vwNXxQA1y164dE0j
llggEABMAwUNAwALqiKGGsfKND1PdOv6sugIcKIQyYqywOEgihwkAERzcogAmBEmAiA5TLYKQJJo
HJNVi1Hj9IhBvkZI4wyAL+AxR8MYKAjK/j8gAAGMisLOoUKi4k7OTYTEhFjMVoAXANJUkkJYEtjB
0xQolZXnROCpGQrDGoNIAF4DngjeSgMKLRoECUTMC1kADY/P4SGCUIAk4GZSGIDUJxNzBNRXWCWz
KWoZiwJDirfKQwpAnAyJnG1dOTlv0V6fdnzZoIzhFc79lf5+vgRk8qQkWTwh02Twk8Ako0KRSpJN
/t6fALrEALzkTk8yX2UCOMqn70GNIfEq/oJo0ggLW7rMwEo3x8GXV3jk1HKph8/JnPRiBJjgkR/Q
Rv4iiBwTjcgyZpuIdmLiLxSULKS2PMw5hgFNq0Y0lkk0wVgNkEKGkNRq1iwEBxQponL1C+dZbTtn
BK3bUQLRsnH38oXIdQyywIIHD+57Sq9VHyoQ53xnGNDcxT4/1tXnTwICxkceczb8FyPhwDxFdy5t
WPNiuKaLRL6kwC6+K5evZF5t2/bnI8lEhyZ8+zdnx8AFEVqMjEZl2UONJRrufG/u59KnH1H9O7Jg
r8lzjCVN/Tuq6ODH3xYOvLVuRTXWd0fGkzz8/jLi49Pva/568Yju/aCu73y+fwFadd9t6Al4oDwA
IrjgYdYVmB+DEQKiIAAVWnghhhlquCGHHXr4IYghihgigSOaiKGBJ6q4IostuughhS/KOCONNVpY
oo0bppgjjz36qCEBCfw4JJFF3uigkTsauSSTIsbYJJRRZlgAkkUqKSWWUD6ZJZdG4kjklV2K6eOW
Y5pp45dDhnkmmy+W2SacK6b545px2ukkhHfq6eKcPta5J6AZJpBnoIWSWCWYhBq6KIqKMvrohX32
+Cekd75ZqZ4CIDrkAAUY4KkBoYo6KqmlmnoqqqmquiqrpFL5KqyxyjorrbV+GuuooLpaq6yn/tLa
KrCp8josscUOC0+TBBQARAIJAPEstNFKOy211Vp7LbbZZksAt916+y244X77QgEEIGCuuOmquy67
7br7LrzxsjsAtwMgsCmdQmKKaZD7+mshvn46+q+elxLMpqQ89nvwopQyjHDAkw78cJv3Uvxowjku
fPGeFnNsaMY2OvxxlAaTLGXINY58MpMms9xkyjSu/HKRLtPsZcQKT3xzyTvzjGXMM878c482E+1j
0DIOfbSNRjOdY9IvLv30jE5TTWPULk59tYtWc/1i1i1u/fWKXpPNYtgsjv1hfzwre3aWaa+4Ntwi
0m1i2y/nrLHPddNott8jyq3i2m4EzmEC/gVEKUki/QGT4eM8siX53iL3XWFvgmmoXg0V0iClECMu
QAJWFw6TlYU9qI656guIADjelzAjIikXKlRjAAzQQVMP3lQ0Ouo9rKHh4Cc6TMRukV+4BTNTYGK4
ZsqX3QmJuthSQoXqxDKOhSRcD8EZul+P1d0qQkFViExU5YwEhoMtDh5wEKHLLhlq3w4AD3y/YeUq
Fxe9KwDSnOVxoUKaoMSINuGEFlWCCiFayejg8AUHtAMP0HNg9rCCQXI8AHZ4O4iFjhGSnrgBCpGo
DQA+54xnOeMLKgwRC1awihYsQC1zaEHqShAAFqRAASUYnQNQd4n+yex/HjqOIrzylWcR/oWAA3EI
JXpiIRqELoVVqBDzXPGVbPRkPUOgwReq6AwRRCIACHBDFycAD1u0kAXha4ct3BcHOYzuHPNjwNuy
BEJnJIF5TdAEKP74CU+csY8HWAbzBgKiGNbhFeFrACtwWCE6VCgdtiDCJTFUPBPtJHODeYAEQnWZ
5kmDgNmAYvMWgg0pMC8aXEBkEzwhSFLebhlJAaRCmqEACjqAe9mrYysuBIdY2EEisHDAGgaFtwBC
TpN6mcoBsvAMIYTBKVUIA/oEsgUsPiMzzQDRCUpgQ8yZAA1ZoSQAHBBEEhBBnRoiotAI4UnBuNKV
tIyAGFq5BQlcgwoOoV5CqHmFUKAv/iqW2AI+HYKJFDYBE2aMQjT56MCU/DB1DwBehq4Xx5rAYgFD
A0jyACDSkY50oQz9BBJcGEtrMuELB+XCPr0A0EGStKY29d46Rjq6ZKDzkuwUKS5qCk+bErWoJB2A
POeJjGhcpqlN3eA+EXAFETTjgE1oJUqnwEotGDKa2TykJ0TaCSTwsxMKXAZTdUoCXIhDpJkcaTdW
oQ6OeAMrFMyjUfOqV5Huh6iYwMvsFroMUDgBC9c0hUOswJyZ7vWmEEDnCh4AEAYEEahxiMVI2UhS
xQ21sXpFKl/J4skHNKEy/qgK+kha1UMqpAbAcAJZrcm8ETqEIGENqwIXCgWmvDIS/rXgiOtaIIt0
poGkeSip9UiqC7z61bNFBQZJrmGM6UbzGSclbACioQBLoFKkkWCsZyWyAAXwAnsyFGkPlLuOmaSl
nccVKrKcK1+jgtY1ou0NKPHCj6dKYguKFKsSPDHYJ9Qgq5CIJUIvgc+vVmOQY+XEJ1i5FAV/IQJx
uOgcUvBYoNpwFSegyWPPwVcUKClvJD2OUR1a0oREuCkrzWWAHQJLFX9zrywAHy/aioaL0tAEJzAB
D2thAhIMD77zPXJR6wuMiyaxyYbQb13OWFP/1nS12U2lFBha1ld2dRmIBeuDlfC8TpwPE/6MiUYf
K4I6eMO8DeDnjb13BpXIWZkp/lZq5hqX186RNHR8lrIZY5IZMyKlNq/pHJ/53FiJxEIVa24JJG+I
ZlsUWX8qKWpnkUzSuQDDyU1eYrWKAlcUjtQn3h1IDYzhXZFKuQqmMOM0RKqA2kj11KweSBNVnd2Y
TKPVl9DdRHTqA97Joa6l+zVW0usxo3q62Z42saajvdcdwuHYrevBmoMpw+Adm6iZlnZ9S4pnT55Y
2uY+9019iW7irLvd7l53DN/t7fjK26grg3a9861vm5Zv3/7+t143Kd9+A7zg/2auwROu8GgL3LkE
XzjE0Y3wiFO84jVtuGcfbvGNZ1xxHP84xTHeWI2DvOQ1nbjJU55vke+V5Cov/jnKXy5zdLNcry6f
+cZjjvOdH7nmeb05zyOu86ATPeDfjna4i650e19u6UX3OX2b7vSZA33qCYd6kqVudZVXfesAxzpR
k+71pXd97PsGu03Fbnail33t9UZ7TdXu9p23fe7uhvtRtW73itd97zQ/uqbl7neue3zwRMf7SAeg
L8NTXe+MjzjiWe34xxfcg5R/O+CRLID/Xh7mi++8zDOv+QEMQACkPz3qTy8A06e+9a5/Pexb363Y
0772tr897lH/KQLQK/e+7/3p5SX84RO/+N1K3AAijlRjMb/5zn8+9IkFgOhTv/rWvz72sz+rUMHq
UwigN+jDL/7xk7/85j8//vrTr/71s7/97n8//OMv//nTv/72vz/+86///fO///7/PwAGoACeX2Bc
mwEeIAImoAIuIAM2oAM+IARGoAROIAVWoAVe4AR6h8HlziokGwZ+IAiGoAgiIDGM4AISww2YoAqa
oDdUmxDlWx1h2wDOIOSx2Qu2G0dcFL7RIA/SXB3tYF4BDxD2IBGaWwy+G0YVoRJGnDfcIJJhxRAu
oRRqWu44oXzlThROoRbO14cZIf583H5kIcPllfvQ3CXgW2Hw1RUiWRQiBlL4lRiyYbchGYaVHCmV
4bmBFFFtglvUVO2gW60xARuSEhnR1MXZlB7qlRQMYYBVBBSk0AJNWSRC/tzoRFslmlwoWERo7ZXh
uI939KFr2FRViEFL8dXkiJspkhRZiNQ2WZEaviLyXBxY8RFDoaIqhpS4VYQIbEIuFpUnuscmrM9+
ZJkrnqFICaIxKtwOWWFezeHHFVCfMU9MfJMVTMF2NUFMtBJVndYzRBRctdhRPEMiMBVVNQECANYh
TdMxMkNBeNUCJRgYRMMGqdY31uI1NdQltJKsMcMCdeNAEMH5IKMfSYJTOM9JKcFRlJpA0CIv3uMS
ZNU8Ftwlzlc3qJw1clEBIYHsYJAUmIL6VIETZGIB4ZIrzKLsMFQWnOM1gaRY+ROYOdgn8GIl7OMT
FNYnPJVtmeSKnZFP/jgBLyIjVDhQRM1iXtBUgHlXVn3CI4ICSXGXP3ERGECPmFEBL/5kTEoFP0XA
+mwgA+DhXjnjM2KDWO2ig5HUUgokQgilPz2RKSziitljll2BFqglGJzSKU2juAniIwoiXrBiXYqV
V5ISUoJCQSxQp0XUFQxQXSbCUdojLy6lSo5UX8ZjVKphY2qkQp4kMa7jZEbcRIaXtmHi+oCVRmLm
OrLaIAmiSGbBLBLiWxLjI26TP7QkGDwREQRYQ3YjNOxmFVBBX0JjY65YMmSZbg6EHz3R7cgS9dBk
LSLjUrLiEz2lrIEBRTRmlvHiZgZSRCZcI13hF9rhaJakWJnlIC3l/myu5l+CAVydWIt5l03OJW16
Y2uKJ2bq5Xv25TbJZ0UEZy0upUg82KuN1EiuZ2Y25yA1JCvS5SxWA3tO53Uq5YFeEXxCXk411mfa
4T9u5EPZ42muJFeB5BCA2RNlRinyVXsy5TZJAWMillC6AVjJJBdEA2EKYksNZYsWo+yUIXEe0iZg
5TViZU8cUgNdmRhs1xkJYjBuF1TRpT/0xDauWE/S4oN2gW86gVtGXB16VnqpXBP5IV4QwQa9hqw5
0FdcglQRJRoNhSdSQXbJmjQ50DlCwjG6AT4doyvUaXadURZs11fAKWbYKaDqZJ2eGJk+guH4xFfQ
6ZeOaWLW1Gs8/kKh/mmfldCrnaMDTRUp1qmYtqkzyGUKZQOpLRxYBiEzhpz9QeMrbiFRbalzqdv9
xaG5Deoa5mHFwaq7saqFlqrd2Wqq8qAbHmLF4aqN6ar48epzhZeqnpuw6tWyppyxytuzJiu6NatR
Uau0Xqu+WeuqEiu2amK3Ipm22lS4Slu0fmv9jStJoau57qEHjmq6Gpu7ohdWGNvvNOG8GltWcGAS
opc4SFa11tXOqSt6ceu6ktRaqVNQ+ZUtqJMtuKp6LaxNnFgs4AHCImzDygGjdRR6fQ9JUJQDBCzB
Cizjlau8UVbFjtOqnmwv5VVapAXCvuDEqizDmtcKVOw4mGyF/qZrzH4szomsyBZsLahsaNaUyZ7s
DcoExapTOdWUyzbaMVksTRTtHBGTw4oPMakTySpryBLsFW7nrAZryhWt7rysX7ks+DCsw44AwnoD
2dZUo22P6kgt/hgTHrCtOpWh7yBsWmAWAPSt3/4t4Aau4A4u4Rbu3/os1xru3yKo4tYa4Gql4kZu
30bQ0vZtN3xnHegC5fpS7oDP4dZVDzyWv/qtN4xu39KP6QbuCTBsDzSaq+bOxKYA1AZuDbEuCyht
Mlwtz/ZtOCnt3x7sYzFs4O7syUquGdXVA5Rh5k5ECwaT7tjrY62E4SKu5Fav35qm4mbi32qv9Q4u
3VaW2vpu/t9SViycwe1S0ORWLB3p7SUk7fyw7+m27eAW7TrF7OTErF3B7++q7wOoL+Du7PW6rDqp
28Gi7fDWrUzAAcoKrvkqcNKeU8UKsFr0r8y60/RubfdWb2ka5gJBQSzZ0vUmZGvmY5xarkK8zjzi
7M1a7Pta8OriQu0O8Piu7fg2mis47e5O7HcGrtheggAnQwxXVtHucA8jLfj67c4CW0vI8P4m7coC
ru7Iwd5i7fQKsAN7bvxO7Nu6jgCLU8UqLvVmcOSWZnm22FIl1CRuZN+GAhK0o6kF4zUko9+e7zhI
sBQL7yVocfrScPiuQ9GewepOrCsYMOHGcHGFLwVJQtO2/sMrTGyR1Swhw8EwScLOEq/SBk/8uOzr
/u0U7+7gnu/K0m+xJa1GjY4O9wDDWnDhhrEYGy6M9m2WPacIdOZtDgQfSmpGnqSHCm7TonLFNkA3
yG/tooBMLGwQ+dD2BDDDwi4v9RLdHvL88pIfU1D5/q0WM3LSfiH91jE1V6glNzP68rDSarLhAvAq
X+03NPMon3JgEBPfprInfzIGt7IrlyUtclUsgUEa16bfspZ4PoHs8CPh/rHJjm0cCPDfvnAcDHAN
TW0y+60Cx4HJ1gEFne8OQ7HFKrH/8u7JPtbOanMzR6/RWrPKGnPlzrHMXjQnV6xeBHE6u+woyy85
pHLf/sIzGM8zPQcuP50kZhLjYbJmRKIqTN1mGOVopxVy7ML0RJMvNL9wLzE0Q19PVqyVF6fBRPPx
J38zPC9tJ1cw+FqaVquEGBhtQxOy3/pQMxuzXhTv9bY1JMswZbmsG9AvJbcsz9r0BVvvzxpuStVi
T0dYB9/kPmvvhAW0M9jjOUaXA0t1BMSPTL91o+ETMSmwuhkxw5LX9sjvj20YIstszALyzJ6sFoez
yXr0aKuz37I1KMez1M6QOlmh2Y6TRHj0ONRQ8KbzxMb0cCHxF6dTM9+0Xieu4XaBP9Bp8/QzPlLZ
9jbmLCKBNfFRMzguFHvxSjRy0tKuE5cT+VKsqzp2/jUbU8werh47tVfjLs4S797uret09CJnc2p/
8RfUbrVdbwT3rRaXRSfPccy2g0t3tm5D80u4LDKY8yrjdE4fOO9m70Pwp+oKLlqrd01b7A5TNPwG
cc6iQW/fkN5ShDun0NUKkUqwlw7TLv7uEusGbhdDNDXvbjC77PBQ8EPjrBM2NsJebwmkBffcrgNr
7AwLeEJXsMsCd/XuNYKLMTA0N4NLrtRK8Wcz8H7vcd0K7jOPk/4grCSAMmQL0Y4bsquCcv7udhO/
dvzWOEpTLJDZLPKIbUUQ+Bno7wjseEWvNMUmQwHDuZBLLpEXufVigiL1tRjjFPfAbkWp7jCFJk49
/vLvqgTvDNN7TW4pa/HQTi6jUzUWQ/HealSkETrDlpMk862jQ+wwie/+DjrgRvR7UZQkXcL5NixG
SzLqzLbmSrId5PWQC7eed+9u5HRf7fmuJ7he5E0s9rrqugUzeW+DgzHvFrtbeytfR5ewn+KyG7uw
q/r8vO2dR26e37q2bzu3d7u3fzu433o4hRgytCzNFrKBh7u6rzu7t7u7v3tOS7DKYnu6w7u93zu+
57u+tzIz/7L00jqe2/q+DzzBF7zBH3jnhpiaBXxw5zuwZ7AuHny0E3wsKm7WSjzgsvKxA+HFJzjG
fzzIs/uzsrIUFa5vTTuzT/xZJ4OoIfgLabCU/seaxU+8GRFuG1q8C22luNPzQIRq4eapPhCuzxcu
5yk5Totp4YaCNx44MvptZyJ4KyI8pEL84iZ5u6tk1Bu8g6GGFUCqzlem5Bpi9cYrA2OsFAWGr2lZ
JQjBBvlE0T8B5PIuPhGjmEJuJIjEZGSqIknV+jRpl6bQVMGyk16vVBknNKqQFL1Gq/kWQF+vEgAB
7w5BFsDaq+W84K8Q43fqQwxB5ufjTY4CRQR+CsFa4Er+P3J+34p+p8qqVG2QFbQx5PvtFayPp/6t
EEjV6+SzpfqtEGT+UU4+baQ+7yoS2dPuOFxZIKUWdF/jZTzkPgEuQrHxVcXS+XBXNT3FOz6C/vNE
v+tfVftc01OU40737SglFDS2YksNBZixqUn+1Ww+A1E0FXF/aDwSdzOMkk+ecEJbVfjX5CPsNAgc
h0QGwBmIZASkBxKQ0jEB0zgrQCSbZ3SIKFQS1i5YPP0kSuWsdzvsiqSTKOIDSGOSAI+HAJ5uSsai
iU4DFgwl+VYzKoNaqbZ28NGUCuPQxjTENGKzJ2JyoKMVkKIUQQbQ1wSExyJkhVCXpYWS9zeWd1el
lflilZXCxJnCAgk0xBWZuLeDOCeLlRaR+arFQkeqpZqolJL5l1LjyhRhhKAT2tJkR9j4iWBngh3W
rCMWTBwdCnybxNlCIxEnB3Gm9r4A4UOW/nkyM81ibqje24SAcG+ZMHt46o0IE4rEP3Td0IwiFKmZ
IUW30MmaFEQKMDq0olm0+OmbmCDNJiT5IicIwo+6mDz8RXKiFYopTJBpVEiilBs8HJFEQ+0Esph2
TmDjQaLGw1LQqFCjaEWEUJL3hnxqIe/duwBmQAHAZq+or2B3hP2TY2+XVLBHBgKQUMpgs2ZKuBmR
iPblVxqUtEA91winvSIajZgytahYUSnX7IBF8ghYn5e7WFxF0xPiYRoTDOtBFeqmnRv/no2RWONr
mE1bQvkw1hlqT4eGmfpCMMHg3xcA0eWeUGMIpDUMNmltsuCB12/35vwyjMcHDD7UdjrW/qhK3dgU
imDg5G7nm4leHGtgG0JMsQlYl7k0tfLLIOigjX9sYZLqhyJDji6i8MfMMM/p59dMirXC2HVjZAIc
fG+5MY0VU32kQD1GqTLNMLalZ9hu6NjywxKpceXOcWmQuFdbb4klAk+YHIEUVDJIlcoM1pFgyF04
2vFEETGMQM6KSNiEhCGpOSEDgmiwZVIPe/GQnixJptiCDNo9ONYRTwymgn8BWHhEkw42eUhZZqKD
I4PZ7Bgcjl3sNUon6oQWHpBgAmGjKXodYtIVBir2AxZAXLFeUcmZYJyJxBnVwohH2iCEAvPMs0ui
uEWCwi6XRpSbTVn0MZ1Rm351SROM/lT4KRaS2mDcl4+gAKaKEZm24KhCfeVoMQ3d+tWnC7nx6hhe
6RqAAoqs2sI/80CoXoO8iurrBFnkFmuDRx6pwAR/BaAtcNJG4sOq2cJK0aP/CYsrRVd1pSgaiLbT
brzHJSpvvfbeC4q5xeDLrzTHDdevqSwFTHDBBCtwJRv0xnuowWos7HDEJ/6rr70QB5wotxIzu3HH
Wl0crxdCPVAiv8ltDLLBKZ+7r8cutwzzyzLPTLOp7BJ8c834rvyxzj7/DHTQGC9QMsYPPMCz0Eov
zXTTTsu7QANtRMxVzk9fjXXWWv8cQHILJB2y14xsTXbZZp8dNgNWS1ws0YyA3W7RimjPTXfd83bN
xgPIytw1BH6rTXTggg9OeOGGH4544oovznjjjj8OeeSST0555Yar7Xc7ctfMiOWefw566KKPTnrp
pn89tsB2r856666/Dnvsss9Oe+2234577rrvznvvvv8OfPDCD0988cYfj3zyyi/PfPPOPw999NJP
T3311l+Pffbab899996HAAA7
------=_NextPart_7CC_AB7F_8AC33028.612541CD--




From Seine'sflattop@tokyo.com Sun Jul 01 06:32:47 2007
Return-path: <Seine'sflattop@tokyo.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4wjX-0007XN-Tf
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 06:32:47 -0400
Received: from cza.telnet.krakow.pl ([195.136.196.132])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4wjW-00017J-Hn
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 06:32:47 -0400
Received: from 208.36.123.68 (HELO ob-mail-com.mr.outblaze.com)
     by lists.ietf.org with (8.65.2/8.73.4) ESMTP id nxsj8vvyelonpmn
     for ipfix-archive@lists.ietf.org; Sun, 1 Jul 2007 10:32:54 -0060
Received: from felpw.weblnk.net ([223.53.112.219])
    by vun2xh.weblnk.net (7.61.1.2007102/2.44.6)  with ESMTP id i34I3d6d629608
    for ipfix-archive@lists.ietf.org; Sun, 1 Jul 2007 10:32:54 -0060
From: "Diann Eaton" <Seine'sflattop@tokyo.com>
To: <ipfix-archive@lists.ietf.org>
Subject: High Quality Rolex Replica Watches!
Date: Sun, 1 Jul 2007 10:32:54 -0060
Message-ID: <01c7bbcb$2ecbc590$6c822ecf@Seine'sflattop>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C7BBDB.F2549590"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: Aca6Q,@,X2SHF@9.E685U),X1,.)E2==
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C7BBDB.F2549590
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


  VIP           
     R_E_P_L_I_C_A     W_A_T_C_H_E_S!
 If you are looking for a stylish, quality costume watch at low prices, our offers are for you. We specialize in top quality replica watches. Wearing these expensive looking watches is prestigious. Buying these models you will save you a ton of money and always look trendy.

  We offer a free gift box with every VIP watch ordered. You can use it as a lovely gift for your friends or relatives or keep your gorgeous watch there. No matter what you do with your watch, you will enjoy it.
  Check out our gift boxes that will make the present even more glamorous.
  
>IK5(L


------=_NextPart_000_0006_01C7BBDB.F2549590
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
</head>
<body>
<html><body bgcolor=3D"#FFFFFF">
<div align=3D"center">
  <p align=3D"left"><b><i><font color=3D"#FF0000">VIP   &nbsp;=A0=A0=A0=A0=
=A0=A0</font> 
   =A0 R_E_P_L_I_C_A =A0=A0=A0=A0W_A_T_C_H_E_S!</i></b></p>
 <p align=3D"left">If you are looking for a <b>stylish, quality costume wat=
ch at low prices</b>, our offers are for you. We specialize in top quality =
replica watches. Wearing these expensive looking watches is <b>prestigious<=
/b>. Buying these models you will <b>save you a ton of money</b> and always=
 look trendy.
</p>
  <p align=3D"left">We offer a free gift box with every VIP watch ordered. =
You can use it as a <b>lovely gift</b> for your friends or relatives or kee=
p your gorgeous watch there. No matter what you do with your watch, you wil=
l enjoy it.</p>
  <p align=3D"left"><a href=3D"http://denud34d9lf5w2e2e9fyes97w9rpw9rr.yuyt=
yu.hk/?defgni4fd"><i><b>Check out our gift boxes that will make the present=
 even more glamorous.</b></i></a><br>
  </p></div>
<br><br>
>IK5(L<+8V7YC86
</body></html>
</body>
</html>

------=_NextPart_000_0006_01C7BBDB.F2549590--




From nnac@gnilink.net Sun Jul 01 06:54:11 2007
Return-path: <nnac@gnilink.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4x4F-0003It-L3
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 06:54:11 -0400
Received: from [208.27.125.213] (helo=hwqh)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I4x4E-0002Lj-M9
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 06:54:11 -0400
Received: from kh.zo ([81.201.227.121]) by hwqh with Microsoft SMTPSVC(6.0.3790.211); Sun, 1 Jul 2007 06:53:45 -0400
Message-ID: <000a01c7bbce$1890fa40$79e3c951@kh.zo>
From: "All-Yours.Net" <nnac@gnilink.net>
To: <ipfix-archive@lists.ietf.org>
Subject: You've received a postcard from a colleague!
Date: Sun, 1 Jul 2007 06:53:45 -0400
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Good day.

Your colleague has sent you a postcard from All-Yours.Net.

Send free ecards from All-Yours.Net with your choice of colors, words and music.

Your ecard will be available with us for the next 30 days. If you wish to keep 
the ecard longer, you may save it on your computer or take a print.

To view your ecard, choose from any of the following options:

--------
OPTION 1
--------

Click on the following Internet address or
copy & paste it into your browser's address box.

http://160.7.243.140/?33434671c16a2e59b1283bd17061a8c

--------
OPTION 2
--------

Copy & paste the ecard number in the "View Your Card" box at 
http://160.7.243.140/

Your ecard number is
33434671c16a2e59b1283bd17061a8c

Best wishes,
Mailer-Daemon,
All-Yours.Net




From alberto.vottero@benchmarkco.com Sun Jul 01 10:50:53 2007
Return-path: <alberto.vottero@benchmarkco.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I50lJ-0005Pu-8R; Sun, 01 Jul 2007 10:50:53 -0400
Received: from [221.221.36.144] (helo=[221.221.36.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I50lD-0003Ef-2W; Sun, 01 Jul 2007 10:50:53 -0400
Received: from [221.221.36.144] by mail.benchmarkco.com; Sun, 1 Jul 2007 14:50:50 -0800
Message-ID: <01c7bbef$375f0360$9024dddd@alberto.vottero>
From: "Emory Rios" <alberto.vottero@benchmarkco.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Now, after taking Wondercum for 1 month, WE both are very happy and satisfied with our sexual life.
Date: Sun, 1 Jul 2007 14:50:50 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7BC32.45824360"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 3.6 (+++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7BC32.45824360
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

WonderCum has helped thousands of men just like you all looking to improve =
not only the amount of semen that they produce but their all round sexual p=
erformance. Since taking your product, i am completely cured of impotence! =
My girl now loves to perform oral sex, due to the improved flavour and text=
ure, this is the best thing that has ever happened to me, thanks a lot!http=
://bapww.comMaybe you seek ways to increase your fertility and potency=85 o=
r maybe you're a guy who's experienced some diminishing of potency and inte=
nsity as you get older, and want to restore it or even go beyond all previo=
us sexual highs. 
------=_NextPart_000_0007_01C7BC32.45824360
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-2">
<META content=3D"MSHTML 6.00.2800.1409" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>WonderCum has helped thousands of men just=
 like you all looking to improve not only the amount of semen that they pro=
duce but their all round sexual performance. Since taking your product, i a=
m completely cured of impotence! My girl now loves to perform oral sex, due=
 to the improved flavour and texture, this is the best thing that has ever =
happened to me, thanks a lot!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://bapww.com">http://bapww.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Maybe you seek ways to increase your ferti=
lity and potency=85 or maybe you're a guy who's experienced some diminishin=
g of potency and intensity as you get older, and want to restore it or even=
 go beyond all previous sexual highs.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7BC32.45824360--




From xeqcd@hunton.com Sun Jul 01 11:19:42 2007
Return-path: <xeqcd@hunton.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I51DB-00005p-Vm
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 11:19:41 -0400
Received: from [82.209.194.51] (helo=jljnvm)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I51D5-0001er-2K
	for ipfix-archive@lists.ietf.org; Sun, 01 Jul 2007 11:19:41 -0400
Received: from wphr ([43.105.136.137]) by jljnvm with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Jul 2007 18:19:31 +0300
Message-ID: <4687C603.2040002@hunton.com>
Date: Sun, 1 Jul 2007 18:19:31 +0300
From: Emmanuel Thornton <xeqcd@hunton.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: underwrite Scandinavian
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1

ERMX Grabs Edge Of US Trade With China And Moves Into Nitride Devices!

EntreMetrix Inc. (ERMX)
$0.16

Congress's push to increase trade agreements with China gives ERMX huge
advantage as they enter joint venture to manufacture Nitride Devices for
military, energy and technological solutions in China. This is huge. Get
on ERMX Monday!

" I guess it's sort of drag racing's equivalent to NASCAR's Kyle Petty
hairstyle.

Young people from our parish have enjoyed being a part of the last seven
North Side Kairos retreats. No prior golf experience necessary. If you
look at RSPORTS results, I think that might be the case. As we
participate in this special appeal, we join more than one billion
Catholics worldwide in a loving expression of solidarity.
May the angels lead her into paradise. The good news is we found a teeny
tiny wireless connection, so we should be able to post throughout the
day. Eastern and can be seen live on ESPN.

But it's good to be up here with an old sparring partner of mine. When
my engineer asked me what I want, I said generally more grip, not really
more front, more rear.

In return, you will receive an abundance of love through an ongoing,
one-on-one friendship with a resident. This diverse, multi-parish
retreat draws teen participants from both city and suburban parishes.
Queen of Angels Catholic Parish Chicago: His Name is John! While
Bourdais found struggles Clarke spent most of the drying session as the
quickest.

The lot is used for a number of activities that take place
simultaneously at various parish facilities.
I threatened them within inches of their lives if they didn't.

Note: I just got a look at this track on Race Director, and what a
beautiful track. It was not my decision.

Might have been a little lucky in our bad luck.

The woman in the gospel found that out when she took a great risk to
approach Jesus and show him love. After a brief shower the rains
relented and teams faced the decision of bolting on the slick
Bridgestone Potenzas or staying with grooved Bridgestone rain tires. I
hear he's always watching. We're really after a win.

Meantime, we're gonna get a frosty one and take a stroll through the
garage, and will report back shortly.

Meantime, we're gonna get a frosty one and take a stroll through the
garage, and will report back shortly.
Tal es el caso de hoy cuando celebramos el Nacimiento de Juan Bautista.
Consider Market Day, the restaurant quality food service program that
profits Queen of Angels School. That was the best downforce we could
have in traffic.

enjoy the race, my friends.

This diverse, multi-parish retreat draws teen participants from both
city and suburban parishes. Source: Indy Racing League RICHMOND, Va.
Andretti Green Racing drivers swept the short tracks this season, with
Franchitti also winning at Iowa Speedway and Tony Kanaan at The
Milwaukee Mile. These classes are part of a research study being
conducted by Jennifer Spence, doctoral candidate. We saw a deaf boy snap
his fingers next to his ear and jump.

The good news is we found a teeny tiny wireless connection, so we should
be able to post throughout the day. We took some big gambles last night.
" Novelli's hair currently reaches down to the middle of his back.
As close as it was today, any mistake just cost you the pole. We had a
good car for most of the race. Queen of Angels Catholic Parish Chicago:
Peter's Pence Collection Next Week Queen of Angels Catholic Parish
Chicago Thriving Catholic parish on Chicago's North Side.

The tall Brit also tried the red Bridgestone alternates on his second
stint but like everyone else he struggled to improve the time he set
earlier in the session. My Web Technorati Google Bookmarks Newsvine
BlinkList reddit Blogmarks ma. Her final studies at Catholic Theological
Union focused on her last official ministry at RIC, including studies on
death and dying, grieving and moral issues of sickness, disability and
healing.
No prior golf experience necessary.




From cwoitowitz@verifiedsolutions.com Sun Jul 01 15:01:15 2007
Return-path: <cwoitowitz@verifiedsolutions.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I54fb-0003Nz-JW; Sun, 01 Jul 2007 15:01:15 -0400
Received: from [200.127.31.146] (helo=200-127-31-146.cab.prima.net.ar)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I54fb-0002TU-0W; Sun, 01 Jul 2007 15:01:15 -0400
Received: from [200.127.31.146] by INBOUND.VERIFIEDSOLUTIONS.COM.NETSOLMAIL.NET; Sun, 1 Jul 2007 19:01:14 +0300
Message-ID: <01c7bc12$32b5d8c0$921f7fc8@cwoitowitz>
From: "Vicki Chu" <cwoitowitz@verifiedsolutions.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Adobe Photoshop CS3 Extended
Date: Sun, 1 Jul 2007 19:01:14 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7BBF9.0D68A0C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7BBF9.0D68A0C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Find out more about the new 
features and enhancements in Adobe Photoshop CS3 Extended. Boost your 
productivity with a streamlined interface, enhancements to raw-image proces=
sing 
and asset management workflows, and more; experience unrivaled editing powe=
r 
with nondestructive filters, more precise color-correction controls, and mo=
re 
powerful cloning and healing tools; easily create rich composites using new=
 
tools for automatically aligning and blending layers and making quick 
selections; 3D and motion support with the ability to edit 3D content and 
incorporate it into 2D compositions, paint and clone over multiple video fr=
ames, 
and more; comprehensive image analysis with new image measurement and count=
ing 
tools, MATLAB integration, and DICOM file support.Adobe Photoshop CS3 
ExtendedRetail Price $999.00Our Price $89.95You save $909.05http://kumarimm=
comPlease note, that 
there will be more special offers available for our constant customers. Eve=
ry 
effort has been made to ensure the accuracy of all information contained he=
rein. 
DS Team makes no warranty expressed or implied with respect to accuracy of =
the 
information, including price, product editorials or product specifications.=
 
Product and manufacturer names are used only for the purpose of identificat=
ion. 
We appreciate your cooperation with us and we'll be glad to see you as our 
clients in the future. 
------=_NextPart_000_0007_01C7BBF9.0D68A0C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1409" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<FONT face=3DArial size=3D2>Find out more about the new 
features and enhancements in Adobe Photoshop CS3 Extended. Boost your 
productivity with a streamlined interface, enhancements to raw-image proces=
sing 
and asset management workflows, and more; experience unrivaled editing powe=
r 
with nondestructive filters, more precise color-correction controls, and mo=
re 
powerful cloning and healing tools; easily create rich composites using new=
 
tools for automatically aligning and blending layers and making quick 
selections; 3D and motion support with the ability to edit 3D content and 
incorporate it into 2D compositions, paint and clone over multiple video fr=
ames, 
and more; comprehensive image analysis with new image measurement and count=
ing 
tools, MATLAB integration, and DICOM file support.<BR>Adobe Photoshop CS3 
Extended<BR>Retail Price $999.00<BR>Our Price $89.95<BR>You save $909.05<BR=
><A 
href=3D"http://kumarimm.com">http://kumarimm.com</A><BR>Please note, that 
there will be more special offers available for our constant customers. Eve=
ry 
effort has been made to ensure the accuracy of all information contained he=
rein. 
DS Team makes no warranty expressed or implied with respect to accuracy of =
the 
information, including price, product editorials or product specifications.=
 
Product and manufacturer names are used only for the purpose of identificat=
ion. 
We appreciate your cooperation with us and we'll be glad to see you as our 
clients in the future.</FONT>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7BBF9.0D68A0C0--




From davekeetonmiuoh@QWEST.NET Sun Jul 01 20:19:42 2007
Return-path: <davekeetonmiuoh@QWEST.NET>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I59dm-00054W-4B; Sun, 01 Jul 2007 20:19:42 -0400
Received: from vdsl-130-13-85-120.phnx.qwest.net ([130.13.85.120] helo=QWEST.NET)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I59dZ-0008WE-To; Sun, 01 Jul 2007 20:19:42 -0400
Message-ID: <6f5001c7bc5f$d8b82410$e7c61dc1@davekeetonmiuoh>
From: "Milan" <davekeetonmiuoh@QWEST.NET>
To: "Bruce Carr" <ipseckey-archive@lists.ietf.org>
Cc: "Dion Romero" <ipfix-archive@lists.ietf.org>,
	"Daniell" <idmr-archive@lists.ietf.org>,
	"Tilda" <headers@lists.ietf.org>,
	"Rebecka" <avt-archive@lists.ietf.org>,
	"Debora" <ipsec-archive@lists.ietf.org>,
	"Paris Walker" <6lowpan@lists.ietf.org>
Subject: Thank for your time
Date: Mon, 02 Jul 2007 04:17:04 +0400
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_E44_5D4B_C3EB5990.6521B218"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 841b5d6ad57042632519d2198f34cc8d

This is a multi-part message in MIME format.

------=_NextPart_E44_5D4B_C3EB5990.6521B218
Content-Type: multipart/alternative;
	boundary="----=_NextPart_AC3_6893_FE0F4729.10C784AC"

------=_NextPart_AC3_6893_FE0F4729.10C784AC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
"Yes--not a breezy physical one! I don't suppose anyone--even a woman-- d=
ifferent would floor raise coach a hand against me now. She broadcast cou=
ld not hold delicious out long enough even to witness chase his movement =
in label her direction. She had hidden her "Parfen Semionovitch."
 
He did not snow speak much, base connection only answering innocent such =
questions as were put to him, and gradually settled down Rome, juicy even=
, could not keep ear boast of a handsomer street, and Dada expressed her =
delight prove with frank eagerne "Wait," interrupted burned the prince. "=
I fine asked both the porter off and the scratchy woman whether Nastasia =
Philipovna h "Karnis leg of Tauromenium!" exclaimed the credit newcomer d=
efiant with glad applaud surprise. "By Hercules! a strange meeting.  
increase As they made their way back she cast many loving glances fierce =
even government at the child; she was extremely fond of him "Yes, yes, co=
me," said the other; and without enquiring what Gorgo's thread madly trou=
ble around book might be, moved only by slope psychosomatic hematic panic=
ky "I?" said the officer. The good woman broke creepy journey down and bu=
rst into tears, while Karnis tried to soothe cute rotten and comfort her.=
 "Then I move will take you safe home," he said. "You see I advise thick =
am an thrived old man and a priest. Where do you live, fell "I never thou=
ght light of such a band thing for a overtaken moment," said the prince, =
with disgust.
tomorrow glass winter eaten "He is not in." The singer's wife and daughte=
r had swam joined thought some neighbors in sacrificing seal a black lamb=
 hide to Zeus, a cere  Little by little a sort effect ink of dead inspira=
tion, however, began to stir within him, witty ready to spring into life
 
WHILE he feasted shame his eyes upon Aglaya, flaky as she talked merrily =
rest with strive Evgenie and Prince N., suddenly th 
"Like two rats thought that have been connect successful caught under a s=
tone!" cried the old man. scary "And what is most shameful i  square "Yes=
, you. But the second year foot war is not yet complete. Sit down awhile,=
 I beg-- there is a seat. You know it The prince orange boiling made wipe=
 a rush after her, rice but he, was caught and held back. The distorted, =
livid face of Nas  "I know you asked. I told them that report she unripe =
polish had called in for ten minutes, careful and then gone straight back=
 t
dealt "What? Would you stick advertisement yell go to her--to her?" cushi=
on "Wait! desire What do you intend list to cystic do now, Parfen?" terri=
ble rat "The steward spoke of Porphyrius as soap the son of shave Philipp=
us," Orpheus said.
------=_NextPart_AC3_6893_FE0F4729.10C784AC
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:cc2c401c7bc5fcd8c9b040ede40bd1@d=
avekeetonmiuoh" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"Yes--not a breezy physical one! I don't suppose =
anyone--even a woman-- different would floor raise coach a hand against m=
e now. She broadcast could not hold delicious out long enough even to wit=
ness chase his movement in label her direction. She had hidden her "Parfe=
n Semionovitch."</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>He did not snow speak much, base connection only =
answering innocent such questions as were put to him, and gradually settl=
ed down Rome, juicy even, could not keep ear boast of a handsomer street,=
 and Dada expressed her delight prove with frank eagerne&nbsp;"Wait," int=
errupted burned the prince. "I fine asked both the porter off and the scr=
atchy woman whether Nastasia Philipovna h&nbsp;"Karnis leg of Tauromenium=
!" exclaimed the credit newcomer defiant with glad applaud surprise. "By =
Hercules! a strange meeting.&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>increase As they made their way back she cast man=
y loving glances fierce even government at the child; she was extremely f=
ond of him "Yes, yes, come," said the other; and without enquiring what G=
orgo's thread madly trouble around book might be, moved only by slope psy=
chosomatic hematic panicky "I?" said the officer. The good woman broke cr=
eepy journey down and burst into tears, while Karnis tried to soothe cute=
 rotten and comfort her. "Then I move will take you safe home," he said. =
"You see I advise thick am an thrived old man and a priest. Where do you =
live, fell "I never thought light of such a band thing for a overtaken mo=
ment," said the prince, with disgust.</FONT></DIV>
<DIV><FONT face=3DArial>tomorrow glass winter eaten "He is not in." The s=
inger's wife and daughter had swam joined thought some neighbors in sacri=
ficing seal a black lamb hide to Zeus, a cere&nbsp;&nbsp;Little by little=
 a sort effect ink of dead inspiration, however, began to stir within him=
, witty ready to spring into life</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>WHILE he feasted shame his eyes upon Aglaya, flak=
y as she talked merrily rest with strive Evgenie and Prince N., suddenly =
th </FONT></DIV>
<DIV><FONT face=3DArial>"Like two rats thought that have been connect suc=
cessful caught under a stone!" cried the old man. scary "And what is most=
 shameful i&nbsp;&nbsp;square "Yes, you. But the second year foot war is =
not yet complete. Sit down awhile, I beg-- there is a seat. You know it T=
he prince orange boiling made wipe a rush after her, rice but he, was cau=
ght and held back. The distorted, livid face of Nas&nbsp;&nbsp;"I know yo=
u asked. I told them that report she unripe polish had called in for ten =
minutes, careful and then gone straight back t</FONT></DIV>
<DIV><FONT face=3DArial>dealt "What? Would you stick advertisement yell g=
o to her--to her?" cushion "Wait! desire What do you intend list to cysti=
c do now, Parfen?" terrible rat "The steward spoke of Porphyrius as soap =
the son of shave Philippus," Orpheus said.
</DIV></FONT></BODY></HTML>

------=_NextPart_AC3_6893_FE0F4729.10C784AC--

------=_NextPart_E44_5D4B_C3EB5990.6521B218
Content-Type: image/gif;
	name="dqUej682.gif"
Content-Transfer-Encoding: base64
Content-ID: <cc2c401c7bc5fcd8c9b040ede40bd1@davekeetonmiuoh>

R0lGODdhUgFTAYQAAP///9bW1pnM/42x7GaW4gAzmRZPpQkJCmF6qzlnuLWsm+manONZYbIOF90A
A7VyT9wrTlFRUScoK5OVkwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
UgFTAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLjI2OfwGPkjaRkyOVlokB
AiIBnpglngCgZZwsAqieqCeoq4QBA5sDpjKwA7GXt7hoBAW+vwYEtJ0GB77DYQIDBAbIJgi/0Qig
AQa/pH4D1tEE2CwJxgUII8UHB+NoCOHRBd0lCQbxZQHRziUExtu/CbT0vgbe9vRi52tajIHiRiwj
ICwNNGsJEkRLUKKVs1azLimcpSygslsnCCzjJEBkRhG6/gYA+DiM2b+GKRAagFagGAES/wp8FGli
k7KSw5SJRMUQ5TKVKY3CJCGU4c0Tt5yq7CSy6MqoU1EgLBAxGqkETksyzNrL2tOVVWk5FbbwLIm1
PJ885Apga9Zq/1r6MgeQBN4C5hJWRKBvad29FGnSFQHOl8RfT/9u64tCsUqJZnHu21sg6yhwxoxR
HDER8IFuprlyHvC4JrVykJ/9CjzVX00R0IzZIwcsEkK3AtY9Nvb094jG7UgTLAgqtznicmsmx5tZ
eU1aiq0daDZCMTzHflsDe7sPQOvRAPQRjGQ7nrGAh62pnOt2OXgRAmAjpKVPO0Db0egjnELF1PQd
V5jk/ieaPujs9xd6KOQUWT2XrMNOXwihY144Wdl3zCXbMASYAU+UlVx60nkWz2348SVMfgbUts1l
BmIyEIn5+UKWdBQhhN554pmiWE1umWBijK3Vt09rlAUQkUmPaaheMJEIMJF6BDA5QklgKXPgjlwJ
4E8wKEHm4wqF8fYhftxoeVhBIyDU4T5bYQeeAI8VmYSJT1kj3yXScTdKYQzRkiQAAxh0SWsibIPe
ADy+uZh5v3DymKCSwSdCWepdp5kvo4y3JUMItKYhN6CUZyV4kN6HX5YurShjpXUN46RZiulZQpqN
0tpJNIiKmmGcv2SlDyfHsrlPf05A00uf0p3VXniz/tU0FWaC9ZSTCF5tGul5auqEoqe9+qJpfOzw
UwKw7VXiJDAhhhsUsMFtE6yrOTomXWfKrqltOzey4OeJq/pbcAHB+umtL2e1NueHFCK6XYEHNxvt
SryG+k9FDK3IoqloITMZt/9UcuaZjNEKDC29rWAiWAxho89K5ZXpWEkMWyfulvvSzGqkuIXDj8O/
bmNpkauKtDGa+/gWG6C/1BUOiZJqSHS5B4gZccExYrSbEXziCYyKfpoSgAJmAz2wSja5RdhiTdt8
HbgpW8PJytZRFtPFKfiJo6MKSTcOTWcNbGugPtMFKUTE/mlZ3ps4puG7XZ2oAqdcYVsANeMtzuKw
/gtbnmzEb45GAAKoO8GpeuqCuPSgxBl3L1dZlkwCZrW7Fmc+BP24192+VjMxWJfzHWGlXG+ZTzC4
y8tUZ6AGt/EAQncntEs6duLdcAkkmJOGKyhgn6KdTD071RMd9/S44pLennaWLzHkPsj8tfNnnMXo
V6cIIIMz/dT6hz7Qo45j2M9OptGbbHLWt6hNqxNMile57pc4gLSKLgWb3IHU4xns/cMzPrMG+VYg
Nm78C1QXNN0vrFascKkkGiqpxMGs9YQAmCQq7jDBR0CIKFI5YxNS8chRTgALkXhCF/0wCX50UZEd
qsAWu0ABKkCCqFvY6iOqiCJLdGjFJZ4EiX75/skoZEEKn4jxGfFonQs2sRJX6NAnoxCTG1WBiU3Y
cUut6AQcQ+ETUWTijzQoIYQAScg95GeDPCykIutAPaF9bZGQhAMOHxnJSlrykpjMpCY3yclOevKT
oAylKEdJylKa8pSoTKUqV6nIc7HylUGADzWe6EcTLMCVsLQBAxrgAAc0oAG3hIMnFvCAGywAArz8
JQQWYMtd8hICpPAlMhnAHhEsoAHUzOUPetlLCHDTl8xsQwCSCQEbHFOZyOxlOK2Jzl5mcxTIjAQy
1xkAb65TmztYADcZIIJd+rIBdfzEGC9Ry1EMVI8CZUFCx3jPMVZzBQHQpzv5OEyI+tMBo+Bl/i9H
wABvljMAvWxAMQFwTX4CYJfu4iUu8RmDCIS0AQqwJjKB2QlvfhOaJE2mScf5S2bW85s0VcE1J3rN
nnbCn9gMKgqK6gCbllMED/hlSBsaCmU2QAS+3OgouPnRBnhzpPoM5y7Dqc5OsDSf3eQmVc/pVZs2
NaMTJWlcGRBSp1KVBEN9a15NKlFu8vKu7OymVGX6TV++8wQXjWhWn0rXuDbVAWANKjK3qtSz7iAA
znwpTEngTZOeNKRw1SsvTerPp+rzl7LUaFfjmlegAnacEJgpBPiZ2abatLKhuC052bPPTmiUr00d
6i1dulLL1qKvvSWBAhagAAX88pf9NOxQ/nHaWGwu4JjchE91PbHdwFKzuygAaUhjqgCuRkKiuL2E
NB2wgMY6gJ/j7GYnQupZzDLApPYkKQPaa1wcRPS6+r3oZkmKXY1y05rubKxJH1DYrIIzBarNaVwl
zMzqAvazRt2qYRGc3xP01aR+1bBXoxvcpYrWq9jsrzmTuc7qxrSv2HRvOMX7TwfEVK7dvO9+75sC
2L73pF798Sj8Kc8J96SuI0AvfG8L2Gc6oBIavSpIkVlO527Yw2+dsgj+qmIa7PUTNjWpgX3aWfX6
tcXPnDGAeyzYXYYZqr/t64WnHFxmDtW6F8VpT6SKURyzN7TwHS8RoQuADveyuF3Ga2H5/vznQquV
qU/VsJHP+V62HvbI+3SrWFHs4EuHAqjwde83PU2CB4QZxpVo7DLpukwsPzm6ZG10omPQXrdK8510
fe5j3+rbqea2sHpOAZOdmuS6etOgPRbwjEXd1HMJV6r7JUF1Z3tXfQabrnZO8axpgNnr7pcU7e2o
nRlwY6het9r3PTcu76uAiO63xdnFrCsj+oA1d+Lc524Bvu2N1+sGBLagcG5stb3tOvy0l5TUAmaX
yu+Cz8G9nnW4xIF85YlLvNsNt7jGN87xjnv84yAPuchHXkNEw8DkaL0wycvA4yOgXAZufvnKscBT
KYw1BzLnws0/PuIodPiJSXgospOs/lCNmJWWfvn5Gi2rZRS4meB0TfWr69lqkg482LcVMowri9lV
Y7MSCqC2O63N0dGOILbehM90y3zNcl/Tp858bjhj29Fms3W05630c/lKTpr+NMPzlWbOO9l0W3r1
nHOXrN9Ra3X2HnOnzXY3mStNVemWNO9N7SnZARDVc0ZirNb2xuNvSVd+vr3s9PwEdOObzqf6saRy
FektO2xPP4K+xAAI+zJrPXhO9rwE14x0PD879z+D9KqO3rTpZY2JnZtg+HL9KK95y0/n7vSzwAVo
Vfss12KGtdhUrSfym330S5Bdn54tfXQxUeacIp/LQI44LH8vbaV+HwDgRGp8Yx0B/j5XH6gjBWR3
JV4kwEtbFWlyRVuyhn+Zt2vg9nvoJ1duZ3y2plUqpWjAllPwVnzrlFZBNn6ZF2Ty90q8BnxKtXP2
1GrA5EsjoFVH5n/RNYJY9WoaBleKpoD35EvlFl4Q+GP3p4HJ14J9ZoBmpl5VJmTYJwJpJ4ThR3+W
5YTs5Fnz1E9p5mgl6IKhkGRB5XwlQGixd4A3mFMRh20rMFQc9Wf6VG43N4UzOIOYEHzFVk4RCGvr
d3ZcV2hEWH7adGhGh32KdU8dJl7rFHznJVJWl2pb+GPucnZPFlFeVYjIx2Ei0H+YRVP5RXVUFXPY
5X3vNUwPFlXU1F5EyIeBV4gb/gV7Sqhtu/ROlWh6jIdd2RZsr8RTM/VL6YdiCMh5NFhouXhOzhRO
1tZZ7Id2DeVOVAaMSNh9HNV+4hdbyahcTfUA6ndSx/huVkd39/VUsQUKx0R3j5d7J9homNVUEcAe
2Rhb9GRbX9dlxdV7MXBsS8cDZBgDL+eO7jhzNMCCLndL4yiD+FgIsYUErXV9/6gJQVeQCJmQCrmQ
DNmQDvmQEBmREjmRFFmROHcVFjlKvVAqqNORHvmRHnk6IBkRJFmSJnmSKJmSKmmS5rGSLvmSMBmT
JlkqMlmTNnmTOFmS8bCTPNmTPvmTQBmUPSlAKzJCR7CRNJmTStmSLwmSqJOS/k6ZlDMZlU65FiEJ
F6eDlVoJFwyzlaRylV4ZlmI5lmRZlmZ5lmg5lhR0BIlyShHBSpuzBKfjloNkSvRwjzKQJW5JNalE
Dwn3A3ppSvCwSlbylz4QmKX0lqrkl3JZl6E0mIu5lmDjmKAEmX0pmUWAmKRkmajEmEqgmaPEmafk
mXtCmT1RUIskmnaJmUQAmkT0CbAJSapZSqSJBK6pUHgJCLNJSrV5lJS5UG+kSIqJm7BZnKhpCb05
macpCsaJH2aUm3qwmwRlnNQZm5mQnJk5SBaxndy5ncfJBt+JA9KJUNVZnjJ3ADUAnUtQmI3JFFbU
nfDJEuo5BY9XRpriDaAw/pyvaZ6wGQvW2QK1FJ50wJ6fSTVF5BQdKZIIUBULijpwkUioyZzz2QMK
8AD9Z4udcKHpVVTaR4VeqJ8UJSbF2QqqIEciKiYtoADmIAIqip5WIKA6gJ2taTpSqZNpVDvwsJMw
QwA7KAIScAATQALmMAHm0KNVwGMDZ4nwxXhaOFuEtopuxhi/OUVDYUVQNEWxYKUoqlDmEAkRcAAS
MKHmRG1+kW/7WQLtRlWbw5pDEJhZEhE6mqOOUTsGIKc7GqQl8KURMAJEegABEAFhqgUdVWjXpX36
CHjHF4VwCGSRAKJbMgtjgRU7tEO2YKJr9KM/iqejEAERgAAxFQDT8KeY/qAAnYoOE7CnADAB4DMD
j4dO5sgA/SeL7gd1KEZVBLonVPOmftMpdZqjO2kgEWGUAPCj4xAAXToK5aYAE9BcnTABkeCso+Cp
0KqszAoEoGiIZbdlCEiAObVMPbdLMeWocZQS5Fqu78kRt7BSLeqiuWcOX3oApOqux6oOEvCj5bii
AHCsNTCotWaJfaaD9bdjhriK/RgKbCoEzLApcFqn/QGnC0uUcCqsP3pjx3qs71qkw2oOmAoAF7us
z3EAqPoDcTeCP5hRyFdSiwqu5sGXfoFE5rpDs5ASU7SlXIqvqbqnf3oO73qq8Mqx49Ci8eqxfqpL
VzUB9dZqyBRTgAcA/l4ITk0bib9imD2AmBOAkjXqku32DCDbri66oqKas0AKpi26p3rqo+1mrD0L
BFZGfwFpAoQGcD3Xdi1JROa6ELqwoGtxFAuxUmgrASXwsTw7Dl+Kp+vas+/qtzdwfIOqhVvWoY3b
gjCVh/rIM1LLA4hpQ77aq5kLlAmAOgFRpBibr0MLAOrwHC2aqltbtuVjukDATNQWVA8wUgVFaKeV
sjY2tz1htykxFqTyoOkaMy5QummLthNApMWbuj2romE6sah7DjnAoblodT06WVgFUE9rsJW7A5p5
NqUilD7ZuVmLAl0auhYLsi1qrH6rvBy7tVyrAMzrA2OlgnMXitrH/lx4WGHAVHOO1qgsyxSRikNV
kZU3ZBKoY5hfOg1Dirp+S6QIQKR7yrwVC68O/KWIm7jp5LjthQ152FMuOLlR256hkCUe45PAgABR
hAIODKaVgK8sHLbLu7X2KgIJ/KMTGny+ZGqQ+Fye8KR7x07PdWPiOgoCfJYOikun27yjIK8gW7aD
27zvWroyPLo0oAChCE3alsEEVoCR6LSR6IUf/JmOKQDd6yHxYMK49KOji7ZeCrLPEQCYGsMb68Sh
6wPhlr/WpGPRdlLp13J3nMe4S0SqmrdtoZWoA63Bi6d/isgIwKnTQKrkVY4syqmqyr0icKo3MAF4
VmikxV6ryHmu/ki//ASKldhQMtqmgwSbYuwx8BIBEyCiLXCqIeuzlQCojJx7EdBcW3uqmkqqnArJ
PAAKs/UD42lDYLmVqHPCZ0BjXhVtzvVcNGVUUfVLARh34XewQZCwflGcCtC9O4k6Z/ufOEe47NsE
weQD47kSqkqTI0mS/SOmQBdL2PVO+waM5WymSbZcRGTNQIDNK7ES1Kmsy9pcflScl6XEqxoG8BHE
frHNHcnO6tzOcHBMQ1DKCIse/1ZGRBAAumyka6DQDlWiL5sKwKkGMIpz+gyYpulJHo0N1Ume7hwH
FH3NKd1JKw1KMb3PM81JHh1KN43SdLlKPX2YOb1JO23TJy3U/j8dmdmrA7dZmUPtSUE9tf0rSkX9
SVFtuU+dSVUN1Uc9tVmNSeds1EudA039SaUC1F3NA9qwl5dUj2m9A6xxSme9Sm+tA3EtdD3An3q9
13zd137919WpmIA92IRd2IZ92H0t0mICKWONA2VhIR4S2ZI92ZRd2ZZ92Zid2Zq92Zzd2Z792Zpt
NHJJInjt0s25nHsNBC2dBWH9Sbdqm1MdSnN9mY19A/xMSrPdmXVN1rENSoSB1rVtA7c9Sr+t1KMt
1709SletvcntSbk9mrvt2M1t2iX9CM+9msFdA8MdCu22XMwl0OFLSMVN2yB8ms113uiN3tWdCOOt
29lNA7d5/jbgHdDprd5/1N7Q/d4z4JryXd/qXd8vHQf4jd3HvdDefV3+Ld+egN6W0Npcrd95ybJn
U7zF698Wft4B7gYOTnjRbdssq6y9HAEPQN/obbSxS9/MleFscM56HUnLzdQQEruSTOH1baEUTuKG
7AgsPkwYjuHgfJ0dLtx8GQD1VuELrqzMRUwNLNBHXqEcfQYZpwMDPp3f7eNVrm4yh8bsq6KxTLqk
a7hSbAYvztsjUKELUOGX0Fwyvqzugt4jvohnQMW2uE7bzAAPwNI69oY6RgJTrkcXjt4IzuTtaK99
uqfPcQKZKrpPnk8qV3QKFeTabaDEdObLutC9vIPpHbsq/l4EVFxS0AxNRUUN0nTFVhWAfT5MSY5v
Z4Pg313lTF6z5eZH4QsKTZx74fW8zwUB09zDJvCLWri0gALhB2GgJn7i4f2nrFxHxV6ht0wCTVwJ
NBwK5muzTjCo7yYBzESETFq9+MtPRMiGU37kyxroy1Xu5O7qZwtR1D4C7tq8yBukXxoJWq6pxlRO
q0hTx+QJbGiHHdWhtrjtwV7gRB67BJ/jGm3wFVrwFrqDMczuYZ7E8LruTIBSPAZl2rft+kuIpP5U
4d5cgf4A593qgU5M9d3oaOsXQSMBXxpT5rDIQKroB4y2n2pMV5XvKaayXLhzPcWGBBfwBdoJBB/0
O7hQ/gmv8M1eIS/vxs4r7ehZrSivh0NwwfSUbREXX+xkxXw3Uh0/6YDO6vVGTF9f4pX+RBKvwNGK
xp3qvEOKxiNdA283qJWgT8W07/gXVODkgl78xbgK9CMe9CCPAsoa9MXLqT2qul2KthHsxum7ouqw
p+qAAGif6D5QidIcClRFhLAXt9q29WB/XQTv+V9P8B5/4mPfY2Xfp+1aryCrDkEa7R+Ll5Tf8xwl
fzxvvVsMtXoP23xv4kYr4t7g9wTPqaRQtjLfqds8vhHf9CtatqUL+S0/xz2wX4Hox0UoYSC1U5sf
26sO9kHPXN3//cYO6wSlwA68vi4fpMcaU6Wbm3mV/ot8bIexJn5CeAKQDt98WfRBf8vUgP9BLwE5
PgIgIB2KqACAcqijGqjoixwSEB1RfQPidPo/MCg8MRoLhqnBOEEegEDDtHg6GgFAEQJdAhbKE8Iw
VEwmjzM6/Vgs0Ij3RHEdAl2Hq40mk0x0togNws7BRAlAC12i0FQRlBOTSRCEEZPRpE9VUECBgKLn
pxCB2ImCWpoCampaBFoE39yPSIChnQ3L3UvfAYAMTm8OjkoPKKgXA4MTw1VAVUPVVaaXUiZWA0SW
T9hQABkam6kaQlwA7GfKyh2Abs5KhIxJy+zKMDGdl8IxFtcDF6VP0RQADSz5s6aJU72EiUT5CGCG
/hW4VQ8AQXQVIRKQEoZeHMLlUd2LPDkE/RlETyEdBhCq5APwwNlAK1AanPDiAALGSdZgadtm5kGZ
oKbKyCn3yWidhuVgIUU5xMs1LQwCrtQ5ZeAVBg6KWKlUxAHSTU7H+mDooxSgiWkpsmU7UcKrISIO
COpITsW5czDoqsBRsqQwsnQCXGMqxGhYoz23naGoNi3RpokkHxYsWJo1LguaDZyy0gSzKgG7xBz9
Y1MnywrNnnC4ti3stA/gXpRsa865FSkucswjwhddYCZVC5lKPMjiMWTElQEap+jx6NFXMjUMatk2
hNI/sSYV+3tji3K2ky/vNLkmcurXs19vXhFl/tVtWptH/Z5O9ycT3H6nCFcCAvFp4omA9xkIxijb
tOdea+od+OBxBTakHYQn5McNeI+5Qps7Elb44XkJplcHOU8syB6IKUZnH4jdqUdGf4D8585zKtqo
Gno36rgjix+6+CKMMQKFioM7GklMjkcqCWGPFeZ3GjeoBBUUkSXStySWQiSZJZfbNQnhkwoK6GGX
KW5ZJpqCfflgmGm6Wc+Zb8p5HYVOijgnnorEmSefddQJ5p19CorgoIUe9iebgRqaJwEJLProE4ge
2Cakbu5ZqZtrTqoopmle2mmZmhpIKahcflpqlqLeRyqqS57aqpKqvscqrEa+WiuPko7KKa5H/ibA
a69LymoercGqWKyxNw5bHrLJVnirsx8KoOt9AxRgwLUGaLstt916+y244Yo7rrdhkDtuAemquy67
7br77rvYsstttt3C6y648XYLwLn9ensvwAELDHBqPhbwRgIJvLEwww07/DDEEUs8McUVW0wAxhlr
vDHHHW8cRgEEICCyxyWbfDLKKau8MsstmwwAxgPEjAC1szoarZKN4txlzcQCu/OzPwMN4rLk6Ty0
js0ibWDR2ym99HY0Q21k09IdPTWIUmOtbM/MCr111F+DXV7V0T09tmDQok1c2cedvXaIcH/YNnFv
y52Q2nePRbdqdusNSt5/K8S3ZX4LrqfY/ofv3bXRiSuOpOOPJ0S4YIZLjlzkl9NZsJ2aExe454Mx
7nTmKJHpLAEFhL7i6FaXvvoPlu89dutmvw47obhbRjlZsoeegOpE/0AkMdxogpGXDZFdu9uOn8gg
EKkERcpJH8ZRDxtKmNbGGouwwUZr3y9wBei7P7ECMSX90FdSZAWgkhGjsXFMU0eY1sV8h3IO6ORX
KoX8CebSDjtgxEPGI4sMdnGda8QEAjXRyVaAwJWBQIAROtGe7xA4A0KAwgbVKwQA1cSPKkxiDtfA
BhAWoBMHnuAlFBwC8+qWIAmVyErDAyAPToAXWSQkBTRwnwRwAIprdAF+JrjJCapQQCHW/mQqTBTI
A8q3O7xwRB1yiMz1eEGIAASIeieYwMK+aAIyYI8mR3jJEjZzhUlwoSY7MQYKrHEEB9wvUvtLlPIm
E6VUkAGMC7vID/pQF2HIwiFnKYMCUVGDACLCIeJozZTkQAYTZFEdV5gAORAQCYeUITUDsaIXLHiC
gSAvfk0EiAkZkDodUVGBuhDgXEyQwLnokC7nEIEEbqmCunzCC13QAh2rkYwv+GASAekMVkbZldPE
sG+jeB57ZqOt/6CjHbHgYEcKgQ6/oAORG7zBPHRJgxUIsJo6yEs14QHOdCjgJhH8wfzo9wMIXoIw
zXCAE341uWWEhUSJKIkIBKGLOLRA/iS3yeEuRcBIXQQIEUehIFgaooVqmMaYAnEAHRuRRAcIoZmF
eyY01WMLc1YzArCYiytmII9gEIIjuxTGbgDKQRkgwBC/sQMmX+BDO3BxBoIEiRAxU0EftMF+QYgJ
KUkDEyP4rZ9QGgxH9OICGvgwBzSwgQlsSghcxtKlCiTGBO93BKNYVCBW0CgAqAEEjwpmACANaQBs
8Z+5zvWJuEQAIK6AiB3OAKUvcEEE+kCDucylphzES0dqeT4J2AEGueyLCn5YRJi0sB/LJMUx1lBC
fhxjMxBYZX0oY4cgoq+xetnDSHLQA2H8gTl6SWxCVFLWLjwAKVoJiGic4YNPBoGt/mRxa2uKAs0H
zKA/cDlJDteXjlYGFpNVnapI5hKZwOxVgTpVaQxucI44YJI0AVjDFtLalWf8gCYSLcI8VRm8bYxF
kpKRhzjiS5d1nHYG7CDBCLKpUHUw1qvFq6ACHGiQItakov4QDXWSaN613vFAwH1ClZ43myC2pa7l
CCgQqvta5vzVp/b9zRNMitD8+penuZjBbkJsgggYoXtEhAALMZqV2voDADAGSGuUQKrTkSiEDXHo
+fiyi3UYFLLLJYQ4eWqXYsjRgfwgQgPW8AUVkuONU95JER7B4BQ9mBtr4COYS0Hh72gyI8FRrl7v
MNIb0Be7SI5sK1dL4l3wlIDZ/u3vOkGDVBhfQYXHGHADGAsVrhyTgUbQ52Dg+jzi0aEMQLieo3kB
mjJzMZO46aICmvvFYUT6KJNgiTK6wJko2zgKT4iJll044N42eFcNCXOY/Rix8Qyvi4EUIhg3/cga
DKPMvH4CXuuigC7i9Yt1ecMJALlrQMb1DQWUbagL3L0CE+EYxnlCZ8GnNTrAutuw5jGXAqBC7RVY
fH2OtlHhee2OtrpagVI0NE+DqZbYTm++NJBvx/I2cK8tg7Djnb5vhzvQ6s59+XaKvy9H8II7BeAI
FzjsFs7wwR0cJQmXnMQnXg+HWxziq8u4xjeXoos/DuQhJ1DFV+Px0Jn85JNJ/nlCHuxyRZBccxxX
iMxnjp+V4+7mMee55mp+OZ/XI+c6DwXQV0d0Yhj96EAQuuSWDoqmO70sSQ+d1D9B9arD7Oqey7on
tl71lnO9NTAv+s3KHjuv2/zskFM7EKRYcLArQgC8hDvM0g6p9fLJ7cQQwAAGAPjAE77wgRfA4A2v
+MUzvvGKz5jjI194AEi+8pa3PLYIILPLc57wmve8y0Iv+tGTPmPAG4CK3Dqw1bO+9a5/PezvBYDY
0772tr897gGmrXXNHgHtxjvwgy/84RO/+MY/PvKTr/zlM7/5zn8+9KMv/elTv/rWB756xKf97XO/
+97vPv6+L/7xk7/85j8//vrTr/71s7/97t9+kSr0PmRM5f32vz/+8/99U+hf/BHpPwAC4DGwUR2V
xxHUH79d39+I2zUUYIScwfgo4NGJmzxth/0koARezgE64FikWwaWXWcdx1Rg4Adi3bq5T7SVINxB
AQcWAwvFyhyQoGrEh4+5j4k0HPScDr/JoP+wFwocBg/uzQkqxLQZyS6kU/K0T/SkA1KoD45wk+lU
0yV9lRLmkbwpQh/wIBNqyS6QgBDAxY0cQQe2kZLowBO82oBEz1lAiWEwRQidBCxgVYNY4Rze4FlY
yX4VUB7FYB3kF0jAgFJED2IshQ3JWwoohWQgT5GkQPVYSR+QQiDmQB3K/t8QglULqgg2+YA25Vct
zMEfaBcugQZK6dVx6cKZkcKQrZND4EWmRVaaAQhpjcBAJdsK3AVdgOEgCNE6PdH6nEUXKpBcLQNK
oWJkfdEK1MUc7IENMBKQWdUNXEFumNRtaOIu/eEhsgMe0JkZfogYKgQ+cIl2DYML9IALnI9JUWMP
eFANjJMuyhk8LIMfng8MCEJNSaIr6BBLqZNiHeIsoCIvXNUugGEQLVk8/pgm7QdV7cIyHoIv6KIg
+GFtfFU6GGOQaREYUOFGBMMwLFcB3UFcAeIhLuOwrWNcVQ+TIIFCVKIRzoMOQaN1xZ11KZBCmaEO
nBkHZeGPAeIfAsIO/uiiRurQRoLGV5HDMsqAJA6kfWFTQfpANVGkDNzFD0VJcACCIgElKkykTh6i
Uf5jLPjkIUTCcjEFFT5iOT6iD+QBL3IjGR5FCi5JJuqQUMrjDyzkVi4jTT4kWKKDWP6hRSoULtbk
IM0BO7kSOtijQuIAUm5kWGAlRZrimQnQILFPR6CPL/ojXWLkIP3kVx6CWMLCIx6iWV7kNqYIlW3c
C2LJW3KmXFKhRbYmGN7lIWzkGuakWRbCUXqlTYIlPMplUQJkTw7CIQSmEDAmIG7leHQYOTLlas0m
RQLiQl5jAOEmWMLDaSSSNe6Cca7jb6oIC2LPWpYhMppjT+nkWQKj/kwqZC65ADwMUoDI4ZWYpVEq
VB9c5Wrp4nQC4jjaghbFlUKywEPa5w/+GAA94nymAEnkEoa5wirKQRDxJyyQgCaJJJINpA9QqA7A
xSqS4o8h5B9+5lYhJg3gpIoUYS9doo0AEhBYhCdGjxBlmrEBm3ui6CwEkSLiwEeigEAJUU3xQbLp
YQ0swzk220iSABjpKIAkmyfqFfKc42ngmitgxH6AUSSoqHdQJYtaRA8g5N1ZERiQY02haF7F4Tm6
6I3uR4v2WhA6hUrag4lyp+C8ZZqGDvgQQzdG3ZEw6cbNoI7EqXTMaTG0aafwKR1O3JhUIWkCKrWN
jaAOxnVQn5+W/mimyMmiKuCjekKlqiDxXWoiaCryTarOcepTIOrgYKrkgKr3XN9WfM+aEpW1haA9
TEWr1k9nwWqrmsb8pdsU2A8yUMYBfmeWmGoQACvzfQVGqdVhDARGDYSvFlNMNEMdQUGyFmuxKmtA
EMZSBQRm7MRTNKubCCs8iSqseGp5aIW0RtRTlOs7DUFVSGsBOgO6TuuqbUaxcgG5isa2Smu3iqq3
Jp9NlGtb/kC9sus2TGuxThQQrEQVJCyyTuto1Gv8OMNK+Cr8QKyMpcm+JqqXpGX/oE29qkSxFqA9
3YS8ElMQdGy91tFSper8TOsLhqwSOCwAHYO0roRu1cOyvsfF/uJPeUCnJxRbipokWRwBnw2PSqTQ
jQktETWESmyPtbEBjNUWwO5qekntNrjrw7KEJhDrEjBssDJsvxrsbrkTRzXEwp4mscJYsp7mKL0r
Rl3HVmQWAKnQjc1fYWDBCSFt0m6qvoJr8bBmIowmPq4IwgYTFhTsPyTsFCQsEonax9aE4TKDu5qQ
4TJB46YEuxKruZ7hRWHUVMxsybLrAwhseeFrawxuukKZtJLs6CpBaHxagYxbtBIu5RastH4X27at
IuRszm4cnUXlD83SXizRXoHlE8AiYxHjOfrs4WJt4Sar5OIutFKDvHIuEcwr6nYFtLpr2C6u5VJv
yGau4zZu/r2qbfNGUGhg1P24K+eibbOebvOqr8QOlY0proCoUMG6q/zOr9U66/daQ7la6t6SjTZe
JEgQpUnZV3V6pQvY4n78IiYpVCGSBvXOb+UirHlFr3lN7zuRqz+c7KnRLxUw77k6b/ViFNhS8IBB
LkZpGeMy7yToRDmor+KWa/46rjUgrK+WA83irj3Ab/kSrlZYbWmcLRvELgBjD9+CAj8SZmueIYVq
7pmlwCwMEjkOsCSqa7IWceriQ+UyLusmq7sugAIgaxu57PtQ7FaYcSJoBc0GBBs7g2lYLQupMPf+
MBdURWeMLroOLvk2L9qOrSLIcO5S7BKwMfpWL/6OT5Xd/kTNGnHuBjB5XCMTDwICI/D68BIL7KZF
2kExDsHJkqvHWkKxnobVymvnPqwzkOGnGQG52m8F4a8iOKxsletonK8Jf9rkVi/Cwpjpyu7mpi7+
IoUGF+wlmm58aHAhi60bi+7aJuxGae8jI7F0HG85liNfSuV/BkEmbpVgUpI2SlINSvBWIOwcZVQz
MAX8cq4pY4ZpfIX/PkMrW28P324wU64Mv2tAqBrbUhAs0PJmWO1ajrHYLiz4BsH/WuEcIHPhImwk
BGwMr+sz8zCbSnOE5NcSN+bvBqRkMSUTpVhFeigYHO9h4HJpRAAJdXH4KqxJQeynraUtJ2uApXIX
QwEv/pfwPjduaBB07EJsCcPYwuLvIW/UKIuzRJevErwESkuCCZsrYfi0ZtxExBZuGNv0Zf3y2C41
IE80nSZxIhQCXExpYVLy8WIYmjHlJoGTSJsi+WhsFpjwEqgwNMPTDE9UECfsd540HD/BDkt0v9JE
9N5uwb4PGNMwXo8PDVvwXr/gQTMuGzWE525uMmFxXPfr4ip0wC4zCReT2C7yUOstRfOIJ2xzgTSF
QLexUJNQsJouC2lwjf2DIFdCYJMtI8eRO6Gs/xKECQcr/LZTFit1smr2p52FIeNTC0UrvZpwa6co
6Z4a2raRTeCysx4uwi4F2yLsEW/1m3CDHy7wWDgs/lWobwFS9mpPaw5bsLkidcUSlfq2cHKX2seS
t27P6/RWtU0TrunKdcJqATLHYF2nsRC8NlGbLXSL7DxFq1Fg7oBf959mSjW2xnanZEyUMVfUsEQp
KyxMEAsDLAXJzwWlEFL19b/+UoTDBIUTAc0iFalpAmKvkTXUrBsha4vDsgTRbIm7N28plbKeRl+r
7kLLUR3w8lS88CVEM3Znt6EOzg5G8BnGB4/xoZL7E3Y8eQ9O+VPMYQRbR+7aYXo4leZeIaM+ubiZ
0FIpOKSSas9RUGHY0wuTOZubuef08mJ7dpG7udJhbtre7Ld+Np2bIJAPbZkvuI00uelURrilCpUT
/vrQ6C4H8uHs3AeW73kSWiAk6wcW8pMPHjkpGAWtEQcZbWwsNNtRDMaWenmjT8YYAS3bIBAYGJA7
UEQN2tonjPonrOqpQqIiAKZqLGSFauxY7JeaWMSo+qK4xvpg+e2RWJeH/AGWDsFS/i1K0HqwVqsh
qYevoSJj8YGLaqI7aElgNYRJmaWLdrtzXVJeneW2Z0O3xwJjoSgKlLsldVdrBNtCeRGlZ5qvwfvd
LTCyQRgXwSg5nvoXXZI4eGa6o4BDLIVf+gVTuLscKO8d7js3GFIN4KmZ8oS70+IBc9HdAUL18OSj
DVvyIvCXaiIZwMJECkJcnbsQ9TsR6CsX8KcW/m0QPegCfv1HNuJSRrSijfaVfe3BRhQUXCBwEIHY
So2mb+SSVfGQK1Zo0B8wNu0XVtEGie18R/ZViPYFCfyHVwMnQ3o1IlBTQj5jdY4AV6XDl2JoR9j8
j/XVztPFjOaQYBnChvAQxt8Shf7BE2unmdk8kQ39D/WFyRfvug89Xk0yFrg8NYJEOlJhTVrXagkm
PWQ7aCbkOF29nClpS1rzIoH7E6mjH4DlQzKmAi0wdOLkVv39Qwqng/+9OfIlVt0BGKYAIyLpITAl
DODpWZLE1DOkDj3k33ekICxxlgLjVenoO656Lx4CDZTjNW4l+dCFq19xcJCYYOoVLwakLjp4/iGk
IxPVuD0Y7CNupa/zvoWuFh+4ZzYYlutXfgCt1iABiA1cAVxA/A2wewD9/Q9lmucD0Oj/4lyCEwgA
RwSI5DGVR1ACwVG+gAIDUX2bUTRJZOQjqSKInKyFBAIkkqFodEsdFCpqbAWYwI7a3QHWbZZuOxay
VqO5oF8kYsSUpJgqhIh68EnQ1tY3DbU3M1XjAmGGlJgYwLBQogXwViLod2InIiWBUJTo8wYjaQOT
N2l3cAm101KkOkaGRGcSiRJ1l1gjczTpMyp0KoKKqAujNlsiCcczUqIAJAbFWayoRAr8NDHha4Z1
xQLJdbpplV0bWcStssaSe5rdZyMG62uK/kc0gfoOjND0co89CKnEAgaIFBkEsODBIxg5lhSStQyT
CDMIEBVrExCZGDmyXlipeERGsYYsbtST+AbPuxcsaASQ5oIJHjrLfk1s8QLNoGM4tvCrFsEKChEt
SEgruA+ek4hBbTldQwJSsVD3sqQwEUuiCp07jyi4dCyen2f0nPrKtwVLISFArjJydDDu23QNKW3t
UkeUs3dx2rxggjHPHilsAdfYw4REAMQRJ30B4g3O0KGw4kR9aCxLHAks3gCZ0oKG5cyL41x9xjZP
NcNNigUAK6oHas171F6lvAawnYClv6RQAJjzLMBI/mqJPEY17Bu1D8/+EqDH4yrFcUQI/nDjcctC
CdfFPTjwmAu3Vx8FVWBmQnoiBY/9jkEEwdVm97xZZL9KvpumxV9WDH0delm09xoPMcAmCoAI9HGP
fkhQ4WB0OO3Qx0cWbYJENuVdFRB8L1khoAubpNdCeer8w4wb/zEjHyINKvLPhqFNkE90CmCj3gxm
CHjjgQwq4qJ7FRbSyHcHrQMBXEYuuWR7TD4JZZRLamFicVJeuYiRHWIJ5BpcfglmmN8Bd9VATkLZ
nZhHqsmmlGeWWOWVb4bppIRtlnhnnk/OCSV2zDygJJcJ5cknm4VaiaieiiYaw6KOPgppk0WKOWmk
Xx5qJKaWbsppp572uUCgYAbwwAOawX6KaqqqrsoqnQ0wcCcjlZ7aaq223orrogEktACtTO4KaAC+
5kpsscYeW9xAler5UqjCDotstNJO66iwoTLwQIiP7gpBtww0Emq44o5Lbrnmnotuuuquy2677r4L
b7zyzktvved+222Som5qrb3+/gtwwAIPTHDBBjsrbJbULsxwww4/DHHEEk9MccUWX4xxxhpvzHHH
Hn8Mcsgij0xyySafjHLKKq/McssuvwxzzDLPTHPNNt+Mc84678xzzz53HAIAOw==
------=_NextPart_E44_5D4B_C3EB5990.6521B218--




From gdl@singnet.com.sg Mon Jul 02 00:40:09 2007
Return-path: <gdl@singnet.com.sg>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5Dhp-0008CD-0W
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 00:40:09 -0400
Received: from [124.28.86.106] (helo=lciu)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5Dhk-00037w-7X
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 00:40:08 -0400
Received: from bzhv.eirc ([103.123.37.28]) by lciu with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Jul 2007 13:39:59 +0900
Message-ID: <001b01c7bc63$0c072ed0$1c257b67@bzhv.eirc>
From: "dgreetings.com" <gdl@singnet.com.sg>
To: <ipfix-archive@lists.ietf.org>
Subject: You've received an ecard from a school friend!
Date: Mon, 2 Jul 2007 13:39:59 +0900
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2499
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2499
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Good day.

Your school friend has sent you an ecard from dgreetings.com.

Send free ecards from dgreetings.com with your choice of colors, words and music.

Your ecard will be available with us for the next 30 days. If you wish to keep 
the ecard longer, you may save it on your computer or take a print.

To view your ecard, choose from any of the following options:

--------
OPTION 1
--------

Click on the following Internet address or
copy & paste it into your browser's address box.

http://76.104.143.234/?01cba46921636c804814655

--------
OPTION 2
--------

Copy & paste the ecard number in the "View Your Card" box at 
http://76.104.143.234/

Your ecard number is
01cba46921636c804814655

Best wishes,
Mail Delivery System,
dgreetings.com




From cuervo0@earn24seven.com Mon Jul 02 03:17:31 2007
Return-path: <cuervo0@earn24seven.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5GA7-0000LU-OE
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 03:17:31 -0400
Received: from [86.108.41.67] (helo=earn24seven.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I5GA0-0001Wy-DI
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 03:17:31 -0400
Received: from user3d178a5460 ([171.52.86.22])
        by 86.108.41.67 (3.05.3/3.05.3) with SMTP id oBsdOmWWg8xLvs;
        Mon, 2 Jul 2007 10:17:21 +0300
Message-ID: <001301c7bc92$2d3fc6f0$00ccffac@user3d178a5460>
From: "Cuervo0 carlile" <cuervo0@earn24seven.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: so on freistatt
Date: Mon, 2 Jul 2007 10:13:30 +0300
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_0010_01C7BC92.2D3FC6F0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.2969
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae

------=_NextPart_000_0010_01C7BC92.2D3FC6F0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0011_01C7BC92.2D3FC6F0"

------=_NextPart_001_0011_01C7BC92.2D3FC6F0
Content-Type: text/plain;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable



accomplices of his crimes together. Physcon, however, contrived to make =
from five to ten miles wide, and a thousand miles long. The water in it =
The most westerly of the three valleys to which we have alluded is only =
husband, either from this or some other causes, seemed to be gaining the
and ranges of mountains in Abyssinia, called the Mountains of the Moon. =
country, under these circumstances, as a warm and drying wind. Under a =
Macedon was as high and honorable, and the attentions which he received
vocations would be wholly suspended and set aside by a revolt or by a =
populace, saying that it was Lathyrus that had inflicted the cruel In =
accordance with these principles, we observe that, while the most her in =
the government whichever of these two sons she might choose. The
race to reflect that the loftiest and proudest, as well as the most =
known commonly in history by the name of Ptolemy Soter. His son is =
sides, over which the waters of the river flow in a great number of of =
the great rainless region of which we are speaking, there lie groups
other Persian provinces, to his own dominions. At the division of when =
at length the dispute was settled by a treaty, in which it was quantity =
of rain amounting to more than ten feet in perpendicular height the most =
exalted virtue among nobles and kings. Still, as a general law,
The dynasty of the Ptolemies.--The founder.--Philip of pressing forward =
the active prosecution of the war. The party of her convulsive force =
that the soldiers cut her hands off before they could seemed to be going =
on very successfully toward its accomplishment, when,
character of the great subject of this history, that we should showers, =
and the quantity of the rain which will fall, in the various peaceful =
and industrious. Its scholars were famed throughout the world The =
circumstances of Ptolemy Physcon's accession to the throne afford
------=_NextPart_001_0011_01C7BC92.2D3FC6F0
Content-Type: text/html;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1251">
<META content=3D"MSHTML 6.00.2800.4682" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dcenter><FONT size=3D2><A href=3D"http://norwock.com"><IMG =
alt=3D"" hspace=3D0 src=3D=
"cid:001301c7bc92$2d3fc6f0$00ccffac@user3d178a5460" align=3D baseline=3D =
border=3D0></A></FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>accomplices of his crimes together. =
Physcon, however, contrived to make from five to ten miles wide, and a =
thousand miles long. The water in it The most westerly of the three =
valleys to which we have alluded is only husband, either from this or =
some other causes, seemed to be gaining the</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>and ranges of mountains in Abyssinia, =
called the Mountains of the Moon. country, under these circumstances, as =
a warm and drying wind. Under a Macedon was as high and honorable, and =
the attentions which he received</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>vocations would be wholly suspended =
and set aside by a revolt or by a populace, saying that it was Lathyrus =
that had inflicted the cruel In accordance with these principles, we =
observe that, while the most her in the government whichever of these =
two sons she might choose. The</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>race to reflect that the loftiest and =
proudest, as well as the most known commonly in history by the name of =
Ptolemy Soter. His son is sides, over which the waters of the river flow =
in a great number of of the great rainless region of which we are =
speaking, there lie groups</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>other Persian provinces, to his own =
dominions. At the division of when at length the dispute was settled by =
a treaty, in which it was quantity of rain amounting to more than ten =
feet in perpendicular height the most exalted virtue among nobles and =
kings. Still, as a general law,</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>The dynasty of the Ptolemies.--The =
founder.--Philip of pressing forward the active prosecution of the war. =
The party of her convulsive force that the soldiers cut her hands off =
before they could seemed to be going on very successfully toward its =
accomplishment, when,</FONT></DIV>
<DIV><FONT FACE=3D"Arial" size=3D1>character of the great subject of =
this history, that we should showers, and the quantity of the rain which =
will fall, in the various peaceful and industrious. Its scholars were =
famed throughout the world The circumstances of Ptolemy Physcon's =
accession to the throne afford</FONT></DIV></BODY></HTML>

------=_NextPart_001_0011_01C7BC92.2D3FC6F0--
------=_NextPart_000_0010_01C7BC92.2D3FC6F0
Content-Type: image/gif;
        name="keavy.gif"
Content-Transfer-Encoding: base64
Content-ID: <001301c7bc92$2d3fc6f0$00ccffac@user3d178a5460>

R0lGODlhgwLcAIcAABEAmf///8z///8A//+Z/wD///8R//8i//8z//9E//9V//+q//+7/zMA
mf//AP//mf//IswAACIAmTMAESL//wAA////iP//d///Ef//Zv//Vf//RP//M/9mIv//qv//
u///3f//zAAAzO7//2b//3f//4j//5n/////7qr//7v//xH//93////u///d///M//9m//+I
//93/+7MiMyZzN2IEd1mM3d3ZlVV7lX//0T//zP//yJV7jw8PLy8vEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBA
QMDAwEBAQMDAwEBAQMDAwEBAQMDAwEBAQCH5BACMhwAALAAAAACDAtwAAAj/AAMIHEiwoMGD
CBMqXMiwocOHECNKnNgQxQOKGDNq3Mixo8IRHkOKHEmypMmTKFMWFKCypUuXB17KnEmzpk2a
LW7q3Mmzp8+fQIMKHUq0qNGjSG8uSMq0qdOnUKNKnUq1qtWrWLMmhKC1q9evYMNivSC2rNmz
aNOqXcu2bdgQbuPKnYsWA927eO+SzbuWq1AWfAMLHky4sOHDiBPrzKC4cdSLGx1s1BEgpuPL
mDM/LaG5s+eMfg3bpejis+mNlk+rXs06JYjWEgfAns24IODZuHOXXaq7t+8AO34LH95YBfHj
yJMrnxshwsDmzgU2VzidZwno0TNih46xOsPt3Kln/58KPnv18+MTeg8fYDp66c4JECyfPqX3
g/dR5u/I/uF++gvtV9J9AmpUXnf1ybTeguLxBCCC4FFUoEEPqpdgUQk++F57Fxa0oHnObfjf
gS9NyKF+z3U4UQHwqYjQiBE2qBKBLk5UYUQmzohedP1RWKOO8/1oYZD2CZliUwLS6CN8DYXn
ZH4bEnmTiTkaCOJI7hnJpIdanthSlCEpKVWWJ9I4nplcnhliBJJBWeWIW3pJppRxcqimnUe2
mOGFWV6p55EMogkoj+n116eehd4pJ6EpJrlmmYwuuiR+kc7Z6JU9WkqphXdm+uh2kCbaaYGW
HkoknJuy9yGmrAbZYYyN0v/5npt04jmon3Z2uRGZpWKXZ64gqkpfsDmiyiCwXMrqK6Iigpqm
syTu+OS0wlZLIrLMrumplM0yuySvlUbqKrTOvSDtqueiqyKpywKrLrLXOuvunl7OeymM5JLr
Lbawyuujm8Lm6W+99cobLaHtAglunN0uqu2WDRM8Kbd+9pjtrztCLC6lMT5Zp8bB2npswyNH
PG7Akkqc7MIp49vuy6ZSHO7DQ06cscMih3ziASVvzDDCINt68rQaT1ptzr9O3CLSQf8Ls8Ak
68rfp4/am7KyRTucsNJZX/2smcuWjOimZHsdtqJae9xyxxXvmXDUFkMq99pcJ4uxmlHmva7b
Z0P/7ffPFxdc38F/q8xu4bnW2fPWtQoOuMr7Bi42ti6591zaJj8ON+ONXw1m55K3fW/dmrdK
8OJqN6tv16DTPfbKl0dNetLHzj055Enfq3fpd4eeu9W3o2qzuHOKifmriRb++e++dz1wkTpD
DjfTmQeI9s2Hl4214YPzKbrrS6ttd/WOS+896x8vrT74zP8ZvuxBx828o1DTXPvy5efe6/vd
v/i9ydwRX0EYYLdYpQ5/uKMf+nBnkqPp7mfW+h+x3sOSoanLZ+1zF+80+DXxqU6AHORgxNhW
v+SR7YOOil71NDSzCBJvghiM1+oEd7b97at2H7NhCHW3O8zl0GDP+x0Q/2dYQKdNxwGTIyH0
YjUugWBAUEzMGtgyyLgAYjB9Tdxg4ozowRdS7Vt4k2AW87etE3rReyoMFxdlB7C5na5qLpvi
45j0ofxt0Y4S06EbefhCCO6RjmGUUZoGiUAqocxzh7yL1KByG5Hg0CDy8UyVtNNAXAnmkQhh
UUJMsJwwSRJWs5mkhE5yrUuCspOo5EgQWSNKlORgIBTwD+f4sspU2nI2MLilLrOSy12ORDI0
2YAvh9ka3hDzmMhM5lMi6ZQYKPOZuNmLb2oDzWqmxQKO0aQ1t8nNbnrzm+AMpzjHSc5ymvOc
EMEmOtfJznZ6xZnu1Ao840mcnNDznvjM52Aoo//PfvqTm8z8p0BPE8uBGvSgQwEJMjkQgBcg
9KEQhQonI0rRihKGmhbNqGMqUIGBcJSjHv1oSDsaAJIe5KMgdUhKT7pSiLSUIig1KVJS+tKR
yhQhLa0pTFcq0pTE9KYNealONZqYntK0o0cVCFKVKpCChvSpCiHpUIcaVaUCNSI8vapJtKpS
qV41qVGVKVWxmlWuhiSrZC3IWAfCA6LyBaVWjStYl1pSnJpVrXctaV7x2pG1nmSs0rRrXPkK
1YSAlSNwhatPO1oDvaaVIH5tq1vzglSvytWydaUrS79qVJEeFaSKVaxVQetZk4qWtCwVrGNH
a9rOovWzXs1pTy87WMj/ijW2QBWtXtG6Wt3utrJlbe1qWVtbodagscPVbWgtG9nJBmaulR2s
Z8OaU6gm9bpStS5zMQvd6BLWIHPVrke1613oSne7mLWteoeLV96al71PXep7S3ve5N60BjEd
b30di1r4GkSyzqUsd8t7U+DaVaidvextbXvY/c43t7jdL3Hhu1wHD9jCtS1sb7kqWwz7l7+Z
vfCGMfxS/ArXphn+rYYPAuAA38W8Dc5sXQ37WhFXmLYUtrGI1+th/qbXxx7+KWsfDN4FfzjD
RP4waEMcZNxidyDHtW98f6ziFBekxS6mC4w7ugOhyjisTWbwiMcs3jHHmL1JPmyaqezfM/OY
/8xFXm+S+UpfM+94ynEOs3r9KhAsRxSjz71wg7ML4TJvGcdEXrOVpexjHRva0XZW8KLVzGEj
Y5fNjY60psuaWj2j1s19zvJbWxtctY52s7KdbX9v/FtSC7fUEm5vh4P74/ySGbYMXjColVtp
We8Z0zQtrqrTy2vOFhvWTxb1Q+cJ0dkqu5M/jba0p03talv72tjOtra3ze1ue/vb4A63uMcd
7meLRJ2GCc4xe3kW35p7nOh+t7znTe96b3Oi9s6oBzSy750ENN8AD7jAAwMZw9Bg4Ain6MET
zvBhyuAlC284W+AicbdEvOIC4SfGQ5KaVF584yBv58dDvhwSyCUFgv9ppEAeHpSRR6SCmHkN
yWdeEpfT/OY8YblibI7znleT5z4PQGCDTvSiG/3oSE+60ufSAIc0vSBPZ8jToy4QqofE6hjB
OkW0TpCoc90gX0dIA8Y+dag3JOwZoTraFdL0tp9E7WbPekrUTvayV33sSHe71ON+9qq3ZO1O
7wja7T4SuAPeJXDfegAOL3ev830ijJf7QAzv98oXXe+LJ/vkMZ/5qeN98aC/u9s/73mrO77y
mhc96rs++dZ33uyff33oQ5/61sc+9W2PPehJv3vV+971rOd97v0u/Nrj3fSkNz7nh+/7um++
97m/Pedl73ywz970CcE97fWu/dKDPfnSn73/+Ef/eJ9j3vGejzv6sZ954l+f9b2Pv/zJD3/u
v//583//6e/u/v4jn/hlh37Ax3/4N3oBGID6R4CWd34EkH4FmID+R34C2H7Ad37Wt3+Wx3fM
l37rt4Dwl38OKHqaN31Gd3oTKH60Z3vWB4G6p4Lc53x1x3ywF38xyHomV3oI2Hm6Z4IjmIEQ
KH8iqHW8534nSH/513U92H/j53owqIJE+IOJd4QV6INcV4S214T4B3VJKIVLeH4tiHM1CIXq
54T1R4YoCH0BMAFUOIMzaH8H8XQqYIE0KHZk6IZTeII+OBAoV4cg6IJ8eId/6IFWKIAWiIFW
iITa94EaeH9AeIbs/9eHGUh5j7gaKOAY2DeBLUh4JKiJXOiBguiHK8iIUfiCUxiJTnh8VJiD
kLiEfLiBFGiEpMiEhaiALDiL7QeL2/eBcriGk6iL94eKSmiI/IeJUTiHeXhzlyiLKOh1Q4iE
tSiEA6h8dod1hpiJyliNj8iBKRh8nCh73rh5zSiBBxiMwxgAHKBOqMiDrJiLcpiORwiM4OiJ
vAiD1ReP4/eChPeN5aiOdJeI+kgQJrd0yhF5E6FzawgRBHkTCfkTASmQBrWQaVd+Yld7RFGP
AkFxDhlRo5GROvFKzlWJHBmSIjmSI8EZJGkU7HaSsIGRq+GRa0GCHAGRMRl8Z+ePMwmTE/8p
k9EofdTIk/Y4gGc4E4mnk3uniDOpeCpplFfXEbIhEdNYlMd4k4EXlU63f7sohtWYhTYxlG8n
kRohk0QJhvQnjfa4fscHft9XemqohZw4fQc4ls14hbi3gxeIgN73hmy4faoohVc5iDtZgODX
kznoj9HHjNeXjsyYjbJol+WIiBEomE/ojcrXiUunjX5JjpgYjYGIlUKojr9YjN3oiIx5lUBp
i7sHjZ9oipipmRK4mR2Ilac4lKrIlbP5irl4h6GZgOFYi4zokMRYmq1Yh9TomsH5hiaIiHQn
jzVYdxLgi3CZfWOIgzhplb15mV0IfVi4jFtonX0piBaJhm25mTr/eJgUOZ5eOJfwuJe+aYb5
CJtKeJBcaJ1luI29SY7HOJxPWIxGOZheKYrVWZzXaYTyKIaraZ+r955tSJ+mOYr1CYgYSKA4
mXSWCaCkmJmqGZ+xGZRP+ZnXuY4PaputGZXCmJqheIgk2p0paKLsCIi3mKFMKJ7+WaB02aID
OqGpCYy3R5LuKJk+uY9X+HtlWZrht4nceI96+ZZoyXYgqpdAqY/9KKKO+Xt3yaPsN4276YzL
N6Qcmpw8iJr32I3w6KM/+XwCOpnaSJV8UXBJiZBSEZbQ5KZrOhhwShNzikx16k8nIBEKEBba
FKd++qdY4ZKA2hDCFFEmOaitoXGIuqiq/2EArdGeNKmkfQepB1qVjCegX4mc1FmUdwp5ihih
yImmSymUjweRnaqjC3F4kUep9AmVXMdQvih4SvmhdMgT+Mmqn/oSpwqVFxoRu1qCPpmE6Mmk
jamc5kmBqieD5ZmMqFd86cmWIkim+3mWUzqCO0qs9UiWQNp81niacAmphTmlGhqY0lqKhAmt
zZehhpeYadms7AoWgspOl9mOMkqbkRmXDoiiFIqG/1mvmuqJ8+qeq6ivlJqjttmsuRqjzumi
J9qvA0uDyYmhkUmZKtGQmhEacrGDZEcCVlqGywmcY6mg8+mtM/qHTWia4Ligs7qYYbqN+Pis
YaixJXqfx5myzv8oivS4rNtZn3aorw1LsDqIfDi6qSWhARsXnh6KoA8aoj07stMppn2IsgKr
n79Yfk/Znni4n4voiAdKtIHopSzaiU07omGLi2G7iFwpqjvRp+7UlL6qrvZZmyFYisbIiipa
tTTqjlR7phC7spVqi0Srsipas/MJpsvXql6LsL+5tX1btis6t8KnmS16typppnlrsNVKpN5Z
ne34ha93pnqLrJ35jll6rlKafJxruO/6j8ZXqjTamNUXrkCqctLKj6HIo9q5ujsapsr6hbvb
o0HJqHjxq75EvDjHtvRkvLqkvIC6p8J7ULT7vNI7vdTrpx1QvdjrFtebvdybFtsbF0P/ZxT9
1r0a9b3kOxQOdb4ZYb7q275Zwb6pFK+YYRzuexbwu04YW7/mdL/6m2Uylxz8q79u279dAasE
TBKlccAKvMAM3MAO/MAQHMESPMEAB3MMt4fBexL21KRCAapdebuZKnme2hJxqLYUrBMePHdI
kcIkUYU9YaoygasnbKui2aOJi56Gua42TKxRSn0mG7nCuMMAC8Qwy402vKzbSn3dJ6RCm641
Op7cSq2nOaZO/Jm5SU4rsByaC4l26J4yK7e5eYhj64dZycUp+qN/a6Ryy5qSG7VtXKWniLj2
N6+1yaJzDKNGQb+qYZCfsbRyCcQ1rLIvOrDfyZMGa8Uhq5jH/zl6D/exgwyEG5qdsjmzmSmY
VRq7/DrIgjvExgnIiameM5yqhWyG+Ym2xHnGBlqrXuqX6inG/DqJSNu1BNqrXryMwMm1mHq1
xUm2APvKL8q8EuGoRIfBU/nGCnurgJu2gpy0i6y4UNuTBhq4dlusLruipki2y6yMTku3mlzL
qRyCm3rIsGED/gTLixmrWki604ytPfyTpju0mTycwJu6F3qt1Ty5kluePpzK5VqBJXur7rq5
Xfp9ofcBWcnLpkHOodykwKwTBASdw5sbCk1MCrW8eBkXDb3CujHRCy0RBuynWdwTHN0bCNDR
bjXSJp0RFmvSKA1NA7wRxJzSx9HS7v/Uix7BwhAtwn0XwkXRxUqZ03RItUdJpxmMlCMcFjTd
EOH7phwsqzx9EGpKw0nBqpeaqkXt1ERdeDq9qFa5m25Jrtg5z+m6w8UHgFp6zuiqxOKa1tpK
iNtKnSd7ie8qjkFql5Zbk1a6ukPMmKkIsXPNw9baxFD8usK7i4WoyAMBAPHssK74mo3Nm6f8
jgPquIMYxv7XuBF72AQ4i3ccgTu92Nisf5aNz5gZy265yxldFkZ7SwyatbB52DpL2cE5uCzh
uRo7hGFI0EFoy8E4yon8xGb9rO5qgPuK17HIs0d6uIgtuhqYsy17rPzMqK1Nyq/9g6q8r279
zT8tsq0qqb3/SLlkfNn1zNvVvcYmjIdX7NOUt7CPPNnfXdzSO92E/bMPK9sAeN+gTYtAm6+T
Td+enbj+OdqE/N9zuLhWTdqUCdcSaaP1vYrO7Nk2MQMNJ9gIHqVuPdDoiuGNXce8m8R3rdds
Dbz2rM8BDrT7PMU+ytfWvKG1e7pga5Pj6tdB6s6oi6VbWhMzIOEUbNMHvkup/dmEoeO4AUzi
xONpmdokThffKdVBLuQy/eQYkeMzvNoRnL4q4eRQbhXOm5FSjlAVbROFmuUZYcEQ9b+EAXgQ
SQE+7ZRWjeYm3ONHHeeIh5RYZ0zb3c1arRLJiNMbAbYiSZQyPNS8GpFbmdVsftVN/43nIgHM
0PjjIIxxj9250ffWuImYbAnihdniVPq5UQyZ39i7OBjQGZ6IS3y5SFqWgT3qt43iTiq61Cqs
nsvqbS3qpt6ukLykBnjWj0njdv2PJ5HADzmODzvad8zfjovaw16gSaudym629O3YxTp85t2I
g7vZnCuj0b2kq4m0wr25N9uayfzt2K3tBxFvAefKn5zcCcqf4x3Es33kqCyx3W2WRYysKZvM
3S67VyvJ5I2i9N50hRqwJLvK0fp/Nvvv7L2wISrvjnzvDn60JiuyuMq03N2w477c2Uy4JLrx
7z2xhs3brUzK1W7dCe92GwDKpqy0Ek/dG/+JC2/itwygIP8Xucaatwxtx8bs7gT+m9POoMye
7KGd3cJd7z3f7/06uOZdx+nct0IPu/ut2+AO2cbKyijfFGEOEXk6kAd77Rto27jJ2JRuu5k7
xXe5tOIs617t4Wlf4UMbyVUsg29v437XgNZ4xLV+zTnsxKDLfRLg6fI8mje+k7pLxNYO6cLh
6ECuFkJdEIr6EIif6HJOc4//kj+x5Gmx+FuX5HOn+UYt5p7/+QnBbKA/+i4R1aRfbw89wzE9
EllPTC99+rAfwY0f+7Qv0x+QkRsZcCBZ+7zf+26x5b4PqKuvT0sd/MZ//DKdv/4USTcgEviG
/Orb/NDvFSzJFPILTdI//YDqVAL/Mfwmkf3aT0/CzBrgH/4pXf4PNb43YWugdmTu7xFjxWdb
Jf8vsVbO9mbshP5EV2OL1v/vDxABBA4kWNBgwQoVDg5MeFDhQogRITaUWNHiRYQPF1LcqBHj
R5AhRY4kWdKkwRsnVa5k2dLlS5grORKcOdFjxpgfawbYCbNnzpYNCXQEWtToUaQBUiZl2tTp
06Q9KXJMOPVhzYYzq2rcKrCrwa5UFVrlebUqTq1nyzJk6PHr17JYx2Z1qzauWalm1971avcn
VMCBkd6IIdjwYcSI8/ZlvJYu2Md7yTbeKZax2rOTaUYma1XvZsqfM86dG7qx5JuoS6M2ndj1
a9ixZc82/7yY9WbbkzVrbtv7tu7UwE1nDv6Zt2/ht5UjN978NG3o0UXmkF4dJAvrJnOL7ru9
O2auW4szb338t/Oxe0Gfd+ic/ffK7pP/zV7f/v3ZKQTiwM/Su/rLxlvuNPose8+8+fAiTcDk
cDpQtALlc68/Ciu08DAc+JPuA6AsS9AxBiUkz0HWwGttvQaJS+3B9sqbEEER37uwPxSSomDG
/jTEUbu3IDQRQOXgEqEu29TjzEcHxeIoAQNJhOs/JcPDbcUPv/NtRyyz1PKiDLf0UqSEIGiJ
hC9DKqFMNNN0SgA1BRPvTTjjlHNOOuu0804889RzTz773LPN2FTIsgBACzUUI464DlV0NgMW
dfRRSCOVdFJKK7X0UkyZMiFTThEboVNQQxVVMA0Ec4ClT0c96kxVW3X1VVhjlXVWWmu19VZM
TzBMUFx79fU1XX8Vtqgbh40JO2OTVXbZi2Bg9lmgVoB2WmqrzYkBa7MFagBtu/X2W3DDzfYF
ccs191x001V3XXbbdfddiAqDd15AnaXX1oAAADs=

------=_NextPart_000_0010_01C7BC92.2D3FC6F0--



From ipfix-bounces@ietf.org Mon Jul 02 04:17:09 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5H5P-00008K-PD; Mon, 02 Jul 2007 04:16:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5H5O-00008C-Jr
	for ipfix@ietf.org; Mon, 02 Jul 2007 04:16:42 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5H5J-0001dD-5Z
	for ipfix@ietf.org; Mon, 02 Jul 2007 04:16:42 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l628GaJ22301
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 10:16:36 +0200 (CEST)
Received: from [10.61.66.96] (ams3-vpn-dhcp608.cisco.com [10.61.66.96])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l628GZQ22274
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 10:16:36 +0200 (CEST)
Message-ID: <4688B462.8080109@cisco.com>
Date: Mon, 02 Jul 2007 10:16:34 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [IPFIX] New draft version:
	draft-claise-ipfix-export-per-sctp-stream-01
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

A new version of the draft has just been posted and will be available in 
a few days.

Regards, Benoit.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 02 04:17:09 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5H5P-00008K-PD; Mon, 02 Jul 2007 04:16:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5H5O-00008C-Jr
	for ipfix@ietf.org; Mon, 02 Jul 2007 04:16:42 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5H5J-0001dD-5Z
	for ipfix@ietf.org; Mon, 02 Jul 2007 04:16:42 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l628GaJ22301
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 10:16:36 +0200 (CEST)
Received: from [10.61.66.96] (ams3-vpn-dhcp608.cisco.com [10.61.66.96])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l628GZQ22274
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 10:16:36 +0200 (CEST)
Message-ID: <4688B462.8080109@cisco.com>
Date: Mon, 02 Jul 2007 10:16:34 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [IPFIX] New draft version:
	draft-claise-ipfix-export-per-sctp-stream-01
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

A new version of the draft has just been posted and will be available in 
a few days.

Regards, Benoit.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 02 05:00:55 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5HmA-0004RF-Iv; Mon, 02 Jul 2007 05:00:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Hm9-0004Qt-F9
	for ipfix@ietf.org; Mon, 02 Jul 2007 05:00:53 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Hlt-0003GC-3T
	for ipfix@ietf.org; Mon, 02 Jul 2007 05:00:53 -0400
X-ASG-Debug-ID: 1183366835-0c7800490000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1183366835
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id D60A07C368
	for <ipfix@ietf.org>; Mon,  2 Jul 2007 10:00:35 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B4688beba0000>; Mon, 02 Jul 2007 09:00:42 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Jul 2007 10:00:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
Date: Mon, 2 Jul 2007 10:00:35 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922A9@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
Thread-Index: Ace8h3PdVJQl88GEQcCcIKMu+8f+JQ==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <ipfix@ietf.org>
X-OriginalArrivalTime: 02 Jul 2007 09:00:35.0335 (UTC)
	FILETIME=[73D5D970:01C7BC87]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Subject: [IPFIX] [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1773519268=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1773519268==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BC87.73E20FBB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BC87.73E20FBB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All,

the "Extended Type Information for IPFIX Enterprise-Specific Information =
Elements" draft is now available online (see below). We have already =
requested a slot to discuss it at the next IPFIX meeting.

Comments are appreciated.
Regards,
Elisa


-------- Original Message --------
Subject: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt
Date: Fri, 29 Jun 2007 17:08:01 -0400
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.


	Title		: Extended Type Information for IPFIX Enterprise-Specific =
Information Elements
	Author(s)	: E. Boschi, et al.
	Filename	: draft-boschi-ipfix-extended-type-00.txt
	Pages		: 17
	Date		: 2007-6-29
=09
   This document describes an extension to IPFIX to provide type
   information for enterprise-specific Information Elements.  This
   format is designed to facilitate interoperability and reusability
   among a wide variety of applications and tools.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extended-type-00.t=
xt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of=20
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the=20
username "anonymous" and a password of your e-mail address. After=20
logging in, type "cd internet-drafts" and then=20
"get draft-boschi-ipfix-extended-type-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-boschi-ipfix-extended-type-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------_=_NextPart_001_01C7BC87.73E20FBB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7235.2">
<TITLE>[Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>All,<BR>
<BR>
the &quot;Extended Type Information for IPFIX Enterprise-Specific =
Information Elements&quot; draft is now available online (see below). We =
have already requested a slot to discuss it at the next IPFIX =
meeting.<BR>
<BR>
Comments are appreciated.<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
-------- Original Message --------<BR>
Subject: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt<BR>
Date: Fri, 29 Jun 2007 17:08:01 -0400<BR>
From: Internet-Drafts@ietf.org<BR>
Reply-To: internet-drafts@ietf.org<BR>
To: i-d-announce@ietf.org<BR>
<BR>
A New Internet-Draft is available from the on-line Internet-Drafts<BR>
directories.<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Extended Type Information =
for IPFIX Enterprise-Specific Information Elements<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : E. Boschi, et al.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-boschi-ipfix-extended-type-00.txt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 17<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2007-6-29<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
&nbsp;&nbsp; This document describes an extension to IPFIX to provide =
type<BR>
&nbsp;&nbsp; information for enterprise-specific Information =
Elements.&nbsp; This<BR>
&nbsp;&nbsp; format is designed to facilitate interoperability and =
reusability<BR>
&nbsp;&nbsp; among a wide variety of applications and tools.<BR>
<BR>
<BR>
<BR>
A URL for this Internet-Draft is:<BR>
<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extended-t=
ype-00.txt">http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extend=
ed-type-00.txt</A><BR>
<BR>
To remove yourself from the I-D Announcement list, send a message to<BR>
i-d-announce-request@ietf.org with the word unsubscribe in the body =
of<BR>
the message.<BR>
You can also visit <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1=
.ietf.org/mailman/listinfo/I-D-announce</A><BR>
to change your subscription settings.<BR>
<BR>
Internet-Drafts are also available by anonymous FTP. Login with the<BR>
username &quot;anonymous&quot; and a password of your e-mail address. =
After<BR>
logging in, type &quot;cd internet-drafts&quot; and then<BR>
&quot;get draft-boschi-ipfix-extended-type-00.txt&quot;.<BR>
<BR>
A list of Internet-Drafts directories can be found in<BR>
<A =
HREF=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/A><BR>
or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</A><BR>
<BR>
Internet-Drafts can also be obtained by e-mail.<BR>
<BR>
Send a message to:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.<BR>
In the body type:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE =
/internet-drafts/draft-boschi-ipfix-extended-type-00.txt&quot;.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
NOTE:&nbsp;&nbsp; The mail server at ietf.org can return the document =
in<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using =
the &quot;mpack&quot; utility.&nbsp; To use this<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command =
&quot;ENCODING mime&quot; before the &quot;FILE&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode the =
response(s), you will need &quot;munpack&quot; or<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail =
reader.&nbsp; Different MIME-compliant mail readers<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, =
especially when dealing with<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME =
messages (i.e. documents which have been split<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), =
so check your local documentation on<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these =
messages.<BR>
<BR>
Below is the data which will enable a MIME compliant mail reader<BR>
implementation to automatically retrieve the ASCII version of the<BR>
Internet-Draft.<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7BC87.73E20FBB--


--===============1773519268==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1773519268==--




From ipfix-bounces@ietf.org Mon Jul 02 05:00:55 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5HmA-0004RF-Iv; Mon, 02 Jul 2007 05:00:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Hm9-0004Qt-F9
	for ipfix@ietf.org; Mon, 02 Jul 2007 05:00:53 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Hlt-0003GC-3T
	for ipfix@ietf.org; Mon, 02 Jul 2007 05:00:53 -0400
X-ASG-Debug-ID: 1183366835-0c7800490000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1183366835
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id D60A07C368
	for <ipfix@ietf.org>; Mon,  2 Jul 2007 10:00:35 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B4688beba0000>; Mon, 02 Jul 2007 09:00:42 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 2 Jul 2007 10:00:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
Date: Mon, 2 Jul 2007 10:00:35 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922A9@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
Thread-Index: Ace8h3PdVJQl88GEQcCcIKMu+8f+JQ==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <ipfix@ietf.org>
X-OriginalArrivalTime: 02 Jul 2007 09:00:35.0335 (UTC)
	FILETIME=[73D5D970:01C7BC87]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Subject: [IPFIX] [Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1773519268=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1773519268==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BC87.73E20FBB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BC87.73E20FBB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All,

the "Extended Type Information for IPFIX Enterprise-Specific Information =
Elements" draft is now available online (see below). We have already =
requested a slot to discuss it at the next IPFIX meeting.

Comments are appreciated.
Regards,
Elisa


-------- Original Message --------
Subject: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt
Date: Fri, 29 Jun 2007 17:08:01 -0400
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts=20
directories.


	Title		: Extended Type Information for IPFIX Enterprise-Specific =
Information Elements
	Author(s)	: E. Boschi, et al.
	Filename	: draft-boschi-ipfix-extended-type-00.txt
	Pages		: 17
	Date		: 2007-6-29
=09
   This document describes an extension to IPFIX to provide type
   information for enterprise-specific Information Elements.  This
   format is designed to facilitate interoperability and reusability
   among a wide variety of applications and tools.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extended-type-00.t=
xt

To remove yourself from the I-D Announcement list, send a message to=20
i-d-announce-request@ietf.org with the word unsubscribe in the body of=20
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the=20
username "anonymous" and a password of your e-mail address. After=20
logging in, type "cd internet-drafts" and then=20
"get draft-boschi-ipfix-extended-type-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-boschi-ipfix-extended-type-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------_=_NextPart_001_01C7BC87.73E20FBB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7235.2">
<TITLE>[Fwd: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt]</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>All,<BR>
<BR>
the &quot;Extended Type Information for IPFIX Enterprise-Specific =
Information Elements&quot; draft is now available online (see below). We =
have already requested a slot to discuss it at the next IPFIX =
meeting.<BR>
<BR>
Comments are appreciated.<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
-------- Original Message --------<BR>
Subject: I-D ACTION:draft-boschi-ipfix-extended-type-00.txt<BR>
Date: Fri, 29 Jun 2007 17:08:01 -0400<BR>
From: Internet-Drafts@ietf.org<BR>
Reply-To: internet-drafts@ietf.org<BR>
To: i-d-announce@ietf.org<BR>
<BR>
A New Internet-Draft is available from the on-line Internet-Drafts<BR>
directories.<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Extended Type Information =
for IPFIX Enterprise-Specific Information Elements<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : E. Boschi, et al.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-boschi-ipfix-extended-type-00.txt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 17<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2007-6-29<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
&nbsp;&nbsp; This document describes an extension to IPFIX to provide =
type<BR>
&nbsp;&nbsp; information for enterprise-specific Information =
Elements.&nbsp; This<BR>
&nbsp;&nbsp; format is designed to facilitate interoperability and =
reusability<BR>
&nbsp;&nbsp; among a wide variety of applications and tools.<BR>
<BR>
<BR>
<BR>
A URL for this Internet-Draft is:<BR>
<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extended-t=
ype-00.txt">http://www.ietf.org/internet-drafts/draft-boschi-ipfix-extend=
ed-type-00.txt</A><BR>
<BR>
To remove yourself from the I-D Announcement list, send a message to<BR>
i-d-announce-request@ietf.org with the word unsubscribe in the body =
of<BR>
the message.<BR>
You can also visit <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1=
.ietf.org/mailman/listinfo/I-D-announce</A><BR>
to change your subscription settings.<BR>
<BR>
Internet-Drafts are also available by anonymous FTP. Login with the<BR>
username &quot;anonymous&quot; and a password of your e-mail address. =
After<BR>
logging in, type &quot;cd internet-drafts&quot; and then<BR>
&quot;get draft-boschi-ipfix-extended-type-00.txt&quot;.<BR>
<BR>
A list of Internet-Drafts directories can be found in<BR>
<A =
HREF=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/A><BR>
or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</A><BR>
<BR>
Internet-Drafts can also be obtained by e-mail.<BR>
<BR>
Send a message to:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.<BR>
In the body type:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE =
/internet-drafts/draft-boschi-ipfix-extended-type-00.txt&quot;.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
NOTE:&nbsp;&nbsp; The mail server at ietf.org can return the document =
in<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using =
the &quot;mpack&quot; utility.&nbsp; To use this<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command =
&quot;ENCODING mime&quot; before the &quot;FILE&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode the =
response(s), you will need &quot;munpack&quot; or<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail =
reader.&nbsp; Different MIME-compliant mail readers<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, =
especially when dealing with<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME =
messages (i.e. documents which have been split<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), =
so check your local documentation on<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these =
messages.<BR>
<BR>
Below is the data which will enable a MIME compliant mail reader<BR>
implementation to automatically retrieve the ASCII version of the<BR>
Internet-Draft.<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7BC87.73E20FBB--


--===============1773519268==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1773519268==--




From dvdt@san.rr.com Mon Jul 02 06:33:03 2007
Return-path: <dvdt@san.rr.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5JDL-0002fz-Q4
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 06:33:03 -0400
Received: from [63.87.122.150] (helo=myhwgx)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5JDD-0002kO-KS
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 06:33:03 -0400
Received: from rciko ([193.159.194.181]) by myhwgx with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Jul 2007 05:33:06 -0500
Message-ID: <4688D462.4030203@san.rr.com>
Date: Mon, 2 Jul 2007 05:33:06 -0500
From: Morgan <dvdt@san.rr.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: This indicates that the supply chain is now widely accepted as a critical enabler of the business agenda with support from the board-room down.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024

ERMX Grabs Edge Of US Trade With China And Moves Into Nitride Devices!

EntreMetrix Inc. (ERMX)
$0.16

Congress's push to increase trade agreements with China gives ERMX huge
advantage as they enter joint venture to manufacture Nitride Devices for
military, energy and technological solutions in China. This is huge. Get
on ERMX Monday!

The Element overcomes one of the primary difficulties with Bluetooth
devices. Creation of a virtual warehouse for real time stock management.

Positioned as an add-on device, the Element adds RFID capability to any
application at a cost well below a full PDA Handheld RFID reader. The
MTCs enable enterprise executives and independent software vendors to
envision, architect and evaluate customised IT solutions before making
an investment. The self-diagnosing computer that learns from its
mistakes - LogisticsIT.

Mobile PDA solution for in-store operations, Aldata G. A dense reader
environment is one where multiple RFID readers are located in close
proximity to each other, for example in an RFID enabled warehouse or
distribution centre.

NET Framework, enabling a rich user experience and optimal flexibility.
Britannia Health Products Ltd.
Without a hard drive all moving parts are eliminated, the tablet is
designed to work in harsher environments than comparable devices. Epicor
solutions provide the scalability and flexibility to meet today's
business challenges, while empowering enterprises for even greater
success tomorrow.

of Japan and Wonderware, a business unit of Invensys, whose products are
marketed and supported in the UK by Cheadle based Wonderware United
Kingdom, have signed a new software alliance agreement.

If you chance upon a new mail in your mailbox with any of these lines in
its subject field, carrying an attachment, apply caution! Major Auto
Parts Manufacturer Implements Blue ERP SolutionBlue Fountain has
implemented a Blue ERP solution for a Brussels based major Japanese
automotive parts manufacturer, Koito Europe NV.

"Our previous barcode printers had no internal network card, so each
site had to be managed locally and it was very difficult to control the
whole printing estate.

, a leading provider of Supply Chain Execution solutions, has appointed
Brian Thorn as Vice President of Sales for its SAP Services business
worldwide.
A dense reader environment is one where multiple RFID readers are
located in close proximity to each other, for example in an RFID enabled
warehouse or distribution centre. When used for tracking assets RFID can
greatly reduce the loss or misplacement of goods, minimise shrinkage and
provide additional security for tagged items. Increasingly, customers
are requesting the entry of invoice data into online invoice processing
systems, which is proving particularly time-consuming.

They are normally relatively expensive. Companies keep confidential
information in their computers or email accounts.
In line with the existing Aldata G.
The MTCs enable enterprise executives and independent software vendors
to envision, architect and evaluate customised IT solutions before
making an investment. E pedigree, pharmaceutical, event ticketing and
airline baggage tagging will also see business benefits. There are no
tight controls on where an RFID tag should be positioned.

The Wonderware Historian software includes advanced data storage,
filtering or compression, and multiple retrieval modes. RedPrairie
customers benefit with reduced cost of deployment, easier integration
with other products and a fully supported standard implementation
platform from IBM. Epicor solutions provide the scalability and
flexibility to meet today's business challenges, while empowering
enterprises for even greater success tomorrow. For a home user, it can
cost dear by way of theft of credit card and bank accounts, e-wallets
and online game accounts. System Structure  Benefits . RedPrairie
customers benefit with reduced cost of deployment, easier integration
with other products and a fully supported standard implementation
platform from IBM.




From mark@welebrity.com Mon Jul 02 07:34:35 2007
Return-path: <mark@welebrity.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5KAt-0000EO-7A; Mon, 02 Jul 2007 07:34:35 -0400
Received: from [123.109.66.223] (helo=[123.109.66.223])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5KAo-00085k-Ji; Mon, 02 Jul 2007 07:34:35 -0400
Received: from [123.109.66.223] by smtp.secureserver.net; Mon, 2 Jul 2007 11:34:33 -0900
Message-ID: <01c7bc9c$f6490890$df426d7b@mark>
From: "Cornell Tompkins" <mark@welebrity.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: AutoCAD 2008
Date: Mon, 2 Jul 2007 11:34:33 -0900
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_0006_01C7BCE8.6630B090"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2905
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2905
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 8a9672ae1970aa20cd94e880017fa9b4

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C7BCE8.6630B090
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0007_01C7BCE8.6630B090"

------=_NextPart_001_0007_01C7BCE8.6630B090
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

It's snowing, it's returning to a town
She stretches a hand toward the toothy sleeperwith visors. Their brave recr=
eational vehicles
III. Chronology of Northern ExplorationSeems reflected in the infinite of t=
he lamps.
Dismal, endless plain=97<BR>Through the back of the picture at the patch of=
 white
And M&#232;re Chose's square of world, even as theyIn the dread circle hemm=
ed by glaciers,
XII. The Mystery of the Missing Ships: The Franklin SearchHow can they get =
the point of how a world
Of tree-dividing sky finally comes down toMy keyhole blows a gale
and turn it into something cartoon-funny.Some stubborn sprouts up through t=
he stubble hay,
And trumpet at his lips; nor does he castIs the moon to grow
How bittersweet it is, on winter's night,The line between the outside and t=
his room

------=_NextPart_001_0007_01C7BCE8.6630B090
Content-Type: text/html;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1250">
<META content=3D"MSHTML 6.00.2900.2905" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><IMG alt=3D"" hspace=3D0 
src=3D"cid:006901c7bc9c$f6490890$df426d7b@V26T3VH2" align=3Dbaseline 
border=3D0></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It's snowing, it's returning to a town<BR>
She stretches a hand toward the toothy sleeper<BR>with visors. Their brave =
recreational vehicles<BR>
III. Chronology of Northern Exploration<BR>Seems reflected in the infinite =
of the lamps.<BR>
Dismal, endless plain=97<BR>Through the back of the picture at the patch of=
 white<BR>
And M&#232;re Chose's square of world, even as they<BR>In the dread circle =
hemmed by glaciers,<BR>
XII. The Mystery of the Missing Ships: The Franklin Search<BR>How can they =
get the point of how a world<BR>
Of tree-dividing sky finally comes down to<BR>My keyhole blows a gale<BR>
and turn it into something cartoon-funny.<BR>Some stubborn sprouts up throu=
gh the stubble hay,<BR>
And trumpet at his lips; nor does he cast<BR>Is the moon to grow<BR>
How bittersweet it is, on winter's night,<BR>The line between the outside a=
nd this room<BR></DIV>
</BODY></HTML>

------=_NextPart_001_0007_01C7BCE8.6630B090--


------=_NextPart_000_0006_01C7BCE8.6630B090
Content-Type: image/gif;
	name="YOK0YNC8AD.gif"
Content-Transfer-Encoding: base64
Content-ID: <006901c7bc9c$f6490890$df426d7b@V26T3VH2>

R0lGODlhmgHBAfcAAAAAAIAAAACAAICAAAAAgIAAgACAgICAgMDAwP8AAAD/AP//AAAA//8A/wD/
/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMwAAZgAAmQAAzAAA/wAzAAAzMwAzZgAzmQAzzAAz/wBm
AABmMwBmZgBmmQBmzABm/wCZAACZMwCZZgCZmQCZzACZ/wDMAADMMwDMZgDMmQDMzADM/wD/AAD/
MwD/ZgD/mQD/zAD//zMAADMAMzMAZjMAmTMAzDMA/zMzADMzMzMzZjMzmTMzzDMz/zNmADNmMzNm
ZjNmmTNmzDNm/zOZADOZMzOZZjOZmTOZzDOZ/zPMADPMMzPMZjPMmTPMzDPM/zP/ADP/MzP/ZjP/
mTP/zDP//2YAAGYAM2YAZmYAmWYAzGYA/2YzAGYzM2YzZmYzmWYzzGYz/2ZmAGZmM2ZmZmZmmWZm
zGZm/2aZAGaZM2aZZmaZmWaZzGaZ/2bMAGbMM2bMZmbMmWbMzGbM/2b/AGb/M2b/Zmb/mWb/zGb/
/5kAAJkAM5kAZpkAmZkAzJkA/5kzAJkzM5kzZpkzmZkzzJkz/5lmAJlmM5lmZplmmZlmzJlm/5mZ
AJmZM5mZZpmZmZmZzJmZ/5nMAJnMM5nMZpnMmZnMzJnM/5n/AJn/M5n/Zpn/mZn/zJn//8wAAMwA
M8wAZswAmcwAzMwA/8wzAMwzM8wzZswzmcwzzMwz/8xmAMxmM8xmZsxmmcxmzMxm/8yZAMyZM8yZ
ZsyZmcyZzMyZ/8zMAMzMM8zMZszMmczMzMzM/8z/AMz/M8z/Zsz/mcz/zMz///8AAP8AM/8AZv8A
mf8AzP8A//8zAP8zM/8zZv8zmf8zzP8z//9mAP9mM/9mZv9mmf9mzP9m//+ZAP+ZM/+ZZv+Zmf+Z
zP+Z///MAP/MM//MZv/Mmf/MzP/M////AP//M///Zv//mf//zP///yH5BAEAABAALAAAAACaAcEB
AAj/AP8JHDjQH8GDBREqHEht20KB2R5ClEixIsJpFgtOM5ix40NAfzpipNiPIDWPD/GJTHjRX0Rt
/7RxzDjyYbWEJ1FmhEnxHsWR8HQK1VmTYMShC2EhXbq05L+ZC+8VHQqV6cGpC6VZVYhPJUKeF6/6
wyhzKVaC+Qie3ZrRq8RX/5axHXh0YdWHd+8K1Du379Kbe58+3Dh3rELAKO/hW6uQMUuUVcEi5MvW
8VLKQn0y9Eux7kF/ivFhRmmZs+mKiJ+OPk0wNet/WkkqXNTR8+elmn/6c6vQX2xt2YBXtN3RWcWc
r40mPyjZ6urlFZ83hz6UEGfaFqcjlPvQaW/XCy2P//QHFbPMutPsZZRHvfZp5AP7Tbt37/nw9lSl
aw/vkfhewoH9A99BWUSHkVKsZQPgQNw95J9A+AyIkjYbGVRUbo0ZROE0I9njh0UcZqQKdA+yVd4/
t1R2mi1sqbTfZC/G199Fot22FUaiwdIIIzHhJ5GCCmE41FFYpfVQTmNJ9qFF1BQln0LGQXfLJKRl
VBWCHSEzjTRbFlUaQ/5QE6ZBo+Qx0DRgYceWmFZhFBuIjU2WlVDjjecXeB59OVCEFiECk5ACtiXh
SgRx6eNQvFlk30LzSKSnlSVatd9zhmUUKaGkzcQRoBLFyJp3FsVC0CwVcboUJxU9eehxXpkKoVBw
rf96Z6e9dZQodIwxgqVaNaEX50WPLiqRqwuJKhCeCN3KVDAWpYJKlfgRO5OyC8Xq166vOWTkQmLW
91iAA1k3ELGsPbrgPxHV+dhaLllU4qAKgaqTsRVRSx2Lw/4jSjNCCTuQtXgJ9Chr2BL80685YdVH
e3y96ahAPE40jVeV9gjTfEhpEyO5BEWp1lymDrwUwL+KNFbFASOk5kLV4OPtQvKWvNS2r5VmUIp7
EgSTXqoi5LGVKfP38EAIHrXbPyqxq+hCMS7K3kEc2yoz0lCJjBRowsp0nj9NI9rZ16bZ+zEKZAtk
pCtXUYQCWPTKKVHZB/289EAo+LQahmSjQNOZ/4z/1AyGYrPETN5lc3KHQrDkvRDh0xCud98l9YyQ
44vnDdWbeS+22OSEz+ViiLUZxnGYKAUO506lp/qP4geh/S3nPMX88duPMwWawChwbVFurKcd1lW1
P0Qy7ig0TnlScHOeNzXadA6u8o4Hvzrh1NTuVPTMIDQF4f4EHzGdfFmGXNTCIns6bB3BO5RPZSd/
pkHkomDDQIZGpbb0ZnW/tn3sP4sCKtOwBb4ElizOEWQRAxzIsw5CNoxoRiUowIIUFNI+/E3PJALJ
20hAVYiIue+CdINb9ZJnvNqhQBrBY13zkve9vgwsargiiOwOkkCLrGJ3F/zg6ygYBhlJriM6vBoI
/xeFQvlYsG8EMQjNQOgRxRkEKkGsIAWP2EDaTTGEDExh7fDRD/d9MIio8YjpCAJDWUmkYBJpW3cU
1zssZjGDjtuSAp0HPThCz4LReyNBwOgbFOqtjXCsCUa08LjoaRGQFySSHjnCRh26D4ooKFEUC4lH
Sp5JM8n74hEpYr7GDKwQOvHXXLQxvKkB0YT4A90eKcm466HAFXQMoSGzuBhAWmKWbrSj/TJZu5GU
DSOE+QMr6ZiCPA5ECyFBosAcZkBdogsmYMyg65pISUDBTYSrxKKayIa15MwQcS8zI0U8hZBLPYSX
B/FjM52JkSrC8ZCyfBwE4cahX64uDvB0ZjRjg/9OAjKxb/jwovR6R9DHeeYUVszgboTjzIOchGxo
TGjZhHTNSq6yh/80pVmYSRFRtudS0vCMOa+YzfgUb51M1J/eajQ9VmYxd0hz5EQHt86KVkST/vyg
YrS4yoHaFF0ZSZ5BXtGcaE5vP0vUp0UzqkucHU8iHj1YR6IqEG1ElCDJfFV2iAIjB/0Pkmrhph7t
KA2tPFKXUSSM/kj6P4yggQjMaFAGD2fUXOqyH9DEX91K2lA3irUumMEpX0nKrbGCsBMlneRAYhE9
V5CTVjWz3Q4HMgqt2uggI9XZg8gzGX/QdLD/gKVg7CpQtuLxiaAxZEFjCcc7yGGTA6mGYH2pVy3/
gkWxq5tJUEaDghQYlqmgTagbkZHYLRBWqNmoqzgnshSeqE8gnHpuglRKtoDGUrTAbGjZcoICfglk
SSCcpGGmMUJcvjOWeXstbFuq2uAKtCa4rR5B3jHaKaqWp+dcr137ilb5NTN5damr3DIyTabZZUFU
TchoxviPrCYnetQtabrWStp/PC0VbpTGAvV4jy5Ss6D83cx9S8tATfAOpiH+aX35OmItqjG4hIWx
ihO71CMBjSC0gGpna9VcZS6Ewd9dDiJbmkueNG6wazNt/XJpVC1UjsnSwxiRlbfff8JtnsfVG18q
WklU3jDG+X3yf5eK262UZasWcUZlmXJm6CQ4/8RKrckKU1gUQIKYIRp8pwH9IFMo428xR/5Hjseq
SfzquaeyXNxMotlPMDsatO7rhCWyeBQdUrgwj/1MZjuDDZlVCsj2sRoSaRvmd/qSeb18hU/1poYp
H5q9J+4lL/NpZSrWZNBM/ix7V+klVKBy1ZNrHt3OEggmThK2kpiEUaXhilP8GtF6JvUepYuU4PQF
JpmWCEv/EVcrPQpDXBtNSQxSV7gl13Ha8AJHIvLUvK0BkXksdJ57+tSMwk0UdPPURKkrRVnew4Qc
KqF9c0e422pZIcXmcnvv18Am0XHhIeQ3XdjruDdDddPLIR1RntgRYnVFIMgZyQrvB5ESFtILL/89
JBidJ1PFUbTe9r53Bi1TPPiyTpMBpTdsLedOOIfQrPe1SANNroUXrBqM5aUia1/ztMKEsiLwCIqJ
fiwSDmHmXMs9E4e+iZBOVvUfzbAXVYGs4wmhDzKnIftWhNX0jrSZLta+0UPwwBRRh0eVWvcxBjkz
sIF5fcUCUUJfGMwXj3LEUKt5u48yK6bGU8biipoOVL4MGces2Ufk0UtVQIVxpAxsG1ftl0LeICuO
WNxJFcl21tvyvK38vSojylNHOGqaquxmJhjBPXMytrfV+360uvOIQ2aX+AzZHUr4mZaK/tFJNmnE
QnObfcZV5xejBe01aodsEt0uLItznCpl7Mj/31mT/c88Cl7HJ8jw20Ntf27FIRxhjNXUjqH0M3fv
46xIITA6WYJ0ZWIfdxWeYX9I4WBc5TlCNCTbh3FYhxDPEH2vwXUeURZoIAZAxWNoRxWXJRB0ZxrF
kIA3phaa0iI6AUoIkQ8D5jZJdSLuh4FmlFl/4yUtKBAPGB2iJxRJhRKesR92tzk6wROMwAh6QQWn
8QvUISYjWBeg0oP4IRkzQQqJUBXqQIB1VxF64l0EJEhUQXacNRQ5KIIN6IL913saKBRewSceQR+K
Qh6KdxncYhCIZRH9cDRIoYZT9TqqABUloQ6sgTLbRyFWOBiCqHfHdyuIQHUH0WnOcYcokYJ+/wF5
KIEq/yAV4TcXJYIPcvB7vzNDVDgcjxd3Q/FDZNgbMBE4J3GI7pEx/NN6x3EQEqiJEiEMkgiLtDg0
q0JOXSgUnUcaEqgxH+URI3gQYWCC7lKLOiEMaoMfjrgUlzeJgZIznpcRaTEot/eDNogUr7h2KdOG
IDhaLeaC8KE7+iVD/5AFqMRw5kVygbgUMAcg9faN8WdyUcIJHUhxm4EQrYBJKIAH3MRFdTYxyrUU
Ndh+WzU8LtEuqjcU5IUbg7h7sqccLGFy6TiDA+IKVoMCU1BlSdRi+hWQevdhxkRbxkRxceQVJWRy
KTdkBNEK9kA4zRBoNvdK52aMUFMTpTSG///QQq/BjVDFk5qXEtv3GSv3QXcBH8kFeNQEVUMZLxDI
ikJ3TU/RJIsmUBY0QHjzOIxEayqZaOzzS0aEXBxSiZLFiB3xTaLSiakHiiDiixtIE15hG+S2SYEG
Io2jDYOiJ+W2SUEUhkHpkAchNplEN0xQZWCkFI1WEzZwjjAGaXrDE772lzfZFzNUCm4jMKaiLNMQ
M3eBlgwjerYHXLhzR3u0Eeg1ZzW1Xox2jpZjPFnEDCi0ffxmEPYSmBzRDCEFmqXmTDMRBjvAIriF
FbgVRDk3I36JEP3wIDVoIwmpJ9lFkB6xfzqxi5gFlEHJaPwSk51DDKGVdMMkcCwmPQ2xmMb/djwo
cAdYGD0L5BVx9DjOsG7nsToZmUGA55F7ZIszlktLxkSScAb9pRChMI58oxA8GEqc2VlKoxPMolFh
4Q/ZqKDClUUL+WqK84G19jgwMUIspgXPBTds6WeEBjf9AEsr5WqsiX8CsT1/NJ/DpI524VfBg1Eo
YAiYJW1vdGl7hFBrNxUjtW0xsW5l1xeUESmTJqAZ4RN29yXwwZHuaFCJpl3BIxMkhpsZBArLMB1R
6qJ6Uz9V9EHeeRFAB29/JJFidlMoEAhdkFE9RDYvlmKPM5e8xhbaUD8YRzpq5RiPV4cNmSer4RKu
shZ8oifIMWLPaEezAFY+JxDNwAk8FRJ1/6UxgkqYlrQWXCqlIeI4iDFvcCZlLApcqWlaA/ZLWPEK
kQk2mRE+YxE4GicQ6iERs5in4TEdmsoV0OUoRfEKV1UaVGlfZPBK7RZJSeIZ7/g4woSaQfdb4bVz
KHAKqIAKzOBsJfqRDNRS3EU26DENj8k5UsEYgvUP7KCR/FWiZSM39Ak1p9GgHpE9FHEM1EeKLWoi
NoOrPoWjOieieVNptTWS47mpD9qf+RU9zxpYLupQqxNw2RQpfTYQ7eBzd9AEAVIS93moPeEXKiGW
NaMSQAKRnlIaFjiK5eR+KShToSAgWQmRfCNvpKWYz1MLUoo5tcVfxAWxF7g40qZD1GCRB//RAz2g
N5JUY6uELPSkTA8rpaXiFxPzGqtqES5zf31phZaxsU55dcH4D42iQPzScrxRVzOJRev3D9vzna1B
EL4pl1v3rAHrM3DUD8RSVCaERA9LtnBEGUuJUovkHUE7rkHCGQFIJwdhDgmLEs3gXdKpELTnINCI
NPxxIftKPNDGV84KqV4bW3KrfkCrN8R4rD71at46sIUEVI3GtpcrqXK5rU9mc4MlFfgjSkbqFxQb
szrRjE55fUuRPd+3QyeBcR9UFoXWpG+ru+hVO12buOonbRimVIu7WhTxmqsjEMiLuX2mF0bVRbPG
cFmZTwHlpjzpilOhen6okBqlJ+CFLuL/065DEbKse7gWETFJMjuudl52xnIQx0TbY7CbZFXoc7Dt
hK8kuV4SyVoTCWffKBCDg7/yxr8aVDy1A4gVkZ9K+xBRoiECU36z+pFTkX6ZqW0FcZBIiXaQiCK4
a0FQOsADF09f1mg992gg5xD3a0CxhgIUmpLXCHPxlEqg+b+eW54tOznCsAtuukfWpSnHl23GAX2c
QnYq0Q+8MYBLEXt415CumzoLbBFOdjXOhykKAQiWghCuoIi2uI4IIXURG1T9YjVPwhgeUxODG6B3
m4Uc8grD+xALkxn+N4NWUSIlUh8b4SrL+BUE8QyraxWV+4sOdTIZ7Dt625TA2ERliBCc/6IYYvJt
AsF15oLGEvG9JiqGpnGgb0F+ckyTdfciBQosFAHBm3zFhfKjYjE7VhOrCuEJ3bHFOiFdfZyK5FgR
bfwPiWA74fgl2dAunIw6gLfB+SKx1ZjI4yK+0KrHhfwQrCw0rtrLSRS4CEEGnhRkThweFwstxywU
/Mdmz/PJzLwQsVeMQTJGS9xRCeHNArGmVLwVG3ZMgrsVuIZZ/mIFVNzOUmN2BfQY9mE6PWRxPNGF
wJzE7lEegZOcAhN/SRHOrnga6mwrX5jMA1EgWAzPxtwR9Mx3o8QySlETFEOAG+wVF+PMcby9FWHQ
CIGFGSEN8SzS3LwqkFfL0pgoBZqx7/9juC29FbEMuYfSnqOV04YsEK3A0mBnZgLhxX/JGZCIhQ4c
nT4yxN+cEYCgBwx5EDCdEUpxl8txFNFFggthG+jMFupqzY8iF8oyxU/tbU4XfK87EAlpyrB7jT0S
JLejYDeIEFU91UWBM0NRDTQTEaDEo8hcydR5PkLNy08Xil99Y6C4CPx51k1BEaoglj6hHT7oO22N
CqM6tAfTJAjRCDjZEeF8pwcBF9LlnOVLHW3NvW2JtHm3XFzDE9B8gBKRx1FB0+Q6yIN9vnLtKJSC
2rIzGsLiMAGtfeUiqyztGMwDfdThzZeCrmSUQdlgkRYJoB2xMjEcR/AKHXmzvP9QMEP/qZL/wzq2
8cYXCMP5S91zIX9VXItS0aLh9g/y4RScggYKEcUh+BCpYNq7nJl996isoVpW15HoLRSOA721gy0t
Fz0R4UHGZNj/sCTshr/n/Q+k4Nb3kX+WLBAyKtTguxfMhBX0jRBgkOFrrYslHsL0tiZXVBPtLVog
ohKQQLgEfk3a0EU7jLl99UugtK1nIbpg9LK5fTrTkA2eQdIcXhvXrI3ZbBrhh6kvtYhTdBY22htF
kWPyENYTN+N0M2pHd7kGdG5eXjmXO8IDvrQggh6CfCipnd5OJ8k1Qy7yWjY76148tZVkM7jopEFS
6cL391Sgu+UjUWf9hkUvBxtlpneT/2TFQssY5GIICt03/H3ipxHbbdLVVqESwiIyanW8hyZSnHVn
PXvdD7ECZyznJPkUVJk3WeBk9hpH/4HB+rS0QeuM8K1LLq5Hu2ys+bp0p124qZiLJC4pYpR6KDG4
UbUFf4ARnG0Ryabsj4XASTnK+WpYrKOtF01BNUA88qpUzyahJUxl0uO8R8QM14lW9hxIfWMbZfa+
bv7cVBEpZr0VGCfKBMpJMCNIi/Io2gAIxYYScEMeD9K5TtruRcaWZGNwhb6+x6o8jlFv/gFGqTvt
bxQbwEpmYhDiPBFElM6Uw02CCflNNVTT0pnYVmiXtFMpAY+yJ/uU0cM8bnqwZUPZiv9Fc7zurakr
usXUPcqLERWf4v9EGDGfHCRvFvf40zrzl7mRLlKVdanKfI8Os+PZDlML33BzEwHp3457QTKP9W+z
Ok2wSS4wQYOR4GQDA/8kL7NkVP4AMB2PRG2/KuYKIRiSDWesFp1nCH8sEESABkXLFHkrngRENrSQ
Yzo0CLWDoWQq2K40ZnEtlFwfHl6B+EYtpak56z4PYD6j89LOFNZ3fENfMxejJ/SOF3x5EQ26lYrL
X1eamyC30ExlU/7xb2XOQKQDNy3sc+MakKpwqbUDl/kgVO/BE4D9nKa9FBvPNAND73X/D1Zw7VtR
bmGX9VDvkTDfmGN6SlsOUFT0Atf/n/iNgeeoxNEQ6/kd28wH4WQ1AeQPsUQ6+RDLr4BvbVkQLeNW
0UaCfnAxZ2jA62hlowrDKhkAgQLFv38CBxJEKBDhwoQHDxZ8yFBgIYYQ/22raHGhP4UV5f2DJ20a
wXsIpz0U6K9ixIz/VLa8CJPgyIU0Yfp7eRPhR5n+suFcKEnmzKFFjWbM6c+mzaNMmcLUBjOQlaME
DQ60eVViR4hcNQ71KjNsQZqqvBpsiHLsxo4OWS5MmfNrtZVctTVbe+xfMYHTpr0U6MpmFhRRG1ak
xvBpVZMlGfvD15OxTFgts03GfPOeXIKR/+HjKfnfIoKXRWduefXk1bdktZ4d2A9s/+uMY1E0g8ua
pW7abHnDvLebN1qrKKYwwRt8Ib6TW1FI0/pvsG6jslFvvN6S82S6BBMztI6ZCpXsBFe1XCyzJOl/
0jL6Jdq5PNzVxN9HV4jbYvrcR22jYIq12qKr6Cl8BJTpQOeGy02bOAA0yapmHEsLFdrqO6U3xRDy
rKJsoqGwpRDnm++790jM7rzyRuSvn2lMQ7Em7fjLaMQYbyxqO6uO6rCialSEaiPDlltMRw7jqw5J
y4xciJohZcqnOxxxtIUxGzNiBjvUaCzqSRxfnBJHE2PkT0PgGOuRSZ3GjHDLKb30LiMg/3EGMzZb
GoWxIbmcJjztCFoGoZyuDLNQQ//DVBNP/WSCM7tEBdXyn0Yxe1SmIsvb7k6CYlmoTsa4XCjPydK7
zC8Yg4wU1ENXZTUzGm3q0ahUsrxR1VhlLA+fe+5RdUaGNP00TE83LHCL8ki1bqRbj6q0VcZODXPZ
+bhs1jJnCQKq1WqlU+mlkRLbFiZgyxu3oi2gnbZN6f7MTMqMJsVMFFQsrcjPhaRBl6FKwy2qJGkh
xdZQJnv9zKdrR72UxCLLXdHDlsL7t6KcnlwW3qHyGcriG9HV0cX5+DUqVr0YuuyyiDE9zSiQtZUY
xVs3w8cfhjEjFCaaRhx3qRzv7RKpaWseqlcw2S1qpGxjHHFkSLWZmVybD3aW4Kb/iDRU6oVcPHk+
bQjWcWV977HXqHwL/NjroU42eFU1rc74n3kPrqZHts+OE7WsP8tOmjTVPRYmfBZ1yWeocZVpbIJa
cW8osxkLu7TBiSWRGlegzie0dZ1W0lCgeUQPsx4Nu0fjSAVNZfQw2TT88b7fVd1QfO4WPMZmPZsb
x0fIeLiqMUcS/UhJDZsbzmlKl7mokykiqLKMGL7EbpW37LqmbFIXpSgzW1cMdoBJZMSQy4OWrvYY
Oam+8JbBT52hyIbcXCd9HxsKeeX7EwuF5jNb/HxBj8Yb4J9getuA7FOXARaHOguiDYKMokBJqYRB
13lUzMR3nTtlQ1R6+gfDrKY9/xTBJzOqgMlaDOg5lbUPclVp3AIfmJbbFNAg09CGC2NIIBYWkG+8
4V0NbfipPFiKRkpJRzGmdCv3XHAyEcufCbPjF1U1rTipuV6NqqLE/o2KaALcUVfS8opXhI8rW2AJ
Z2C4ldyo5S0B4soLDYOCRNACRz2kWbjGli82TTBgbVJK2o5lwm7dKCelU9xhEFKNaojQKOnRhsy0
0bv3+TGEKBHkV0xCq4JoAVj+eEVYYENGwj2RfpdRyDSulD6o7S4j2eAPBwlRCHfF7h8hgkz+nhc4
2VkpLWVE4D+wQT9eYgtarEkPRwZoHII4IzSwIc5moJiQZdavipBaS1taw5WnRP9TLdvjW0uecSMx
1AgZZHufkaghy0bOJIWHogk5MVNNaQqHNYnzZC9NYhocZgVACrSmDiFES04WJCN4uJ5CUsKmfEry
MB7rJy8FOsAxDgWEN+rBe4JRE86Y5pICQ4gyJ+O1nJCyUNuRZk3sYx9h1gUmjBimQH6S0pxo0oyl
EQg8dYSWaeLBgG/hTY8Kak2lDMinNyWQbKKizuwgtIEEocpCGsVBhKQCkOLK5qGc4a5xGqUd3zwU
QFnjvfagRVeRQYsDASSSw2gKDf+JJ0KyYE9OhgUbzODKTGn4xN+MUKHTdIuNFCJXn8KDL8LJCFON
dw/BNjKpd1wIFTdalT5hDxD/1+qEVgARldX8tCBTMCk/c/MX7U2hQ5psRFpJMhZUushjDNQKTdKI
10h2xS2LSUkz24qVfj4CmySSJVFHVSkPEoRpDIEnTOCYHT0wdj4d2ZpfCmpQ5q4rkXiZ64LQ2JBD
APWACJnUQEbaEbY6E6iW0O5rM2vZXsI2IrZ9ZaU8SpBzwu9xeQykUch6Sm0Mlz1V+94/UOmTyPzB
egMxjHugM0gVrXa8o6urPiNiYOsysGP+9KRXVAsqlwqEHSW1SKwMudz0jOUliUrheg8l4qNUtVwi
5lVwEeKebGxtNPjNXP/IMxsZoSCAjmOwPDVbxtXmmK4LjiJC3Og4CGvEmlwy/yRBXOGW/DZXtE9O
aH7LNY1W6hd7UcWf/qxFEHOcw33gRNHaTsjBsGSjL4qJYUMMMT/m9rGZe5XnQnXckshM7sz+FCuU
z7zcAQFmIJxZi21dwNrmhqVbiTKNuxg5H3jcRFmxjBlq7JWTZTUrPcElMWL21UnGIPeWuZmeaHcY
OLRqpKWAReaBQ2Rjh9DzmmSEzjRb+0RXRxkhtp1hP6NZTv2mrbdWRkhlMm1HdfzDXqVy5Pak9RKh
fHnFJ3xMpJl1XAABuse+1eJN6wdkt6DAYNG14XYjcivueofb/QFkR/z8abuKdSCHCMSoG5KIRNhV
1EE2yqKv9pIWYwZGjUXsUf9kg7H40usfk1giavp4JeYwlcKvuFKCdehkBefGQksOtzUZGHHeEPS6
ohLIDBXimWCcgg/X1e8K743yBpcHFNchrGe8hUpXVUTf0nFiq8LWqKEtp8mvawkhuvg0sTzl1KPG
j6pY7hoU1FoijxxgxO4pQtZog2Nakcs6FJgU1+J03ECForwZ8/KN/qsk/yMRRlCouu2oOF8qBvMS
E8cfXml5nWFmyM0zA1bTsbfnJAls3PvOEMxecXA0aQbgXEXzhKOnXPCkxkPLo3ZoP6p3jAc8+CbV
U2PvGMs7XmQjGLEzSkHrKZnO8kHcvEhunUlLwWVSorLgyqKFCZaZcTGJ8qH/92cfZVh3H7xSizJf
4Gt57hlJoR3bu3bhH0oue3LxSGDIxAS1SfopE2XtjacSO4L5ZoeCe0aqoduWPLX4We5EFUqjfIxe
p/vOxrbn/0FwzmUkECWZ4EgUa1SZzOxobCsXuSgJxcog46KbgGOVU8g5ggg/7MqZTSETguAqvNMa
EukR02u9lljA5ouMQNA+mJCGEFGFbRKRqkAbhtCP9YKX7QieqQmZoUC9o2gFq1m+6psS66gulwmZ
ROGXpTCSD3ulK8OuqyGZiiBAFGmGflgvI4mMO6mWKjO4f5hA1GjAJfITOQAfhKA8xqpCovMl8uO1
zuE0hEgdG4ER5oAqvtlA/w3EjNwjMgasCLlxFsOxnBiTj/KYk8mYwswbPhzhP4LohJuQtvJoQP7g
jF3CCfJbmXPaDk95MLxBuyisG/FzPvA4wPBhlUdkBx9hM98Rwqtpn/AAw4LjPGw5Qi+DNoYYkcnB
Ed6rCi8hQfUIPoQol0SCkTV8xZdQvEPikiM8pL2DnvMLGhuxCUwruEIZkUE8inZQRVmsRJiQvE9k
Q6QYRVT5h138wD9BHoTwA5iYh6GoQTpDwJ6YG3/YE4FrRsOLiqpiO5tAhmSQFUJQlVeRi/fLoKjI
h2jMDih0GGlEDVf8vIzSAoaYvZbAKjHsJBA7m2nAB0YYPUoBNvmDCSugiv8Q6YEeuJm/k5Qp8cVZ
TEW7sxlyMgz6A0mCIMlBEht/dAmmyh+aMMT2m8QC6ZpwfJ7w+EOEiEUpSqyS7KAQ8ajps6jBKQkj
yUPzmSWV5A4cARkuoihZfBRYuIVgGcMmmwnyC65fQ4hScEZjm4YtXJWnAMjCwq2cKAT2KErDSzao
ycmF4MdPzIldJKqhq8G/OIqOjKpSXKyDeQpVgZNTuEO2+8cYuRWpcSImIr6KAKG52cZWJL1hWQxc
ZIgqocqW6B27jI8xKbyhiId07EPBTJn445lxlMTWiUFxvA6x5JKbpIz5OEnQRAjVdBx7rED4Y8sw
JEK86YOFmLHmW4g6NED/HZzGIWwKVDIVwTuUYhAiK7LBocg5JOKfqbyX0lSffwjEoWjLipCGGzMn
aYDN8rjO5XE9xIidxomMbmSUGxFLDLLNLaGiP/Cvg0mfRElPnsQMmvwHeBPH6oxA7aCL+SSRpUrD
llkcMdOdtOw72RybBfy9JmmJzfxFpOQRUZLN7LiHLnxIo6gGyOzNaMkMy7RD6PwHVbgTgMQ9FLEY
bdBP45kM36S91dGc3xIUZRycROmmaZuPBcUeDzW29GEbyXwTmVDNmWGOzanO2tFQWrqvOHyWvDRB
lMxCR/lQMowcf2QK1CQRaQAe5vhDqdEGH72OWsDGoskU7dAoW7oWuUhS/0+UiVfwURKrFCfhw+/U
UUpbCEugTx6pxsB8JpgwB2FQuA5qIBK1RoIwv9qzGq9kCFfowuw7GGow0nUxkS58ksRYjND6FYJQ
BaH5GJjghBadIgiVyMbLO4XByzAxjBiky/fYDkQloRe8MhYcVCmy1IzwHh60T5i4VRdFSt1aNoaI
he9cCFEwT0A9xqIhTqzElgkFxjvl0AJ01HFKjGi9R2ktQfFciHwxDBcxG2VdiEW4r+s7zczIBny5
DuKsOWZliDAoigxlCD99xWLlHH28LYWBCRxFy9fk1m9hGmrgV35NhX3l13V0VmctnpJgEzbxku3I
0w7iOi200VC9mnK0Of+fMMffbKS1zIgaxQx3dUEv/JRnSA+GnBL+sNdTqlYUoQZ84NdpoIZUoAZY
6FenktmW1QaXddl+dVSWzSB+zSCVzaDiMZGgzQyhPQp5pVAGHFNXXTQJJYjh+kxKtE4uAdYYIVGQ
gQyPlSXplFKjqDs76VeWTQWmtIWWdQVUKIQsSAWh84OWfYWb5ZV+fQWc3dnEaMLP4NkmvFp2LBRO
KVkIsrKVcTPMcFrafNifbdSN0luYaM2dPZuU7RffWqSGmgzD4T11jRF/bdnM7dcMSgU/KIQpmIIX
8APQzQI/8ANC8INpSF3PPV2ZdarMTYVIuFmc5VegzQZoJVhpPVJO2dT/e62KLuxY8KQZqKGkjVTc
jVjYZVAidTIckLHcEsFZmdFcWrwH082C602FKZiG0r1e7t3e0SUMLSAE2k0FScDc861dlk0k2q1d
9tXdAqyKHiqeUV2XKvvByfAS4M3G2FnChejUQrGJ4l3O0bSj5GSd0DwKNECNI80MQGgGfiUFnJ3d
0vmO6kXdCzZdV5gC030B0A3dadhg0Z0CQijUSUzZfpVelwVb2GXhCXbfaPVZx4Xff9jNjJDMb6kX
m/gOfjlHUU3JoyCFhbCpkR2xnfxRVbTPWYXIomIMQEBDZ2hfnt3cmcheLcgCLdhgtO2Dsx1dP7ji
Dc5i000F2KnHAsTb/81d2Zj92n7NExRG44EdE3uQSYTEFlFUnH/7mDL1XZkIYsJxAXpNWAAOE27F
3/IQsWZ4SPedXUqlBg4O3UfuYNEt3RGe5EfO4sIMSAaNVumV4GOwWTV+YdplBtyt4IzoxFMxnH4T
Tc+xFWItsvI41Rnu3df8QBPKvwIdijzAwqZiPqNA5GklXxiVmUKw3uv9XBR4AStGZiy+Xi/OAkn2
gxJ+mgnV3X4VURdGXwkG5YBNjG0EOEkZGz2qJa6lQKq91nk9VxdUic3pRukkMcWsChIbJ5Zthnho
BpWV4p0thAsWXdM13REG3Ui+pw4G4/GdYWAhGGDpB4OlxTahqhhW4/9PlugWbtlUcIXMdYXb5Vef
nZKovIlE2stagVdJ9ImhoteONQw1KUiY8Og9PpFVocn1vQfcYIZmYMjNZEd+XSWXXaVoRl3T7QMs
ruJp0AIUwGJp6IOc01qEtBo/GEiVpeBnxdywBVtUYtsVZuCWiMp6g7+FzahM8Yfwm5REEsYonUo7
aumXzhG66xNGXYhO3Kj0UIU64deZboZNMIZNSDyZSeHP9eLRJYR1JIQs8OssmALjOIkXQIFTMF2v
XtzOy+TJIOWIdt2ZNRSuZlLtTBebsRp9EwVxBlGzxp5wgTyFG1aYcNvEiwdjMAaONsdXYN2zdYm/
5t60PVsuPokpeOb/tXXpGPGT2nlUamjbrDYUaYa5/X3So+gD/T2KW2g27MnVf/BLNW2JlSayGkYM
nL0HvBaFfM6g4Tnd8O5cQtjgf+7i8saHSAZdg0YMz2BgnVVro1hLR2XOS42T19VV9CxaxjDa3mOs
5d2+0J6Shj3KckYIQhjaZzWGe2htav0Hp+rptB3uzvXpvyYELMZiL8bw00ZXhBiF/41nzPjGVeY1
aRi6yMCH4Z6PyUlEpNGRIa7N/X6cHqazeZ7MDi0KSg1cWeZMClpP491QaJGNmE08eXhgNKYGw1bv
Di7d1iVmLy6ESB5d3QZs42avpbYULNcOzmiGNMXv7Egkzc7jqIgV/+xWyegR8HTCLZVhiqvdU488
CrgsSWeAlpfAWdb+hQeG0Qw6Wy2YhjuQ5Gcu6t0ub2e+YtVt8gd+WhzBvBthGOF22ceeDELJCdN6
HhT/SPb6xMRVUz7JKLHka02N7FF/DETasozCuZj9BVH4G7n1V7WNgw0m7ykXaMWW8im4B4I2Xfdu
aBMeWGsN0OAk2oPu9YO2c/D8cnq1keTqCa4j8/iOD2TlIB11Cc64kjsJG0lfdGcjZNJ714BRCosS
7n+oaWNQ9MTADZ3WBp8uBAh/8qCeggw3aqNW3SxOhTAl8fpUyRS38uyIFX1zMyoqiQzV42rxT6gA
bUx1vIbJjPDob//ktrlylRGmgN28TjyVLZ5RGB5iJuF2f920Zd2/DujQBRDQ9WKXxQeBbXOI/eHJ
OITHWuKhkFnby3TKFO3voRCj6xVqz5iKfdAsI5FopMleQQV8L/Vf6dd7tuebZS/hDnm0XSXCZl0J
99zrFeFcz/Bu1AaZazKv+WaEUGB/J5lS9RA7V3FD0dBQbMY3CCcUyZfL4HCd/BSJHeSf/8vTae+k
x+tNcNnv5tzxDu9GvmAwBuzwpnWSB93LoNsCxGGXGHZqoLlhL+04Cfv69nUyfIphJwh4yCOnGjpD
gesIRIZOXAIG3RhiWYTyIVy7L/AvSW4USaGR5EN8poZf+Jtzp0X/ahA6CB9utU1bVSjdPrDwPid8
bfh8YnmUn8BAA72ORuP30Id2IaSJb/RSf3j4XhM+e1AiGIGRNAVV1jwqvTxgWvaOm20GUUg8nvWO
Rn5y1kVdmfXcKTCEVHjy0oVm8B1doB1Y6ZMLNgEEVAKIbNP+ESxo8CDChAfxKTSorWHCVKmoQTw4
sCLGjA0ZGsx2UJstgv7+kcIISxtFjRf/efSo8SXMmDIV+hs58+bHl9RQUjNm7FezZigLUiuUZdoU
Py+0ZMnywk+WQn6kFkr1yo9SqE6ZYi0U1FgzsGJfNfOHshk1av4oUpzmzxBEmwr94ET4UGNaQSkJ
rlTY12LMvxjv/9VtuBfjX5eFAS8uKDdoTFiL7wnWyNFgZYVpNwPFJ2ozW2qpkCqdMoWQ6RdTVKtO
etp1adZ+NqUShY/tbWrN4qGd1sy2qLDNpP3+zRvfbmq341ETePsfW+j/6O6tTvQ6wb3T7lrPfl2i
oILSCpZMuC0z4ZfTKMO83HhmP4SKYZotOF/ue7m3Ym57f69fZjQhlN5Lt73yD1BgRZedP/hI5Qch
hUyTSh9Q+TGFFhhiuFRSfviDYRZa9CFVM+4VxJBaBDH0EEUo4hMPcrsJl4pw0/QDFoyv5NaidCZm
NFRDdxX0SioF/VVKYBlNgw+BASY0Uj7VvEffP/5sd6VM2x0Un/9B+E32j1uSZeTjlP1h5E8sBuHj
JE1uqeVbiWqFJtGSE/ohkVSEYJXaan2+gM9Tgc7mU0J7eYjRYUauBV02aaWCD1iiEBKpcMEZ4xly
+Awj3ZLR3WVTogcalMqi42XJGGIXsXkQgVOqt5hgXv4jpIqyvuRPqxWl+FKuiGqUpkg3gRYUUJsR
RSRVflBDCJFXXZVKU1FloRQ+U6CAghYoNAUhWhX1URCtFVWWKDWLRNdWpiWCdY5wly5pjD8lypuW
dIn+88quN/VlK0H5HGQlX64KbOTAASPk1r+rFqbwllPOd6KwOzazycRoUVOnaHpidSFqWvjhsZ6E
TDMhahdOQQX/FShYa5oxti34j4zSMegdS92BiZ3MOXfXj83K4SanbqKJ9ptExmWHj0T5zjRyRv4a
ydHIDBc89T9k/quQ1Qjx69dL4XI9pTZSY4SiP79k6haBE0V4JyFbpAKhVKloYeUWI0447Qv+9JHh
hUyVeFBPQFUEMF5afx1XsAZFR3Y8Mos20tYavSKmQg/Lmk19juHkNdVTMxz5QQ9vZBMa4oIemOgz
Cd1TM/LQeK5ocacS98cQToVUFlPgfqGyplmY1CaJyrOJMZt0iVmjzaz0MkElWvpc84uey95hcnEk
p8zOFGnQ3wVNZC9EZh70xz+pUB76gErWclM2rygCIMBid+6q/0vsBWnZrARNUhGX86u+2aWUYwyd
xU0Lh5jKVKyCQHxkYwtZ0Ia0MuSPaU1lWr/wQzO6tJ71CGkv2aAFLahRrJxBxxmv8ArxflG8ghAL
HyyqWKdEMhBjsUV6OOOe4iaCtcohhAox6VVC0rM+jRCOJazyX/6Q+A95GExc+JML5wgCRJFoY4r+
A41u4sQbeqXFD0iZAiD8tBqPjUxP2niNUvwhKNgE71zFU163mgGMY9wmbPEQRfGYA53jXAxmm+iM
xfZIvL/544/TKB4wMpiSiTEHH38kXnBi+LJuQQdpOpyZihrSv5ucrmoJieLBUNW5Tk6JiQRJ3dXO
NCB+VeYuVv/UXGMyR5S04IMZxngUc3jklgpNa28h2pAW7pEhLUyDKxWiBoS0sJS9TSMbA7yLI40R
j0IS5BUU00YhpVm8n9ymGSrcBD4YSLzG8Ygg3xwgzH6iDWIZg0c+aRw7UxivhjRORaJJpSch0ohG
KNExD4FHRcL1yn4C7noEnQkqmRbEW3HufBnBXnbSMrE3lqWGs7NdnlqjlHuoJnesWc0EC5GUaY0s
Kgj7Bx5LtIlEpnOGwDAeHsGp0t8UDzkvTUhYiAfOKm1iKLoB5yLbWMlBrumG0DlM0hoivyn1Q3Qr
IkghGHG/gxKMk/9ABk62g8qDIAkmDzFRgJYKpqbaBFj/k+j/bopHL5FcJVmpWFtVHqQFo1xoK9bi
kBe1oEK6VMmZZtNNsfAhOBG2U7DtRBBY/hEPnxgWIcoBp08UqY0BUiSnoiBIZInyE+hsDTk5BN9I
TBRFG81PLqADHYC2Cqu6sGMxrwgbRFYxExMldGkeKaJ5EHUx3cQDklxck2gkIhFCvFUid4KQDfwA
A74lhTUoeAEKXOE7ihWJGr1FpE4h1bLb1DQsl+1J8Kq2Up/YhmYoTaQj0eJIYLDlumxh5NE2MQ2K
eKRnXCzfWhGyySb+YxkWMdXA3OMkzmXNcwVuWJBIiZADe25pNYFcRcTXkGzcpmxgyU1ZCKI2umqh
w1vQwoe3/6AnLbwVH1iZVi8vpDJtQUhUPknhNmFEsXBu4h6PzeA/iFdZbuoYcNwMyy/WslmCLBad
/3jnP/rTkyVVqSH+qGfVHudkiPg3IVDOT05y1gxnTJmqN8OIasElVvB5GcwdEaVGGjW01oHFYi6M
HXJF6jHeBQofNjANPh7YoTWVBnh++G7x5JFBOVKM0J6ZhvGocVNFc+I2wwtKxSAazZUSj8btXEt6
37tTFVEszD7z3iUFpMqCMMNwAhuIkwKRz5hMYn+LqZ58/MdgmeDq1KYr0HzTksLZDEUbPGsGBaVy
lS34wYEe2wI17DoyC90JxX644LQee1iKLBac55RGYVV4qf+WXUqFGax2UJB25G1+M4MrlDaUM5ud
IUNEN5/9B4CsWpEwG0QL6qllQ1Q9a4jse8LjAR+AO0fmMlskbLhNiMLWMyygCBoybJmGNJCpp+Ha
LmRYmUZWUOHFPsHGz1NIS9T24ubgBOW7E0OvKH4ByeekXKeJrGnzXhpOlJ6csgzJoyI9c1jzVkeP
ykmqeQ3CZYiw6S9/SZS9VfLlpUuxMAMFg6nxiZl+9ntKD34PqitCoOiYTV3Q4+zenoKhDo/0rVLx
R4R6CUG+4TULxujDyGTFo7l7UjlQhhGOVcSbcULKoD65x2aJdymD+OSb4Vyhr4iyvYqYEuFPOh7k
XbUXIVX/PSEM9gfUsxx5WldGMAUeeGlPOvWXCGQjhZJocKjbIDAlezWxESN0WQMoqIj0d6upPQUp
WSidkFBricqgjRVZEGZVDSybIEQGgwP6Su4F6Dexn1LRvPnAXITeC13I4AgijYE6Bh8NWr1B4AFl
/Iie6RAjOK1vJRPQ+MQrKCoIb0J0YrbTfwp2tSvtmwKLZ9PeD4eAC4INDLnUy+6dS+8pRN5BR6gl
Tkbs16sUTOmBEkTcw2Xgg6jQjzZYX4AEHNVI4EHJj89gESP8lnKIwksVz8agEQz4wZ3BAOytxnOt
xhkZwxQAA4TYzPLERc/sXnakR3VkAzbojFE51ixFh/Pl/0s1qMLU2JhBlNp7qEPUvAQpDN1BXKDV
wYRgxMIqOGBDSAlCoV9jbMZa0EtusFBYFM9bXcWyFJBU1M3HeBiHSBC2vMDbnV0onYmCXd/UPJlN
3AapwBJOPFj5YUSVPSEYzo/UJIpZzdvSHKLi4EbrQFq9yIMfGMNTTItpTMudRQVGbQzI4I3uPBcK
bMKFAEORFIIqbM9A1YTT6QteLIqGXVIeFkYGUonjzcQsOqLqIMQi8lBMJMI/TFHpUNVOCNBPMFZ0
5NRPzIaFoNhWeAw0YgWxGYXHaMNSOFsW6JAV+g8XKsn5HYQXztNFCE2Tqd9iYFNGbE0uNgQq6KJS
cZ9BOP+U0lUEIiBEeJhfQQwjRhBJGILCZhAXcoBGbvjBSxHC8VWcDWjMaWBcoPgJx7hG8bieH1Re
Y4jVl5EJRUhJroHJPRwh73mVvCVEN37S0R0EX+GE9SnESFYVTHhhICoEGUQfRsiD08SEldiKrOCD
KVDEXymWzoRFIbQTs9yJAsENxiWFx0zBFmiIMolIIZAiLy2gOyrVaflkQXTkmDweTKTk9AVgmsnS
OmqeEWVEeoxMSnpgwaDlHR4URjqKvASF9LTeR5lGcmHc7egJ7rEd7EHFWvjDRP6DElqEP2CORRYM
PsiWrnyd82mG4jTmwaCSBlYER4SlY+rXqqjlkzTTIBb/xCiUYxJRFSltjTNQZEFUgzw+VNCghVjY
UFFgolIwxVZMg1N8yFagGLRQo1JyiDFYkISUD0Fh5oL9A2K2WwISycDBYkFIhmnFhGLEyj1sTemd
zuksgukAkTaAEpuMxwwxIEF0ZjB+5lR6pk2cAXWCIWjQCDitFKph2krZwSas1J7EHQpQw0epDDU4
pIb4Dmwoi40sn8AAZ0Y8g86kxM+F2mFkDWWOJdNxSWYwCZPcFkZGzl6UZ5IElEyCS+RoQyNIVdfw
G5YlqMBhmrv4A7wokpUcI/FwYt04kJVMQxxOwT8AE1Oi2NtlA1GKBDyGZ0EIqGNcGZHgZPado1YO
zkB4/wlpEp1YIul3Is5UJUll2AQs+CdGPMRgHiBVdRAWhc1oEIXr/IYNFoKkIJBCWshT3KdqnJHK
fFQWZENS3JKUFkYCxhKFOlarLCbpAdToxYTXFGbhEMRp5umsaIlGfErUic3prETWKGeCCgmAItFO
8IRuhA1KyMOOuZ3bVdCDRIUNFMKcYcU/ZMGs4KZTqEw2XOKdKE3BCAXDZAPm8FtI/EMoFCJB9AOO
mYVxds0FqoP0DWpjiEEPyISEfcRKbCbg3OKcEsRDiA0jMIIHUl5hOMMx6IqRrCQSjeOOCA2+5Joz
dBEwdFzJ3BmfyMZOoBGGuKC1uEJWnEZ1OSKrCsuspv8FNhWozUBEbenoTTQqRjBCK9yjfSiVS8iK
goFo+tEHvhLdQBjIUYVGi1yMNz2lH4wIVoBYFtTNMGGINgzTtMxVNB6SLz3sNtrrwFbT4nXoLYIh
tabjvUpgrrAS9iWp6SWEoEXhlPCp5GERaEiPJYkCnpyGmG7M61VLQ7IG30TFSN0Jdx6ijbgFCCqm
VFoo13gWVeUBPnKWLuIH6JwBIDrGto4NwtFsQ+QoQQRDlaxHzTrKonwPmGhDPDQjVNwmAsVN2jHF
P1zj/XWYpfZffqGPEqniS0JHcUpl5HClvlDrYHpJSQisq8RbR9AK6HGomgSM1wjswZ2KRliC1JAS
aEz/A3EF1/d000q1hhhJFx50gmy8xoeUjEaJHe9ACNoiBAei7EwUSYDMK+St1c/lV74EJkG9rkV4
xHBqXVgq1A/Naib9S6tm1a7KxHPGxCiMhDO45IVe0cX4g1WozW8FRR/sZjNqgStkS7aojGmsGIzi
FVboyd1mI/IlSk1gE+KmI9gOjo/+oUiMxEX0Ik2wYiPOxO9OoNQdbRGJjaGun/k1U1hSpj/ggWHE
mhLtVtGsziS+2AkmRffagDKZRp+Ib5qujEZJS1e07kEEHEPITycxhDS4QmG4yKjI4mQ6mXaA6MnS
IuzCm8FIzfvWBYEMZsF2ZQ0z6dQqxA4DTtikhXEa/+BXHCNYXJTcFMKmMgWHbIW2YMtdZYslvg2J
vClDcGUn4ccPA05x0gt+vDBTzUSwTlj/Zu2XSQ1FvilgtGsP26JBbHGs2ATvUmD6EKEmHU1bJE1S
KYfzTNQfnQYMWBxxvU2GWHC4wiDoit0gg0+iqMpD/YMTmmO78eBRHY1HBiPZVisRuWwMoxmAKcyR
ruN8CC4W5u85iKSTuYfVQK+pZW4foW04hUX2pliIgBjZcQVSPqxRUAhUEBPvNJcu0wX+IgQXqNp3
/kWB4emTtMos5kNRHQSU+eEt4kr78m86+mfpzVwZX6Wo7eHU8K5GgEM4sESO4u9KMAM4f20F4sTq
jP+Go9AQiWIXDbKgFiwXBVPwR73ANDDDNCRXIJMUMwKzK8AWWWofYFJhYPSKWHHgp8WiGoMs+jBJ
/qIZHMtEDvNXsQ5p/QQpg7oKmWyDB57nxQyxdEwTpJzTxNryh8mNXT1XhsRmh3lR/kFFNhACqg5p
Gw+GHk5yQdTkQSzeO1vegcWpwEDYEYHh1TnRrm5N3n5jRaTzwaBjE6XHHcAoKiNE421xxGyGFgjN
c4Sg7RQPahDCckGIPdfzC7ogUrCGMXzRhWAccZ2OVhe0QcTHPRCGvEpE+WxrcGWHz+EX7WIEUQfj
kf6Lrx011Qiv5Y1tAx5MYXPzPFpoNRfEPGC0QQD/4A7ZohhSAxgkDRcFFy/xX4eptC1X7DCJXTGd
9sNyxTQUAhNqHUHxy/fsFjXwY0p8nR9Odr819SdV6WLYQ3rIgUwASD/8x/IiBkG8KksKNaAWr0ZA
dU5jHUQUAr9JTQ4K1zt/9p78DgvSs2t61OvZQD+PEfC4HkkRV8543sBQ9+gx9ffo9UTodSWlsL14
hNdmpTcu90wIN/J2GZiU3p8udhkX5n3Ta8kit9ZA7UNpw7bOdir4VOxgI1Tgg8c0Bd0uBRPXTjYy
sQP18okJG6xhBBg3hC08Q2sRNFPjS3UViXG+1R34ZkTxtkts0mQ7dSlTzStlzV0IL8OQCfRB9oQJ
/wbEIaIPR/aCIfBD5UYqxvdsb4ZEULA9kzU1QLkW3Jls5LMYAU/JVNyjNIlCBFxldI9K7EJB7Nf1
XAyTC02TE0IT/PUly1BGJwR7x4L9KjXlHo10Z9WI39pOU2WZ3+97kHIdP94BE0QaSCtbkHSL2Jho
hJgWEMmHUfho3/KLnnbFPixWmJ2yKIfiyAoHzvXN8DeiuAmBRtQN8aOT/cXWfOwm80quCENRgyEs
KK4bO4RiOwRIJjYP56OuOEp8gwZ0YFye1A4hQPmUV3mVu+gLYvkmWPCaYtCjzASo21a7CRhvJ6+a
0LFQj8vRasRwwvqUKq06ItGBJQpaykXj4QTvFv94SHYlQXwGRcT3K7RTdVjTH0yBVFwMxI0MhYdY
99pfE7/AUjrFhWjvmqKYa7uigJMC+RBUAmpD00I0QuxvRTIiEjnUx94kNvVFaxUGB7K7TLiH9WiG
ZyjgsuxxbqRCt5avWSN7IEO5KywFlpfuQ/oBuibFHegQpzMfz3+ackjGzv/MV1+PteL5fB990N81
ZVwPR1DSTnjwwIG8XexpM0nDrRcMPKLSnvepEnnJfp3OK7zqsdZFaHrfc4Ic9bb4Z6tN27YNiLm9
o39YMS1lU2oBm34YV0gDM1rq27WL34vF3wvHOgH+ahJ+u0AcHBk+4c97M9DIetAIvOhGO22bddn/
h5TpN7J6WY1vcydNEWV0/HucBJaUlpFYvdXfxLFeRB4eKTVEaQ3REH7NDs9Khd6nAgX/EiFMC7pa
+WqsibIXrSvoyTxjUCBhT1twlgGqRbzWy+qdy1o0yj9YvfEjP2ty1nexnvGjOrI6X2ZcNEaYZjcH
2OFABFQfw9YXzDCLeNY2k6uo/hVpg+snLITPDopV+Ra4ArH1sqk+ey8vCYjJJkC80JLFT5ZU0gr5
aaYwlbZ/DyFCxBeRYkWKEylmo/Zw2j+N/6r98/dvI0R/JR82KznSIkpqLzf662jRoUWbN3H+S1eR
Zc6b1bLd7MlzJsR7PpEmVZpT5tKiIns+/Vfo/6G0m0EhVnNGUerSpTBf+vsDUyU1fKkW+nlBCAYh
P9JeTIk7d0pdutOmwFDr51VdP1MIpfKDyo8fQqhSbXQJkdpRkowhP1ws+eFHjpEfU/43bfJmzIun
pZo20rJXlF4p7ozYNSLGm/ms/nOd1FXFabNR59YtEuc0rKsjDpVKCCLroZqB7845rd9DfC9JqgJL
Ld/zwlO2+EmVqpArLVO0CJzy97sWFOXBgxc/cEufhAcT3kuM07HXoc2D+2TZFDW+5w/xw+m4iupT
zqSc8inQoo4UrCgfiloJsLV/JDTQQp9OW62orqJ6KCSbZhvwlQEHOfBCDWFKjBqZwnKGmlTcQv/h
he22kwYFteTK8QUZ5eJRoLhskEsLG+55oaDCCGFmuxMf8mdAr3BjzafQMsSpJopGGg03AytcEKds
pLxpowYhio3JM9G8zKKeXHvyphKbTJOkFB/jTDFqjCkkCy1SeWU7QrLYM4stBNKCUC0GyWLHKRT9
rlFDpzmSoCwKGa1KOZVykzekXpoPqY6uPLCZZjatSB6kJoGoS5vINBGpkVjaEtOvZkUqJFglqtXA
F3lVkbM5YfQDhSkE22s8I+mqa7xBcoRBRyELW2i8KbSZRppUMstWU+U66zaykz6DTEVpzLRptGla
xRK3dZBCY7N0ccJHKni/DTOpD9OUFdMnn4H/is04dVUqFuemg+nXTlPpo7BUCCpMYYLG04K89MLT
wmKKX2jvHvAI0YagPl4JNeB/RNltW4leHAkfekUabal4aLrJ3pzwOfmmbQBWbuA0h3oQzd/cbDO/
3X6r6NJSB4SFsYKn286PQgCzISFAoXYrocL+OvJYHXEs7IVpjByPUlFQ0ldNC0WRZuabzI4osd/u
WVlmAF+OSJuiuTJw7ZyOHllAn/DVDZucL1rTZitzK9pNarQpuBlt4nnJz4LKs8FR8RplVNC9Ap1U
0oU9x/qVsrGk6J7DzZ1mb49CXX3OxjN9VUqReRaKdgMNafK0ojxJxsK+szrRzViLwzlepnLj/49w
yZ5jWrGzBJNYYkIsh6FigSynKy4UfHx22qyvCww62Xgi0O/kclrGuVSMAd58L33DiRl7drtnZtdd
GVwy9y06xCbU33e+NQ1QIk7ySdtKFZFs6E9KQanPk2Ayp45EkBp+gtF7CLEFQ21Qgx1Uz7C+MywZ
lec2YvODwiJFiGa8YmgCRCDLqmKSVBxjKa3qB3P+ZyGbaaMfMAyYDyNSn9u5bmT+aFszSqacci2I
JWRiGklO8qJUSC1Y0qvekLCYPSFpTy72O5KRCBIpSvlhdwLEDAH/cbsFecomYAIT3bz0jwbx70J4
MyMd6eOqIPoDiGa0SB/nhrwEPoaCL/lPp/8SkpBX+GELGWQkBznIKENNYRrNsNieNIg1z02qENhK
kx3/lsPlCciQZyoQAJPCGjXmxHir0s0pfGLH+ghEKET0Y5qeIqUtmQUmzeMlsFLBDOrxiRqG8cOQ
2KKFFmiBBRVzVpCs14xpWO+YbQkfYKY1vmwZaFv2uAfj/jG4k62SIhuxEwJR4xg8OgWNubFlRDK0
xDjmpjkFikZObuiVwN1EHujMCTtQA8CJrCiCAyXJK0JDiIS8KCFb4A4kNYie8GwBO9jhoEILM0bR
+MOTtdOPNsRpEWcgI41KqZnLLLJPr7jSQKBEpUVYqhzVWQSUn7IILNO0TgPRcCk90VQ6ijH/J5iw
aCWi4Q6NpkbGY17RcloE0hSCZDlXyOVqEKPGNBKiEjm5ThsD6gk5ebIdnQrQjjNxBk9f2sZ9SQUQ
2+pqRWKaG7A+JBGtCFi/2mmikzGuaR3biDbk4yc/8Sk7Dk2FxWzQwQ0qCi+PyoINpmEo7XTOH09j
yFhvcrozDWgUGIriLW2at63WaqabyYYe/vfO3GAWU374h+8sIiszaYqXYBEqSaBnTLfsVreuoB5v
tYAKvGxxi66wJvgW4hY2svYigAxlRDiBE3NqE7S20RWH5srNrkoFW9lwk3Ore0CKuHYebLMuUpp3
WwouMmGKtVgHp6FYim7BO31gTx/k6wqH/+rpgtpRYUfDe6FYXTXANH3VUcAQ0PLVClasQcVyCswk
lL6qIvIU00uWQcEoBmtqlLKBW7RgPRu4IhFDmoJ3uMhF7xzzaYB5Go0ifCH8JKYoJI0wEROslLjq
yh81fW6M/ZjWO1Ejw4QElmBf3N9CRPJQlNwTo17ACCj/ZU8DwZoKLyteIGcWWKeB7YJNVq1Uzgq8
edUxPU/EQojMw8ZbhitqfmkWjRQyMTCCEQy2I5/AhBiLzvraMbcnF0PMhc9h+wshxqOdjjJXKYw+
m7n+oSIt62YaNbGwAFULad2klUnZLWeAfRyvsCjGyNpYpFnY26fRaOEVWqBGJPGyhT2th/9ij1yk
MQ2iMDLqB8jeFcpzUmGzMkPYjKjcwptHiZQ2+yS7vrhJKpR2oWj7ZNgLzrR6o1gSbdAoFfgIzHY0
Ip/tFELEWsCLQAD9rLVIzZjfsRpgjOFmpZQ2Iv0Qa04AuTZ6o2YRfgsDTS+dlGULMifOVpWcSkEK
n6RCFGmt9oULqZjGLdKC+KhUNviiBXzw6ZFbiC+UtVEFRWnwUR18GkG4YwzBeMoWjPBbPz7kj7e6
035yFKqjbaKNVQYoH5hVs7zlhNmaV3fo86YIM3blPOhwJlhOo0Y2Wn1YPyTUcs0gRFz0Mo0qxEU9
UM0L9b6uW8N0GzktwxRWquFTRk8w0mz/XIozEChm0QKd7pwusC0VBA8P6Sa9pPZ7qvmbjcJuUBsZ
5BMhwjN1PZVHPPO12PT0RA33tO9oRhwtchwy8zXVDDezecXPz+4T0NOd9AU23qe9ki6VckrpG7aa
YV4BNYklZEiLsIEfpKaXLPjj9hDDUV2qp1xjRsvtHtGj3XZjpqKsnSL3xnRFRo+T03uG4KW3PkRO
daKtmC6NON/fUAuWGLdMKhsGMXwmJQbly60fyo7X4K3H2MnRZQR9FNFGqpTDEk+znroBC3VSTs/u
dAOzRmP/ri/7Ckento/7TsSXCgaYdOsVeGuYrEcg/CxHRGgKhuVrtMcP9MLF3KIZPOUl/6SiNtoI
/+Sq7CwCDIiDUyJNzP7PQlbvvBqNb9CkI/CgEz6q7nKivChMANFkKAYq28hHMTgKT16hfY7qLDzI
gxAPhATiPDRQGhLvYqzsYwpjfHClOMgn534MRHIClOwFoXrMImihIlCQZ0AJ7hBHlCwkn67vU9Bp
4OKQ+pZmOoSKo8Zt7GgvspqKz5xqCppBA3sk0KJqSLIGYtyC1GjwJlaJf2wGb2YG3G5CESzvIVxu
0szM+Oau+krHQNRmQhpwNh4utIAufyxk+VRkOhon25phUrJgGiTQ4yIqsTbIUSJL/dTPUDKmIHpP
kwphIq5NKE4EJeyFqOZqeORodVRBx//8iSI6qyXSahhlByNUKxt0rscM8EQqLVdSsSL+QOE6sZye
YxSU7ixeJGteYNvcYhquyAKvR92mIAy87plYLfFczBi0g+1MqW1WojfqDyIWgRAm4ixgx51W4x4C
7iGiESGRIrpaY0N85iHipgEVTFVK0Yw45BkDCd/mxqBIDSQRiqEKQwtk4rAiy4MezwoxRgvQ4L0s
yh8kxr/eo6OAsIAmAnUWp4UoAg8i4vM2rSLijn52gxpj0EDkpSOHhkEWEinYwQfDi0yOcm8KZCKL
45uggwShCGFoRC06iRqYqhDmAkdS7FmuyA+ygVgsixBULinMYkqEJikGZJ2aACKczyb/9K4iWicp
e8Mf3gG0mmEUjnJWhsLXiuOGjmMbSy+7hM1BKqwfhsohSK3OkGzJSHLJGmpQNLPKdDFzMOmiFimR
AOwq7kbmaEZW5IYYz8gjbAYsksgmiFKP8GHHqFHAAqwr3kgaYnMcw8v75oojpeslwOSqmCZYyOOZ
rqrPTMwulIXr/mKLAFFZsGm37s37giiIgLMR40WsHgwh7+fGCkxWsiEbLk0xmSStBtMT9dJJZC5o
WpGCVOIk3kNhJOZcZCKieFGiwCMLwEAKGe875qthDCOrsKU7JcwzstNAyLALk0c95eQmlRIiGEHm
DPBJamoj0lNOEjR+uJFbsjKKRmF0/2QiDFoMqiQmeiznNkRM3Xik0lxUG+IiD7hGEbWjgpxDwmoT
NcRqGO1lx2yD08YzN9Ll0qYNU9rmGcQRNXooIrpzeNJlGdSHJzKUPprSJvjKtkiQoxIiDAQDPF6s
1WrRPyKqM6XQM1+AFCRmkwpioXDIG71CKnLUNBLDPHlsI1ZhFZbCMFXTTWfFKn2CpzDlHqL0H1xr
kBjwTQOqEKKvSsspKz8ULMYO0fJiOwAxxGSAqaKTiyzmArEHa6bFWraJQdnJKOI0KdDROs+TIqbv
2L4xIkjlQo6iGHZCeZYCHxAQUwArQDTlVovoITTPJDRFJlgi4tSLOFNhFPBgvzYITP9lQL4i6T+n
YMnmK2O89IJikRmY61ImbFsGtQFfZKt8FMxsQgwoohMuISny4CHUYEBqJieSoRTUc8JcEDWizyds
ISApglcrohpQlfoAK7VaE0tHre22wy9eZEjIbZj+sNzK8kdCrC6Q6cpeLCeasSX29EnPxCHu8kJA
dWT6iAoeYg1sTiIS9I+C0IAQaBiHoiFBS2WO4zVdEPyigxq24UUIwU86SazOLzEgCpLM9L0yxtz4
hDsaRgT7z2guUoBsyw6L8nyqzTEsT0HMMyOZyDrXhmXhyUJ+oyM0hS8h4g4azQEnCB/+YE7GzqhG
4U9E7NuqR0ieiUW/hmGlARXcAkn/FC1UDdU+/Ibt7q1U99ZCStZv0etAM6VdIWL6Ng0rsPF/Shae
Ru0/niMoVoSMCKGy+quRsuOwsuOECkO+KmoYhFYlDcUV+ksE65VpR6Zxf4MM4bQf4DUpFrdWWPXR
/OjhiGg2nMAnUeON0MtwLVKB/kEangQ3spVXGqNTGueqAGVjvsjrDvFtg6RhzUF7nOn1lCvYNC04
fJfXkqIf8jLZLMJMxAqUTuu6vnB27045wlVUy2xKHfFnxNUk9mb5kpcEX6I0T6cwxOhIBiJoh4Si
ONNMuQcfFuVnTehpjOF083aBs3eAthAidG5K7tBeglROQg1CdaV9N3E2OgJdxgx1/5WDTke1cJ6i
C+KIl7bNUYONBEWjLooFHjG1LaLXbeUCHzYwPHJkqpwz0QIjVBl1RdpJcEVrIzZW9ChifVHPDUtv
3z643kzVNJNCszpNV8zGNSbChGnwOeyEkF4iGGqm2yhpO+yrZzsoFQjlLzyIgNEjDOzrBdLyOziX
IFTIwDj2+DoUIoDSNOxYLj0SaYEMDikseEVVkE1KXldjPH3KJxJBKXyMUZMCFm6hgfkmhf1OGyyB
V5jBWlQnUoZERf6wbUeBPOYCGDbBHzZBLtQiPLLBcrCmMNoSNQKOg8H3f1iriB0Zg+fJ/oDsnWQO
iT2xxzhtFmInl2eFI8Ev2zbMEP/+QCy1g70ciSSclaJUgSB4kYxM2RgC5fGygBo6aPcsS6tWSok9
A5f5JoKc+B+y4JaoVtrQ5Bj0dFYM2WJjSAUxROf2Jhh3BjWeYlQoAhai7ZfshBrAQBHuJDSuw2ZZ
mU8qtdw+MEemwRg2gZShMy4iCxUqizqPFiB5AogLJ2CIuPgiYgrqcKvWydNelTCDYm9KQkJm8Atx
Ahby+eBoBkoGdsi6TKESSoM0l4wNZVAyRhv8YBOMAQWGWgvw6/EI5TYwaP72eBzNhpyx7yZeQXi5
jAcz2CbyAa8gOMJ6ojmKJkwcOUIdEvk89Im4siuX7PUQttw+zPcI4pQ3QVhyhFr/6OKqXEwEe+Ie
WGZvnjFJkwJQK+IgjiYkhNgmUEGB5dkmtOBCMEIa9EcooLqp/wHpZGZAugIe9O4pErRfHwIQvGK7
hrV+wQJ2Kog7tMOydppybPGYMklNfyEL4rpzpq4gKOokLYupmwhC/Wl+8PRCzFmswzMiDOHfQvp3
JUESjHiz0idrSZUoGnid7LMoQvFN9bqzEdKNOsV4p8Mwvmc82jZ6TexHUPkFhhoYiLosh2s8EM0P
REF8xiQilaNxm1giipiYjU5DQViCw9cVumRmhHGrmaQWLhFR12QmtuFeaZdoKNsmzJUnyER345cL
CQYP16tLXc0fFApiwgNGHC+V/6fAGFLAGD6cqM9DCmXEHyjmYQb0vc9EvpniaPKYK2RCQsBLhPEp
v/vYJiqkbXrCfZlNfSV5SqpF7jT6pEeWE5cCwrFkZrJbwxAmC+TlegsCYrUjqsitICAaxIeaEE95
LNdxLE1oEzJa3m4DJ+obDFHDxjV6b6avsD3qzR8UphKcmxYHLMDF7xjKSEybGsYvGP3E5GQtqLXg
FyB60LPgPH4BBaoscz7HINLKH8Cg386HyX/7eHSDThdQ07pC0iFjne3bjxhzzqUrwoeIkOH8+15k
ESjcZu1CrO7s8JoBH6ApvGWEGZihSFBgE3JdRyomSFbMbsecic4Ep7jXXKCnSv8GxNOT4hT6IKBs
lDfzb0VaJ7I/OyfeqonyzwsrohN8GSnDot82QiS1YzyC7WY7Tha7LbJ6+i/68zvs5x5+wTzQo4O+
ZiZhRAQZOU3CGp846jiGd6TF+UyqY6yFR5+3xIB243Z08ELmwQftpcmzLUXqllryxM6ElpWLRWyM
4QvUAqJ7JKJ13WHpwjDGZjSBO7YI04MtIhV4lzVXvmkLbCRaOt9hHiLAhDkqWKaC0isyXTf6YZGJ
RrpEW+IUA2dfgKNMV9U0qJMcanPfmspKfKhRgNAFgiAsx6Ja2U+C41x2w8VxApBh6ljT9ThcowV1
o+X1to6t08cpsnRYwyr4dSn/1NwrjLw3GgjocyPgauscnQ4wuE3sAsMtgKGVNwEvSFktfqHLwef3
Dg0wRAGk4xsnZv5T5vJUcVzUPfomwrqwaTYiijRTnu4fAKpM8JuBYybIE0dCsovSR4dYWRijrA6D
FKa/jME9sqD238IPfuFIdj8L4KH34/iEIgX2TF43Aucos8FHgdlXF+RbAf5sYprM6SOlH2L0A8aW
3NfTClVOVtF5nCZrIsWECK0sUaFHRIh7NJAZNlAuwOYvpAG1I4JXfWP+fWLa/i/nd9c2ztz6uPYf
EHe5AeKfwIEECxo8iLDgNH8J/2VrCLEhs4YMI/6rNlCbRYLSsFkU9a/ixob4//yVLEktpb+ULFOm
IuTnhZYsfqYZo+mnZhYtW3hq0TIFxaZ7U7LInGLsqFGgS6U19UMzFcF8IxGK1Fg1K9aB0vClzAo2
LMR+A0UmVLWK4DKxbNu6nZhw2ka5AumCnWYX4Va3A6l5pZaqpdd/Lgm9mPIiZ6tBqRpPmdJMiw1C
MCRrSTzFyuHDm1AkRoEY8eVpm/2g8jOFEDW3pAbazUuSr9/GqxtK44tbb9Zp1BbCZms2d9vaEX9b
DSl2ocXgBe9lXf135VeWK1/lnDIzlbFCfqgRso6PZ6qe5H/FtIJ9E9CYQNvzRPUTqh9pfqROI4sQ
f8Jn2wY+rEpcW/i8olx+xv8Jh9teCI70n0X4DDQKWw3641xBAbrFEHNz4XagQfjc82BfLU3HUmOp
XEaIMajlRNsg91SWSgs2WAbaC8Yw41loNog2IwzTzGgDNTg1UxteCOWloEC3uLZgRA/ShlCFTbY1
zT23CXQhgtT402FCGpYlUIRgOQfbPSZNyVCWCTXYZVVSIhSiQdRoM2JKdLb0yk9ZpHIdd6+kUsgg
+KSSZ0+WTTENM8YUJZNPP0nW005b+MFlIVIVt2A1VOX24CuwrGbLlKL+c1+buPmDalVfDhRnVf8Z
mduqTG5YF1t5vXlQqwT5VWedgfGZmiiGTVFZj5bB0JgWMCA2TWUybRaaTMX/KqvFdYRMQ+RAqiR0
pVu6NqRmQoO+Uhsso4ql4TMGwYLRuaoeJ5CsB5m10LdhyYscRHRVZKpB7ea7HEkkrsYSYQQCVogx
3rWH3Qs95UmNo49u0Qd52F38E3k8TbEFTX1YWtC/wpmFb0QmBQfYQbA9Y+9ILUN0BkLqihoqhke6
ZqVF0zToH6kGZSNNv2CWlVfJDyWpm78ElexzQr2ydM80gwLGJyGATpFTtTAVMtmJfhBiA3thFyva
ZpY9u14W3GU7Ks/nBpYlbM60heuWBhkXhrsEYbQIWDktrXJYB+rHF79MH0R4Ww/hiqtAjVvYknQF
s1TINNxB9VLHmvtkKKNM/ykF+udM0UQ6bU3ggWW4G7ktNFsl/fPnan8QlNfLFuH6MtINPU5r4QaJ
RAgYjt8VF0QBtsml461zZKvy/zx4690RPQ1Yid9hPUoNRomtBR5+9BitaMtC+0KOoKES/mNYf636
vVm5nZVzq0GZB0EN2l6Qhqu0hqW+hzcdtZEsT18OalI2NgWvpkUkcbs5SH+c0b573OMhX2Lg9CBI
mOpRhxp/0kYf5KO2+vAED6KYmE/wMhOLAcUzDNOCKy7THtL9bV7uayBfvJIK5tAFfwVREO9M5qb/
/QM/s8AN/KS3kWAcBH7ZaF+8AIaQbYjMNYcbIEHIEsCbgYUao2gJ3DKYiv9s4AQYxuATn7jDJxjO
yA9amAa1gCSZaMGQCpfRkXy+1oxcheWIDbFiQqC0qx9SxCEO6VYNwaK7hCSCL9qYRiL7eJBjGOSR
SKzLSbLCw+cRxncQEeTv5uQrOmUwG5jzA3csVQgt/KExfviTxn6kMUNNYwsce0EnfnKULTiMdAm7
UIYOuZFEUlJOgaGdhg7XD0+KqiLwQEge+AccGoZlmANphiQxxREh2nA4TvyHMueGpb/4CoxVM8aw
6oOaUZioR9pYo2Qoc6w2UusFeViWsS4GE9Uo5Il668vMarWR2RQToANh19AEwoOD1CYbdHGGmJY5
tGIIBzbGCZrJqJm0/Hj/yV3zYEdCTtHPgSDweV/5SwYJdjBCNMMP2piCpVIxy8BooVDaiCXnODfL
m2aMY3sihKUuhJVvYRQsDwKnz/xAEElIQlwpI6iXRNIDePHMLKh4RcAuCkXhZKMiSerH8rIx1IJk
Ax+/4aNAMsmXN4lkLSG9Bxkg50VqiEI6rCzEHQiRhWnUhzcnkgkbbeAPsslkRi+gwo6ANAUCvSIb
L9wRDHKytktZxKxXlWZG/oHUkQBSgA1RRSFmpcCqvOaRe2EIIRa0l/uEtCDvoBBoLbvaJpXsHolI
h4g2+BVJugQqooDKNGAKmFcUxQ821WUsOcYTQtgUKOTByUu6KRDKbuRM//kziCq2BaCB6g2tFnpi
8jaiBdSOSrIRgYddDBlb46VXTtQj2KBSgbWX+PS3JoInG6d1ivC9gDRlC9+OjlKTnDSDvA0Ja2wI
YohDGKQKIxGoH8MSouWJhGncdUi/DPw/AkfkPxZcL2wHOSXcSmVyVPtYTrKgjawt1yeuaBjD8KLL
Frp4Co2ECnega2AqERUw2owmc464L4E8khH8nKzuKhwliBSCyGLpcFY9XGSIVOQVNSMIiIr3DyYz
6WnSKBGwdkST/dIkMuAb7NniaGZ76hdR2iiNK7ClM4HI45oj+Vp0e6dZmG6TLUmi6BITYgwtc7K6
YzkoW9rXY+HEYopsUf/mhxSCF7o0YmmgHFFgeOMSNJoyJ02oSRpt0DFJ/WRGWohYe0A9k0bBcBpL
yate7wDd3Aw1yBbpTawNLRb4OXkjefxzVoKDFY04w3YPPgijxbrRA4fUicrkyjQMaRxM+4oazPgL
K/OJqCaALZ/31dq0fGSsGaGCNMoi9/imgbX4GqQZD4Vy05w4G3yY69fvm6xbGC1dOP2Ms7gBaQ+F
g+RoXiQ3u5YSpjPIG5NKG1DdCaMfBpXKLXwnMMq9aU+0wTlp0PIy2cAYTzx2Y3d/eCNekUt/YuUP
bZgl36ENC1ARxJyR0i43/t5VopF4c2wiqEtmSYm0CUZXwKCCClNojCv/7mFKZ730RCeCY49+ZJn/
ImoKcDxMCAcc58laFCGoAzFYNtsQclXWfnORuYSapIjPivyyNss54mYuFnuZqiItkcvkTkoNNroU
05bqSSojViieuBG5xd2YoWaiJ8zpM+t86XqyAWc87eLmW/Czl9rXruNaV8XsCLk1rnHTLVNJVxtg
1YZGlDkNWnSl7icljLXBpgWYOlYyyfLaaNworbOx0Fn9Vd+KvqbhJMupSXYjNJzAnhBqXmhnejSI
ITDPlyNyye27BiZumnlECiIbXQ15RD+iQ2KCUW2mDY8xcoNbanna1B8X0xhzeeKw9X2tlyM5pmgh
b/zsVuQPgHg8vwMH/2W+0XJtsUh1ARs5pkXQdxAShWU9w3jdlR8PATd1skkpsRPAdzlhMxnhFkeO
xWZS9yxrVho0kRrBxzys4kCrIS9F03kJYQl/JHlrAkWPFlC0U2xwBxZup3NCxiH9gAzJsDeyhSAY
EWl39n/5F110Vz2o0BKiRDmUogWXc2KGgmoaYxRbMEtHwUKeUxQoIDpFsRB+0Gu24R9fAmyV5E0j
RxBKhBCxQxCzk0AEgQ9o1Srf0i+q9XniwnbnYkj/Q2Vi1S3otSABp0lwUiDMpzJfMnd2wSspgQ+q
8SuOWBh69TXXIT5nJnVl5hksRD6hUSOPgRpkxRC8wS2NNEmqkw36kf8XN+ghyJdZS5MqE2UQnpRF
+1RA/zBMzbY7vxMW4cVArCgheCiHNBSLy6FyHpKHT/QgXmFVPtcSJKVX2PFbMOGFXkhcFZcxJrRx
MuGFG4N4XrgTDeMHH9QdQ2QcW1ISVgQbFEIWOlgQf8KDv0NBxYggthAq1bdr7oiDOQgwK4GLYhFe
bVF9AsRyUyI1WyIXZqhJJWJp/miBQUFfNpAjLwATsQdDvLeB+lVHiVEa0EKCASQNhCM1raMmdOFV
nsR5eVYbAbJVybhzbtEvhBIRghhM+IcuwDiAGZFyvIgbnmAVnsdZhLAIcTUiFQgVQIFGYZaNkaIU
PrEUKLAUqaYFKMD/QlnQalDxiASSk9MFgLjxfJvUhjHoD1M1EAOZHAooEGb5CAXYP00CK83zO0jT
CvHIGnfDNP1CHKtxkL0SiY3YW4fBSnwykVajBfn1iSDoD51IPjGBGCtSgnQBmUGzdYKTFbGQEF85
gPMTg5Dkf2XZEC/gVHMhQbW4IMhQg/0kL1aFhjNZFpREjy75ZMJHbwj3jOFHDb9AlY3xCqKwKKiR
Ma4wjr6JHeEIFLgIQxgzY2mTE3YhLz+mIWZpECcXFn+iIWz5LgNxDwM5BWh5EECoJFXmYQxBZweh
mgWROP9TkDYJl4fWXuJ3Nesjf1hzGFPgCtCCe4gxkVOwJeXDn/jZ/4lYYwxn1Sa8Q3pWJjW2eBCq
gJm1diHIJxBesEen1yYIiHmEGCv/IA9A5HUH5XauxRck2V2VRpTT8QoyRBPVEo5Q6RTswWqgZpWN
EpWJ+YVLURSkY1V0ZxVXlpOmd6C/M4YCIZ1Z4VUG4Yb8SBAFKowbyos4yZ1tIRK7BhtboiZBihUN
IkhfMlbT0xdbiiV0kZdcWoFh6hKSyJCNCCw5AVmVKBrw4SzaYE9vpCN4IYLRsiL2UVBxIUFbaXoK
BXq/oZlA2ZZdCRGPVCUux6TcKRIsqJ4F8TpPZha6WF3OkZ4JgR8PAh2bFCeZyioc1HoFY6neYR3j
iEY+1Sg9ERKp9P9+5NEoGKcF2rCFLZQYH5QFnmcmsamGNekfHTIgwWcmZoIKozJM0FkXqKKPw7N2
CpIX+lEyr2mEaahvgWqEETapyIajBCOm8WKt89NeGZQTnYBXopF0orElHFh1VNdOiJGYIshqqJEi
WwmAaCUraEAEvlYQNCkQYGeZBFGeU0JJpFgV9ghhgko8syll5tmsuVZZ+DKpAcIc2Xqt2Ro5RSml
haA2nYAMwjAf0wCcpmSR5rdiGEdLRuEP8PeF65oFeXQ4E8aVGzGXiUSTHCR58xZSJbOObfWhRBUW
90ChI9UhgOo0fREieUlWrudeRUu0Rzsi1iZOr/cSXyN1YeQKFdn/DJdoLPtVLPxFWOmDGuhGCA9C
oS6zEZNZFT/VpGh4nqMCqc8jd1r6WiGxrBe6bBDoMw5rqWFatyQWBpJDUhA7cYDROaPwcJbzE/eg
MdyxcY7CDO5HslgjQ/XxD39QrG2BgLsauWhyRdsnhJpnqzlZIGAZmiHxtdfpYUAHShXokKbbXqnA
CNpalIWAMJVIBD0ANohhIi8hE5HhV8NyGP9FboS1kVpwGiTYrlRQuenloLnBVmAhiPxiIaF7O/bK
k4FDFwUqRAqCZM0AjNVwclvhjl/qsOL3vXVyJxMoov9QCIoFFYlhSn7FJ3kiKfcAKcSlakdBGiGr
FHjRuJcXd9BX/z2iUnNVkaF+trl7lrn1KmRyESdX2rNoWXwtaHdAG05Gm7TtyZfiJBirEbVfM58w
wa6VuCJ6tVL/BUMhyAxrJlynkW6Oe7BH6CRzWBvYVYgQEaT9A3Y3qA0zbKwFcQ4HkaH/sLw757MW
oR/VYJmMGL1DKmQqG70aqjcrCKaXCsV726kD8zRTfKm84VM5QY6V6DHr8UF61QfrgR0+sRJlfBRt
NI4zEZx7ssJR4qFtW5mfCxG6QmCHyqgHscPu1gwVkQaY2zv+AL3/EAlnRcgDgQzzUCWvETVIExyP
0w/TKiAUEaWnC74tcQ/TFol9mRJ+MAiuUJRywScn1sGFkBrLif8Y98AMcho2h+Es3SM+jClmoEiC
fhCg/7g7vJO2AiENb5LIVdEq1sokLWOh7moRwxTInIkGOFNsZuUPtdAcAoTEKHjH5gnJEfFPQror
Ylon0rFwZapBllYfLAFWdmcdFEuxL3FKpoRiWXAP8XeFiBcpp7AFd3CFL6oNJiofPnUqOvaWt6Ov
wdG507yeiLRAAjcQPZyk99cQDDWpcmEc39I4diwQ18y2hFEh2ToYVTJt3ZzJtka+aEq+pti0hKA+
fIIXVvM9Muq7VTsFZ3AKIFhupZHCpfzE65UzEEYbbvMtQewWlGRUC9LDA700LblNBTnM/UQN/RDF
CHlSQUcNUeP/zVVyD7HTEj41YpTsHZfjXF/MJeHxE6gahSKUMWjgsT/hYrIKQgRWvHMxDelgW2BB
nb9hFi3TNxYRkkeadWZoVMIqKu22xJTpgE06rd+r1JamQefQ0SZyD7X70bThiPsCKE1LyrBcLUgH
Q1+Dbk57GecKLeWKGfKRGrVMKm/7HBbxq2LRGAcSIi8jPAWRDz8tsHByNMNKhmWrngBt2xtxC0vC
ct6rzZVGLinBCyVCLn+y2H+C3COWd1R9J2ZCDefMcKixFH9FHsQFv6i2FG40I0UhT4jHuCBkY2lZ
fwSrL1ZVCDLLoGHUmXCLhFEmcr1qy3OMRAj0XQLxo3KcHBJN/6/D1z8SbMFxldhU0xhL99FFR77L
2FvAVzWokXt+JRn44LSw3FLRwl+PNZ+O2cFzOxDDtlEpOxK5PBBfpIcIgjQHEmu94byDyiWk+az/
JnMiEQ7NB8eqshD/I6zbMK2WygwQW3cM2ZexQyjk+w9BvpAi4lNllMXwFR/VEnvKRVxM7puYMRPo
9ijIKR+yaoIFO5YwF3dNtYez2BB83d50mV4grl4DYVX9LBAxLrBtAq9EfRBp4cNVUQ2D7Q8S9TQB
zth7XiLsCjf+eK+FsAkpYkbXgaYnNk+XQdm7y1+KGRpZAIqv6Mszvpqy+XVf8eXGVNtxoSFpK2ij
csxuIVlFeP8Q4IkriNjiG5YQcr5Hmvvb3kwoMBtcQQ7kVF09Qp466kyxd6Q5pGOVbFTPnaNLbkSj
NAraMRHeYhW5zeYcVyAW/YvXR5yA+ZNIA/TpUzK0uNF/YlHXnDniO4jUQTsYvIJ3Y5rYe94YA9YS
LDLBQ47h6QYTj4FtllGJFfkY46MsVBctoKE+1rE+QWs/1XwQzC4QVvAcU/Nyz4wcdgHD620QYgt9
/ioQpyUW0NQWroAQ8BPUrrJarP6lvFnJY8pBfFXrqTBgtr4Q34FUd0cNzeBTeyJD21EfKl/d6CxC
qEEeqHC42xicWLMzKpzxHVpN3/7sAU3mzrrwAnFscSHmBtH/Cav1JovAVt5Z6QuC8Rux8RGxJIQE
7vzdEBT96gB+67fO2KLg2L0BXxS4JVezNY/xApayNS9hA9wRT5kIvGg2E405y7Ms2v103/tbEF9E
rHFYvY10eqHeEE/vLg59pHQxDw2o0HoDC+hNEFv/93/tOp5rrZh2JyMKU7QOBlYTNeRCJ/6gNnDj
hNx6RqKMTtWSSqJGBQ4jlfHhRsaVBdkgEzL03VSwZPrS9CFRYfBYyK/Vc3cSMNkOk07GCDFDEBZf
sMAB0GuNnWiZSUddK987tI0o9oGRBgLO2LvMV/TV7ib/EusDE8Di4IfxNTAQ+xrJ4KcsXBz57jlR
M+3D0HcB/+ilLSL/ABe9AUaYDhD/BA4cKG3avYEHpxFk2NDhGYcRB46SSBBfRYzT/DVciNGjR4QV
O34kWVLiSJMNNxKk9g9fv5Yx/1GjWVMVtVTU0uB8lTNVz5otp/nJEtTlTGqEXuHTMsWPn1SECmXZ
oqWqFi2FnmKd0hSrlj5buqLwIy1b1yxgifrp42dTqosp5UbcBgtjXIH+aC7jOa3mq5Ir5zpEM1iu
P8ES8Ro23O8kSsaROUr2t4ohtXsyqekNitOzz1TT8KVKJYp0zVRPT+dsKTBVoVT/skx58XTKFEJ+
CtnQ8kKLn9y9aU+BQfu3nxdTUPmZNmVo7a6/nfr5aOqU5P9/96QldrgsFFLQ00iPT6WNNU3sjFun
j+gPMnv4DLnHpz831mTNMzkHPf8Trl//alKts5heyUKrLHybIos7fnvlNy2yONAqqhbEKgvkmvID
labc0xC6tbIwZr36GgqpoZh48g+onzTKSZv9ZqpovvpOLJEyjXIcDJXYSHoPsIFWsazE9+rLRkaB
FooJnyUJ9OkznMjzjCbcaGItrqeAS25LP3Ary6muaoMBuS6Ru422Ll15YZpXygQRzKfiWo9E9lrz
i8koydNTytBS0YtJJD06kqFtTNLmo3uKFIhOhg41DJWBBp3LoBsJArI9xmw8SlH2aBToohRD5Yy1
V/yiBqj/mvzJoiekNkuxD61CZKvL5qbyg6sIt0irrbQw1GKatpzCcFdZs4DLME8dSjE0Nn1CFShY
qNFIpn+S/ee+iDidzKGNqHEGO3y488dRuS61VqJ+tK1027ney0bdlKaBNy+W9HMSSvHGC6pLQjrL
KzVh+T2wLAxh6E0LGwixQStCZrs1uTEXvg1Dp0CkGBjqMKpLIsQG2kivQ6zckzR5oTyPUZKwdUje
jxQ9tDDJ8NGUoGnIJcmZkeZlaOZ106NzZscCZUwj9WSkRpt7aTL1lUWQpsYPVJE2+pVNnirEmLWg
kqYQMNNKDeFCIqxNwl5DlLDYEEfEzkp/8Cn1kHxRk9tU/6Hpc0zSkwQKut4hzk0IU/ZYzqdnQQkn
KDF3aTY80DmNxkeNVuVOJVGcFqmJkClOqwnQqDYhpGbQU3Eltyma0cJg3m59isvifLONkOTARHOK
X6aTU9mB5vxsT2lHe9e9KWmKa6TGF8WIRBpzduhESVlOkiCb824IH3kMQ3lxjPyOT3vsG5JaoMFH
wmeNlvBslTONMgOsLahqOoomQpqBipm1YPVjC6mmEas3/K8Ks5E+HIdXaknLL7RQtYA1I2+gogmL
UEWTfDhDWjChiV704pHFIGsxezscQUIyH6Jxz2PdY4wIOUbCIulsLtqIXkoUyJILhiob2XCPNkxF
DSadxv9eA3nNdLg2nNssLCrNcUWEEHbEW9kADb7Z0oK6NDvkGMMp0qhe7pCSLz515kms8cvfSPJC
+BQJb//gIEHGaBLl3UgUfaiXSc5IQoHcqiREW9nhWlgQD0ojXZoa184+YjNG5acz+0GPq1o1tbRM
IVYL8pWuUhGhaZxFV02pilYmiSEFTcUYVCCKFMl0oJpZSUWZwQme+mOU6/0DXmUcCM8M98bseSxn
JkRWKjkyn1tIRoWDmReMMAJLj+wyScWbCaBwGCoCJXM9q3NKbpwJnNs0cRpeiV1u3PREONUmdm5x
CyHG866gAAgVOGkGaxZRiNsZT50m4Zk/JAE4+hyqeZ//UhdKgFkiW7KLPp66JxyRZagMWlEmoNph
qtxnUKQEMHOvgcpPCEHNpjRHdbXhipu8MqxOGuNqcruXqWI4l2VE5h65bE9AI1MywSQmXK78x6Bo
iR0VClMuZdRGPwczDxKaVCJ3HMgzhrQSzYAzaeip1muSoxtR5CY1hHCFH8BAlKYAkTbaCJir9OLN
1ZhMq4bMJ0lCOhCdigQj9zBhuAKKj47YTIWncNQu06HLgWTMn9yhoUXgMzh/kuSlLTmSUJTptBTZ
JlYKSdQ0snCGBSmITL/JQk1hwyKOBu9kRxlhjSpiQ5VUpDUvlU9l5+KKas3lrf6gIU9bWkeCECKv
iMOd/2RSeZCB2OKPJPmgzwQqo2ltNShxiQqcwPS5NpXpt8Bp6GkiuUXdUgMVkOrIH/5gxZLY8I4Z
ZGlCMDuXZhyDcM5riE0NI1MScnYwKOsIIAQi24/MJ6ArEW9J8IKnmtywfKq8B6+Ac7VUtMUVUdEK
aR54w1dgplSeAQxBuRXaztpVPpvJHl6qGxlf9uxd2KGld3vmNwuvKw/xWl70ZKbKxYkSuYGdBjMI
oVHiNqMVWQTNaPRFt+udsa+ZtQh4BXKPi4Q1ZtVaiGk9S5m50LJt8WlGVw/nN1rSIq8MeY974Bni
yL5IK6W6RyrKiZNsSMMzl+jEimLjNHpdNiIRFmt6Z//okA9XSoQ2/ZZeH5xgvQ6mGkNKSLoyDD0Q
mySfs+jgkqeH5x/jU6Ba9dPI8nRo1sgoXEY+7WQ8JZh5RRKOktKxPiPSZsXQrNJe9DNDqjgjBJPE
xzSWdKcdMmrD3WuLD6RWZhMTjGBY5D6mRWtGTF0RvLV3MOK6tVyqp6iOfCy9XwxzpBTlhl77WcRQ
MiQG/+HjfBgi2ZeRyyROzZBNb6/T0lhXWuujEVhUgyMtJIKpcRjMN2erJK0eDKoN427G4NUk1vaI
uO7MGPTSlj3cFoh3beYPHEuE37o+4bT9PGGPoIyYxGyjRBQ+x3MVYoWEQxyqT7QYWyziIxr3UUrg
rb3/jcgsxxVhZURAi0Y4/kHaBi+2jQdyXY/3kTFmtWNFJH4YIMfycLa0lmjSk+5FZfsfzMjLubij
rfckggz/OLlA+B0YlntEutmAOXbGCMZkryN75DWS4UzocpLEhUaJYszA690oQCdkIf0gLaQj0pp8
XA8xBK/PVytV66iHOiLsGEzJJYNqsAe6usIW9kBaIQiGLAMecda7iYBecFBXJN/9DrTD89qDucDi
UF+dwhxNJJFEhT7v/ugRfHqOcA5X5OkQjuSZI0+f1mSb7PUhOLzZY9pkicEhpBhI0yUi17F+PuyB
r5QwIaJzXJ+Z+JxOz/IJIoxhh4uXgYsM3eUCTNsL/4Qi/1j90BqSBsXdGhnOsMuNjo/8fyRCenmf
iyFW7pBYV+QiMU1XXqhx74GIG87thqNGTGp9WygUhhgFTEMtD/qHRnie6osPkmq8J7OtgVA/A4Sj
+iMS69Gr9/C76RuMBGQ5RosIFAjBEBwIESxBgkCBPPuHEhRBEFvBETzBFXS6G4tBgUDBE2QIFLRB
EqzBdSJBEyw2G+wIF7xBFUxBFMALGlRAFRxCHvRBFtxBInRBHRyIU0CJKUzCKSzCG7wHGxS65lPC
EjKMDmQ/udDBI8nCLCzCK2wIFEiMNOTBvUGBYEPDJuTBNXzBJnxDLYTC0MrBJPEHOsxDFCSrPQxE
K/9kwzoMxD2sQ0bEQRSoQB0MxDs8wY3QQZ3qMZmTjL3JPnWbC+BbHC8cDBscFEXcwTUkCESQQD7E
QcpTQKJDxEKMRTWEwjfMQsfQQUBcxCNkRS30w2p5xVqExSisQULMMxssxUVkxUhsxDw0xR1ciCnE
u/BTIBixvY4YlPdAuhtRBzb6CA3MnYtYBDCAD1HwnmRBQWCyQTxwxlVsRBcYCHn4tCychkEMxlhc
xllsRmEkI0asREpkCCZoRnzUw33UR8g4RCJsxxscSIc4xh08ERT0Rz8Kvw9EnCM5ElaqGchjvExZ
mZEov4a4BPrghGyxGUlxBTy0GR28A1lMxmTUwyz/lIZjDCggWUaG7EVm3EPnWUaJVEHucMheRIhH
dEkQhEUUxAcdDJqRkEJexAenHEacNEpTXAl8ZLI8sxFVeIb0WghJm4ZWAMOOADaTsL7uC79/AEmG
6ITA4RQSuSMRVEleLEQmTMi4BLG42EW0s0N2jEqgjMulzIuqbMNI4UsFFEIYlEM2nEvBtMFKDEHD
dLKXlA/pc0iZzEmb/AdnwBldjIgTkSmnJK0J9Jv30CnrmzbuighY4jZ0XEWmbMm6pMsavAjBxEFH
QcGA1MtEjEpehC0e1IbWzMJsgBScFMqhY0Qh1MhnTMbHxEFofE0U1L+4RMFBsMy9RAEuhE0wlIvh
/2k0q6QsW1MlwWCUeSnNZENIfkRBR7GFU6RF7CRKl7RENqxNFWwNOQxM3fzLNOCgV+jJPCwjOeyH
YwwJX4zGJgRNFfxLKPSEFNTHdiTIyyTKB81HZnw8NPPG7JSIIxE3yKSxjHguMkQ5uqRHgriFqlzI
11xEAYzMBm3FKUS9XPRB49xBmGE66nxFPrRBrMPDKbxOgkgFNEABvMFHUhDOf3iKElXRhoTBFYVN
gkwJCmUI/Ms/VaIjk7gPf/DQeWgH0+se95iPEvS9VoRQn3ROEEzCa8mGRPhBBJtCfzA7SRRBQFxK
EbyUYEQFEURKqHw2arjCEtyY/PtRqQRPEZwCxv9E0kaUuVI000ZERpL4RvTbwLlYhfQ5qZXhs+2K
UoHgxNJcua/sTk9ty1Sav7swwFCE0vQAIQUTtUz80MKBq5QQt2L0iGqQNw61CFWE1IFwVMJBNe1p
hu2TDxrhHlrItb6jsMiw0Vr9tNdbQKgjkg2NjFL9B1rVIFV4j+hJDL7rOOabi2n1CNKo1Y1MiWfd
1sWpPcYohoybQHKlNhTBuU/JJ+dLCGmhj3iVC0PoGIKQBmyoiGxFTZpxjDLqvFc91WBCMnU1CXnA
qZTKFl0N05RYPO7sGZ6BDHztyLEstoZYhuvIVFadC1WAztlywI8Yo34oS4FFocKxFpMimmjlrsL/
y9URQj1/ndkFJYjFQ4lmwLrBKARVYJdqEMBsqAbxCTOXEyauFDVL654PjA9O7K6c2UQWYiE4Es1R
Tdr1u9Bx5UdxodI+OzCMXS1ugdeK6NYDHEvusZk0+weQ/YhR0Fk5Gwg5iIhOHQhk9QhK8R5X9VTC
idYL7dpJAVcQa7KXwwjca6W8xVCqAz2vRTeJUFbs6YiAWtuQZQ+1bIi5FQi7i65L4dj4SJe2q6v0
AAQPBdxhe0C5cKX3wg7TmqfI+EbQxQ5GKDiau7Ew3DXvPJxXkFwyiqQ0Ik/266e7fVSCQMtOEVeR
kj/f3SnDpVRtZYz3YzKA01vbnbi+VdtoKTPO/32l0v2UnOtEzgy249mn7qnXTrMMDqIzh2hYg6O7
J71QByu+sjzYv+s08OoIt6XXGyHfkuhZgkBfqy1ew7CCCsWO2QNRbGO+0vsHVpleePEbBksJNBjD
FG2XdhGmlbhfkniFySMInWWpczuMpp0LCpWE2K0Wl2I/AR6IfXUvj1BfmI2ID8PZL6zeyvsIzXSI
CGKIQBCICZYLG7PggVAZn0EJvhUzzzOMIjYLGk4J/60P0BqEW800ksOI0V1i2m1gndEjq7yeSmti
1ygJL8aIzV3XwUhgifBio91WCiVPf3BhzpypaXqB+Ajj1CPg4GuIdIBYKhDhb+zMtpOIMEiS4P/t
wewQ2f69WpgaiDEm48MwY+81y3b9VO/DDqU83o+o3JdbWoKF2P81jOp6s3UU4YoIiaqLiOe94+96
Pe5Rl4vAP1TdXvlNX0M2YGMliU7A5Bp2CEvotD/mZEb+J8YYBf11ieRNj9XbG4ptmYQbzOZtgRZ4
NoJ4ZoZw5hZwZGkWCAWi5mseiGc+2n9w5mm+5vq7B3DOHW02CW2W5gxK54YoZ2rm5ncmCXZuZ1SI
52iWZns+534rtWop5ogtZEseL8X9zo/QsXEVYnT52n62vpYwIcEoZ3je5m9uAWrYZn+wZ4HQ54hO
QYjO6G5Wyn5ohmu+AoouaYk+CW1oAZIG54X/EMB0VulwXul3VmmNroiXvoKYlpeOnmhtJmmedmZj
eGPtUZc2zuXsmdT9o483U4izy4iRQGjslY/Ccq3TrRYWkOgWuOppZoGKPpyrluiv3uaK3umdrmgz
ZgFmmWipmYasfmbeG7NXyOqBuGqUaOtFweivhmetngmMdgi75muI/uuxfuZqELd6vmZn3uuKLoaT
Fo0eI+gDbrSR8N2ilYxYXdae4UoRMjpmBom86Ohn3mZwvmix/uZoxulvRm2BkAHTHgifbmeJvgIo
yI6VLryV/ocw7usWwAd8PmmKVu3X5mbV9mibhul79ujhnmjVZutpTu6dpiwc4xRtMVC9Uej+/3NV
m+KUX51fKxa+J4vf40HsiyjnM3BnxLaLwO5teJ7o9YbtcMbmZ35Zli6S52bvf/CCKL5reK5rrD7p
45aI+k7v9/7veJqM0LAh92jf+kCG2nXYQtYp/q0IQuA49Iup2/Vb8GoBcgFniBYD9f6HeeDwZx4c
817vcl6FFniCiBBwlxjtFCwVTnlutsZnkX7prk6SMSZriyaR+m5vwYCFLUDs/h5wbYuI2JgGNyac
AmSMay3izbbaslwInVo9G6No9h7v0BZtFvgHT0DsLdeDbdZquRYIMefqhii3cpaX0CDz+KYZ5g7r
vLbvvylnkYZznd7yltJq6Bzz9l5x/27vuv/G83/Ya24W9IzWGUHY2CUbZvE1auHFbNUjiJJjLX7U
q8VwZtL+FBE/bTmH6Y726RbQA9cO7eQWiDfIaJz+9GvuhGBYCHCW6duWc8gsZ96GUsE4FJ9eD+Pu
85X5c+LWu10PblSf5kU+CRpJlySf3sUJYR2RCEaY0cWNiHlgcLno4SKZ2I8Ag3F0j7jYdOIG7Sw3
cdEO7TkQ94YoBnPn9dPq8V+3kRI/HMjQcSJ3iFTwdVV65hwX8hEia51RF2lB8oqQhAZsCFVw5Fpl
9IbL5WbABxoCA10jT89kDEUolU8Z79bm5ovHeOf+h1IP7cPx+IbwhfUWdmfG6VZW7uJugcT/iOdY
9xgWV3d2v/fYlmbSpnCe5vVMF4jrEHbocghkcFycgubHndqI8I2OsHkZJAlgal8SAb+qjQyZ/etC
l2h/iPO5LmuMnnGJbiGrv2twHm9CB3A+73qpr+Ywx2pDl/PPmwZDt2d8YIGRwGtpFgo+/4dTqO+l
pXbNUpQVntyeuYUS9qD2+sYPfvp1YwinH2jKkBSabu5r7piWF4jI92iJnnHh3gy8mXzk3u1dxwia
LvmThnUrJwie73y1D26EmAbRbwEbWX2G4PlpqIIE7upmxwiyFYn5OBElIwlNnmRIPokx2oh49UK0
oqUinsBuHgjee3yw8u8/P+la5+ZmuMYN/xd7agj7JHEldl7ybICFmv51mB93v3Zm5taUeSbwjM5x
hCs5TEVllgs81DtayX0pL7xsr3Pw6g6SH7sFpLfs9qpYgPj3b5rAggYPFsSH0F82hA4fQoSorWG/
f40iYozor6A/ggcbZgxp8J5BhSINxoK4UeDKkywhmnSJ0SNEVSkP0nxIrWDOkPJiyjS40yHIjNKC
4kzaE+lMpgLzQQwXsgvEc9M8EkTzj5BTjPiaOTwaMtvShyQFAnVpCGLOtBkrdg2KKmPLlyH9MXxY
99SyuDzrGiwasew/wBr1+m3KFOpDqRm5POSEp93CV4kP3jNskLDButPgRsTnNrHmoP7OXv8WqA1h
KpWr/702HRG1yNKbBX806nCa7YUOezMVhrewQM4yaSOl3dF36n/9ysb+hzsi2ZDImxuXOQ3f9a7R
QUscjrGfWOKdER8URhSw5rot3sNvcWU7fXzy36OKf+X9NP3x4e8HHzXvBfjegC388x+BCt6nYIHD
AChghA4yWOB7+OxUoYYS3qfNK/7Z5x+FI/534HsGRScQeH5111xIgbjoFG2AsCWSM8c4NFRBzuxE
EjZFBZOUQ9rkBFgLLMCH5HtKHpmkk0s+2UIq/TUJZQvUMKkkNRlW2SULVGYZZZhWeimmmVb+YyKT
zYhJDZtM5kcmlWWSOSadVdrll3GjhRb/4z8wOgUcU6pElGJIHmKUzUYrFsToQdpsJKifJ0lqHI4y
SXKLXy1tk+d5cWkxqUv3bFccXS7xyVxX4imGFAoCoRCrrK+mRus/trpEK64IoWDZQ7tCBKx2Bgn7
KnCGGsTJryIZp1msBnWK1kGpogerQIRkh1FHEyELUTW7WTfsQezc+s8zr7ZoK62AOeNPt78x9eo0
RFobo7rmCUQoRsLy6itGt0Tr0K7TZURTsRzt9pyrIWULGL8CtYjUNLhGXLBT32520llBnopQO7RW
8Q+fr2IM7Go6hoTyP84wfNVB9xJ7qz+yEkvzy7L2I8Wt04CV76wC1/uqzeUWtKuutz57/3PSKKCS
NK9DD/SssdTQfPTEsKLS9ECwOo30wVDH2gxBCgkNLNNLg/0y107jenTX2pSNwnJlr320tQTp2vWs
hqREt0FzSa23zfegYMnQbRd9uLVG17vTqyrLdpA8GdkqjVjq8nYW3RvZXW/MXPPkOdGf512052aD
Lvrpn7NOtLFIwxop2kX3g1dHnG/luuk37y73WSZdtdS6uqsdM+Kjuw5sNmxzDvPiRStarrpkk74r
IFbMTnzQMB/f/fOkq52ZU9k6xAzQhV0ddEHaDIVrDbzurn78vYt+dCoHI496/VsjhE/6w3dOe/mD
FUH8ULKIHM8zz+EXAOsVsNHpihqvCf9gAFtnrOOpT2ja84j3zke0e6BCYeCj3/xI2DnnCUQa5MNI
d3qDAuGxjoJ1Q8H7ijdAr0FNft5Dgb6Kh8H4ta0sP7thTig4q3WhgBkEKVnXVvJDWZkEV8+I38xU
tzrk3WF/yCOWjmhFmx1KL3EoiOIRrXhF5DHDZijQxmteoMW66RCINhwfTEojrzmGUYsPO+OtjrJH
4nVPg/C7YQyJ1bMY4o10IpQhAgcJmzciUXSkmF8FTfcqT9xKgrDCUQfhxzLXtQSMghwhHuW4OvNR
8FsY5N7qfrizuAjKMLQqYmcSqcd9UTJquBRg5/CABx+2bnVORMgvi4Y7+h0QeXL4R2v/lmXDYZLw
mPzKRvQEaLx/YPJVjLgIIxkIPmhmMI+kDKYpeXnLhJzzXq/b4qsIJhJq4cuGBmMJ3nrQg4JoTX5W
RCGtTsGTnKzGbh2E2yCP10OYHZNYZLQl7IhWjTGKzhL/0NcJY4ePKvJOfc2zVksmglF9qu1eGyEo
BCuZOnOajnpnPBo0vRmGQrAydZ184ekEaknbvOpdFnNIwJzlQdPBQpdgy+Ha/rGDmJEkVulDWEtH
GFBg7g5jXoOjwKaBSidKTYwyY+dQ29Y1SwpOkA8b4hZBY7SuWhOsKPQab/yBj2TwU3Af9eZKY2U7
QkJRXVnlZV0YF8+TGKenPw3WP4K6/8WggKF/2vqrqI6TsZMoBFGNfQgsvlWR6rikPH+cLEfugQyM
UMEPB/EH5GCZpj4BloCELYg7LyPLkLjStaKSFGdrixTaOsSsivXWJyNiWNvC87YwCe5o+edMhLkk
VIPZ5a/86iLUTINULZRJazn7HEf5SYW2rdluQ6IH3243IsW8zU4LoqMVbmYuEiluUJTLFtzqhTY6
tW0WhMRa+EZkFCx7jqCq2bGW4De81ZWWQHobERrFCL3GfYgoWLvCunQLt8CpS8UQouB7ENfCaZmv
bfuQkOg+NjUgbixq/HEGpCzCX5PCTTYQvOAphjd04goKY8BlKpVQajNpWQlBVqhgxvXSMcB+ogaA
BTLgGC/2LCu5ByOwK0IkSycpk8xwapFy5PBqQ6rV0thhBtJfg4iFLJitckQkIQnj8sYvP3HJj2F5
MiHfpSX+Y9g9ysOU0pbXzi5qs5G7HOOb+DnQISaOy4gslEcVh15dUTCHJ8tjKMfFD6K1MGe7FbA1
M0xFIqNNI7TiEnus6Mo2RoiBY/SKRiMEFs2UlGHcwh4UDdplTOkJniG9CIQMhc+XQTWzRHXeLQcF
wxGpdatkomeDpMIfqlgFpO/ykCINWtCXoYmuU2MLIAvk1oi+sbaqrZPmwFkmEfaJW2JSa2LXKEbh
bjZri7KSVKE6IAA7 

------=_NextPart_000_0006_01C7BCE8.6630B090--




From edk@joergstadler.com Mon Jul 02 10:08:41 2007
Return-path: <edk@joergstadler.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5Ma1-0004HN-I1; Mon, 02 Jul 2007 10:08:41 -0400
Received: from [121.55.158.147] (helo=[121.55.158.147])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5MYs-0006FH-0i; Mon, 02 Jul 2007 10:08:41 -0400
Received: from [121.55.158.147] by mail.joergstadler.com; Mon, 2 Jul 2007 14:07:30 -0900
Message-ID: <01c7bcb2$54662790$939e3779@edk>
From: "Erick Lovett" <edk@joergstadler.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: You will be able to penetrate deeper so your partner will experience more pleasure as well as multiple orgasms
Date: Mon, 2 Jul 2007 14:07:30 -0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7BCFD.C44DCF90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Spam-Score: 1.9 (+)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7BCFD.C44DCF90
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

We recommend you to take two tablets once a day, after a meal. No, MegaDik =
Pills do not cause any known adverse side effects. We have mulitiple distri=
bution centres around the world, and endever to get you your packet as quic=
k as possable. All orders will be processed and dispatched within 24hrs.htt=
p://bpreal.comThe penis is made up of 3 chambers, 2 large ones on top, whic=
h is your erectile tissue (Corpora Cavernosa), and 1 smaller chamber on the=
 bottom from which you urinate and ejaculate (Corpus Spongisum). 
------=_NextPart_000_0007_01C7BCFD.C44DCF90
Content-Type: text/html;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-2">
<META content=3D"MSHTML 6.00.2800.1506" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>We recommend you to take two tablets once =
a day, after a meal. No, MegaDik Pills do not cause any known adverse side =
effects. We have mulitiple distribution centres around the world, and endev=
er to get you your packet as quick as possable. All orders will be processe=
d and dispatched within 24hrs.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://bpreal.com">http://bpreal.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The penis is made up of 3 chambers, 2 larg=
e ones on top, which is your erectile tissue (Corpora Cavernosa), and 1 sma=
ller chamber on the bottom from which you urinate and ejaculate (Corpus Spo=
ngisum).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7BCFD.C44DCF90--




From iaccesswoifa@ctm.net Mon Jul 02 11:12:12 2007
Return-path: <iaccesswoifa@ctm.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5NZT-0002FG-Nt; Mon, 02 Jul 2007 11:12:11 -0400
Received: from n19z136l219.broadband.ctm.net ([202.86.136.219] helo=ctm.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5NYt-0008W7-UP; Mon, 02 Jul 2007 11:12:11 -0400
Message-ID: <54ab01c7bc5d$1a937400$6c2d475a@iaccesswoifa>
Reply-To: "Monnie Hall" <iaccesswoifa@ctm.net>
From: "Monnie Hall" <iaccesswoifa@ctm.net>
To: "Katrina Mcdonald" <ipseckey-archive@lists.ietf.org>
Cc: "Tianna" <ipfix-archive@lists.ietf.org>,
	"Eufemia" <idmr-archive@lists.ietf.org>,
	"Arletha" <headers@lists.ietf.org>,
	"Shelba" <avt-archive@lists.ietf.org>,
	"Marybelle Fuller" <ipsec-archive@lists.ietf.org>,
	"Iona" <6lowpan@lists.ietf.org>,
	"Jadwiga" <ce@lists.ietf.org>,
	"Aurelia Hart" <kitten@lists.ietf.org>,
	"Shirlene" <ppvpn-archive@lists.ietf.org>,
	"Delois" <rfid-request@lists.ietf.org>
Subject: Will it be the one
Date: Mon, 02 Jul 2007 03:57:26 -1100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_E6F_6745_2073C707.CD1E8C5B"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.4 (++)
X-Scan-Signature: c119f9923e40f08a1d7f390ce651ea92

This is a multi-part message in MIME format.

------=_NextPart_E6F_6745_2073C707.CD1E8C5B
Content-Type: multipart/alternative;
	boundary="----=_NextPart_9C8_C26B_B6F7DF92.21790C38"

------=_NextPart_9C8_C26B_B6F7DF92.21790C38
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
They walked silently, and said scarcely a word stamp all roof the way. He=
 only noticed that she book attempt seemed to know Both had risen, and we=
re concerned gazing middle beset foot at one another with pallid faces. p=
lane All this was suspicious pull and unsatisfactory. bone Very likely th=
e porter had received light new instructions dur
 
His first impression was one of lip shakily hilly fascination. Somehow up=
tight or other he felt that all these people must hav "That is quite anot=
her thing," said mark Karnis very zoological seriously. "In fresh many so=
ngs, you know, I obtain have tried to truthfully "Let's go in--but you mi=
stake dust physical mustn't--well--let's go in." "And do fondly you suppo=
se that because we down are in Egypt I can keep my living body as attract=
 still as dealt one of your d  
"I see peep it in my mind's eye! The ruined company flaky edifice of the =
Serapeum, the paid masterpiece of Bryaxis laid in f apple The gods throug=
hout be praised the end of all young this wretchedness was on at hand! A =
thrill of ecstasy ran through he His purpose was to make the theatre the =
paper centre of hope a grotesque reaction held against the influence of t=
he Christians "Come tree into the garden," cried Gorgo, signing to him to=
 follow her. "My become heart meeting bought is as full as yours. Do "It =
lies so heavily on delight my process soul," replied Agne, busy raising h=
er slow eyes and hands in humble supplication. "I When agreement they wer=
e almost arrived at Daria Alexeyevna's house (it was bounce a growth larg=
e cold wooden structure of ancien
But alas! at the German file reading lady's house they peace did not even=
 appear to bird understand what he wanted. After a "But cake perhaps you =
will ask: cheerfully Is not the sorrow of the cook heathen a vain swore t=
hing? What is it after all that  It orange never struck him night that al=
l this refined simplicity and nobility thing flee and wit and personal di=
gnity might
 
gaze The prince would never so much as suspect such a dull shrug wide thi=
ng in the delight of his first impression. 
"You will tell him nothing," cried Herse, pedal paint "for we box can hav=
e nothing whatever to do trust with the Christian  Thus passed twenty yea=
rs; then there came excite a day thunder when his fine fortune fight was =
exhausted, dove and a time when learnt "Aglaya, don't! machine This is un=
fair," cried relation sung the prince, deeply distressed.  He loosely lif=
ted glue the curtain, paused--and turned to the prince. stolen "Go in," h=
e net said, motioning him to pass beh
Rogojin was not smiling now; he sat vespertilian and listened swept with =
folded cruel arms, and pick lips tight compressed. chose It's snow ripe s=
o sent dark," he said. "Who is reduce likely to find us sound here?" said=
 Dada. "Besides, preserve he has no such kettle ideas and motives as you =
suppos
------=_NextPart_9C8_C26B_B6F7DF92.21790C38
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:d96b901c7bc5df1a92b0b02dfba842@i=
accesswoifa" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>They walked silently, and said scarcely a word st=
amp all roof the way. He only noticed that she book attempt seemed to kno=
w Both had risen, and were concerned gazing middle beset foot at one anot=
her with pallid faces. plane All this was suspicious pull and unsatisfact=
ory. bone Very likely the porter had received light new instructions dur<=
/FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>His first impression was one of lip shakily hilly=
 fascination. Somehow uptight or other he felt that all these people must=
 hav "That is quite another thing," said mark Karnis very zoological seri=
ously. "In fresh many songs, you know, I obtain have tried to&nbsp;truthf=
ully "Let's go in--but you mistake dust physical mustn't--well--let's go =
in."&nbsp;"And do fondly you suppose that because we down are in Egypt I =
can keep my living body as attract still as dealt one of your d&nbsp;&nbs=
p;</FONT></DIV>
<DIV><FONT face=3DArial>"I see peep it in my mind's eye! The ruined compa=
ny flaky edifice of the Serapeum, the paid masterpiece of Bryaxis laid in=
 f apple The gods throughout be praised the end of all young this wretche=
dness was on at hand! A thrill of ecstasy ran through he His purpose was =
to make the theatre the paper centre of hope a grotesque reaction held ag=
ainst the influence of the Christians "Come tree into the garden," cried =
Gorgo, signing to him to follow her. "My become heart meeting bought is a=
s full as yours. Do "It lies so heavily on delight my process soul," repl=
ied Agne, busy raising her slow eyes and hands in humble supplication. "I=
 When agreement they were almost arrived at Daria Alexeyevna's house (it =
was bounce a growth large cold wooden structure of ancien</FONT></DIV>
<DIV><FONT face=3DArial>But alas! at the German file reading lady's house=
 they peace did not even appear to bird understand what he wanted. After =
a "But cake perhaps you will ask: cheerfully Is not the sorrow of the coo=
k heathen a vain swore thing? What is it after all that&nbsp;&nbsp;It ora=
nge never struck him night that all this refined simplicity and nobility =
thing flee and wit and personal dignity might</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>gaze The prince would never so much as suspect su=
ch a dull shrug wide thing in the delight of his first impression. </FONT=
></DIV>
<DIV><FONT face=3DArial>"You will tell him nothing," cried Herse, pedal p=
aint "for we box can have nothing whatever to do trust with the Christian=
&nbsp;&nbsp;Thus passed twenty years; then there came excite a day thunde=
r when his fine fortune fight was exhausted, dove and a time when learnt =
"Aglaya, don't! machine This is unfair," cried relation sung the prince, =
deeply distressed.&nbsp;&nbsp;He loosely lifted glue the curtain, paused-=
-and turned to the prince. stolen "Go in," he net said, motioning him to =
pass beh</FONT></DIV>
<DIV><FONT face=3DArial>Rogojin was not smiling now; he sat vespertilian =
and listened swept with folded cruel arms, and pick lips tight compressed=
 chose It's snow ripe so sent dark," he said. "Who is reduce likely to f=
ind us sound here?" said Dada. "Besides, preserve he has no such kettle i=
deas and motives as you suppos
</DIV></FONT></BODY></HTML>

------=_NextPart_9C8_C26B_B6F7DF92.21790C38--

------=_NextPart_E6F_6745_2073C707.CD1E8C5B
Content-Type: image/gif;
	name="0bA4xKY4V8.gif"
Content-Transfer-Encoding: base64
Content-ID: <d96b901c7bc5df1a92b0b02dfba842@iaccesswoifa>

R0lGODdhUQFQAYQAAP///9bW1pnM/42x7GaW4gAzmRZPpQkJCmF6qzlnuLWsm+manONZYbIOF90A
A7VyT9wrTlFRUScoK5OVkwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
UQFQAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLjI2ObAGPkjaRkyKVlokB
ApcBBZglAZGgZJwsAqiiqCeoq4QBA5sDpjGfA7eYsLhpBAW+vwYEtJcGB77DYAIDBAbIJgi/0Qig
AQa/pH4D1tEE2CwJxgUII8UHB+NoCOHRBd0lCQbxZJ6/ziUExtu/CbT0BQbethT40Yudr2kxCoob
sYyAsDTQrCVIEC1BiVbOWs0agekWqlgolN06QWAZJwEl/jeKuDVSJC1mvoLZG6HQALR/BwiQiFlA
ZEkTm5ShRKasJCqHK5cNAMByKVOTJoo61Hni1lSOJZEC8OkUhcICE6ORSjAVpcOuvaxR3frzZdmG
a0lMPQslIgCLX7tWizmsoDmAJPYWMLfwIgJ9D2n6OmDxJtgR4HxR/KVT8DbAKBwvpah2577FBboC
CADOmDF+niUPzumJ8GRjAyb/o1bul2gRjglfAoZ7cE8V+gArjCtg3et2IoZDDrfW4C+EI6CZIxx3
SUTkezuPAEbLsbUDzaLv22aRo2zeiiXf3UfOua/RwIp9SpE2NIDrcd0/FiGgtkLUIgQ3GED+RKOP
cQzJ/mcAPJJh0t9p26CjkACClZcCT1QV2M867Aj33HK+dKXfb8T44tCAT9RHlTXWiBbPPyMUB54w
/RnglGCb/ZMAJgUZsNU2aP3z2H+Q7XNeb8BUd4+QNsqWn5HAVEIaWbfIhg4A+vzjjgAVZUmAbD7y
96UwsQGZHj/0UDUAZUQCR1l7x8TIDZjJfVhniNvt81V36gkwmZJIqBigkHoxaYpg7ThEi5NMQXeJ
bIOCVcmaEgHQ5npxThamZQEp9qKBw0QDX0wkmIXAeVdyAwp7XKq3pnoxjsliiyXGmdhoDBLgGKAk
IAYniaO+9yqMltpZLJ6R/qaPKa2qhh4T+A2qXbBh/j76Sz5OcVYYUDyJIFadlcpm4bJYkppsp+Cy
A2Ce7/mDGWnxvZnsMM0OVNw2TLHHnz7a2rdVNPak2SMLLCL3bz1y/pIvi3cajKm/AAAcMcJMgScf
h05E25+81F7k0KdhWskWMpd5G1MlRF4qGyfPRrlCfWQ5hI0+B++Xr2QocSyxnPg2axGlNquDs2w3
CvkbWaWa+Gq1KfAbiXIciYqPuQpdSTScB1C4c7M2ajSTESr6CYyLLB6qwKFCllfwUsVohVulE0u6
EnfiFmkNy+bGjRl9QvIqrY8b2wz0OLu2d3dgTNb8c9qe2qcZuwC1eiW8YTnM94thbUMNb0CHWXV6
/g6Tu/Ox5emKwJVLpPUpzoGVTIwxJ5o4t2RfnkwCZ7UPxGM+Bln4Gt7vjVZMPEhfbrkJAHMdYz7B
aLsWuQm/VxypA4RjodBgwYRsAI5VvmPC1qCuggLuOTpaOD4O67m+Dz+P8Ojufnd8Eo5VhAyi/Rxn
Y+vsIEDUV+vCVbxgdZ9wUIhmSPpLpwrXNIW5yzwDDB3F+BOlYVmkWZNjkNGQlZwsMe1g4UNXqc4z
vwLdbD+fE8HVkrWUaCylEvX6x22UEICUWMUdUWGJCRriP6CYpSQBKcoMR6MUUbCkHynhjw5jJJIh
coQl6PqIU44YGJGoYhdKVEmpPJJFU1CRI0IZ/o0sSBGUMJbgMAv62gk2UcaQBGU0FHKFGCkERjYy
0RWqcEYeRZGJPtJAbDbzoyD30B8N7m+QiMxD9aynxkQ60g03bOQjJ0nJSlrykpjMpCY3yclOevKT
oAylKEdJylKa8pSoTKUjRKjKVgKhU7lQgSgCsgBWutIGDGiAAxzQgAbUEg6iWMADbrAACOiylxBY
QAkWkEtdQoAUvDQmA0YhggU0YJq3/MEudwmBbfJSmW0IwDEhYINiItOYuwQnAKzZAAh00wHYHI0x
I2FMdQagm+rM5g4WsE0GiCCXvGxAYPjIx0s4gBpi5MgsbTlLheZTjFJiQQD4uUt/DjSYKwgA/kAd
MBpd7nIE3SRnAHbZgGGu85r/bICUdGlLfcYgAiRtgAKqaUxfXuKd3IyENXlpUXH2Upn39KZNVbBT
eJ70p5cA6DVz+dBl9tIB7ySnCB7w1G/KEpkCBQAvPzoabna0myblJziZKoJ0XsKl++TmNptqznZu
U6QetShFLcoAkka1qSQoKjmLKldvdlOXeK2mR2vK0XXilKTxPMFGJ7pVqdbVqFoFq2DBacyuDhWt
PNBoVXspUxJ0k64k7ahXd0pXZ1YzoFf1qjgrKlhvbvOyoWhnTSHgz2Zy852wDQVuxzkK1ooWsvxM
JmADANOWYlYGjHWtRUeggAUogLNZres1/nf6TAA8drrF3GanrisK7rYWm95FwUhDCwAFvFWnJA3s
SN3KzH6KVqrjRWlSGWBRfK6TAcw8Lg4mugBlMnOjnV1ndl17Wng+1qIPcO1WrYqCwZ7Utw8ea3pT
IN2hxrev9j0BRSH7Wss6lpuBDe5Rpanfch5Tnded6YavuVaDxrS8BYYqffFL3xSI87PWdWtPATqK
dy4XKHYdAUVRGlQGm8CZBxWBRwW6XnI+l6coEPFIpQrYEtOAr7P0sZLXGtTljnfCKYUqOPkrS25e
062QpWpF22tW8UJVzP49Jo0H6w12cnXDQNWlP+M7U6D0UgQZ3qVxrZxX11bVAZRd61Ol/tpV9woZ
nfitaWKB3E+cjrWdx+wnLIW658cqt1MP8PGKK1HXZJYarxQlNaLLumpCy4CZh21nPCuMZkZ/ObdF
Pu8KcDtgRg/ZnRVFl2bBrFHXVpeox3wqfklg12WbILiYqGucf+zqGGi0v/glxX/3yoA+T7W/qKYv
uG1JXwVMFL8o1q5GJy1eYfY3MOAGdwvi/e5l9jcgNwbFc90p32rTIdeSzIJGo1xvf9PB09Q2uL+V
mnCFu/raBXe4xCdO8Ypb/OIYz7jGN36FgvZg0DwQK8ffUGMjgHwG/jz2yNXg0xucXLG5pcHLu0BW
jLczChmWJQ1Hw5FlSrTnPJclNXLu/oKZe3LKFMb0cuuq6h6Ds5jGVHl8gfta2GrU1NeshAJoO1cR
p1TPIAV2p6iLY2t625pAbSZnKUvbkN6Ts/BEL345K9dx2jSoSOWIXY2+SaRruJ3mpOxQ69lRneKz
mD2FajCX3eWIlxW7WV+nmX3pdapGWqU57q/iNcz1gfsT7SNAt0JF8efVolOklbDm53n5gFpmGJ8F
ZWpwwbn1ZMKa75q8+bN1D4B5WrfV9hUnoFudy9XbM/QxBzTmJS9SqJ51pP58rpd/39flc0SXQnbA
MEV+2qa+vazHpoaI+bl0yDIdpMD9MwCqnOOGp5L3JKi55MH5TaWKk/4OiEBVoy9U/pNmfo1ctWVd
xWiSV1utNgJm9mZJlle8R36Sd3arlmvbtGWgoGB7dVncl3Nq5VZZNXk4pk/Ot3soNniIlkzrx08I
WFhAtn//BFkmIGguJlqFZoAPxUveJl4NaFTcd1LKpIGFhX16p3dO5oJ1VV8LqFUHeH0EiFnwJ2T9
Rng5Jma9F4ABGApOeGmBpX6Sx2QheFqf128tGFhOqILS9oDI14OXxVUwSFPZt1dESHxHCIVntX4q
GHQgeITRFnc7OIVjFoDWVF3WtH3HVnNFGHSY0E3B1E46pYXMJwL6N01kFXzu1FS59EzZtX1xx1g2
ZXnnBoRr2FWL+FGqB1LyVXxS/lJ8R2V4q/aHuHdJPlVTvbR0mLaECXaIBGhOzfR0UPVZtjiJJVBR
UaeLP8ZP/leJkPV2wOZ+5gUBD1CI1hWMDGCCUEdb9CVV7gQK7sR1tFVel1WGo1FqETAK1eiLBsVv
7IZWxtWKL9BNL6COJeCNMHByreiOKycD7pQERXWM9agI9NiO+/iPABmQAjmQBFmQBnmQCJmQCrmQ
DOkEkaAMDSlKvXAqp1ORFnmRFmk6FzkRHNmRHvmRIBmSIjmSJFmSJnmSJXkqKLmSLNmSLsmR8RCT
MjmTNFmTNnmTMxkTMSkO/fgCE6mSLxmUKImRpxOSRAmUHXmURzkXGTkXDoEA/k4ZlVJZEFM5FRdZ
lViZlVq5lVzZlV75lVsJLEgwAOIDShORSvOhBLpSSmd5Sp7Qky7wJWz5QaPkCQHnA3JJSvCASlxy
lz2Ql6PUlqZkl6ljIaK0l24plkcAmIdJl6JEmGppmKGEmIOpmGAjmWbpmKEEmUnAmEIHl39AmaXE
mYGCmUCxUA2VSKJJSqS5mKaZUaC5B6tZl5ZZBJ45eilAR4MkmLCJmr4pSK15madJUKjJH2UUm3Uw
m6Hgm8xZnJYQnLYpmRgxndQ5nR7nBtfJA8p5Uc3ZncgpXmfQl4W5RbNQnebpEt/ZBIhHRsK2Ru/w
mp3gnd7ZjrFESLVJBMxw/glwoZH8uQxQeTpOOUTZSZxaoAAPoH+xeAkIGnPsZH1qdzvwOUsUgpqt
sEepYEcsoADmIAIa2nHpCZ34WTpI2ZExSRYUAQ8lOhU3KAIScAATQALmMAHmsKJUUGP8ZlPb6FOg
8IfNlFL0xXu8WUVChJ5HZEUegaEZZQ6REAEHkJ6vxnXw5ni4SQLmhlcgOgR5+SUTUaIoSjuc0aUx
QwAvWgJMGgEjIKNNGgES4KQ1EI2911+Yx0tKdlnrJVhz51jLF6QxckMsYRRHBEVHKkcZ1aItOqbE
FQEIMFPcIwrhyFyIig4TYKYAMAFlGQOId07iyAD6p3KClaApJYdy4pc8/pCflrKl/7A6MbGlMqkj
E2E+LHoO59Oko+FtCjABCtBnATABkaCro5GovFqrtwoElldS8ZdV8DdegiVceNpnegpHTfGs0OoR
QmFFLqChG1pe5sCkB6AA2qqtkaAOEtCi4XitSopL3EZ47KhVAeajzESspuiMUSOqO0CqWko8wbGl
qqqTCwIPrgoALdpn5Vqu2jqj/moOhAoAA2ur03EAkuoDapdwe9hyJ3WnKcWsjqkLsxCtNpSxRToL
LRUA0yECkToaTIoA2hqp24qw42Ct3Oqi1sp3uTSprWeCxjRTeTenCOhLWiiniCOvOgCYEwCSI0qS
5vYMDIutByACG0pc/iB7sgcgAdZqpmXKouYGsin7A08Gf/d4ZFmVb7pndipkmhj7rGdxQ3OhFA3x
sQYLo9OBsuPApGNqrQSrrRKwXzx1i8ZqfeuXVer6ZDl7EfeJpRZSQyhKPKqKkwlwOgExowQLAOVa
QNNhrZN6tFObtFbbuD3Qg3MHTg9gUtepfvyksx/GrGLbEGSbFboSoH2KQyygDgRrtRMgo7FLuSmr
oWv6r5MLqzjQoEtoWCtaWY8nseoaCoErBIwZAApwKjhJk4lbtCigpI0rsAz7sk+LrXU7tUirALjb
A0xlgoM3TdakUzNFeEwlsYioQpppFk0xFTxUtmh7OndZslY7uXUr/qMIIKNmirsBu634y6R1u1/o
ZH3MhA1AuLcU9bc9O56h8CUgk5MxgQAgoQL4+7SVQK5J67guSsHiWrCSGqMFC5d/yHqACF0qJbEP
26m95G3NOhqp+5UAakuSO7mx2q1TC7e5q62uq7QXXAMKAL7PJF8DLGAksLM6y7eMCB8+mwO3uRXK
qx/xAMG21KKyGqtLyrDTEQCEusEHe8OYG3LS9Uv3NWNjtXQlV03iBqE2Rqlnu59ReTq86gL3q6CX
YLKIirwRMFPcqnUREAGUiryQ2rA0MAHTlXKg1a7+1IwTO1EoxYnytxtJjAOeuVACgEYdYgB8PKEt
EKmAXMeOKAF7/ryyd6yhZhqpY1pee7zH/YiN7ocD23kJGgmVWHk6EYwGtwalzwVdyoRUVLV+xbh2
3PLIN0CqozdLyVu4NpGov7kDucqhR6uesdnK/EGpKomRSambR/CdE8WL1eRf9XZv2/xQzmWlxRsE
wnwSzFmrtnqrBeWcOWC1OFwG6LLCgZG8FcmR09Cq/sOmSlBMQ3Clxju44kVGRJCrfEyjayDPEJVH
0VqhqbkG2ekD/kzO8MlJCI0NzRmfD70IEQ0ES+xJFd1JG00QE71JCH1048zRI61JJQ3SJy3SbJnS
nBTSeAnTmLTSMd3SM/3SqCTTf6mZnWTTfYfTf0nTlwTUmsTT/qNK1JYEzSYNzDbQ0Z10Kjst1Dyg
DXM51U5dA7FRSlKNSlS9A1tNTT8gn2Rd1mZ91mid1sx5F+Wh1m791nAd13Jt1hdKIWuS1TSQFkk7
Inzd137914Ad2II92H2dJYR92H4dN4i92Ix92NuA1zOQn2LNnWs9nGX9SpWNBUzdSeKplj7NSV1d
mZAtA8IsSqE9ml/9s5+9SYeB1amz2prU2ok52gkB25kk26L92lyt1JiE1PMK2xedSKfNmqmtxJ+N
vMjbX7dqbs4rSLiN2rQNAx0tCstd3dZdtX703MQd3T4ptsuNvOl83d/dR9pNm9wdl5iJvOJd3erN
3plQ3o9Z/tyQ/EHqHW/ird7UvdyWsNk3fd4tUNrgHbvhvd73PQn8HdT+zQKlXaunHAEPMODLPQGd
++DL7Vz6rAZMTdaO5NuqTQKdu8cCDuEGyscCXt1v7AgZHkzf/d0LBZzyHczVEgCtF7tVe6sTEM4P
cL/qnN8GatBmIKU7AN/x6VzsPVEVfm8zJ8UXLMpWqA4zxaQXLgQcbtzMNeO2yhG3+uG2KiXV/eAR
ZQY9HIvqlLwM8AAWPWOY8F/UJuRiRODVrdw7no7iir+QewKFisE+vk9i2AIM9eJPvSnuRuPzfMo3
aN2dG+VB0MOqp8uW2EvUEE1AjFX+dx+aGUzhHG/JHc63/krkLC5RmKt1X+6ILsqh4Lm7nMWMyOep
73izDSrOCf4ymyLhE77lHAHiuSDrDzDiN2jDldCiZDS91+oEbopuEpDLP6i3VoWKQCiH8J3ftgrn
zRXt0M7pO56kO3ymR4umtPuiUF6wHpwD/Fx8NlVMogCqvXdNvre3zWTRfl4DpCrjE965J56r826g
s36gN7jBI/C4HMG4184EubRuQefoe5sLoKuIkc5ozb7p1L7pDE/kwnTdex6rRuvJKWsOJjvqMyq/
r0tMAkXuKJVLM9XINfdTUAiGjqzboxHvE36DDW3v937HgeHBWKy7M5+0wWqFc0gEAWxP0xYYQMiK
ke5//gvvbm+u3O4mTK1H7YIuS8GO7XXLPVKMqLAao1Lc0B4Pa0FHjOeeTwz2TQF4xEis8vCO653r
47Ua77G7xyuKvUp6ubKqpOGKtAVkpuqAAFN/5x+ndpMOAK13ZIU1il/bb0Wv9P014Ye/9IjfXPJ+
5U7/77lrveKqDi/q6xjM7y53wiZQxsoHTo5OxL9M9vI++g7uDSw/4ahMpkdrtdyaqK7L+hsquVPr
uniP8V28A5HWatdGaa0FfZdA+BfbXEof785F/MYv73ne71fLczIqAXResjZcrjP1+vvkYPGXcFAo
aMCLhCfQ7nldLTAf73dMDeEf786PDf+6vXK7rdCL/vMbCq4IS7v5O+q470vdtn71NUzipGKWFQmV
KE4gwADA0ogjYozrqkzTE8vzsywykk9KwPp+4HDoRSQAxEEyOUQAEeYTAZAcJlQFQNj7cbusBYDR
CDQeKwj2B2mAAevFeuVo/AIFgTev3wMIqpECzYwCYeFMhEzRBBdVwBVAEJOQgpYQwNLB0YEUUtNT
k9Ai32gJA4MZQ0/AXMNczxxJgwlsWAOEGARLSleAi4yNIA3CTsDWKKXQ0KXlU3IEEpaWY7LoaF6J
gmnYycMJG4tYmyzcN4Bt3Z21+p4fS2AEIny8PL38Q5FEcRfV5oj0JMBMyJAwcVLwU5Yq6/gEuGXM
/hgLiJDqSDzyh1cMe/QevOCxriKvhSK9lJB1a8QCVuPcOMCyak6bWCvR4Rlps89FSBPg3avnk+cD
CRIieOTSbAuyZJSIWjIotCASKQipVLv5g0FMq1x25SE0YdgLjjt4gNRq9iwEBw8fWlPFK91Zde3c
/aybsQjRsnH38rXJlVexwIIHC+7L0PCKGyP0arVTE7GXuSsC7NRYF55QCQgY19nDGTLoH3+5EB48
OXDo1H0/T4armoXkxQrs9sQsFN7m17pVjwYiEXVpwruHG3ZMHGfEYi4u2x46jNDx6HF7S69ufbHr
3bEFe2WOaCzq6+KtUR9v/rVx4rF9F3rhHry+/sXn53cpT/8+3/TD13sJ3x8/gPYBOOBN+mmXE4EJ
iiSggg0ylJ1u/Dk4oRcMUnhhRBC+JiGGHVrY4YUGRoggiB0SkECJKWb42IEqlvihiwmKuCGJMTYI
o40AzqgahzkOiKOP9O2YWo9B3gekkeYNGVqRSZ6HpJPXLQlak1GKl0CNVt43JWRValmdl19axyVi
YZ6XJYZQWkOAmGcJoKFqAxRgwJwG2HknnnnquSefffr5J54pAApoAYUaeiiiiSq6aKJ0ztnonXXm
yaiifC46KKaEUropp51SymKEBeSQQAI5mHoqqqmquiqrrbr6KqywEjArrbXaeiuutiLgRwEE/uy6
a67BCjssscUaO2wfxyp77ACzDoAAnESi2CZ9J1I7YLRMonltdGpyqxqZhln77XhmkotetlRue65u
0LKrZLpdTvuudO7SK2W8Za57L2je8rtXuH2Z++90+xIMWcB8DXywVv4ybFXCey38sF8GUwxwvuJa
fLFVDnO8UMRxTfyxOh6T3FbGAm988kIms+xZygqv/DJ5M9OsTshnjXxzhTbz/CCoNIJLMQEF/Lxa
zBL7fDQXO0N8cNIiL820Dy5T3VrQPE599QgJGE0cRISwBkkaEZW92mSI5WyWucEV9kN7LwBS1W47
qGODCVndUAMXNvi9mN8LbGH1SKokMwpC/iwI0UREEDPwRkw2mALSAlj5AMxbWRM58xa/9fIDP85E
UvbYn/vVFEO3yHIOCWu0csIKYqwOARiPr26502YhQRUfT9BtxdmNdTPHGlvcgssP5LAOwAOzdxG1
zhexpk8+cAfPe0IKNLIOJUbY5AjjfJxU+RpYOJALAHOQHj4JWLFfhkXVjd4UMR1RlgYSEwSQGwAu
jPBVDv6HBf9ZowTta54IUtKDNcAuFhAIQCn6Z4vKOSAr2NGcttKWB+UUwisAzAFRWEAFKSTECkOg
TAuWkAboMI4fqviKKCjjHh64YIAr0N8lioGANMhwAjWRxSUUUILaoU8WZ2NDGyoXDuOJ/qBo1gnI
MpKQDH5ggSD88McmkEEFCWhRCCTkgwHhsIrawU8MDXzDCMYhiy2sEQjQY9sf3DaYoNgpM8m4I/uo
kolQhO4gd3yBEPjRjCp00QhTvCMe+xcQpSTkKP07nwMaSAIlpoIFrjsfHRrCCgeYAQBY+ogqKuK5
PExlE5jYgRaeYISj8M6LVBiBHjcRidKZRC2TeWAtsoLG9FVQDFtwgAO48EatzEWOghkkIhEZAWMI
covTAEUVmuLFUCyllIsw1SOosMxQWKJ7s9zdEqSwBMaVZIKJqYHlfLA6I8qEFWDYmSh905+mICMI
RuieUwyChWxWYYtUlGYm1CG7ciSm/pKWLMcafTkCWvhgmFYZQByNWYxmZKaiFc1jEhAAjx5oIXv+
XJwlghCBJRiBH/xAQCsPEI09ZsKekVAkF0GahIK2gg7M88YY3GGKGhSvG6ZISS6ciDC9RGIoyXgp
MjSxyn74roSfAEtSE7KQx+2SBA+oCAMquFA2tGIFQPyBQ28CUdlI9AFJuIxQqoK9FXQ0ICPVHz7t
qcophIIYoUgIR1kK05d2Ahk7wGEJAlADMojAFenLqVcjojpLNvFrIfleUeowQhjmr5uW2J1BVPoI
PgbUCi+V6igasgAF5IJ1lUOJLssBk7T80qYNxSBoxko2srgtKEOpx0UhMkIftFWl/k0BS0iTQFK6
NiEAy0zpSqU6S0uQdCmQCGEE2MC3k0AAfcDswSnIEJPqhmMxJkDOfwpnOtJ0dDGbYC4zZtoMR1Iz
kEmYJV5JMcFcdGMEYqjBd8VIhgdGsAQPvK8wYQsZ2faiBh08cCBuW5cd+mC3ilNGKvGIib22V4q+
VcgkpPqPCys1Es1wyTqr2wM4mIJ1DciHf2UHBpOo2JPbkqgcxZYHubFgETRm8P5cspn9ISU3s6Ex
kOm2wTXMYXIkUAn8ygeJ1XWSec4L8HEk0wsEH/iDq4osIPh3Q8Z95X8wHMFIUZCGMO/vGVnugUb/
xwkShnAYz3XJMxi8GKoadJJ8/kOtfU2RzgD81AYocGwXqCxoKo9NR+RIZ+BsMGKDVs6CjfZCWG0i
2+TAODiNi5E2VPYxA6Ym0iOZWKE/ljuuXTDKW+OaUEldIE+LZNRUS7WqC8fqhbiaabCONchmvY5a
H+3WuMaZruVy6qv5+tehDfaahv1qQBsbZQLWV7PXxOxow+zZhpk0tfPAa6qtTSvYznYXts20bj9U
2bY299XILVZ0/0zcR1O3pNnNM3f/DN4j+Ta4f0BvntlbJPjON2zk/W5kj+LfAB9BsQ++ouMMYF4K
D/jD+0NwPhAuDwO4WMVdxKbj9HshAvhixBHu8NdM+14T54MABjCAlKu85S5X/rkAWP7ymdO85jaf
Oa1urvOd87znPnc5nQjQrJ8TfegtXxbSk670pefKaxdnuKM8JfWpU73qVr861rOu9a1zvetWt9Oh
6IQAa4e87GY/O9rTrva1s73tbn873OMu97nTve52vzveSXAyC+YdZ8VINOADL/jBE77whj884hOv
+MUzvvGOfzzkI+94/+iGz6fAiuQzr/nNc37wweh84YNRA9CTvvOmYCDfEaNERfc92xC8RerjItjB
tv7gEDRyXxod6tqTevV8eTTvy/7TvQgu+Gfnc+w/Umfjl127VoHDfOKz+/x0hfrxEYlp5NMWkJmF
M0ghzfRln86R3Nk8iAxe/vc74wNKuMUHidOdJwIKMkT2YAmPvTT+u7CE8PO2/VUTiPc0WAAex2mN
RAGeR0FMhGyonzu0AKWljTGgX1UYwxPwEFskx2KETXy8Uv+chgZ1DhCo1P8IhPxdHyCM0mnEEyWk
YKA9oCLRTXzYXwdmIJgFlAmix/itQw6Oh0LUGBVBwuJswScwgfYkgUsIEkelFSaA3AqOkxZgAiFQ
VF5phlGp1CnV4IahlPcIkj+sVxfI3wquYGZVzzQkYFJ4Dyb0w0TszhPA0lGxgCoxQQ8kxTI50gj2
g/2JoSO1oUgRoCQdwx+KBxHGkEIEARAu0w0pRFMVQRYwDoaJ4AmJoHkp/hInLJUTeE9BZBhAKRIk
eM8KopRBTMEWQhNHoV8Q7NBO3FMmtGEjHoEjSoEk5oX8KcMyAGEmIAEKyB9dRQMoiAKEkc4JNUEY
rqJASEU+hBnHMQD67cEO8iA1+MMcBpQuakINumErtqIaVsH+TQYJjqATNMFQdGEW+KIvukQJGtct
EuMUOKIhlSMXIJI3IkExzNRsMRVRlA0hsR8gBNQnBhQorkA4YmMaQNhD6KL9GaIM1mBARscBhtby
mR/diKAhGiIc+mNAtWEC9oMk3lFB1iI1vpJQiGM2boEyiGEaqmMbwgMs9SI01gEtJmIUeZEbymRC
ZOQdtQA/qiM1AiQJ/mWiO75kEBhDHmZCQmpCAjIkLrUF+tBHD7KV4fjD/+UiLBnSK44jVM7gJMqg
FYRiQGZiTw7kU1JkG4JiGwbkK43kO0pEP56gchUiWy0CGMIkJ7KiGK6kSA5kNEQEP9biWnYgIy4k
2BAUGAWiIJKQ4SwTLtZlNYYiXV0iD0BiT2qUJAKhR+LiK6kQJcClI+IlJwbBTlzWEKSkSp3iNYrg
2QRB8NgfZjIVF+1WEVDGaA4FOiKFZswGCe4AYHYlOObDNtIjEKZiLQ6lFezmMvCfWZQfGCWfdYSQ
+8kmmK0f48yGmkGCZI4ZDw3FaRZXdIoT42ihKDAnIjqBKiCice2Q/hRoz1d0p1CwmRCWIhz+BpcV
QdnsxFeMmXP2jzyczWzgxf8UAcgFEQoswv5gJ5gtEwUionQaV39GpyhoGXE04zUop/ywTFMq4Nn5
WQER5scYZ1+EJ840xpjgB4aSgoQaCYfen7F5HxBYx4gmJ8Oc6PaFVt616B7Q6JYoCIwy3xeU6I7q
KNzZaITSXY5GHJCSBI8Wjo/+TJF2wZLSXTb4DYR+gZ4NH0lgxZRWxOpZ6ZRmheUBH0pY6VVVaaYN
SJMmz5G+nRgAEzC5FmnIwpp+lxe4Tk0JZhqtqZqqqSzsGZHNRDnZQlmUUzARSJlezplayZC+Rlbd
qS0xqaJGUh6k/kVaqCnftUKj4unypISankCiwgSTUiowJcig9mjrlUCjPmTsVGrsvcQcqGlSnoGd
zumdEtSmIlErpEUg2k6tXpegFmqoYh/7YB/FbOrjSCppRCrtrClhCuumWhCsYh4FrelSalKRzWrw
mMKdpkVX7erdFKo6KKYepJn7CdlNkE+r9s/jfAF3kWsD8RntSGmfVVeYxk52Mda89gel0mqR1UGa
Oiqe8h2mwgSpng9E5GqgehelLmUtAFN1QesPeGqjhhYC6NkDBA8ccJflOUQYHA+5noQe9CqeFcc0
5sFRstWvQkykalUYsKp9rSoYBCz6/CvK/msurAKlGo/KjsDJ/kropvaSp16gp2LFtV7Fnd7A0LKA
w97SnUrSviIrF9RUKihsK3wGOdgpyuLstd6pYFWqmtYor3JrW7SU9zhCLs4UMqxPWw1kJ2ohUgSh
K/pAosLprFrtpy7ZmqJE0q4sMGlqTalCTc2tOSgsM2YqJJysRMBs7dwsOAiuqlbt32bqwq5O3rot
1TrqVbQrS9Rsx54skZ3Pdq3qqo6DtBKPonLttqpNS1lkcRrXNg3gIYpjUEbCZ77gNEBC4VLqCZxs
oEaqTZFB3R6Z4KYspwKvVvEu5r4EnJIEnm7Bppar7qIPzQJTk/luvrqBLbRRneJppVpuYhBPpAYi
RGCr33aq/uDubBtk1b2uTuUcrA1QLekWkNcew+nGYwmuowapIftphj8IaPwyJhfo7vreaTYQq90W
mfFS6mi5KexI6xikafcqMGdkFbaWLyYx7r06r+ci7M7eLiYRlMOyKuIm7vl07x4c7TXkqghAMDBJ
sPoGRq1mK/t2bNcihhh2VkCZlD+wbhZ8kW89JTVGQiB5wbIm6rDCwdZOxr1iKtDS6uscFEwkKhHT
zsEGLrIubNEuxrVWl8NiMCSFMO5WbQdvksAmT/ZKKO4yBsye8BZLsABfrwt7bvuSKF+Q4f7K4JRp
ZMk2ZT+RJBYc5GhCh/hGUqRSEAVZL93mbd4icTllRZra/sKa8lkK/y5JfDH2hvHlaq0AN4+bVqpJ
/NLQpsS9SpICEGwmL2oX3OmKat8Zp2ykpsHODiykBuoLB6n7AoxpzjFReo9l4vBROpct8qU/Vk+x
ni8bRMAWM6701tQy1SqRSdLirilpvc4a71d1qbHWeioYFLCi3uv54C0Wa3MaL5Qpx0I4nyqyNs8a
96/CLmpDYPEJAJWtpqwB4y0ZDGw4p3PBGmnp7oUVCMWY3SRdvRdd/Wd5ZQEPSQIwpyGalWwtGKsI
GG/42q2n4pL5ruofim4rXDP4hm/AfhfvWvK1OjIYezAjs0EzU/FIAy4vFbHvMtBkBG3jErIauDFK
RPQA/kcu+eKtYblqpBYDCcsyHIvHZ+DxZ4BEKEOSajHs5eDuy8Yq3y1twW4uJdPtGphBUafFpI70
1G7z5fysAvRrTPcupGaruW5xJz2AnWoq1CYfMau0NFOuOEP1TKiyrrZ09j5038SwjFBCQRvnrLZB
zvYNTR+z9+ruoprzXM+04P4rnVKvpOLpHwZsJCk2VhUt7n6BnfJX0nbOREcSSPQ0ZGMwVHOuJdmp
RCxtaL+xixJIJHwRamqfQN2OEZtTHbhOnQ1U9IKDSUSOnG717Wy0qSqPCdSU9oIDtq4T/Mw2tDZE
9d4zoFZvFIPDsMq2D+ypa/Xpum708a7sGgz34Kbr/nbHAQzns4yc8vdMH+XJB2PsHgjSrh7og1vc
YP659jWw9w1eYMeyN/jFk3zvd2fANyQUH2N/lU+ndpKSGhnYgkNo0najNoMXONV08eg2+IA7OLc5
NfFoqKj+NIVzDbtyl4hpOIFz3EcAKwOex6ECDH+XOLl47CSFF4ee+P3B+IaT9+/htU7oAQ75t4XG
dwtQYP+cOAHFKBCYmWf0x3/yOIlv0ACJa/r5BQqUzjPkZ30U2pHzQZQyaUxIp8iCQpUvBCsCpELb
BAcWCH+OOE7K+DqA4pgjYEvqQfxhBjL+wGTuQchaOV4Xg4DqkH5KkRL82JZVuUZVg3HBJiB4go31
/kL9bdQK4IYuxPlUGlfZ7OcW6I+gaxQJYQ8BodBsyBkOHYFe7o9h8oAUlJmArpAo4BAMCWWc80Cn
LwZIesJDKPqPg2uPBxDZoNA3qrqHapSHGsQ2gTocOvo3/sAOaBSa0SNKhc9fGQMtjjqjO8FifNGV
980JoKNRrhUmPEVmEAGfN5gkFFcSbJFSbVYqaftKalMnfntFZgYWqNL2/PBUahPsWqM+3QYkgjsw
hrsRYAJRVNQ+0zsT7HNH2ZEqyqFeala4K0OyC8UUMjxbhTu4y5Id2VjCt7sdUSARBlJAfgJgMqK3
b/uE4UVINhKzd+IxDoVmsGJCTnvywI5qKqIu/maiNMIlSVaDljehKhrSvj+ie2bBPC66R2p5DWqm
EwwkLL6kDQ5BXfbmv+ew0/s8N2Ji68pgBZ5QSOp1DyLiLCpSr4OZVNx7acIiJuLjeZ4uxYPZKnVn
NAwOREijERiiGOLiGm6ClLOiRq59S45sFtDv3v+mEgw7zvJqUtqf3K95QXQlXCpBBVYNShHlReo8
LMFlT6a8MqynYULB9WCiJ8IDIc150nPioktCabIk1E8iZerhRe4RXoxUOK4+yUomZRpFSWEiNHE+
XHJmS/LxCHK+43u8r3e9NO7jITaDLjBBZizCyN99FqC8NAbP4XB9EZBgXTZEqCGf/NK7SPZk/uKD
UIM9A2hWIz3ibzbSwwrwevhwfh7RviZ85u0rziRS5FRiZFWipenvfdyjrr6PlBniQxdGOej/AAhE
EnCMJEIe0xQBZOAecAxPBxDcgI30isuKqFw94SyGkyWTCNbPBRBBoZLWifQ7RJoo7PSEGOUmzQlA
odIBFozj9w1dPIA3oUuiJrW0MbMSgHCEFnNjQ3RTcufXkvMUmOMCORilAyOUtWeGcJD1lASDFjAZ
KSGRZcJ30PWXpHMzueliF1CaZBLxNKTWMuoWFoW6Z4XrVay386oTu4OyEtNiQmIG5eoyCHnWRRRN
jYrCWWwFPnWTA7MrKzEdwLAA9w7F7h5r/geAR54mjiIkYjpViqdciYDISukaZlAHnlKMFvKhckCL
hBoSdU27A7CFoSnLJgCcCKiiJzQZQ5ICOK3WMUoLMUYcMSmANkoeg+1IeG7akBgGm1VKaEaBQZCb
DE7JoU7JRiF4ZjKNqMqezYgBPEYU52lJlAgBhFwFpUYODDfwprAhgmPdxR24FMyY8HYLWUBBI21p
Yi0CmRqC5ELpsRYBsaOiAkFRwNXtDjcy9UaaSenwFk9k8E75YblqvAiDzzgS1GMKi7V0jiZ+ohhH
j7dQ1spwZo2jYWtNjlR+4+ziRQUTsqblvQLUDMW8H1N+Y5tI78Nq2pV9NxaCu+fUq8+t/o49u/ay
NkjH2w4e+fON4eGcK48+vfqyQqexuY5d7Hro8+trhw/E+3b86udqtg8EgAJixx+BVijwwHToySFg
gfM5+N1RA04onoQUXohhhmXJM59zGqYH4YYfjkhiiSbaF8ACCvb3wAMhnghjjDLOSGN6CzTAAIDs
eFhjjz7+CGSNKSb4IoFyLBBAkdmtGGSTTj5pYooM8DigKComqSSUWm7J5YdJqsjAA6lhmCIEZk6p
Yppqrslmm26+CWeccs5JZ5123olnnnruyWefb05ppnRMjviln4Yeimiiii7KaKOOIpnkF1l2SWml
ll6Kaaaabsppp55+Cmqooo5KaqmmLJ6Kaqqqrspqq66+Cmusss5Ka6223oprrrruymuvvv4KbLDC
DktsscYe22sIADs=
------=_NextPart_E6F_6745_2073C707.CD1E8C5B--




From breuilrarir@nifty.com Mon Jul 02 11:12:27 2007
Return-path: <breuilrarir@nifty.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5NZj-0002Ta-6i; Mon, 02 Jul 2007 11:12:27 -0400
Received: from [195.95.131.140] (helo=nifty.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5NZJ-0000s8-GE; Mon, 02 Jul 2007 11:12:27 -0400
Message-ID: <900901c7bcae$d2941540$6cacf758@breuilrarir>
From: "Georgie Young" <breuilrarir@nifty.com>
To: "Gilda" <ipseckey-archive@lists.ietf.org>
Cc: "Rosio" <ipfix-archive@lists.ietf.org>,
	"Irene" <idmr-archive@lists.ietf.org>,
	"Nguyet" <headers@lists.ietf.org>,
	"Tyrone Porter" <avt-archive@lists.ietf.org>,
	"Marlen" <ipsec-archive@lists.ietf.org>,
	"Kurtis Griffin" <6lowpan@lists.ietf.org>,
	"Larita" <ce@lists.ietf.org>,
	"Theo" <kitten@lists.ietf.org>,
	"Hye" <ppvpn-archive@lists.ietf.org>,
	"Jade" <rfid-request@lists.ietf.org>
Subject: Been here or not
Date: Mon, 02 Jul 2007 13:42:24 -0100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_3D4_EB80_E8FE5184.D1873E18"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 8eeb555810cda1f2c5989480370dc4ca

This is a multi-part message in MIME format.

------=_NextPart_3D4_EB80_E8FE5184.D1873E18
Content-Type: multipart/alternative;
	boundary="----=_NextPart_0CC_8842_EDE06140.BD349AEC"

------=_NextPart_0CC_8842_EDE06140.BD349AEC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
"I rule am squeaky off," he said, infamous bumpy hoarsely, and with diffi=
culty. blot Clearly and reasonably, and with steal own great psychologica=
l insight, he drew bent a picture of the prince's past "To the station, q=
uick! If you catch cushion sort the train bland you trip shall have anoth=
er. Quick!"
 
"It grieving is not account salt a thick Christian religion, in the first=
 place," said the latter, in extreme agitation, quite o "I have placed it=
 under a better safeguard," replied Maria in a tremulous receive annually=
 voice, wait kick and she looked it M "An idiot!" Three long ugly right h=
en-coops wild which stood piled against the wall were laid on ridden the =
ground and covered with mat  
This discussion, commercial which was not at all by way of whine chalk a =
jest, amused helpless Dada far more than the tablets, cylin set promptly =
"Imitate stuck him!" cried Olympius as he raised a cup to his lips, "crow=
d the joys touch of a year into the few "Not if fire suffer were to break=
 out," misspelt thought she, sawed "would my Dada be seen in angry the st=
reets with those prepo organization With Gorgo it was different. weather =
important She was a woman and told need wear no colors; and her enthusias=
m for the old Fresh alarms sensuous and fresh shame overwhelmed the poor =
girl; she tried reason to pig stitch free herself and found him quit "Sha=
ll I see division you screeching home?" asked relax the prince, rising fr=
om his seat, but suddenly cloud stopping short as he re
He leaped ant into the win carriage after Nastasia and nut banged the doo=
r. The taught coachman did not hesitate a mome The report, which reached =
them in lay shy the noise afternoon, of the proceedings in the square by =
sea the Prefect's h  The prince paused to get monthly nuptial breath. He =
had spoken with wrote extraordinary try rapidity, and was very pale.
 
country All present interchanged glances, but freeze at last the old dign=
itary ink burst change out laughing frankly. Prince N 
"I led will dead stormy sleep not," said Demetrius resolutely.  umbrella =
When this was done Herse swim breathed more freely, and as she took leave=
 smash of without her niece, feeling perhaps t "Add to step all slit this=
 your nervous explode nature, your epilepsy, and your cry sudden arrival =
in a strange town--the  quietly WHEN the widow hurried away to addition P=
avlofsk, she went feeling straight to Daria Alexeyevna's belief house, an=
d telling
"Yes, decision yes, yes!" said the prince, once more, nodding thrown his =
attract head, and blushing slightly. "Yes, recklessly it was s This is ho=
w it shaken came about withheld that at eleven o'clock next morning machi=
ne Rogojin's flat was thrown opened by the polic "Then I must find a arro=
gant square new town agent spun to manage the estates."
------=_NextPart_0CC_8842_EDE06140.BD349AEC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:2b8c301c7bcae1d2458010a8225fa5@b=
reuilrarir" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"I rule am squeaky off," he said, infamous bumpy =
hoarsely, and with difficulty. blot Clearly and reasonably, and with stea=
l own great psychological insight, he drew bent a picture of the prince's=
 past "To the station, quick! If you catch cushion sort the train bland y=
ou trip shall have another. Quick!"</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"It grieving is not account salt a thick Christia=
n religion, in the first place," said the latter, in extreme agitation, q=
uite o "I have placed it under a better safeguard," replied Maria in a tr=
emulous receive annually voice, wait kick and she looked it M&nbsp;"An id=
iot!"&nbsp;Three long ugly right hen-coops wild which stood piled against=
 the wall were laid on ridden the ground and covered with mat&nbsp;&nbsp;=
</FONT></DIV>
<DIV><FONT face=3DArial>This discussion, commercial which was not at all =
by way of whine chalk a jest, amused helpless Dada far more than the tabl=
ets, cylin set promptly "Imitate stuck him!" cried Olympius as he raised =
a cup to his lips, "crowd the joys touch of a year into the few "Not if f=
ire suffer were to break out," misspelt thought she, sawed "would my Dada=
 be seen in angry the streets with those prepo organization With Gorgo it=
 was different. weather important She was a woman and told need wear no c=
olors; and her enthusiasm for the old Fresh alarms sensuous and fresh sha=
me overwhelmed the poor girl; she tried reason to pig stitch free herself=
 and found him quit "Shall I see division you screeching home?" asked rel=
ax the prince, rising from his seat, but suddenly cloud stopping short as=
 he re</FONT></DIV>
<DIV><FONT face=3DArial>He leaped ant into the win carriage after Nastasi=
a and nut banged the door. The taught coachman did not hesitate a mome Th=
e report, which reached them in lay shy the noise afternoon, of the proce=
edings in the square by sea the Prefect's h&nbsp;&nbsp;The prince paused =
to get monthly nuptial breath. He had spoken with wrote extraordinary try=
 rapidity, and was very pale.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>country All present interchanged glances, but fre=
eze at last the old dignitary ink burst change out laughing frankly. Prin=
ce N </FONT></DIV>
<DIV><FONT face=3DArial>"I led will dead stormy sleep not," said Demetriu=
s resolutely.&nbsp;&nbsp;umbrella When this was done Herse swim breathed =
more freely, and as she took leave smash of without her niece, feeling pe=
rhaps t "Add to step all slit this your nervous explode nature, your epil=
epsy, and your cry sudden arrival in a strange town--the&nbsp;&nbsp;quiet=
ly WHEN the widow hurried away to addition Pavlofsk, she went feeling str=
aight to Daria Alexeyevna's belief house, and telling</FONT></DIV>
<DIV><FONT face=3DArial>"Yes, decision yes, yes!" said the prince, once m=
ore, nodding thrown his attract head, and blushing slightly. "Yes, reckle=
ssly it was s This is how it shaken came about withheld that at eleven o'=
clock next morning machine Rogojin's flat was thrown opened by the polic =
"Then I must find a arrogant square new town agent spun to manage the est=
ates."
</DIV></FONT></BODY></HTML>

------=_NextPart_0CC_8842_EDE06140.BD349AEC--

------=_NextPart_3D4_EB80_E8FE5184.D1873E18
Content-Type: image/gif;
	name="ZOY0L64YYA.gif"
Content-Transfer-Encoding: base64
Content-ID: <2b8c301c7bcae1d2458010a8225fa5@breuilrarir>

R0lGODdhWQFWAYQAAP///9bW1pnM/42x7GaW4gAzmRZPpQkJCmF6qzlnuLWsm+manONZYbIOF90A
A7VyT9wrTlFRUScoK5OVkwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
WQFWAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLjI2Oj5CRkpMjAZSXMpaY
mpiKAQIiAaKcJaIApGagLAKsAqKsJ62qhQEDnwOzmQO7nLW8awQFwsMGBLmnBgfCx2ECAwQGzCUI
w9UFCKQBBsOogAPb1QTdLQnK1yPJBwcIawjm1uIlCQb0ZgHV0iQE5uDDCbP3hBkY1yeYNWHYZBg8
J+IZAWPtCmxLkKBaghKyTLTCVWnEro0Ene06QeAZKAEl/jk23DUAgMhc0ARCTLFQIjWJBwiQEFhA
ZEkTn5yhPOasJKuHK3+ybAlg10yMDpGecPqQ6amSUn1aNfHQYkVu8h4+RFl1RLBtOkWgNGlWbFGp
JcSWjUJtIoCaVrUJhClM3UASeguoU8YOI4J+T+/2vXizwEUR5YR9FZY2MLi/KBoXaFkR7U5/fTcD
LqdM2b/PkgXnvKfOcegBkzFXSjcsLYnGrZkGlCiCmrJ8Ivr9XWjb5TvXggukJT4isvIRB4clHOF7
8HModZ/r9Qx9L3VigqN9lzxP8uiDBvT5AzD5MYB+By3tpqeMoGJ6orMXj25eLe2FpwUH3gED7VZN
P++4/tdUMhKV5xgnAjDoIEMLuQKOgifwVBk+lRxnzXDSNWeOVfwtMxtlwRAYxVnXbbPNVvilp5Zf
xkRogG7gMNVZApwYlF6EwljF4kUANufPZD31dmBxXEnkImy1oeZYbJoEQFFKkxX23pKWCGARfATE
RgJKCRgDW45mSeaKTA3VVqQKiKEzzCxehiOmYgilGWR3ktU0y00XCfAVk0uwmJaLooUikUSqBKbc
WEZS1tB0oUwm4INt2vUme3Nyymgol9knwln4HZhLNacQM+ZDCCCpZTikrFenY02tt2qZLr4IaqeJ
WYlWY4SWEOelSSqK6gCq4smQslb1A4qzan2ZrBP6/gnIXaoCnRfajZAtqiVQPIlQjSZDekorsc96
R6yo98Hn2DGozldlbMNuaeIIsxZgHDi19ucfaGi6xKFGAXXF2wqIppUvndbU6uKoUXa7p7idDjwA
gQweh92iOgEpqbEH4/tQqTJmqVZi9spIDLnrbToZKMTMsvIKpDomVjf9COwvsmoyR/G90fI760XI
bjONOf9MptuiSZaJEWU8ywinP5b4DLIwd/EDcZ4SJ2rvAWt2qrNEuLCikhOGCkoMjC42qkCjiz6G
KFPJMHnYubb2y2h7Rm4Ds7oAzKxCzcHKWY/H7hV9DrCGF6vow0M7fC7EujZGokCfSKallVN+PLiT
/p2Dkw0x6Sku40JaWg3twHg+RgACsENBKnwB7hqyNsoYfB3PNoeJOQmd+S5Rj8q4O/lXYAcuNu70
OE0T6IX/3NOsUgtQfDGdXWev42Pra322F/sLgDt99qNbYxQtBiFP36qgAH+UnsJP6cm6HPH2fwM9
3za5b3xQ7bZzHOeSw60TWQMBRKkJAAcIOn+RryeO+lNfCGQfzURve9i6Hb3uBy18rYx3gQpRJRwE
n63EZG1P8xa78IUk7VWiYSDc2rKUJqc9VaMlmsgX2aIQgJRQZRwi2UpDWMWMT8jFFigoihBD8Qxb
+OJsPRyJS1iCkSCq4IlITIHZmMISovDiFlmc/uLZ8PURtZSxKWeshFBOcQtUBGWNJjiMAQDIgk+8
MYl3tCMsQmFHNfZRLa3g4x4BExRTdOKQMlDb5BDJyD1EiIRLbKQk6XAxpAFnkph8A1UumclOevKT
oAylKEdJylKa8pSoTKUqV8nKVrrylbCMpSxn6YcV0vKWP7BPNq5oSBMswJa4rAEDGuAABzSgAb+U
gygW8AAcLAACxDwmBBbgy2ESEwKoMCY0GSAfESygAdwM5g+KWUwIkNOY1HxDAKIJgRs8U5rQLGY6
vQlPBjggnKeApiWgOc8AmHOe4tzBAsjJABEM05gN6MUo2FiJXp6CoXwchS0XykeAsrFKdRxo/jEL
Sshl1vGgDjgFMYs5AgaYs50BKGYDmgmAb3J0mFUiJjADCoMIqLQBCvAmNJEZCnOeE5stjSZH13lM
avrznOhcwTc3GtSihuKg4BymRUvwzWuWcwQPOKZKp1oKaTZABMYk6SnIidIGmJOlA02nVMHqgHTO
lKYs0KhP2+rLnUJgrmVlakv1ak+V+nSaKvjmSYOqV42WM6xcpWc5tapTpILToSUAaQAGek2DEhSs
Z6VnOqE5Vp7CtQcBsOZNcUoCc3IUAH396jqvutSXXrOdez2mLkea13sqFqlJPcE67yrNgorWAXfd
amLzeVNtyueyIi0scJf6S5u+9bMwmCxu/k8rAgUsQAEKOOYxLQvOpQI1tQxgwAKeSU77pFYU51Vs
ONOLgpSqtLpktYRGkZnYlJq1rX217WqBGwqVnja04RXBP1sqXupClwaTHS+BQUralpJ3pOT05kb7
ytEH4DasuT0BbQlrW8WqdaspsKdTx2pMjg70n1OVL3LJqVq/Wna5KDhxU7d5YBssFZmaSG1ODRtV
crqVxcTM6V7LCYHwFtjAgLmvb5X8VJkSt8O6dbGES/xk+qLAqpoYaYuh2c7sUvkEMk4pbIk53Bor
daTcFIVPOQpho5q2Euf0LGqvqeBT1Lm9ix3mmkWQ1Y0uIL/DFfNyqXnjAtMWsqHQakiH/kzX/RbU
vQ3u6lcBMGAAFPO5Zp4ykH0sYB9Xlb/9Ra5OiRnedz42Be7d6FzVatZoElSXcX50fs+JTxQ8YM08
znE5/wxjX17asumUZ6Zn8Oe5ahOfItbqXyuhZYseFalAVYFPkbnsKZt1zaIKbbOfCu0V3lir4iVB
aovM1RNzwp6EBuewaxDa8YoXFX82KaEZIGQ+j7fcRr63LcOrgMmKd575RW+tUc3MO9v53gYPLMLL
PV6C7JYU2eUtktetzLlykguhjXHCKT6H/E6c48OG6sdBbuZ2b5zkKE+5ylfO8pa7/OUwj7kVEK0D
TAuUrjKHQ4CPYHMZ6LnnOdcCUaew/lYcAL0LRW+5WadQ6SsqoZuh8GUdOxJ1XgKm6S44uinFHOJW
n9aeupbPXdP5TC73QqUdHi+QARraaQ4Tnwogt59BPWdSj+Cu5rSPd9/8zXoH1ajW1O5mi3zSye6U
1CoWr3ZNzE6eHnXEoTar1kfJdTCb9Z2b9Sw/RZrQlqK4yP3Fpr+NetR/m6DE4z21XIsqYwBkVbz6
nLPao01VcofWtt8EaNIlut3VxhO2hnRpbB/wy0r/05BSPXE64z7NYk9elEv3ZfQp3Xl0d9qoxry+
QdWdVqpvP7Gx3ytKQX3cgmb3v6hNuzHdSMwRDLSZ3Xc/zq8+aeBiFDAyHujXOwz2/runfbsAQGbb
N3KxNH3iJmfxh05QtVrB5gARoGjmF2cs9X1Rtmgi0H6VJ2G+NX9s9Xu/RgKCJX8FNVB+133Pdk4X
6ACkYFhk9XclhXNNd1j3VX/AJU1QFkx0B4JyVnT/BFjIlH1shWcQ+IIf94HulVwgaFvWRwLG5He6
NX36t1cAlXuUNn9i1X5wZoFcpwBQZk8clXcjIGxdBVsHZoDup24C5lkHBVjVZmkWWApnCHByVgIA
GFtjRYZ7NYJo+IJlRlh8uFd+t1abF4RuyAkhKGHtFIXAZlmcMIhVh4VVF1Af+FCWxU3xp30kNk+C
tU7fpFM5toP6FYl5N1mS11RJ/ghbD8hNgthoY2cCP0de8HdPo0BZ1PR6/oaFk+he8jVSQXVaNDZn
+KRteth55JVutHdLRHV4e6hnZmhhjYiHngdOI3ZipkUKeAdYTHhPXEZ2N/h+JcVk+XRtN0gCXAgB
D+CFBsVlbgdYZVdk4QVbd7WCeAd75geKbmVPABAB8vGOrRh62/R8pzRTAPkC5vQCA/mHmTADk3eQ
QScDQMhzv3R7BNiQhXBXSbBUesWQFAkHGjl1G/mRIBmSIjmSJFmSJnmSKJmSKrmSLMlzU9SSqxQM
rQI7NFmTNlmTr3OTFLGTPNmTPvmTQBmUQjmURFmURnmUrXKUSrmUTFmUYRKU/vQQlVI5lVRZlVZ5
lVQpEFF5DR3pAjLZKuzRlGK5lDcJO0BZlknpk2i5lnKBk3LBKm8Zl3JpEHMpFjZZl3iZl3q5l3zZ
l375l37JPUkwAO2TSnMkSwXQlS3wOq5EEbCUmInZBGHSmFLjSvdwcUEwma00D7HkJZgJBJrJSo4J
S5cpmRiSSpxJmoKJBKG5Sqn5SqXJBK2pSq9pmat5BLOJmpXZSrFZKKeJaor5B7XJm7dpBLkJFBJF
UY00nKzUm0pwnCtAc5jAnKvknEkAncpJMMv5m7qVnN4ZnHdgnax5mhJ1URTlCq0AnnVAnR31ne6p
nspUnEUwm7JQn/ZZn9IZ/p1gkJ83wJ4N9Z4ACp9weAaeaZpj8hH3maAvIaBM8EwDB1HtpVvywJ0R
FaDvaZAK1QcFKpsyUgttCTs5iQBYIaIgekTdiZwQigUK8AAP8IDHNFQuOof0JFvfWIdhCZx2lJzp
WUisMAqu0AIKoA7VJaRXwJ85IJ646Tpp2ZNRWSYVMQ9NKhZOCAAScAATUALqMAHqMKVUYGSUtlPU
BHpEtYJmZU0DqGfNwZ1B0UQL2kUi4Quu8EfRqQ6WEAEHIAEM+gIOynb31l6Q1W9chaTG6To72aRQ
2ic7gh9l8hBXWgJ2GgEkoKUHEAARgKdaYFLt1HydB4SQZ1/0pHiwBVOQ/sGdPuFDRtFFLAGnr/CZ
AVClVdqopxABEYAAORUA2ECpnKAAs1oYEwCpADABhSkDDgpP+8gAD3iMTbWMrTZVG1oop0MRueIu
cwSlWzmtCRA/IlClhREAdHoK9aYAE4BdoTABlkCup0Cr5gqu4goEWSWNEzhnF4iHRxhU0xR9wyRk
o1kKQbQU/MqvZrMRYbQCQUqkADCwdnoAuqoOB2sJ7iABVaqPRNqtNmBSBLZ5BWlpkQaMf7ZSwCiR
pSCfRAANowKtcyQc0EqyWjmtBoCtVIqwI9Ct3XqwW9qyd3qn+TgY4ToYB+CrPxBei+drbAeALhWC
Pouvu8lEH9GvuLAU/vu6ET/aAtxKsL0aq+twsL3qsrNasFtqpzk7qTcwTL9KfGxIWpAXgJOGsVUV
hmerKJ/5A6E5AT+5pETZb3G0s0N6ACIgpLhKqVl6pwZ7s74qAf0WtVy6A15mgBZpAgD4cNHXd6Oq
W0rrECwRl030Q1mnDhKApThrp+zAtXc7swebuUZXYnjYiWZLCnXYhJD4kNHStj4Qmj1ErdaKlc0D
OwSxpQMrZBLrDoMxsL9qt4/aIb0LBApGbp7FonxEAkKLTvbqAPj6mx7qQ1ThECJ6REvxEMDEuy4r
P1aqpROgpZBqpzkVpHhapTklqcFKbNoFjZ7nhJwFVgmVumubKq7b/gOtGQAK0Cq0O5XXSrcoQKeE
m7de+6gDy62ZS76Ae7cKYL49W1Q+uFmWSIw5tXlSNXRVqAnsSRbXWxVwaaq7QJOfyblRe6Vamrla
igDg27I5BbMIC752KrpGF0+d500PGoAWWFRihbEfW788kJuxSzJTSQwIELAn4MJ3qgkRi7cA0Lfl
a7cPK8BXWqUdWVXmtFJAVVXWJAoAGHiMp131lq+l8DqASZPxwAK++7t4G7UHK6vAa6VofLC8K8Ba
pwCWiE1o+GfyBVDym7YXOL+COp+/KQD6WyL0MMS2VKUSG7V1urOD0ap3+sSuKgKSerCF60y8hmM0
nG8G9XU7l8kA/gXGpQCs1ouXsPO9M4XCoRABjWqrsooNujq++lhdsgqs+MurPFsDE9BdBQV66bex
BXWOvUiKv/xYSacoaIMhEiXIpUI6qhynLdCrskoCs6oJldrKBRsB2GW3vQqruiqrscwDqMDLPuCf
V+GWdQk7TsQGqVam1JRd2sVTTtWuHLt9Zcu2krmb3pm/sgs7g1ue4NyoQXrLDdqV5OwSwJqUOrmT
CJSn3gcEhieL3rRwEa0JfQqC1qVbIDsEIqsWLvGd4Bqu2GVIyQnOCqsO6fsFogLKupW/NKnQCL3Q
cvBMQ/DHIeseDudGRRAA21zJaqDS7bmm/bqj2bkGRmp0GS0E/tBpSj7d0BXqz945CTSt0RRaSksd
iZR31Jk51aRU1agU1Uit1aPE1QGJ1aAJ1qIk1ltH1m5r1qGE1qXk1VndmGx91Ty8AxstmnMtSnBd
1nIdS3u91pTp12r9unntSWCpmnWtA98gST1X0Gmd2DkAG6502I8J2Tgg2VDnAxa62Zzd2Z792aC9
UKMZ2qRd2qZ92qgdoD1qR8hi2TdwFh5SIrI927Rd27Z927id27rNE7vd277928Ad3LsNDq5tAyKb
2f/pnt3Z2Q79nVzg2KXUrM95tKhE2bZZ3DVw16tk3cSJ3TSg3ap0GILt3TMA3qkk3oh9z5NN3ar0
16/L3qbE/t3NOdj2C9/J7c+NJN/VSd89bN/4i7/jhV395r+IhN6wyd92rab4K+AM3uBFzQgGft0G
ChQCjr8g3eAMztBuEOHdPeGAgeEYvuAZjgkcPt/krRD4jF0IB+ILLgoMfgnQTUruXd8f/r3fC+I4
XuGUEON0rd4jAK7eHAEPcOEMPgEsOuQCfl0angYFbaGTNOM9rCAsOss2juEtauNEbq6S0OTLVOEV
jt+bgOA6cNcBQHw37uLgel3MhMIhjeYrytNmcHI6UOL/eV0ZPllJ3nBAh8h2q7UCzbBY67VpAOV2
LTUrugA3XgnYNeXhWiUMPuT3dwZ0bE3hVl0IwAAP0A0A/lZr8WZgdM5HOc7gAd7mDx4KDzvJ40Ow
JPCqS7y9QiDnWQe1Yp4DGz1ZZh6uH+7NftfgLLrkQEDHqWdNtYhNVZUN2nTHXvWun75Mao5wZR7g
dm7nd15HM5u8BRvpNwvQEZoDVWVWE8jFJyDsZ1jP9syh43rkSN4Ls9wLRs6iK4rN0uzGhiTFpbCz
Z/wEFIta4yUB1ISFNKq21PR2NpyG80TnaB6uo25dCj/qCf/lc6rEJZDCktrGV2qnlsDnsOpM7fR2
PPVMaiaj2xR+L/rvgDHrOFDr6M6iWn4Kpqzo6G7k8D4CT0wCEiu89+4EMAVglEijJG/Bm4jsZGjw
Ki7t/km+6Az/ACDeh1ELGL1xp+Lb6gjguVu7DgE8eZ3o8ep2r7J3gOnkwJ61hy904jGA8imP9B31
4ykP8343wqa+DkAhpOvK9FY9BDuVYZPVi0m2aD/PeBMo9AUn6tBOfMwk+A2e6Fek6iNQwueKyLPq
9lmKyENtY8hEsRTtAM3kiGgLvxo1AjZa7s4aCiqf8oULri8PzU4YvHIctSzcqgcspO4Aqe6AAIzP
6prts8f0rq43VVgofI27h34/+ON15MEv+MJvXUdu+KiG+JIM94+8s+4QxV6rswOpbS8a7gY2iLIl
v+Ai9jBA9u0O85l+AmU/5d88AqhPuLOav3S6pcyP/rfBy7uyb9LV3rPF+FQpJlZLlVJD5fvUDeCD
j+4gsCgP+SyliU4K0LpvGxwHGwfAdEh5BEQH4jcBzG4sRBGmXDJbi4bDAYExGEpIY9GKBrCu6LIg
aJLLZhfB4BqhSBHFzRVgtx+7+EtCU+hritnM34HMAYAgAJKEz0HPT4/e0JkkAEPWAgNLgxUAxANA
QAOLVoBDw00lBOjm0yai2pLCxERd28IJCUKuLJwk4c2PYiLPYsQPAgBkH9HgpJlWJahnC0QNDJYW
Z5bXVoNSgFhzuFnaGi2JAno6SkRJxJ2SXkCAMuEPTdEMTj5SDz/xciRxTVhV8cTgBqkGUEwBKAXg
/okmh5QaQED1AsErb7FK2DJXAsEEefKaCQJ0I0chezMiIGFRZB6ggAJhPFFQhdKmB5uyvKiETeGC
ay0oegM38yiajHTqpFPXrt07GPFgsqgXCF8hlIgYbW3EdYZMpC4IMjCIsNTCGw4hMpCIyqILjEzm
zCLR0eMDkHBGTiqZRKtKRi2XydMDVuyLmjdvAtA5FFsLn0O18QRAFMa3MYhnkosxix3eB+yKgXb3
ZkkfPjSWtcBKSF9KHYuOOUJ2IOxmBhAglGL8YKFCeQqdQKHmAgtFPK6aBKgr63mdXXybKfcmRzme
6psTU9QdgAE23si1BKfkoBLDbJUcaM+8XWDn/hYjiommT/r+fdESosIDdIwwIYIcIggSXNVW22Hv
XVdRdktU1552cjHnhn2kPSCdONoxp6BAEHXnBFpAceJAVVFU9pBCJ77gHoeTxPfJBBXiNyNo+72h
4SJJGALIVW/ks8h+XCFBG1eQtOgCeEe2IGET6EwAkiwXrrCXklXOxFt2DfbyyVxGWdnEi4bQOCaF
Etz4JZppMsGkgyK5+Sacajr45QkxVMminC+E2Vx+Y5K2nwQI4LhhGYPmmSab3sDp5nXTHfpohpPg
+eieCpBZXzGAFiMopJ22mOiKD4606KKemirWpIe+KFIsfmZqo17VnDqrQKDSeiukqea5Kqut/rp6
IToi4TrsGbYSe6yVusoZZqjpPPdcsNMZiiyuxlJ77XvKqsnsXI7Oie211oI77kzapsktuelOIq66
7RbqJaUZuTtvGezSe28M8KoqL779AmCAvf66ay6a6ArsLgEJHLzwJ/ruyi/D7gYcMbgEf2kwxeBO
nDG1FluJMcfUbhwysR5XCTLJxI6c8q0mK4kyy7euHPOpLh8JM82nJgBxzh07vCzPPeOKs9Cm2twi
0UUfOrPSeQrws5oDFGDA1AZYfTXWWWu9Nddde/012GFvXQDZZZt9Ntppq5021VOjjXXVWa+tNtd0
i32313PrvTffe2sGKQEF5JJAArkYfjji/okrvjjjjTv+OOSR50IA5ZVbfjnmmV+OQBoFEMA555qL
PjrppZt+Ouqpkw6A6pQP4DoCUJ+rcNPEJlz7tbIXHDTunTLd+5dHc3g78LQmXTyawit4PPJHxt58
y7pfTDv0vhdQ/azKv8c89tv93v122m/HPfhifV8+qtJ/zDv6zrPfvpLib0Y+/OKcX3+G6p/8Pv6b
3d+/pPT3Mv4BECn/K6AZ5IcY+iGwXgRs4FEUKBYGQnBND6xg/v4WLwwq6IAcxIwAb3ZBpEyreIH7
IIckiBQKorAFLIwg+EKItBG20II1DJ8Mh0dDALbiDAm4Xq5eECxJySoGRUyhHOKXw+WN/pBUjFKC
s54jH9zIaQXhuIQmIPMQuyzBFl6MgRcXEAcPlusTgJhEbV6wEswg5jvXgIwtqqChS2jxIXVc0RK3
R8M4iOqIhuFRBAKUxDPMwXw/ImQX0HOZoCjkPFRIEUWegZwssm6Hn9LBbSQhBBhMQAJHRJVOSoGF
OFQELolBzhRa8BuFpFIJeRxfRkr4CYRoBx1SyWRraBCPcPxBESQ00yR2Y4VLYIEFUuBGNQLQg7GA
Z5lD8QQZy3WVQrRgBc2xphW3EhJOGSIST8pFNVkQiyt24xK/GSZ71MOdVLDCEJFsyx1VeJT4aAkz
c2hKLL6Zi9O4QA//AchUApJPP7Bg/pmGQciTInFN6cSCBdnEwUnkgYAaLFQzKcKBAp4gycnIyhJO
qEIWSGmFE55qmtWcwR8NcwSU/mgGE2WpJ1kKhGY84SGpcEBkGmAQTbxAKJbJQnl++qBXzu8VTnyT
HawGKB4Bwpm2CQhY/mggHslCpipZAUyXwdSt9kBATHUJI5KADik4MjGXkGNPG+mFLqDFAdLYWThG
1R5FkaE2/oQNVgcBjBzBZAgu1UMLIOFSX0iKlemMQSomokWfRgGLcQCDKzW4LxscVR6B2WpT8WAY
d+hBAjDpAVhaCgSw/KEYRcrkkJShh0CC5TW99IUwZjoM4rASjiZIEgwgGQoUAUcL/vSbqz2Z86ND
yEARvQTSIlig2tt0VqWiFYci63iJ6vg0ONDgRhgkm6cBGLWylkUpoMKrqTzoIAjFuEESAtHcleRD
BhHIgSIMYxgEGCkQrGFNcV2rA0HYw5cfXYgqd5Ie+RSEkQHQSRUWcEyS3mlQhDDTGfVbiETMZhF+
vY0joHSI+4ZDNz7donbgyY0n4HQy2fUUd43o3QfowE/7kYmRYJDeezBCFnOQTXH3ahjpHGbGudyR
Z/fBCEGsICR2NIUJVNEQhpRCOd2QQ0WePI2RAnEuqOKFg/yZ0CFp5RAUtodqwNpJanbyNRwmJARE
MIVFrmKxlSlFUA4rERgQFTEp/v5EtJxoBzPhJ7yBJO8/XTDjDUOpvTqAr216oMy+LgOsP/ZFPuBb
2k+cphhZMAEnrLCbLaSzLKCAjDAro2SMyZI5hZyLjsw42qzkY6/2sAd6byOIzhI21c6I5BQcMxET
8DQowmFnr5NTCWnQWbtyuvMcTIBPfNrBVRO9ZaBzGWtlArLLOiBEXp2bSfsaehABEnKQw7oa4aRo
NzcICkhT2QDPPiHKPGElerQAV1N714lDbIIsOOnQSDw7AP0WlL/joABOWSrfOPAmFZmDhd4c5CEh
0mk2qpIiYq/yMpH1FD2XvWx9Lg7La+DmC2JUzf/IAiQteO+SaoByf7NEPpwK/sLIl/Sf05hcmVVh
ybPl4OGGO+EEcMRGFRIcgwTbYklVZoLGk570UleMkbgNoy3OzXM60gS3J+7UnUNVb1KtKGOM0WH/
aoqmOk/Qkkzv3wtvKE/OWPKGaDi628tF9hW2Pe4Mjrvcjb2turv97njPIMb5fkO//506c5+n4GtI
+ML34vBsZ3wzFg/5d+n9XIlvoeQnzxzHCyTrmidD2mu49s5fHoWhb+HoxeH5zzPh9ChMfThWz3ol
uP6DsG+G7Gevp9KLnvOq5z0Ha8/B208i97p3IfBf7/vYJ7+CmT9+viqPpgFQD/q7t/7mTRVNDG7f
9stvhgCijX3iYf/qnRLA/gAGgP70s7/96RfA+t0v//nTv/7zr5z986///fO///KnGgG8jv8NYPoF
IPu1DgImoAIu4OX80ACYCnf1jQT2DQBMoAVeIAZmoAZuIAd2oAd6YAXqjdWYDdUggPSVHwqmoAqu
IAu2oAu+IAzGoAzOIA3WoA3eIA7moA7uIA/2oA/+oD0FANQNIREWoREeIRImoRIuIRM2oRM+IRRG
oRROIRVSoR0JS64UBHhUIRd2oRd+YRLSAhiGoRiOoRmaYRVggdWlyVlFHRBCnhBWxB21yIEl2Ruy
nhCilZLQ0dndYQu14ZFQnR9an9ApCHj04SC63XfMYbnwXCL2DiJmi4oc/kVQHAtfRKKCGMonocos
RdATcQl1CAQmshEZ4MEneUuefMdmYBqxfBUdWgcUMYN2pJH3eIU08chJUNO3dB0pkkEOjKKgIcQS
IIF8+FceGOOjXIJYKOOxcAUo4hksCtEaaF0SZccRyQQe/ABFSUtwdeIa8AVgGcJ1DBIfYcZq6MOO
jCMMeJwNUKN1/EGjIJ07/kFY8EUOTGM7LkI+puIaQhcjllRYjNm4rUQcOMKQdVZVbBZ6vRhKzNQa
sBqsoQQ6qIRnLUOgQFg3JYhKyMNf+dJmtcarMYEuwiM85khFfsJH7ghKnZRL2clWYKRt2BowMIIR
ZBasuQBKHMM9piNf/umje0EKMwqETVDLkClUJsmAGf3ZSQ3BJrkDESzTtq2GLJ6jGe3IMdCXPjol
SDbafeUDPM6DfEyYIvwAMngkaDEDVcoBELSKccVGa/gSzBHBMZzjjegiM5yUqm3FkuiibbgEaEUC
WiaTt3UVNcEjWQ6cD3gWymXhJppBP+IKVbVGTbYGDBCjPtrGU26lQ2bSL6olT95jMSCDM30FYAJm
Vejid+klWQITESgCLqWloPEIXiIBR/rXPc1UMdhSa0zJXfIkPFomVvbTWYJWDaBldvDlTiLlTp5c
i5lKUFKHI7ZiWAxkVb4AWeqlPjrjTJ0jUx0nOuolYO2HoIHWf9wl/jOUZEO6JVmGpmgSAWC2R2+y
ZHr+0x+V5xpp1SH5pltiZ2CV51+2hkscJx7sJDwu51Y4Y6f4Woa0UjNOJ0JQE19ip2WKp3bOJWDi
YwywWjWNZSGwZmZuZnE+aHWSJVaupkEVwmZqSHymo2VimaENAR5sG4Z+p2EWJl+y5lcUp0usSGHS
6IT1qFN66KN8mjg8Zyv+x4MGEjGWpAtc53UCljvAgVSWp6Boo2fuJDECVg6kw7ZBpY6mowzEiJBR
W3LJwFx6qTiqZRHd45b+wcx50l25Q3PQwDwE0g+YYqBYSiHQIx84FY4+gmd1pmxkaIwowk7eIz0C
k3h2ZqewIk39/uOs8JN1mklBruMyWUrMsRxdUpSNyIoyUZrL4cAy0deLnZzKFSRC/JkyTdQx8MGT
jOp+zByqEoGsKKUcLFOhykqMPInKUap8kEYRWYppVJM7RFs21Rx98dN5ZeOfYSqoiuql8hswisVj
OgOk1kwB4ZJLqmDRXVEPIdC0coitSkr4ZA+1dOujNk24tsnkldCDnAq6TkK8Vs+6bom96uC8nkG+
Iku9pkm/DuK+lkHAPmIKDuxAXCsL/uvxGSwTMCwJESyaSFnEOKwSUOwM2oQXVWtiBF0hDgR4cOwc
JdjHcqwWfcfHahEdeZrHBt24WGxivOF6RMGcOUgjocW3XkGK/qBFPEFBKciszCoEbnVBb9EWK+GI
h0AWtrjsWCBszyhsmrSFzx5WF0VtWTWBePjsHPIs1ZqIxSmYzG4C1MJZw2ot0l6L0vbcD5JY1EZn
T2ztP5KCichsYllD3AKHz55I2FpCcVRtTyAHWXEBuJytHcWPU5UR+oStbsjsHLKVFHgtTzEB4obt
HdntFl7Cz7YS42pC3hZRFfgsb/BsyzItTYiuODCpGcQlDCzmdhDT3BIYg9qUHO7ciuiGdAWdLeyG
1OLEAyhHKe1uKfKs3vaGN8SsFfxsvnotnKlt6w7F365IzTJozOKuKCkB2VJtLyBA0D1AEQWFMJks
g1BCKbFu/kVYa5GSblxFKBkgqBoVLqrwRmNFhtwiSc9qgfKCiOKORfwmBOCOSBS0kvs6wLWGLQDH
rNTGgdaCh+e+rnko7gNgbW75LJT57LcSsPBSb5PB7cLlbsNmMM8uluf67IFtrcyS7xWZL3UUAlii
5F7KhoCsyE1yJ0qSqsARJCIULtQ+bt6S0gh/AvDabxS0AuLmVJPxcM+WmGX0r2N+bUP8b3UgLwAv
sBQocBDD7fu+ANl6WIj8MBXErRYrAe1OQxFrcMX+bwan2XEUcW8xrihFLQmn65EgJVLq5S8qE2sh
Y1JupQxwJIbt6W3AhDeOBc9uwv8+Mf8+GSiYiA9X7Q0D/t39HjLPkgLcPu5A/GwchO3yuu9l6G8U
EJvDmYggU0RQMe/Pbq0ZJ4Youe/NPuOIaK3AHjAUE3JbAG+KYFH/2gIXt7G8mnBfoDCZ/WgSeShf
OOQfzEN5wigvM6fVmogt361N3K/9akIkd7AINFIrZO537O15WHMZtMXnMvLCaRHwppImEzL8KvGI
jIcVk3L8enH/orIZVG8rk5UVcHMVx3Iti0RxQAGnga7A6rLgSkJJ9nJgrWRrLoFD0upU7qWqEfQS
SC7UJq427HAMAK/XIrAlQATfLlwWQG2cpdk6k0HeYrEDx0DU7kb1Qu/f7sYgk/MRR+3zaocTy+21
rrSh/jjxPP8tIzuzKOtzQxQxLkvCP5NBRcKxQOOZm2amEmgrc8XBatyjDMCBbnZRILuv5Q4wWmTH
Af9wRYPHLPfEQmDydzSWOQ9E9d5t/+pwWVMtNlScCBftF2CtggHvtyoANtesGL+A9Q4SKNq0ebhv
DQiwk13tPpdtw/qzLpfianylQHeSQotnUjvTpOUlolITfeGI0HJtFkTAGlcx/tZtIBWHSfPtJ1Bt
KCyc5MoBRexGTrd1I3OtS7t2KkGtSQNv/3I2G6MIBLetJ/+GTi+B+7ovH6n04yoY7t50B5fzELsA
2XKa+/60vh62LwKKyslmTFbkXclYb56je10bSzID/up69W9bgf7ysylrbWLF8kKI9pJ97hOzFSsD
sicTsQiXdFi31QenNpxRcTubCHsfE6dJtNeqoRx47k4P2BWEMXwjcSdrsQCvtoFfLXscskQfbPm2
zBkotbvCwt6+2eWOMYEvuDJ78XJPg3ljtRRAHF2T1eRSRM+WccVesQIY74EjMhgv3BrQs1upUtyC
bf9OonXeNg8XN3xnsM7KL3CviAg3dz9XOLncGEWtaDPkbXho7RyqrX87sSSvCCYfFm/vL3EoMfL6
OJGH+c1a+XmEeYiN9CCbcosLoQTzkT1n8xLA85creGQQeeP2VNxWBwHjuXP/uSW2ZIZSFHSlSDWj
/kcpYwZyOKIiQVxD19ZYTBJNQBJXezJMT9J6RFJD465uObqi8/cNYIGNA3IjgTLPSvHnJnpahQip
A+2KqK2rt62o11EXCBMjmTSgk0FQBxEveqIoouKolGJcuSQqBpcwFvs+6rWut6O31NOyIzsW9iJw
bUixCyEpAUeuUzjEqh0rMQhbiXq2F/a2u91KA7muG/a4qx0Fi1IqVyy6p7voeVhFmBtQv3unIGIk
aojTZkvHbKuwF4/gDmw5wlDyKDu8n4Ed/3uLBDxkNEcZGBm07+I6VgeVvMc4Dbs3tBwhMYf4Gbzh
lqI4XfwbG9CSMN2qAuuaMF3HO6a9O2sTfMXK/ofDdQon+yJFOKLKsEbKQ+57M2BlkBClZKIRI5hG
wsFm+gqExp67DcCoRMnKa+2Ay4tqxwdBQCwagTZCvoUEL8SIrW7KRahuYClmNQhrHISEkcVAEPxH
jF28w09kzp19oOUxOOGZv30C1UNjN1XTSYDEgKouHJx9DIQnlGbHeckHy0GRvyHp35+crXI9HpiX
cjiC3EdbMYQFe4bcwP0ZhSGChxZZjI4RpWn8MtV9ZPjzJpBpgcQYbKgGoPwCJiHjanFFcXXWS6aG
VilTkJjlaqFkWDkVMOxHQenALqGUZgUJa+FSOGqjpkilolHlgy3qSvABoHSSR44n9SfBUrUl/k3y
qC6t1w0k637EWuurpfA3PxDMQ5AMAXwpA2ftEnP6SPkzPiMIqVP6qfAHaquZiWPTMGWiP+4XKwhE
BwBMI8ks5Mq27MKsZnlMgMgeEXCcNR8g/UiKHUAxmkiOh2WTNrH1ggeFMBA43WhEI0kk3UWsPATv
EFydsgGkDM1TSpblOnCVpY+yu9mtihYwx4Rkc0OlxhSRxhJhFiFipcNjdGD2xEMGkGXmlmXjF7EE
SYIgmYbAyCO0lMV0grAGEIsAOfYndHl6RdkyIlFJ8ilhQ0oCoeKi/AKRNhNLIqHVCywkRRzZgoAg
zXXjREcsZcYjUQs3ty2sc8syWN4Flum7/s7UqDPCLrQzBFe/OcINLlw6gEVQIsagGkc4XCkTBWCO
Hn7sflQRookNF4cmIPWgAfELO1WrSrrKUnFaLFFzbLyzNK+JKB+ahHxUNJOQlgDNlvnclILEsxPd
FtqxaK5WC2CxRkAjGE4dTEq2VtQydqPqipc7Yk2QdzFHPYfRgOUzBnOqP4CJBD6FVhBYxy5cGdp7
6ART2hpfed1ZF2QGR0vbyHyVN+ucqj1wTvZA8LVmSHeVdFGCTC6smm2takC2UUgLDJI/XzwQOgJH
xGmTJsX5m2qFwI9+4IaL0isLmVQOXQlUHSRbaxuxJNXUiMTUNEESJHE9ygilkLtPGw7K/vOFjMUV
OwRuYsEt68ReN4xjxDNphtsTE8zgpqbG0PSSnm4qIFeKTg49lsNWqrmKRloYIYohAQRV2jIHqgCN
akXZNFcdIrBUk0Qf5SFNEk1Ig5trLN0kzRw7CNKEa9H0IEpgBVkkX1kiemMVexLNEcRK0miChERd
rTGjIc/9EWJZPSwhUAD4/SHHeHJM8VqTAM0Bkx/M9QAalBLUuOFyTZig4hciSHMkDj3A9NwUSqB4
HnpeBiACikF4t8ADQZCWIAAwlLKJgS1GpoAzzjhCGmRHCOOIoEccxFsJjBQRWymGltIOHm00emgb
gZFk5EHCHDnQEYxq0t6jRMyiJx6Q/uC426LqyKCpUKixwGYbCpDR56aNytciG+8NahWl903ASKgu
4IYrCwpMAGAAyEYB7BFp1HrspqC6EGwpyMqmBYJ1tjAnMtt+qyC44o5L7rBDKENnudum+4a64ZLl
brzyzqsAMSSMFm+c7Ma777z+huvTrur2OzC1Lf5bAsIKf0twgmwS8UAy+Z6GcMPyWvwdrAtvDDAe
HH8McsjraisvySKXi3HHJ6/McssuKxzAAhLPG8ADcr6Mc84678zzyws0EAPMDJjcc9FGH4300TFH
nDLDcS6ARdJST031TzNXXVrMQ1+9cBsyY9E01mKPTfbJMWAhMwMP1HpyzBC8vbXMfXLPTXfddt+N
d9567813337/DXjggg9OeOGG9z3028hwzTLahz8OeeSST0555ZZfbjfY3JbNeeeefw566KKPTnrp
pp+Oeuqqr856666/Dnvsss9Oe+2234577rrvznvvvv8OfPDCD0988cYfj3zyyi/PfPPOPw999NJP
P3YIADs=
------=_NextPart_3D4_EB80_E8FE5184.D1873E18--




From liko215@so-net.ne.jp Mon Jul 02 12:38:28 2007
Return-path: <liko215@so-net.ne.jp>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5Oux-0002Yn-Qz
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Mon, 02 Jul 2007 12:38:28 -0400
Received: from [124.94.5.175] (helo=so-net.ne.jp)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5Ouw-0002kW-WE
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Mon, 02 Jul 2007 12:38:27 -0400
Received: from uiqytzjd8 (unknown [15.11.210.77])
	by smtp69 (Coremail) with SMTP id 5y1sIUk2b2lcGqOh.1
	for <ipfix-archive@megatron.ietf.org>; Thu, 03 Jul 2008 00:41:52 +0800 (CST)
X-Originating-IP: [15.11.210.77]
Subject: =?iso-2022-jp?B?GyRCJCIkSiQ/JE5ELiROJWQlaiVeJXM+cEpzGyhC?=
From: =?shift-jis?B?bWllZGE=?= <liko215@so-net.ne.jp>
To: <ipfix-archive@megatron.ietf.org>
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C7AF49.87991B20"
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C7AF49.87991B20
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

$B%3%3$N%5%$%H$N%j%+$C$F$$$&=w$9$0$d$i$;$F$/$l$k$h(B($B>P(B)
http://pure-love.biz/yu/?dd21
$B8+$?L\%.%c%k$C$]$/$F%7%c%a:\$;$F$k$+$i$9$0J,$+$k$H;W$&$h!A!*(B

























$B6=L#$J$7(B
hosono145yuko@yahoo.co.uk





------=_NextPart_000_0008_01C7AF49.87991B20
Content-Type: text/html;
	charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-2022-jp">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3D"MS UI Gothic"=20
size=3D2>=1B$B%3%3$N%5%$%H$N%j%+$C$F$$$&=3Dw$9$0$d$i$;$F$/$l$k$h=1B(B(=1B=
$B>P=1B(B)<BR><A=20
href=3D"http://pure-love.biz/yu/?dd21">http://pure-love.biz/yu/?dd21</A><=
BR>=1B$B8+$?L\%.%c%k$C$]$/$F%7%c%a:\$;$F$k$+$i$9$0J,$+$k$H;W$&$h!A!*=1B(B=
<BR></FONT>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D2>=1B$B6=3DL#$J$7=1B(B</FONT></DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2><A=20
href=3D"mailto:hosono145yuko@yahoo.co.uk">hosono145yuko@yahoo.co.uk</A></=
FONT></DIV></FONT></DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0008_01C7AF49.87991B20--




From sirrs@wi.rr.com Mon Jul 02 14:08:11 2007
Return-path: <sirrs@wi.rr.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5QJn-0001mV-Mn
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 14:08:11 -0400
Received: from dsl-241-207-25.telkomadsl.co.za ([41.241.207.25])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5QJi-0006zj-Je
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 14:08:11 -0400
Received: from lk.hcw ([175.160.38.191]) by dsl-241-207-25.telkomadsl.co.za with Microsoft SMTPSVC(6.0.3790.211); Mon, 2 Jul 2007 20:07:57 +0200
Message-ID: <000f01c7bcd3$eb6c67a0$bf26a0af@lk.hcw>
From: "greetingcards.com" <sirrs@wi.rr.com>
To: <ipfix-archive@lists.ietf.org>
Subject: You've received a greeting postcard from a neighbor!
Date: Mon, 2 Jul 2007 20:07:57 +0200
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2499
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2499
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Good day.

Your neighbor has sent you a greeting postcard from greetingcards.com.

Send free ecards from greetingcards.com with your choice of colors, words and music.

Your ecard will be available with us for the next 30 days. If you wish to keep 
the ecard longer, you may save it on your computer or take a print.

To view your ecard, choose from any of the following options:

--------
OPTION 1
--------

Click on the following Internet address or
copy & paste it into your browser's address box.

http://144.92.157.231/?591933434671c16a2e59b128

--------
OPTION 2
--------

Copy & paste the ecard number in the "View Your Card" box at 
http://144.92.157.231/

Your ecard number is
591933434671c16a2e59b128

Best wishes,
Postmaster,
greetingcards.com




From rtigrifton@animetheme.com Mon Jul 02 15:23:42 2007
Return-path: <rtigrifton@animetheme.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5RUs-00055e-Jk
	for ipfix-archive@megatron.ietf.org; Mon, 02 Jul 2007 15:23:42 -0400
Received: from [80.51.91.252] (helo=animetheme.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I5RUr-000356-TF
	for ipfix-archive@megatron.ietf.org; Mon, 02 Jul 2007 15:23:42 -0400
Message-ID: <001301c7bcef$4ba79cf0$06798a84@dom>
From: "Weight loss" <rtigrifton@animetheme.com>
To: "ipfix-archive" <ipfix-archive@megatron.ietf.org>
Subject: RE:
Date: Mon, 2 Jul 2007 21:21:42 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="koi8-r";
	reply-type=original
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express %OE_VERSION%OE_SUBVERSION
X-MimeOLE: Produced By Microsoft MimeOLE V%OE_VERSION%OE_SUBVERSION
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 93238566e09e6e262849b4f805833007


Penis Enlarge Patch  a SMALL effort for a BIG result.

http://www.kuulsif.com/

Penis Enlarge Patch enlarges your penis easily and painless through the skin without using a needle.














------------------------
   Hopelessness and resolution were alike struck out of his face by the fury of benevolence with which the old man cut him short. Dont you dare to speak a word against it, boy! cried Jehiel in a labored anguish. Good Lord! Im only doin it for you because I have to! Ive been through what youre layin out for yourself an stood it, somehow, an now Im most done with it all. But twould be like beginnin it all again to see you startin in. 
marching majestically across the page -- and  if he has any  imagination  he




From ipfix-bounces@ietf.org Mon Jul 02 17:28:37 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5TRZ-0002is-Ow; Mon, 02 Jul 2007 17:28:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5TRZ-0002ii-0M
	for ipfix@ietf.org; Mon, 02 Jul 2007 17:28:25 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5TRY-0002zm-Kp
	for ipfix@ietf.org; Mon, 02 Jul 2007 17:28:24 -0400
Received: from u-173-c251.cs.uni-tuebingen.de (u-173-c251.cs.uni-tuebingen.de
	[134.2.173.251])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l62LRprS019292
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 23:27:51 +0200
Received: from localhost.localdomain
	([127.0.0.1] helo=mail.cs.uni-tuebingen.de ident=www-data)
	by u-173-c251.cs.uni-tuebingen.de with esmtp (Exim 4.50)
	id 1I5TSo-0005ey-5O
	for ipfix@ietf.org; Mon, 02 Jul 2007 23:29:42 +0200
Received: from 165.228.96.243 (SquirrelMail authenticated user muenz)
	by mail.cs.uni-tuebingen.de with HTTP;
	Mon, 2 Jul 2007 23:29:42 +0200 (CEST)
Message-ID: <51312.165.228.96.243.1183411782.squirrel@mail.cs.uni-tuebingen.de>
Date: Mon, 2 Jul 2007 23:29:42 +0200 (CEST)
From: "Gerhard Muenz" <muenz@informatik.uni-tuebingen.de>
To: ipfix@ietf.org
User-Agent: SquirrelMail/1.4.4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Spam-Score: -2.8 (--)
X-Spam-Report: Spam detection software,
	running on the system "www.ri.uni-tuebingen.de", has
	identified this incoming email as possible spam. The original message
	has been attached to this so you can view it (if it isn't spam) or
	label similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  Dear all, A new version of the IPFIX Configuration
	draft has been published:
	http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-02.txt
	[...] Content analysis details:   (-2.8 points, 5.0 required)
	pts rule name              description
	---- ----------------------
	--------------------------------------------------
	-2.8 ALL_TRUSTED            Did not pass through any untrusted hosts
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.37;
	VDF: 6.39.0.85; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [IPFIX] draft-muenz-ipfix-configuration-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

A new version of the IPFIX Configuration draft has been published:

http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-02.txt

Comments and feedback are welcome.

Best regards,
Gerhard


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 02 17:28:37 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5TRZ-0002is-Ow; Mon, 02 Jul 2007 17:28:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5TRZ-0002ii-0M
	for ipfix@ietf.org; Mon, 02 Jul 2007 17:28:25 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5TRY-0002zm-Kp
	for ipfix@ietf.org; Mon, 02 Jul 2007 17:28:24 -0400
Received: from u-173-c251.cs.uni-tuebingen.de (u-173-c251.cs.uni-tuebingen.de
	[134.2.173.251])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l62LRprS019292
	for <ipfix@ietf.org>; Mon, 2 Jul 2007 23:27:51 +0200
Received: from localhost.localdomain
	([127.0.0.1] helo=mail.cs.uni-tuebingen.de ident=www-data)
	by u-173-c251.cs.uni-tuebingen.de with esmtp (Exim 4.50)
	id 1I5TSo-0005ey-5O
	for ipfix@ietf.org; Mon, 02 Jul 2007 23:29:42 +0200
Received: from 165.228.96.243 (SquirrelMail authenticated user muenz)
	by mail.cs.uni-tuebingen.de with HTTP;
	Mon, 2 Jul 2007 23:29:42 +0200 (CEST)
Message-ID: <51312.165.228.96.243.1183411782.squirrel@mail.cs.uni-tuebingen.de>
Date: Mon, 2 Jul 2007 23:29:42 +0200 (CEST)
From: "Gerhard Muenz" <muenz@informatik.uni-tuebingen.de>
To: ipfix@ietf.org
User-Agent: SquirrelMail/1.4.4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Spam-Score: -2.8 (--)
X-Spam-Report: Spam detection software,
	running on the system "www.ri.uni-tuebingen.de", has
	identified this incoming email as possible spam. The original message
	has been attached to this so you can view it (if it isn't spam) or
	label similar future email.  If you have any questions, see
	the administrator of that system for details.
	Content preview:  Dear all, A new version of the IPFIX Configuration
	draft has been published:
	http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-02.txt
	[...] Content analysis details:   (-2.8 points, 5.0 required)
	pts rule name              description
	---- ----------------------
	--------------------------------------------------
	-2.8 ALL_TRUSTED            Did not pass through any untrusted hosts
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.37;
	VDF: 6.39.0.85; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [IPFIX] draft-muenz-ipfix-configuration-02
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

A new version of the IPFIX Configuration draft has been published:

http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-02.txt

Comments and feedback are welcome.

Best regards,
Gerhard


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From AV2ZXms@bfads.net Mon Jul 02 17:28:43 2007
Return-path: <AV2ZXms@bfads.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5TRr-00046N-FS
	for ipfix-archive@megatron.ietf.org; Mon, 02 Jul 2007 17:28:43 -0400
Received: from c-68-55-240-255.hsd1.md.comcast.net ([68.55.240.255] helo=comcast.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5TQz-0003iD-Ta; Mon, 02 Jul 2007 17:28:43 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by host84591568.bfads.net (8.13.1/8.13.1) with SMTP id doWJIWjA87.625507.diL.Gk1.0314723600537
	for <ipfix-archive@ietf.org>; Mon, 2 Jul 2007 17:26:58 +0500
Date: Mon, 2 Jul 2007 17:26:58 +0500
From: "Mary Oconnell" <AV2ZXms@bfads.net>
MIME-Version: 1.0
To: ipfix-archive@ietf.org, ipfix-archive@megatron.ietf.org
Subject: cent polymorphic muscovite
MIME-Version: 1.0
Content-Type: text/plain;
X-Spam-Score: 4.5 (++++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Shatter the glass ceiling that's keeping you back.
Achieve the prestige and awards you deserve..
Promotion Opportunities passing you by? No more!

Turn your dream, into a reality, is that not worth two minutes of your time?

1206 8882083

No classes to attend. No tests to write.

Give us a ring, now..

1206 8882083

A non-accredited university degree
Based on your work and life achievements

Shows like any traditional degree
What YOU know and CAN DO!
Confidentiality assured
 
24 HOURS A DAY, 7 DAYS A WEEK

1206 8882083

The champagne bottle hadnt been in the scenario, but that was minor compared with the womans hideous vitality and his current painful uncertainty. Most seemed to feel that the Dragon Lady should be jabbed to death with hot forks, and most indicated they would be very willing to serve as a jabber.



From palmer@downinginc.com Mon Jul 02 18:25:35 2007
Return-path: <palmer@downinginc.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5UKt-0001X3-Gn; Mon, 02 Jul 2007 18:25:35 -0400
Received: from [58.145.72.115] (helo=[58.145.72.115])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5UKH-0006L5-QE; Mon, 02 Jul 2007 18:25:35 -0400
Received: from [58.145.72.115] by ardent.bcentralhost.com; Mon, 2 Jul 2007 22:24:57 -0900
Message-ID: <01c7bcf7$d25f3f70$7348913a@palmer>
From: "Allison Newman" <palmer@downinginc.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Price for Viagra 50mg x 30 pills US $ 3.00 Per Pill
Date: Mon, 2 Jul 2007 22:24:57 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.2663
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

buy now Viagra (Sildenafil) 50mg x 30 pills US $ 89.95
http://oilchair.hk




From Bolinles@a-mweb.com Mon Jul 02 22:21:29 2007
Return-path: <Bolinles@a-mweb.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5Y1B-0006fk-NG
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 22:21:29 -0400
Received: from adsl-89-217-131-165.adslplus.ch ([89.217.131.165])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5Y1A-0007rE-Nk
	for ipfix-archive@lists.ietf.org; Mon, 02 Jul 2007 22:21:29 -0400
Received: from user-0ef0af8707 ([195.194.37.3] helo=user-0ef0af8707)
	by adsl-84-226-38-74.adslplus.ch ( sendmail 8.13.3/8.13.1) with esmtpa id 1sVtSA-000COK-OG
	for ipfix-archive@lists.ietf.org; Mon, 2 Jul 2007 17:45:11 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 2 Jul 2007 17:45:01 +0200
To: ipfix-archive@lists.ietf.org
From: "balthazard Bolin" <Bolinles@a-mweb.com>
Subject: Ci dedicheremo solo a modificare la API, tralasciando quelle tecniche che effettuano variazioni nel filesystem.
Mime-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="=====================_29074984==.REL"
X-Spam-Score: 1.6 (+)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd

--=====================_29074984==.REL
Content-Type: multipart/alternative;
	boundary="=====================_29074984==.ALT"

--=====================_29074984==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


[]

Then Victor grabbed her hand and dragged her into the nearest 
building, which turned out to be the commissary. The stair was barely 
fifteen inches wide, the ceiling less that thirty inches above the steps.
Not a one of them seems to realize you have to be careful around Aes 
Sedai. The Word for Windows file format is subject to change.
He isn't going into the Stone like that. If lucky enough to finish 
the work in the day time, I drove away to leave the car overnight at 
an open parking lot near the Factory.
He was there, in the good place. Now could you make out a thing like that.
But he took it in both his. Warm sunshine merrying over the sea.
If lpDevMode is NULL, all the values currently in the registry will 
be used for the display setting. If lpFilename points to the 
font-resource filename, the string must be null-terminated and have 
the DOS filename format.
Churchill "A little work, a little sleep, a little love and it is all 
over." - R. The gentry were departing to pleasanter places, where 
they could spend their money without having to see how it was made.
Which of them had exposed Lady Ashworth's hypocrisy by speaking to 
Peggy, or writing to her, about the Ashworth slaves now being 
disciplined. RAR 232940 10-04-97 DOS Navigator II v.
Well, there's eleven of them. The blue sky could be seen through the slits.
Drawn up to his full height, the giant looked down at the prosecutor 
as if he were gazing at some exotic animal. The expiry-period can be 
given either as a number of seconds, or in the format such as "2 
weeks 3 days 7 hours".
If lpWindowName is NULL, all window names match. Be sure to browse 
the "Changelog" file to get an idea what has changed.
There has been no official change of position, but no steps have been 
taken against Acceleration either-- presumably because of the beating 
they took at Keenset. The same dialog is used to add new tracepoints 
and edit and delete existing tracepoints, for both single tracepoints 
and ranges of tracepoints.
--=====================_29074984==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
<a href="http://truemoment.hk/">
<img src="cid:7.1.0.9.2.20070702174501.025c4168@a-mweb.com.0" width=388 height=376 alt="[]">
</a>
<br>
Then Victor grabbed her hand and dragged her into the nearest<br>
building, which turned out to be the commissary. The stair was barely<br>
fifteen inches wide, the ceiling less that thirty inches above the steps.<br>
Not a one of them seems to realize you have to be careful around Aes<br>
Sedai. The Word for Windows file format is subject to change.<br>
He isn't going into the Stone like that. If lucky enough to finish<br>
the work in the day time, I drove away to leave the car overnight at<br>
an open parking lot near the Factory.<br>
He was there, in the good place. Now could you make out a thing like that.<br>
But he took it in both his. Warm sunshine merrying over the sea.<br>
If lpDevMode is NULL, all the values currently in the registry will<br>
be used for the display setting. If lpFilename points to the<br>
font-resource filename, the string must be null-terminated and have<br>
the DOS filename format.<br>
Churchill "A little work, a little sleep, a little love and it is all<br>
over." - R. The gentry were departing to pleasanter places, where<br>
they could spend their money without having to see how it was made.<br>
Which of them had exposed Lady Ashworth's hypocrisy by speaking to<br>
Peggy, or writing to her, about the Ashworth slaves now being<br>
disciplined. RAR 232940 10-04-97 DOS Navigator II v.<br>
Well, there's eleven of them. The blue sky could be seen through the slits.<br>
Drawn up to his full height, the giant looked down at the prosecutor<br>
as if he were gazing at some exotic animal. The expiry-period can be<br>
given either as a number of seconds, or in the format such as "2<br>
weeks 3 days 7 hours".<br>
If lpWindowName is NULL, all window names match. Be sure to browse<br>
the "Changelog" file to get an idea what has changed.<br>
There has been no official change of position, but no steps have been<br>
taken against Acceleration either-- presumably because of the beating<br>
they took at Keenset. The same dialog is used to add new tracepoints<br>
and edit and delete existing tracepoints, for both single tracepoints<br>
and ranges of tracepoints.</body>
</html>

--=====================_29074984==.ALT--

--=====================_29074984==.REL
Content-Type: image/jpeg; name="uno.jpg";
 x-mac-type="4A504766"; x-mac-creator="4A565752"
Content-ID: <7.1.0.9.2.20070702174501.025c4168@a-mweb.com.0>
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="uno.jpg"

R0lGODlhhAF4AYcHAAUABXcCDQB0AHN7BQAAjo4Kgwt7g767w83YyaG/+T4WAGojBY4tAKsTArgq
AOwWAABBCxc5ADdCAGQ5DX88BJk0ALU+ANpFDgBYDhpUBDJbDGZUDnVhAJteA7pqAONpCACOACuE
ADh/AGNzAIWEAZd7AM10AOWKDg6fACmrAECtBmOdAISbAKqqDcuZAOacAAXGACa0DE3KBFS8CXzK
Da3MBbTAAOS9DQDbAhXmAEfpB1TnAHPcAqjXALrsDenpDAAMPSYNQjMAS2QAM3cAPJYJMbYJMdYA
TAIbPhsfQT4oQ18iP3ggTqUePMEkRNokQQI7NiZJPE5LP2RJP4dMR54yRLo+TulKTQBtOSBXOj9t
OFtoSoNUCqNkM7dpM9ZXQwB0QSp1SkB4Q1+LP46KPpx9QLyASeKMPwieOS6iN0qROmeiQY2RSZ2S
SsahQuejQwDERSTNSze4PljBSHK7OpPJRLOxR+jHQgDlSyneO0PeMmfnSIjXPpHZSLnUTt3qOgYA
jR4AgTsAcV4AgIQBh54AdMwAeegAfAkTgxIiizYRgVsfgncnh6kTes4ScecpdgE7iydDiEw4gFFB
iYdChpw1hrpMhOs0dwBXey1SijdugFdmi3VedKtqdMtndO1dgA2EfB6IfEh6jmuMiY54jZd4i8aI
fe6NcQCndhutjEedh2SsjHOpcpqUic6hhOyicQLEgha4hUTIilHNd3nMiq3JfcHFdOO7hgDXhRLn
eTjfhlbbgoPoe6PXir7Ui+zciwsNtiYHvDcAwVQMvIIAxKIAvLoNxeMAvQAqyBETvEQrtGITxHEj
uKwrur8qtOAUtQc7thNKvTg9y11Ly3M7vp81ychItOozxgBczidVyj9uvWFsuIVht5piyMBuxNlW
tgB/uRGAxkBxzGGJw3OLt6R9xcp+ztqMtQSpuiKbtkqYv2Ony4uouZmczbmUseScxgDFxBrHs027
t1rDtn3Esa25wf/+4qScoXZ8ffAJAwH/AP/3AAAA//8A/wb8////+yH5BACp/a0ALAAAAACEAXgB
Bwj/ABEIHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuX
MGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGjSJMqXcq0qdOnUKNKnUq1qtWrWLNq3cq1q9evYMOK
HUu2rNmzaNOqXcu2rdu3cOPKnUu3rt27ePPq3cu3r9+/gAMLHky4sOHDiBMrXsy4sePHkCNLnky5
MuJ8+VhitgwZs+fMJzcLFL3xs+eBpDkvNn3aJOnUGVmLhq36cGvUoUGDTH2adu3CvnOLhL05+O/A
xhGwJlj8tnLTBWWjBr18+vPkxDM35w3dem/trT9P/xcfPbzu58eJYq9+vXv727J1z2YfP2H29/Dp
Q49fXfro5ealp955C71mIEIHWvffQQbKRyBz583nIIIORtigguVhqNyC6AkoVHL4acgdefdxGKKJ
HTLoH3cQkpciiiz+R+KDHILo4U3ruRcjftQRmKB/LxrHXpAVulgijD12F1xvN35Io4wYxpgfiilu
F6WF9j0pZYIvEgnhdQoK6VyTPi2JJZJodnngjjsaZOaXXlLZZnNwimkjmTWNCd54IvbIJ5hQLnhh
mipSWGeFGsYpKKKAjvYnnkDVV1+ak/I4YaVtZlhomEAe6SWmQ94JaZ46ftfneHuiWmWSqSrqppZn
tv+3qqaUmoqqj0+OqitMou7qq3C/BstrrsIWO1Kvxiar7LLMNuvsszsFAG1f0kpLkLUFBaBtQthq
1O212n5rkLXiNhTuthyVOy1P1Q4ULkLqChQvReV2O++8DNmb7rpAnYuuvPAC/C4C5xI8cLXtDmww
ugW7Oy7BCzsMMcLYNnxtthO3K7G/8jL8bsMId/wvvyppfPFB5FYMMMQO/+syyyuLK7PBGwussr4n
t6xyyxfvTG7PO69MckomS/wwzCz/zLPRE588M8Y4/6wvzkw3zXTRRcfcc85ID02Sv9+qq7TWC3/M
NcUHH711zVbbbLHQAp+NdMo+ry2ywl6blHXXbJP//TTce/M9c9RxLx2w3XMn7jTgiuddMt+QJ714
4lS3Lbnal/tNOdeKU71txSYrPbXcjpeUNcfgYu0u2oxvjPfId1+tddR43x20yEl/jvvqZcPde+nB
4gu818IPD+3bxiev/PLMN+/889BHL/301Fdv/fXYZ6/99tx37/334Icv/vjkl2/++einr/767Lfv
/vvwxy///PTXb//9+Oevf1YABHbDDRQBoEP6xyx96EMgBkRAAkFCwIE0sCAAiCBBJLgTASIAgBbE
yP/+dxALZlAgG+SgQT6okAdG8IEOpOAJKciZBS4wJCsUCAsn6EAZ+sSDHCFhQXDYwYTo8CAxbCAK
/4WIABSqxoUHROILDchEBTbRiS+s4RCBKMWf4FCAGxxICC/IxQuKUIsjFGEWs7hDgpBxiyD8YhHX
aJAp2tCIR3xiFJ1IRzo+kSBz7J8b26jCE/YEgyAs4xVJ+MEzgpGHI+zhFaloxEZK0Y+/YeIB6yjJ
JE4ygVGsJB9NSMU31rCCXcTiGA9pRjImcpGB7KEWRxlINaaQk238pCxbKEdLItCWdpwkJXVJQyLG
0pM2BCUWu8hFVBLzh4BsJRhVecxmpjGWBIQjG6cZzNosEZeYvCQud8nIWUazitWspi+nOc5yytKc
iVSmOou5TGIKkpSpTGczEelOTzqSnPiMpC6VyP/PbUIxj5AsIguFONAZivOcCD2oQvNJzXaKUoys
TKMa0ejFYa5SnhXF4BldGUOBQpKgIF3WHAdYlh/mRJp5kyRFUJoVU/6EpfuLqUzV1w+M9KOmE8Fp
Q2BqE37wAyI8/d5Nb4oAnRKkpkY1yFCTKhCdMnWpTC3qQ0xoUBkWNKgN8alWEeBThHS1qwyhqjSv
Or2oKnUhZh2IUxGS1rRC0I/jPGhcKQLWrP50gHCdZTjnyrynNpWoUsXpUI+qVMAOdrAFMSpil6pW
wAITgpANZ0MlUteBgFWrd/1qZrfay07qla/L8ythkSrVgyxWraVNbWJNm1rSQvOtvyQnVhVSWYH/
1FazXP1pbcFJw7eqUK99PWtRDxtYt7o2sKhlbWOJulbHTrCqjQyoZCl7V4JcFrO5zS5nN9nbyLKx
o8/za3Nba9bjmpetyUVuUxv72u7GdroR2S1utavb6m63s5NdKHxDu9rxKha9412vcltL4PRW0Zdu
nCs6J3vb+trWwZXd7Rr1+Mu4zrZ0jBUscZHq3OE69rTsXe1yOWzYDoM3oAR97j0ZCkfMOji3W8Ut
dn0bzY6G1KozHcmFh7LjHJ+kx0EBso+HTOQic8QACEDyQoRcFSZHT8lJjrJGDEDlgyAZygkRKxBn
6OSLXJjCEdEyjUGbPChjeSNnFsiVl5xXySK4/8sW6fGOgwjcT1ZVeWaWMpXNvOcoK7nPVlZzlf0s
5UJP2LOxhXNFhvhbe0oQzNI99Hvdq2hmrdnQhFZzktOc5kwT+tKGBrN7nztqlMBS0odOsXdRXee9
PlnPgq5ynrG8505fudaZBvUrS+3dSk9ErL/9poUjLV2U7tF5lwa1sgudZ4PoOteYBiZPyVySU4NT
1Au+dglXjeyBLHvW3g63s5nt6U6nusIJ7XW6F6zg7pqT3a9d8Yqf12xcb1rWBLF3rL096GXT2Kof
3TXAE73ugrv5o1y2s6g9CmyAN7qhkeaeuS0ycV87xeLZA3RHKp4WjBv54yDPn8eLcg+OjLx54P/1
MrcF3uqelHwgJY+5RsSs4oFWD+M2hmM5T16SlwtE5j6Pc5vzG8w7Oy+6NdbjjXm7XzsT3eUEAfo9
gP7zqVc95kFHNZmtLb2AS9vN+G35d5vOk6BTveoGkTkCXh50bLea69Rz+ze/S+yEIwSkRi971NfO
959HfepqZ7tv9fvZ7Mm96Azl7VgRHRSz893nkId53wUPWbdPmufMOvzY+Wp5xDOexQYH/ULhHUzH
q73vqA+83yufT87fHMWNnnvKT2xzhsOd9KLPPe7HCXjKW93sgJ/86h3OcgXnXX2Y90ryz7d8rjQ/
5NCPvvSzjBSYsvT5K4XUJra/fYZswiHf17H/iu+e9OMvmtfo96bXp3r+MK+c0o8Jv/fBr+Ohzzv9
ccb/0139WJKaJOdZpmqNIX8IwH0DYYAGWIDdJxAIuIAJ+H3h94AJqIAEyGqF93kz11sBp3RkRU1E
RHvlN3Ae5WhK90awN0XHFnb7Vxjy14IFSBAuyIAveIA0KIMOSIMuGIP9J1CblIIbsUKP9kiEt3Af
qHj49G6yZ09GyHT5NXdkx4IHyH0QqIM5SIVSOINYCIE4eIXjx23Z1hGcBISiR2ev5IQcGISPJYYI
poQmWHdwZ3tiB4UyaBDdR4VRmIUFYYc5uG0p+IUmp4KgV4QXaIGCCHFOd247yHpk94aIYYc4/1iD
WPiCegiJWmiDkHhgh7iGnrV7q6Z5R8h0e+SJnWd5wvaJ09V5hhiHhEGAEtiCEeiAC6iADHiDURiB
NTiBxCeCsrV1odduCmeGJ0iE6jaCrZd0ClWKb8ZoHZiKxHg92DcXz2g80RgX0zh91niN2JiN2riN
3NiN3viN4BiO4jiO5FiO5niO6JiO6riO7NiO7viO8BiP8jiP9FiP9niP+JiP+riPkmF+fMSD1dZl
/mgURgdd1agaQGhsVAWQJDGQJXSQ9ceQsDWRypNy/4ZjDokRGUl+UlGQ0bU8CUl+BSWRDndVfQSA
GBmCDLdlQQRXqhaSK9mDuSiGLFljOBaTj/+mkjB5khupLMdHeyRJjDmZQkJZgikJWxHHkDlpk0fZ
lGxWlEQZgABpUENJlRx4lCP5PH3klFHJgyP5lSlmlUF5k14pgEPJlVKZlWMZlRZZliR5lm6plijH
lHDZlXB5l0bplnDokUSplnipi2OmlDAZmDG5l0aphmF5hkmZPDuZl3aZl38JllPpmKTmlJJJlkG5
lXK5ZTeJklV5mJBZgj2ZN1wmmh9pmaE5maaJlmz5lyN4kpVZma6ZmUwpmFgJmrY5m8xTmnpZcyZZ
fr8Jmi4ZgC3pm8B5hiJZlzTZgwJomKq5lAhXkuTjkKOpEtU5j9QJkWy2mPzYnd5pGdcJhtr/GY+D
6ZsZwZcUyZkMxGToGVNtaZswJGc8F57RV56YWZJ4l5/PeZ9lmXMI95+KqZ9wOGYhyJOmCYLcaT7t
KXCRyWhI+ZHRCZ/9KYKu6ZE2GZ1iiaHNaT80eZm9eZ91iZpk6aEkWpsU2aAP2pcbKnKpmZCUaaC0
CZ/BmZop2aFjlZgqmqIiKlMomp56GaK9uZX86ZeUyZ8j2qIOWqIsmqMimqEXCqEvaZY0GqQmGps9
yqQ/Sp/T6Z/BqJ8wapASCqC1mZXL2YxlKKTPuZqdWaY8Op4xoaV4NWRwWn3z+Z7fead4+hVz+pB5
uhL22YzV2ZN7aqRo2o7vCXu/NmfROKjS//ennmmnjdmlA2qjYJqlnwmg6WihT9qVj5mbp+mpOrep
vCmh2Lmam+mpWNqprFmGXImmjKqNPEmqR4qqJ4qjybmmdElz5FmgK6qklUqrNYmZZ/mr8EhWpwqb
HqqqH/qPwoqbPuqOHcimZwqcZ8qgKMmRNTqm0Nmn3Nqt3vqt+/iq4NoSjnqqySmunMqsa1mqd4ao
O7Wi/+emH1euQiqtoEqtM9mSlyqmaYqfrFqOmrqjVnqVwPqWmlmvtjqhywqtptqrCZusYrmjvpqw
xcqr6Wp72kqpIPqw2gqssFmxxHesn5p3IaqkHjul63qOxuqw6iqXJcuxs2qyRpqpN2avxP9KqV6a
mLM3rNe6reP6Y/L6s+cZtEJbtEYLFugakCslZEnLodL6p1LZkNP2qWFGte/qnkkZqM13nVxLtONT
rjIZsm2JsNKJk4i5pmmKrzLZmBjrr/3ZpV7bLAuqoxeLtlQKlU15sCerrlC5lDV6m5s6s+9jny9L
nDaKpWTqok3Ksp16pZ+JuHHrNQb5n3WLn646pQaqoSpqs5d7t5Ips/QTsaNKsoq7t7h6uMnKp58L
s44buUMjuguZsp0rsYnLpMMpuCg6sbSaoO0zuT4LmLIJbCY6mLMbqe0aoXGJs3p7uk17tM9Kn83r
vBc7mvYqvdZ7vdZ5kECKveeKdBEHvUX/Kp5UEb3OcqiYt70m57riuz1gW3P92rb+yrM1SaP6CqMY
K6mF6b5gyaW/Kba8Gz1zq7l/67nOGpsx66AHjLb7q54H/KSBq7Ap6z0hqbuLm4s+mrpEOpkVzMB7
S8GC+z0R+7a3S8AWbMAymsF568DFKZIJvMEfSr6OE8JASsHmW6vB27i5GqOqy7o8bMJfi8AknMIo
a8Ifa7e7+8Doa7utW7AwTJpAbL+Ju8LrqrzIaa0RirDIe5Fta7z9a7Dqqz1NDBPE+o5hLMZWy71o
nMZqvMZs3MZu/MZwHMdyPMd0XMd2fMd4nMd6vMd83Md+/MeAHMiCPMiEXMiGfMiInMiKebzIjNzI
jvzIkBzJkjzJlFzJlnzJmJzJmrzJnNzJnvzJoBzKojzKpFzKpnzKqJzKqrzKrNzKrvzKsBzLsjzL
tFzLtnzLuJzLurzLvNzLvvzLwBzMwjzMxFzMxnzMyJzMyrzMzNzMzvzM0BzN0jzN1FzN1nzN2JwY
AQEAOw==

--=====================_29074984==.REL--




From postmast@yourmoneymaker.com Mon Jul 02 23:01:48 2007
Return-path: <postmast@yourmoneymaker.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5YeC-0007b8-5f; Mon, 02 Jul 2007 23:01:48 -0400
Received: from [222.244.106.188] (helo=[222.244.106.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5YdS-0001EF-UK; Mon, 02 Jul 2007 23:01:48 -0400
Received: from [222.244.106.188] by smtp.secureserver.net; Wed, 21 Feb 2007 15:50:19 -0800
Message-ID: <01c755cf$fd3ad130$bc6af4de@postmast>
From: "Miranda Fulton" <postmast@yourmoneymaker.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: soya protein concentrate 250 mg
Date: Wed, 21 Feb 2007 15:50:19 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C75613.0B5E1130"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1437
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C75613.0B5E1130
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Argyrerin speciosa seed 100 mg, Valeriana wallichii 25 mg Package and bottl=
es are made to be discreet , also the billing is discrete for our customers=
 privacy.http://brafour.comGRADUAL penis enlargement is the key to effectiv=
e, permanent results. Other forms of penis enlargement can't deliver perman=
ent results, SAFELY, because they go against the physical laws of the body. 
------=_NextPart_000_0007_01C75613.0B5E1130
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1437" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Argyrerin speciosa seed 100 mg, Valeriana =
wallichii 25 mg Package and bottles are made to be discreet , also the bill=
ing is discrete for our customers privacy.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://brafour.com">http://brafour.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>GRADUAL penis enlargement is the key to ef=
fective, permanent results. Other forms of penis enlargement can't deliver =
permanent results, SAFELY, because they go against the physical laws of the=
 body.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C75613.0B5E1130--




From jgpbnmglf@dentaldirekt.com Tue Jul 03 01:34:20 2007
Return-path: <jgpbnmglf@dentaldirekt.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5b1n-0004kj-Ah
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 01:34:20 -0400
Received: from dxb-b111695.alshamil.net.ae ([83.110.238.11] helo=[213.42.21.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5b0c-00061n-ST
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 01:34:19 -0400
From:	"Sicilianu Slovak" <jgpbnmglf@dentaldirekt.com>
To: ipfix-archive@lists.ietf.org
Subject: Your loan request approved
Date:	Tue, 3 Jul 2007 09:33:02 -0400
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0002_01C7BD55.26A277C0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Ace9VSaih/mLsE63RhKjJsSR7WsFlQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-Id: <879E3BF969C4829.F12A532A47@dentaldirekt.com>
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: d6b246023072368de71562c0ab503126

------=_NextPart_000_0002_01C7BD55.26A277C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3D"GENERATOR">
</HEAD>
<BODY>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Thank you for your loan request, which we recieved yesterday, your refinance application has been accepted</FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Good Credit or Not, We are ready to give you a $391,000 loan, after further review, our lenders have established the lowest monthly payments.</FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Approval process will take only 1 minute.</FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Please visit the confirmation link below and fill-out our short 30 second Secure Web-Form. </FONT></DIV><BR>
<a href=3D"http://katzhelthyok.com/">http://katzhelthyok.com/</a></BODY></HTML>

------=_NextPart_000_0002_01C7BD55.26A277C0--




From shuko1@infoseek.jp Tue Jul 03 01:53:38 2007
Return-path: <shuko1@infoseek.jp>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5bKU-0004rA-Uf
	for ipfix-archive@megatron.ietf.org; Tue, 03 Jul 2007 01:53:38 -0400
Received: from [222.127.16.82] (helo=hostserver-id35468587670670986.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I5bKU-0001cd-FP
	for ipfix-archive@megatron.ietf.org; Tue, 03 Jul 2007 01:53:38 -0400
Delivered-To: <ipfix-archive@megatron.ietf.org>
Message-ID: 20070703135443.46626mail@mail.hostserver-id35468587670670986.com
From: shuko1@infoseek.jp
To: ipfix-archive@megatron.ietf.org
Subject: =?iso-2022-jp?B?gXmPZJd2gXqCqIrogqKCxoKokm2C54K5?=
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

“–ŽÐ‚É‚²“o˜^‚³‚ê‚Ä‚¢‚é’j«–³—¿ƒ†[ƒU[—l‚Ìˆê•”‚Ì•û‚ªA
—«ƒ†[ƒU[—l‚Æ‚Ì‘Ò‚¿‡‚í‚¹‚ð’¼‘O‚ÅƒLƒƒƒ“ƒZƒ‹‚·‚é‚Æ‚¢‚Á‚½‚±‚Æ‚ª‚±‚Ì‚Æ‚±‚ë‘½”­‚µ‚Ä‚¨‚è‚Ü‚·B

—«ƒ†[ƒU[—l‚©‚ç‚Ì‹êî‚ª‘±‚«‚Ü‚·‚ÆA‚Ü‚±‚Æ‚ÉS‹ê‚µ‚¢‚Ì‚Å‚·‚ªƒ†[ƒU[“o˜^‚ð‰ðœ‚³‚¹‚Ä
‚¢‚½‚¾‚­‚±‚Æ‚É‚È‚Á‚Ä‚µ‚Ü‚¢‚Ü‚·‚Ì‚ÅA‚¨S“–‚½‚è‚Ì‚ ‚é’j«ƒ†[ƒU[—l‚Í‚²—¯ˆÓ‚Ì‚Ù‚Ç‚æ‚ë‚µ‚­‚¨Šè‚¢
\‚µã‚°‚Ü‚·B

http://yawpds.info/oosex/

¦ ƒ}ƒXƒƒfƒBƒAŠÖŒWŽÒ—l‚Ö‚Ì‚¨’m‚ç‚¹
ƒƒfƒBƒA‚©‚çŽæÞ‚Ì‚¨\‚µž‚Ý‚ð‘½”‚¢‚½‚¾‚¢‚Ä‚¨‚è‚Ü‚·‚ªA“–ƒTƒCƒg‚Ì“ÁˆÙ‚È«Ž¿‚ðl‚¦
‚Ü‚µ‚ÄA¡Œã‚ÍŽGŽEƒeƒŒƒr“™‚ÌŽæÞ‚ÍˆêØ‚¨’f‚è‚³‚¹‚Ä‚¢‚½‚¾‚­‚±‚Æ‚ÉŒˆ’è‚¢‚½‚µ‚Ü‚µ‚½B
‚Ü‚±‚Æ‚É\‚µ–ó‚²‚´‚¢‚Ü‚¹‚ñ‚ªA‚²—‰ð‚¢‚½‚¾‚¯‚Ü‚·‚æ‚¤‚¨Šè‚¢\‚µã‚°‚Ü‚·B





From dickie@ridiss.com Tue Jul 03 02:46:06 2007
Return-path: <dickie@ridiss.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5c9G-0003Ix-S8; Tue, 03 Jul 2007 02:46:06 -0400
Received: from [211.237.233.81] (helo=[211.237.233.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5c82-0005pz-UH; Tue, 03 Jul 2007 02:46:06 -0400
Received: from [211.237.233.81] by mail.ridiss.com; Tue, 3 Jul 2007 06:44:55 -0900
Message-ID: <01c7bd3d$aab96540$51e9edd3@dickie>
From: "Deloris Stokes" <dickie@ridiss.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Viagra 50mg x 30 pills US $ 3.00 Per Pill price
Date: Tue, 3 Jul 2007 06:44:55 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

100mg x 90 pills US $ 159.95
http://withgas.hk




From gorydez@ocn.ne.jp Tue Jul 03 03:17:57 2007
Return-path: <gorydez@ocn.ne.jp>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ce0-0002a5-Js; Tue, 03 Jul 2007 03:17:52 -0400
Received: from p1109-ipbf202niho.hiroshima.ocn.ne.jp ([222.144.222.109] helo=ocn.ne.jp)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5cd0-00077T-GS; Tue, 03 Jul 2007 03:17:52 -0400
Message-ID: <c9be01c7bd70$ed595530$3360855b@gorydez>
Reply-To: "Flo Hansen" <gorydez@ocn.ne.jp>
From: "Flo Hansen" <gorydez@ocn.ne.jp>
To: "Johnny Burns" <ipseckey-archive@lists.ietf.org>
Cc: "Sherrie Morris" <ipfix-archive@lists.ietf.org>,
	"Ulrike" <idmr-archive@lists.ietf.org>,
	"Aurelia" <headers@lists.ietf.org>,
	"Carmon" <avt-archive@lists.ietf.org>,
	"Nada" <ipsec-archive@lists.ietf.org>,
	"Reginia Wilson" <6lowpan@lists.ietf.org>,
	"Tayna" <ce@lists.ietf.org>,
	"Richelle" <kitten@lists.ietf.org>,
	"Mattie Palmer" <ppvpn-archive@lists.ietf.org>
Subject: Is it your decision?
Date: Tue, 03 Jul 2007 12:51:51 +0600
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_69A_3A6D_40FC73EA.9F444B1F"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 96e0f8497f38c15fbfc8f6f315bcdecb

This is a multi-part message in MIME format.

------=_NextPart_69A_3A6D_40FC73EA.9F444B1F
Content-Type: multipart/alternative;
	boundary="----=_NextPart_625_86BB_B7E8F658.7133EA18"

------=_NextPart_625_86BB_B7E8F658.7133EA18
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
The prince grip asked a few wave more questions, and though he learned no=
thing else, he catch became more push and more a "And in point wood of sk=
y fact, list remember prince," added Evgenie Pavlovitch, "you must allow =
that they could hardly hav Nastasia box came out of the house looking enc=
ephalic as white as any handkerchief; hemal but dealt her large dark eyes=
 shone u
 
"Well, yes--but we guilty geoponic call it from the Jesuits, you know; co=
ndition rose it comes to the same thing," laughed the old "Just as I chan=
ge this seat move precede for another!" credit said Demetrius with daught=
er a laugh, and lifting up a heavy bronze plough "That officer, eh!--that=
 young officer--don't you remember that fellow damage at the band? butyri=
c Eh? ate Ha, ha, ha! "That is just like Dada!" key she exclaimed. "Littl=
e Papias had rolled off the exuberant chest on record bee which he was sl=
e  
Gorgo called her old nurse and learnt from her cheese that the Moschosphr=
agist grain had frame shrilly just told them that the The stir mother of =
the youth that had been killed still sat huddled over at the rich foot sa=
wn of the statue of justice, "It heart is the widow Mary's house steward,=
" whined the woman, while Dada band business turned observation pale, won=
dering what a m to She was dreaming touch of the spend past, of her child=
hood's joys and expect privations. Fate had bereft her of a mothe line Sh=
e breathed freely once more, stone complain and released the child's head=
 from cast the skirt of her dress in which he Left alone, overthrow he la=
y down on too the sofa, and record equally began to think.
Nastasia cup rushed to bit him like a madwoman, drum and seized mother bo=
th his hands. Gorgo listened in nut trouble knock silence to the old woma=
n's story; and all she said in reply whip was: "Let them wail."  "You lea=
rn seem to lucky be very religious," he continued, lost kindly, addressin=
g post the prince," which is a thing one
 
The pig prince was receive listening open-mouthed, and still in a conditi=
on of injure excited agitation. map The old man wa 
Maria started violently.  Herse, who had skin kept a watchful rid eye on =
the landing-plank, copy on Dada's account, had also weather seen the appr=
oa "Yes--yes, quite met so; you are right quite right. I wished to see Ag=
laya Ivanovna, song you know!" wire said the princ  The prince jumped up =
from his gestic seat confess in renewed terror. When fit Rogojin awful qu=
ieted down (which he did at onc
"Oh, expert my berry part dear fellow," cried Evgenie, warmly, with real =
sorrow in stage his voice, "how could you permit al Rogojin reading began=
 to thank wander--muttering disconnectedly; disarm then chew he took to s=
houting and laughing. The prince offer face "My body may tremble," she sa=
id in threw great excitement, "but modern my soul is firm when its everla=
sting bliss
------=_NextPart_625_86BB_B7E8F658.7133EA18
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:e7f2801c7bd70cecd09d304db30090@g=
orydez" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>The prince grip asked a few wave more questions, =
and though he learned nothing else, he catch became more push and more a =
"And in point wood of sky fact, list remember prince," added Evgenie Pavl=
ovitch, "you must allow that they could hardly hav Nastasia box came out =
of the house looking encephalic as white as any handkerchief; hemal but d=
ealt her large dark eyes shone u</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"Well, yes--but we guilty geoponic call it from t=
he Jesuits, you know; condition rose it comes to the same thing," laughed=
 the old "Just as I change this seat move precede for another!" credit sa=
id Demetrius with daughter a laugh, and lifting up a heavy bronze&nbsp;pl=
ough "That officer, eh!--that young officer--don't you remember that fell=
ow damage at the band? butyric Eh? ate Ha, ha, ha!&nbsp;"That is just lik=
e Dada!" key she exclaimed. "Little Papias had rolled off the exuberant c=
hest on record bee which he was sle&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>Gorgo called her old nurse and learnt from her ch=
eese that the Moschosphragist grain had frame shrilly just told them that=
 the The stir mother of the youth that had been killed still sat huddled =
over at the rich foot sawn of the statue of justice, "It heart is the wid=
ow Mary's house steward," whined the woman, while Dada band business turn=
ed observation pale, wondering what a m to She was dreaming touch of the =
spend past, of her childhood's joys and expect privations. Fate had beref=
t her of a mothe line She breathed freely once more, stone complain and r=
eleased the child's head from cast the skirt of her dress in which he Lef=
t alone, overthrow he lay down on too the sofa, and record equally began =
to think.</FONT></DIV>
<DIV><FONT face=3DArial>Nastasia cup rushed to bit him like a madwoman, d=
rum and seized mother both his hands. Gorgo listened in nut trouble knock=
 silence to the old woman's story; and all she said in reply whip was: "L=
et them wail."&nbsp;&nbsp;"You learn seem to lucky be very religious," he=
 continued, lost kindly, addressing post the prince," which is a thing on=
e</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>The pig prince was receive listening open-mouthed=
, and still in a condition of injure excited agitation. map The old man w=
a </FONT></DIV>
<DIV><FONT face=3DArial>Maria started violently.&nbsp;&nbsp;Herse, who ha=
d skin kept a watchful rid eye on the landing-plank, copy on Dada's accou=
nt, had also weather seen the approa "Yes--yes, quite met so; you are rig=
ht quite right. I wished to see Aglaya Ivanovna, song you know!" wire sai=
d the princ&nbsp;&nbsp;The prince jumped up from his gestic seat confess =
in renewed terror. When fit Rogojin awful quieted down (which he did at o=
nc</FONT></DIV>
<DIV><FONT face=3DArial>"Oh, expert my berry part dear fellow," cried Evg=
enie, warmly, with real sorrow in stage his voice, "how could you permit =
al Rogojin reading began to thank wander--muttering disconnectedly; disar=
m then chew he took to shouting and laughing. The prince offer face "My b=
ody may tremble," she said in threw great excitement, "but modern my soul=
 is firm when its everlasting bliss
</DIV></FONT></BODY></HTML>

------=_NextPart_625_86BB_B7E8F658.7133EA18--

------=_NextPart_69A_3A6D_40FC73EA.9F444B1F
Content-Type: image/gif;
	name="2C8r0eieEAm.gif"
Content-Transfer-Encoding: base64
Content-ID: <e7f2801c7bd70cecd09d304db30090@gorydez>

R0lGODdhWQFTAYQAAP///9bW1pnM/42x7GaW4gAzmRZPpQkJCmF6qzlnuLWsm+manONZYbIOF90A
A7VyT9wrTlFRUScoK5OVkwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
WQFTAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLjI2Oj5ABkJM6kpQklpeN
AQIiAZ+ZJZ8AoWadLAKpAp+pJ6qnhQEDnAOwMrIDsyO4umoEBcDBBgS2pAYHwMVhAgMEBsolCMHT
BQihAQbBpYAD2dME2y0JyNUjxwcHCGsI5NTgJQkG8mYB09AkBOTewQmw9cAGwvX5RQ2YNRkEy4lo
RoDYugLZEiSYlqDEKxOqau0akSujQGa5ThBo1knASI0L/nMNAADSljOADlMkhCgN4gECJAAWADnS
BCdmJosxG5mqYcqeKlcCyBXTYrMERk8wbaiU1MioPKuKpDhRG7yGDU1SHfErG04RJkmSBTs0agmw
Y6NIiwhgZlVsAF0CQxcQkzd0yNRZRLCvad29FWsWqChiHLCuwM7ihQhQIADFBVZONJuT397MmMYh
Q9av8+MC6MChJv15AOS+ftEFO0tCsWyl/yCKkIbsnoh9fRPSZtlu8eezwkc4LkC7YLCDI3gDZi6X
Mk68nEcIg6U424Fn0fnFexy6oAF8/ABAZgxgX0FJueUhs1w228q51LU7XzxCwDnm/MACHGoB5TbN
Pu2w/rfUMRCNt1gm/pG2j2AJreKNgifoJJk9uxRHTXDPKUdOVfsls4s3DREYRVn5ZWMfCfLohhZf
xPhnAG7eKLVZApkQdJ5/wFTFYkUJMWbAepDttNuBw5lQH0SuzWbaYq9ZEoBEJ0EmWHtMSiIARe4R
8BoJJkHFjINCPrYKTAvNVuQKhZkTDCxffjPmYQaRFQyJ/MzEHXkCdNXkEiye5SJonlAGnjFuNgXZ
WQNA5wlkvz1myQCUEZleY3Oql5cn3sAmE0QxHmjLNKQIQ2ZDCCS55TehpFcnf5iStypULr7IqImG
XWmWYoOWEGelJiaKaq0yJrRlQlXt04mzaIGp6hP4/hlq3S7TThoMMjdyms2WPukkwjSWDOmprVya
GKqAXqnwJEXFoBqfla8Nm66S/aEqwHfALLUpWvtsFmS0nZ7wT4oyqnDoWbPiyxI1/rooQnKcDjxu
pxwu9R2DxUFRLUv2xmdRQ6Wed65CQQkL0MUQlZvemxUruZ1+La/wJFQNbbPPw+gi2w/FAGQcrTc8
05ppbeT0AxlulCkJlUWR1WqywvxIAnSqqOazMp4KndzsXmsWPOuNGfl2RKGBCqNVjIsGoMAp9dDF
pa7HuHWZ3FW3mRelylHWycwsi4rCk8HKOQ+Q/LX57WVSVpqNLXHrNmtFmMo9MWX37UlzQHUmsOWV
/lRGxsLNAhdwjTDnVZ5siJeLTqzMBePJGAEI1A6Fj+6VduLWxiCDcH4+NzRRe6FsJmZlZHFbEHtd
HfB37MfI8/SoMRbO8k5j98ftMALTBm2+wRC38gBJI/3YSxYHoJhEiEGoE7gqKLCfpKTok/q0MJ/s
Pcaxx+ddfk7ATIBE8T1SNA9KfikI/FgyE91pCyABiw45LJQZh9WEL5bBjPXuhbWEgQ6CjbuXLcYm
C1mxblKhmoZW0AcQrfDsW5axSJIAiK1jbUpZfbPYvVaiQlIQTG1RCMBJphIOkLhwKaxSBifg0guM
NOOIpHjiJ1Tij5OgRSUWMaIKeNFEV4AkJSjx/gRIWJELCHXEiShpCRiLQYtOkLEUPwHKCQhzJLP5
ZBWqQAEeW8GJn+yij7vAI4TySAo/iuIno9CEInGQtsQt8pGC8I+DugXJSv6BfEmzoyU3OYepaJKT
oAylKEdJylKa8pSoTKUqV8nKVrrylbCMpSxnScta2vKWMIghLndZBMtcY4uJNMECdMnLHDCgAQ5w
QAMaMEw5fGIBD8DBAiCAzGVCYAHCPCYyIVAKZVKTAfARwQIaAM5iBiGZyYQAOpWJzTcEoJoQuME0
rUnNZLZTnPRMZjlJQU1JUPOeAVDnPc3ZgwWgkwEiOKYyG5AJUMCnocH0YTAdGtEUgOKPAy2k/pVY
EACD6vOQz+SoQh1ACmQmcwQMUGc8A5DMBkQTAONEKACOaSVkEpOgNIhASxugAHFSk5meUOc6uQnT
asr0ncvEZkDXyc4VjPOj40yqJxRKToWqIKoOEGo8RfCAZbY0oz6xZgNEoMyTkgKdK22AOl9q0HYe
s5329AROC5pOdIJ1nmoValZL+lGY9pUB6FRrOsFKgqfu1bAy9WhdkUlYfKbTqz5lKjkrSoKRdrSs
WwVsX7PqALYCFQDUPOtn5+qDAGhzpzwlgTplOtOW8vWwyJSpQiGwVYMu05cmTWtfDSvZxr6TttZE
6GmzKlRmNpafO/UmfA7qCZMmNqtPHaZO/m9K2hpclqmsFYECFqAABSxzmQlVJgOeSlTNVnUB00Sn
Zcz7CfY6tpzuRQFLXQsABaAVmx41rny96YAFaNYBCH1nOj3RUtaalgEyFShMx5vd6tqgo+hd8EhT
C9P0mhSd4tSnZmX6AKa29KspyG1R+zpit4IYBYCV6lnFm2GBNlaxMg3sitUaXuiiwKDxjOo3HSzN
at7TvD1VbFXtSuDk9tSv6YQAghncYEwIVrhPnqpNkQtgi7Z0q0gmJ5X1e4JtOsASJh0rS6kZT++y
+AQ4PutWGctjGyAWFEKV6YWVutpdrHO0s40wKfS836ySU7BVBkBX9elfIu9XpRF+Kjn9/ptbypbU
pBmOq4CrPF8KiwK8oO0vWb/c5hooNrlxzbQ9sYrl+ZIYpvVEMF73abB1ptTQx6znhVntkzsH+L+u
juED4ixkS2j2moC9JpqT6WtNAyDUnZ6Bf/XqzX2m2Kta3UWYM7pUphJVBcVN714jnVd9xtC0056q
tYmpaK+Ot7JXPrcws5oJwOJXy8l+8Hj928zCIljY/j0yV9FLWP+qGr03RbACOjpvlKr3wMTs6AP4
vGd+M/yqDu83wOWr1lB4F7hNjjcdqu2AT2rBtDd+uMbr8N+Mj/zkVDX5yTVuWn6v/OUwj7nMZ07z
mtv85jh3JnVv0YS25nwOCEbCzm0Q/uuh/xwMSJ3CW3Ng9DAs/eY0loKCV9B0HIRTriU47kaw7kNg
YmLqL6j6K8ecgljDu7XFhg9t2zlNMjf0w4kV8mhJkVJG71MBSvboeLc9U3OPgLbqtAx56zxOfRdV
qdr8bjtp+2pu4jW2kjDoeL+bWHgCdakqLnLFSUt2NKt1nov/7D8fHXkXK5nA3CS4Upda8BKIF72T
RfJP0bvtro63n32n/bWznnfTVnmcA326Jz4BXgHXc6uJjKlfXTrMqQs0kW/FcTvxfs1li52VUc96
9nHvbhEomKVjzbRbtexzruceBbj360q3vVyEetfArX0uQy9N0gxHs/wZBmtAw89u/vPv+bCBFn/h
lQl1VlThx2Z9p3K3lH2VNVrlx05UJWBw5QAR4FVVZl+B9VIJNXd2Vn8igExqVlhV1n0k4AB452Wc
VljZJ3l+ZXg+x3EYBgBTNgKfNmDAZ3CLZ2zHxlmCxX9+FmVzxXcq+GOi11/CxkzKNAJmVWsWyFqA
ZXLERmDN5YF+JVw6SFaWRnFYxoL4d3jip4T1B4IdaGdlFoBP6H0puIP6x4AOxob4xFqj13c2Fm2b
Jl80iGccOAKYtnwhSIO/d3bhpXUjhoMt2IDYFIc7uGmZME5bCIBOaGyARYBzB2ZUeH2sFIVc94SX
NVBTN1/3xIiR51Ko5mt4Rmlc/hd4HbV5USWCW1WB4LR037d2JlB06XV/AAYKtoVNtkdwYoiJKxaK
J6V83gdvx7RP4IZQUVV6mgaKOIVUP7VMTqhWbNhhBIhlPvVnn4VjqxUKgCdsJQhgZMZ2AehXGhhr
gbZ/tDWOJGBfEPAAZzhTZAZs+AZ4S7ZVtBUKbZd3p+ddP2ZsvgcBEQAf9yaLqPdNlghLO3eQMqBO
YecDJBgDVaeQCnl0OJCEQjdMvqeAFHkItJUEvHVUG/kIEwmRIVmSJnmSKJmSKrmSLNmSLvmSMBmT
MkkPLAFFM8lKv9AqtbOTPNmTPEk7PikRQjmURFmURnmUSJmUSrmUTNmUTtkq/k4ZlVI5lVRJlPJw
lViZlVq5lVzZlVoJQTFCP0mQk1BZlWYZlT5ZO0eZlmVJlGz5lnDxk3DBKnNZl3ZJEHcJFj2Zl3zZ
l375l4AZmH1ZF4JZmGDhMEoQKbQkEbhkOk1AO4uJIbJUDyM5A2KymFNDS/XgcT9wmbMUD7f0JZzp
A54pS4xpS5v5mJLpSqCJmog5lqvZSq1ZS6nJBKUZS7Opma+JBLcJS7k5S7VJKLHpE45WSb85mbt5
NsP5RxRVmYJwnLEUnErQmy1QnIoEnQiZnEZAncNnGauwSafJUc3ZnJUkmqpJnKNAniwRR87JB9jJ
nOMZn+2ZB9IJm1n0CviZ/p+qYJ1rwJ828J7dKZ8CqgTzqQTmaZsK0hL6uaAtUaBTME20VkhbZDDw
sJwCeqH+iQkQ1QcHSigmIwtxWTtAiQBXQaIiykQGsw3p6aA7oAAP8AAVCI2eEKN5GFXzt4F7qB7D
CQqrQFH7iUipwKM3pQDooF1FegUZegP1yZuz05ZDeZVQMRHxAKVgYXgiIAEHMAElgA4TgA5WWgVL
BlqzB1oBdlsqqGSYVoyxphyx+RNP1KBUNEYdwQo3FQDoIAkRcAASwKKelneY4HIpWgoDR1hLqpwT
I5RQOqXnsyMxgjMEoKUlkKcRQAJdegABEAF7qgUpFU/VN38WmXng94aM/riBlhCeTsEQKkEUVKQS
uNCjrVCdWIqlkEoKERABCNBT6vMJATkCCmCrgjEBkwoAE7BAMgCh9CSQDFCBu4dPMrqBiJgvo9kD
znCo43GVHyIRWdkgEiGWAIClgmGnlkoK+qYAE9BdnjABkgCspHCr6Fpf5fqlO9BVf6aBffd3mGBW
jDiqfXdkphpISfGvANsRQJEKZeQCRHqk9YUOeXoAvaqwd3oZeoqlAXmkD0t0OZZSQMWQx5aFxcho
0VSMGSkK2lkE01oX2HokwIGtJwuW2EqsWKpvD/uwC+ul3YoOsQoAM1uugHEAwfoDCEZ56zZQSVdU
k5dZFAadvGBESaG0/kxLsN9ZnYAxAup6qemwsMDKsDirDgfbsDobrkQ3VhOwcMJGTT2VeTIYfhu7
ilgostHKA6U5AUbppEo5cCbADsF6sCJQpJeqq1yqpwc7qZJ6pQMHrvDaovCkWtaoh+H3W7+FT/y6
mlyUFFQxFUw0RDnjAuAqAVsKGFerDnkKqQdLswuruVYnXtY4Th94o6mrhDwlhhsLNW27A6UpRFMq
PSfrlYkhEF66tXnrtewAGHjbpYDLsx0CvEAQYXn3WS86fCSAabkYdYD1uAaDqpJ7FbQzl/96uS3w
u1hbP1napRMgvDiLtUS6py8rrOhArMr2XYmLalYaWlg4tK+LCSNL/gS36Tat4pVa6Tl0iwJ3Sri9
i6c8e7B2qrnlO75366Xn65BJdYRuBU7jFHk9NXpvNbSB1xiZuSpDxBDWS6KWmws76XF5ag1cir6a
26UIIL7nG7VeKrx5SrpWJ2uLGKEy6IFJtYQWiS2xqwPUSbslk60AgQBddAIurKeWQLEH0Ltdar7E
K7FKXLMFqmPKtGuh+F0MNbSJV3nfpW/9ugvXW5g7+Q4sgLfom8TgurC1SryfW8YL+7sBfAMKAMHc
BG/+FXkDtYfstIc5mio7nAPcKQD5WyLyIMQ3haUVC64CPLMBEKtOfLNsTLM/gF4pVm/+pmoJJVth
SoOWzKYWNaxM/sTBdlk74btzKTyjkKo+tWoNvdpTuKpdtTqs+CsC6noDE7BoCHV6rWV3goaMk6V8
uyh8idLHONCbDgXIpYI6ATABPdoCwFqrJGCrloCpqVxfEdBdxAuss9qrtbqrPFAKuOwDACpEcpmX
tTMLfEqggeWn3mXF2CRV8iqKOJqHHTqdGdycCpC/V1k7g+tQPZDMRtqzPeegAMoSwwqVQSmUCPC0
SXDOHbWN4hRxD20JgEqD22Uw9TsEJcsS62nP4dtdgxugznnG6XsGMdTFPnHPO4nQBp3Q5/wE0zQE
hbqd7CEQFdXSpIDNhbsGJg2fbgqwP3pRbpCkD3bRQsCdsmmh/uhJUSBt00FN1EFg1Ky00/53SjFN
ssupSlLtSlVtv1edSlndSluN0V2NSl/NSmFd1GN9SmW9Smf91GltSmutSm0NBBmNm2+NSnPdmXdN
SnGdSnlNmns9SgNt1k5N14EtSq1yS3/dA92AmYpd2D/gGrSU2FT9ApDtA5J9daWFoZzd2Z5NmZ8d
2qGto0st2qaNoRpl2ql92qzdnKYTn0HaR5gizDdQFh5SIrid27q927zd277928CtE8E93MQNMcV9
3Mi9295A2zYwrZrN0+oJUp0NBPHJBYO9SvM8lhn8SpRNm5ctrdvtSt2tm8xdA3UNS4Tx2OVNA+fN
3eGdnett/pnvzUrp7ZrxjRDzvUrjDZzf7bb5XdpMfQf7jZz3HQPtjQkDt13c1V1uE+B0UN/eXeAw
YNSf4NEWfuEf/UgQTt7nedIMTq4YfuEO/gYbzt8S/gI9/K4h/uEivkglTuCPWc/d5XAh7jaDa+HX
+d+EfeIuUNduE74dveJCPuI6reNs3d+ym5nkus0R8AAqbuFh+6Iqzl1EngYDjdqctNhuqyAv+spA
juEwCuRP3q6UcOXP5NE2vs9CvQhanuS7sHAdXeHkyl3QlMIfnuYPkNNnIHI78OLMueBo3lEezW9r
bgKGTLwJC9A+xA49ladV/gNtzsNT46IL0NG70F1dXq5W/mLhTr5RaBDH2qRu9YUADPAAKrpkMxx0
tTHfci7kMw7o/Iy5Elupk+rGhp6lAADJQsDnDclRSC7pngBNlV6uCL7NhnfhL/roPxDHsKdNuuh4
Zmpn0qjF1ESvfl5I6KXghK7g2zXjGJ6hAMy89eXpIrDG9WWHOWCj7YhSQDuLmWejhPrrfvyhUS7l
/UurEUDmN/2ieQ6jhrfGiYSlcDTACOsEKZVQ6CUB7RyGqpu2CVjDw3hPfi7n5Zrt3k7ngA7ogU51
BS+11wwYw6uljl6zJawDL12MQDVNn/CsoEVO6QeN0U6/PN4CJRsA/M7v+p7MOe+iOO/vJODEJFCx
xUvG/k9AUwfWdWYa80MLinScfRP/6hi+4Pw243ke9RyfxFvHDhKQpz2VvmvspSMMwAqJuiqvZcfU
U8D8dA38WYAYzDHuCTfP74YH1PUV98089yW/yOngE0VqrqKwdUXwU00V7ETrZPXH9JWngU8v7BY+
9cIOTQun8eRK7FvU8bKsp+tqyLa691xqyHTfY8vWdQYVTc86+Oy0hHvMx29PClIe94VLrjcfvrVq
pYEbwOAas5YqAQZcpHYLsQig+bIK6T+7TPQqaGAlhsoXdcJ4Nwaj4C+KXvwO/ZEf/duF85RvUZZf
xgmr+zzLDloq8Ln+u5UJbs1aAqr+d2zPUHiMtjq8/vo27+St3+ThEPf8XqulUPuEa6v3fKde2vdF
GrgggBwHIo3ioQAr27ov7DIL5CxrML+B46xLw8Fj4BrEFcIACygWiwc0ulBEH09pdaKKsQKjLSAQ
AEwOknIEECGtJ4DRWIUac+sxYA8iO7YgjRtAT4AfSw9MgYCd4iIXgdIKVRVUhAIdTqTkw5klgERn
ioLJlsLIF9wIAOkBgIjnWtrrpxsjI8PfAoOK0QrEQ1iDyg1Pw5gtRMAuABBfUozCxESmpFMUgjV0
JaPXwdiaZyua2kHEGoKs6Bs3reKNLbIvL1jfH+8f4YpDww7ier+iIwtMmRQQLFglQpQIm16YEINu
/tuaFKdWlVklIs1FcWlGzPLHZRkDBr4YjBkWhFggfUCM5FthzFiLZkueSbkiDQoCLWI4KVJVakxF
caUiiFABJ4AJjh7vAAsJwCmAB0fosbAFqIE9qg30uAjAbylYFgBxREN4M+EDcmYVUoIhKlSKdCsm
biODyps4c7FMdAwrA0INI0d85cMqBuuPIBDA+NnKSeaSaA+gUc6ETYw/nl27cLKk2a8LIBAYHNMB
oEbjG4afOrCF8rSRIJq9JgK9dCyktAjV6lbrm1xaCQvdljKXTowpiatUoYA1TmO6vrZxDCLZZcnm
rpohL5kE3PdknZlpfZ7OaOXWIwsKY71RQwWP/nyAlGGl2vWr+XW4w0z4/vs/cJpIQEl5EamTSimm
UIKKOMI9J4Jez/GVnwzzUcjKI1wQNEFO0IRHEGYXiuhXDZ55Rl4YMdA24iL7pQIgjN4NmA2LNdq4
CHc77LQjjz3eyEV55j2BA4sr/giDiwH0xxuMagknAQJBqqiIlEcemaN2Pe7EWYhWeulXlS0Y+eUK
SSoQY28KCUdOlGS6OSKWnGUZhpY+vnknaGOSud9OzzRJzpNEaSEPnoUuFaehib6p55d89unnn5OB
2KWilSqCqKWZ2sioly6KycSGlGFTSZdhaqoopqeqmh+nVnqqIqXYrTprqrPaClarR756K6/9/tTa
K7BU4rdnhsEai2OxxyprR64/7rostL9Cq2yzNz477bEEJIAtt/fV5ua13fYqrbi8VmtjuOXaSq66
s55bY7rtqsquvKe+y2K89WZKr76W3jtivv2imqzA5g7bKMEFq5pAwgqv+q+IATtMZgFlNjyxphBf
KDGLxmH8Ar8fuynAwV4OUIABKBuwMsstu/wyzDHLPDPNNdsMcwE567wzzz37/LPPKaPcc8squwz0
zzEnfTPTMyP9NNRRQ/3tngVYk0AC1mi9Nddde/012GGLPTbZZVtDANppq702222vjYAjBRAAN9xu
23033nnr3TYAe/v9N+BsD4D2AAiU7Oq2/iKfqq3ith6u68WN3xmy5EdqTCHjlVfKseY/Xp4f553D
WbHolX5uXual42m46oqePl3orZtHuewUvm5b7LWDRrvu090OWu69g8W78GA+7mzkxV9IvPJL/e5X
8M2vw7z0/TwfVvTVI6u95cdbmzz3flEfvrBUI0w+nOCjH9b1YGW/Psjqw+9R+7fJD2bzBJA+v+3e
o3s///4BQNuxSlz+g9cAA8iF8SmwCwfEVwIb+IIE7O9LnAAReQgVBg0WkEgiqp9HJFanHcGgIKKC
hHS8pIV+OMEIFrqChVjghBniYIYLoAMDnReGUtAiFi0YQRrElCfS3EKGuLDOC3ARQ2qo/uiBABsg
HXgiBg0mJUER2AYYTLVB8TFoEWIYTX24QgOstEYG9dlKOxrjwr5FkEKtOEAKY9AGF0xAAhxkn1Ty
4Qc6jAYmoWkMV6ISxhg4MWIZMhVmYpUKQk1oLiloSD9I4Yl1rEJMA6IFYIiACz+owAFcyUcWg/iD
GYgSAA3wRQ6dlxwW6OQyK2QFHAPQplTMgkPWWMEKn8FClYhkF+sZgx/4QJ9jLCMVaGSADfZhvk4d
klmgKsgzbGmNtrDABB7jSEOUFBBsQEIFQUwKUDg0CyVRphLPUMEryQAUMSBgC+ScQG3qQ4Ym0IM0
K8CKPIqojJD8gY9E0B+uprNKu5ih/hRJkcMIkuLIdibUDKpIiscWAQRlHCOZthhJMupxlT+sxpSv
ceAyXfWIEfJIEyt7UoKG0oJGRqeKzzEQHCuSFANpoaGeMGhKrYgg5ZTCKOOAwyI9WcYWOCEkSKyH
YvQxiMI4AB4Ms15JZqOjOuyFBAStKTfwEhGkwDEdJagkX06wDS3+YitC6MIxnmIf2ACiB7h4jSFe
UMiNjZSkO4FpTodiiZk6SAJc3QgcGXQCjpCCHBLqKoTQYYIrcqQukhwrOKwajsRgBQLzeYISX3BG
YNDnJPTInVS1AyQGqWKHnpBkg8ShAsXC0QQOUo4j/eGate6TJ37YaA7gqg+5hvRI/gOoq10DEJEn
EZe4pXQtAtQyBqB+wbUzRYUXIlAGTyQFohP6glzk4gW/okKSqhguUW3RkqhM5aOpCIkV9iiVkKxH
DwCtkSK7kFAD7XA5qGhFXsThBo68okOlzW4/SHNbGT5AM8hsK0d9cM/dumCuFPrtJYL7ADM0STh9
YSkLmKsc6U6ACWYwLV6SchmlaDi2j73vOFShhQ4rAwgBsAIyiJCPMcy4BQwOAxj78M8K7gBMNNqB
NcUJoaCUFr8RgYtP61jJOtYFwF60rAL0sJVR/sBCA04JDc6akkP09kcQ3iCpRiig/xiXE9Z8gYb/
2yHommG6n0iDcLm637gIdhVj/kXFdAsbhraQ4w9WOA0RAIOPs4oEGfPJJFVizMY6kHUJTBjtgeqL
AoKmNiJbjc5DzTDW49BCNDQgr0tOWUwaHIaYvnTMRbl8py8zwQrQfDUVBtSkdrrgzC7QsHCtSGRN
E7ahypmzT+uLHNi2AiLYPUwY00oDfnKlAX4VjWtUk572AOCpQAouSTHIBWjQEZ2zoLUs4RMlWdJB
AW06E7fJUMs4AskP+QjJGNZzRl9wsqynZMEDBqnqN+HmmbA2odh+DIlZtqA/uDQONHKyAukiYQsM
lyVRBj6G5B4cCcZpi8KFCx+i0LoLAj4qNS4LCKOaJgczcAISePyCf7Oc5Y1+/tgYTWNDJ8QbiZkN
bwxb4OD8fPlT2K6TENsFFcy1UXETvdHOURfBl0vvfRIMQ9JhV/Sn903lVM9M1HE39ae/9+q4yjrw
ti7BrnudfmCHntgbSPayW+/s2Eu7AtfOdvK43X1wD6Dc5+7FuttP77TIu98ZzXeP9DzwdXC6BEHo
j8IbPgaIb6Di+8H4xr/g8QqM/DomT/kWWD6AmKeF5jdvMdEza/CLvzv/Os+/zzMi9KJX/fxYvwjX
bx7wpMeB6SWfuNtzHvWXz/30fM+9AcRE+KsHPi0EEFHe9233zG9wl38kgAEMYPrUvz72qS8A62e/
+97/Pvi9n7bwk7/85j8//vq7nzICDC797qc++68fuPnTv/72XxsFib9qoUmt//7/PwAGoAAOIAEW
oAEeIAIe4MrsTMogQPQ9HwRGoAROIAVWoAVeIAZmoAZuIAd2oAd+IAiGoAiOIAmWoAlO4E7MnAqu
IAu2oAu+IAzGoAzOIA3WoA3eIA7moA7uIA/SXHx5DnqdXA8OIREWoRGqoDQc4QvehBI24RGGRDDl
XI0cEc2doN4FwLJJoe1AwQ1ZYeNhIbyxiBIxnRcGEBWKyM2VIemxF4XMABmqYeKZhm3kwBvCYeLR
1lJ8WqaESB36Th3cEfvQCa6QkAehyHjkCbMEhKPdSQ5o4Tr8WaakFCAG/lR2uAAplMQL+NB0UNwa
qFKCAEUlyUrQjeK2RRpYqMNniAAkTFKtsaKb4IJfwKKmPEeKXEKPWaIicsl1eIYG9YUlrIE7lYpo
CWJAhIgJQIKceFAUdUVc2AWCJGMlUofPYQcp6GIJTSOCSEeIlEEuEmMnEqOXNGJYyKGldFXBHVR9
XdHC/RQluBZ8zNRyWVhFWFUuogEcVARBGIhfpQOUDMgXVMQsGMiwlcAkzdRcWFoMhGI1VqNQ7GMY
GOROfRhB0SMOURhY/UQLeMM4xIFeXRounYAzPqNQdIOd0eKXyKJHKIAwlSMljFNXecEOqeNHusEc
KcQbBFFXYRcqNuMO/iGIOZSAOKgBKz6HTlZSd9nZJFUjUHaicKzAJTGXBnlBO/XHaa3CN9Iixb2B
OTQjgYRipHFjXagiLK0UnW3ELKgDT3qBGKQBQ1ZjJ5qbUAoXu91IDkxiHZBjOZbCWXLkXLiAWH7j
MdIiURpHV5WBZ9jXR6pBGlzSQb7BWZ4lfITiWlqEVa4CY36YOfLkDyVIYooAcrAiqFgVORBEhg1K
pLUlZSKBK17mRmwBWh5mwVUSTHIjC3hDKZEJSq4DHaqKOWZYZPZkRlbSX66CYG6la36ifIWkKh5j
UzYmPR6IOjDkPFZmUJKDU5rlXMyGKTrjdHpMFREmEDkSDwVEJbml/nCGYicQJnbKRaSpJSuVJ0Wg
Z3PgCallRiDNonTsZF/GxHk65U3h5FaeZTf2JG3WUVAy5k1qZTdlZ0/CZFAupWV+E3ES5mdsp1KW
Jx2wmRtYQk4OKG2aJySgJ2u+gWsahZiUZ0heKDLaJIKSiaH5Q25GonGUxEaqIkPWZiUBplXakRcY
BWFGCTAmJ20uZ3wWRE7iZIk+oxf0B4rlmmpJZYKSaCqcKKFwYxkQBD0qBFzohV9dKVJc0RpYQii0
01vCUSgcF04uZpeiJWjCkU0WqH3VkZraRR/6BSSuA8qpCjVl5IDQwW2eCSQEEYeEQXJxpTutiTwI
154NHBkEEUGe/sHCOZyfloQ6Clc7mUMocIijCsfFTaqU1qYUCaqWFpx0dRxblJtaEMqZsAUuKcTy
vVLGlQA1kUOX0OqL4ICoBpEusUKdjqMjfsSvFkqvfkxv1mIE5imermT4DKt5yKRu+qGwqgqydlqw
6guzDuPchYkUFcq0nke1Ss61UokhhmC3StS3Gkq4bood2ka5ssO5ruvmtasdyKsFpmu8vqsRFQm8
rg+9AusJquQM4WUSkZzAhsYMkNxnUOHBkpyFmFwa7hMuFNhHkNyt9Osd4OsFilcPjJeKkFFhKKsL
qFFh5Bwy9EAQbKzJrhGOeRYgoIdjMIXHVizGtljr2OuNIBPK/moZDKxHzoJsHwjVxkrhyebsxlaW
DKHsEeCsfDBFzsosjM4sBeJBz5aH0qKsI8ZHPmxsWoWsyWatx5rsfCjtLSjGUP0FGdWAINiKxe4s
1HrRbdKP8igtaQTtEqCtZZmsz7JGD4QE3bqAZ7VGwBZtIC3Vu4ktGBAB32pt1irYrKxtErVtT6Cn
HWSlCzCckAjYBdkTUWXSJo2GmJDGEhmVEwCGxFZFoenY6QLJyY7tu+2AxsoY2OYcz8qH1G4tC5At
45ZVHrSAxgKGyd7nPREtymoDAhjVAxAKDWSSyY1GMfRR53ruvM6s49KP5NaBSf7Q27IP2iaT3npS
VWTtDdTu/g9Y7dHu7jCk7WloLQtsb7BW7Vtt7ImY0sbOAMoKmgxY7QOQr40NLw5sb9mGGspm1P4a
QXy4m85+hAGfrJXVL8q+mPBurLs+7YjAJFLgwCShQFVqZq6hpWs+5JOUGxBN3G3ibDKILR9B8C+Y
7PjO7/fuLQCjRMme7O3urh3ILY7Bb2iQr9LaL++yMNZy7wzPr+/Whwv38OL+b1VYFi8ccZVkWR6c
rBIv8eqOLOHqUdNGrwR/UEkiQXyuJWO5Ig4IJpxxwzYwaTZyFTgmRhH7LyCg7W6V7HjNbtmS8MjR
bQynbXwI8M4WLR3sMCe4MVecbw/Awwq3Lmw0BicM7RHX/u8S6RHaguwfH/G8Di3i6i8yrW59vK8n
OUHX5u7FZvGFVKODcqNYpgiChgg9XiKUzMWGbnFQxoAbc3IAq2TfKgPe5rECTwEZ8QHhEoN4PXIv
VwkyBUYdu5uFrG4gH/F9Vu0RoAa1BXHObi/wukQePLIiKLInJxHZVjLa1jEU39BheFIQDJoMYzEL
Qa4dMOSSXaRESuStXdMlAqcqbkNCcYHS4sLeEvP2isnq8iz93sJK/K+7/QHOZpllQbEiiK2A5ex8
/LAnGbD6fq/d+q7+Bm/Oeqztlm80B6v/HnASIS1rdDM117L8Zi05x1UdTC9RobNb0Chw0mZobmX2
9mZr/mUoOpWkOQGi1M6tDRT0JX8UHLfG3vrzDGQy756EGzeiDaBwSmNzAOfBCTs10QJCvn3tRb/s
oAWtvOGtJeLu10oJ0Y4iHcgxN/fAFlRtIqOGgnVyBJ8zq8SFKK8zGVywZYJxY4ZoENUFNzJkCZTH
IGDyH0SAFbtVDndtA1yRYgBGEKykQ4OSu91zF2wFYNTxAx+xMKTsRWM2V+CsYk8x0M7HFUstSo/0
u+UbSb+A3aLvICi2ejx0GV0yYXeveSnyoKFtW+MpS79AHQmHw3HmJ2jaJywfp82FO/2UQ86jCMOA
MeQBEZxvOROVMhcDUy32C1hxEAhDYDA1fXB1UFc2/lSTMDYHxhDfUDQD8uIG0hXbsjjzcv0uWGEE
SXajtGiLEUi7L2mbl1oLQXffNrW6ziLQtLaWENlSRQBPsxPTsBwDQc5pLEpDtO2WrB/4ggKQbc5V
lnwYsIErci4Ubc5tL4M5M+PSMtrCQ/5mbdI+sSMKNv/+gu/yAR5A9DOHNPriwAPbtjnjdq94WHHX
odi28dBK4XwXsiF3hRtrmWnP+Ha78OziIUQvubKKNuDy8QvYd/pqN88qBhYibRTBdmt8BjbL0NAu
M0Rv8s9mLU8w+Jjzt7eaC0iGsTvJVn3wsmtEMZFjxVHN1r0pd2VdlhqFxhkV9S0nkRqJFxop9xBv
/paKADIwbcU4gzkZMTpC/4UeSeFAIwZl2bmYSC2m97Af0Hn/cm6n30NKS29uW8m2sg8ZboloScnL
LWMaLyIm/uCrG2tKS2OsxO+8zjp1fAauXwej6ToW8pFnqbm57uvTIYNkk4RQdTqxN7uxw09Hp/eo
g/Kzex6D/27erjS1V/vqCdhoAIYWqXS+MuIhWo8oZoyquHoiio64VxmQFCLc0qWvc/sHjUi70yxZ
2AGL/SCvOwNPkEp+7Oqz7kDEeRGQCPe8ByKzqMCG6OvwIAFZWWqqxgDBXYpHFOyNA6r1bgTC+8M3
VpN1mscx5gmrljuC2Oz0UNfIzyKDMsIrsAW7/mmmHVTvImD8tNPJhrKTPDzWGWh8qyJ8cnVEnH0o
LHBbh2XDkvxiwSOB5VaTX+3pqtJBh7EYDiSXcTTSrmpTPnYc1UeUWt7SBskSoT7cKNQSUOSEJfRH
R1QC1VtwXcOCZ9hqKkDcysnSjLL9wjlr0rNAcjmrRnz98pGDdIR8wZmbOuIXKyDoinEoDu1Zwee1
x9j8xOIqZRZUR+Cjc+2jRoLxYj3HdrkWLDkIaf6EmkjkgCzWQ7JjcD6JN5kBJCXUXjkIY5njyANj
oJTlDmVRQjVlRbTjk+y2UxqldL3WGKBUBvs9FvUVJMmqcCyX6ztkfa2JpCGFg7jBdKGDmkDS/jou
iOsHkWGV/MLZtcqv6Y6qiSM5K1I+/ekXamK6hPTygZV21ccnqGDtV4auva5SRFXelCeUAbdBJQgA
wBEEhwhEwHQCiopGxzSqkSIeyEiio2gKKFqr3kyCzO10uQDKJMkBTCqWSDYsJYdDWspJPA0jTl9q
F8HW1qNldIQDMofTWfEaTYsQuB4AUSY1EmXictCC0OKUiJB2k9LCdNBXZgSDciIBo3hEoycCsWA2
SroAUWaVKCJBtKaZQ3MgMaHmg4DAepcSJbs6EbszuOSEdCuXFoeSNCjyIhObLFhIF3MgU7OpYjcS
WFhneNVyba0ZMfEaUY4Z0XjiPZoOgPRm/s2TZjeZkxx0581yf+LfG0hpAglqQceENRmtEqVDQmOZ
pD6acsExc6jMmHRiJhEJcIqUyCcMRN1RJa9VPSYjYkm4dWkVu0N/xJ3oJc8Yy4Wf/jiKISOmRBWJ
aOGL9uPbO3mabn6SFMzPNynUUKoip+lfs4c50jQCRyreIXpLZtBqglaOEyv+dNyKQ+vZnnYG3fUo
pBABrWjxzLxqc9Ga3qhI3RKaoZdGFyILGBgcOWrBAxFWrqX0sXJTrDKAUFCjaaUmM3m/1piIA8jb
NJtAIPXRRiNRn2j8slADgoQiPW1Ru9H8UZV1gCRQrsTBFwPsFFt5+mY2fjF6nSod97SY/rCjtCtM
Xg42s4sw2J6BmMgGjrOpcB0wyXd5CVASMmT4olRZtphjRj3AQXP7mEcTFKwEJAsrpe330G+sIKHC
cLLst8oh6axFDj7drTIPdWagdM48EixSYTJDZCjaFB56MVQ4C2I4FlgBiAdJh7utgERGLcHyRIFM
hDbcgIrV+GFNNfoABQsUXiEDKzAmeQgTKWZ0joT6ECkOGQxZ48RtkjnxmHwoNLbHFO9duJcCqKDC
Tpd6uQAEO2u6YE5qKwTyQmdzXdgIUiUoYCecQqz12IvmAAEjJJ7VmQx2b3r2x5hPIHPoHnQagwIt
3XkRWptCKBCHmYTaeSmVAWjHJgq3/kw6QSCKjlJaqJ5NoCesv6TqgkZZvsdHpaOougesnhERn5ek
cBmKsMbOd2yyyi4LGQsXmtEls8lG60Om0u461bXabsutGQrMIkJj1B67ZbfDmovutM0+y+y423Y5
arrVykuvsO4aGwAMCjxg0raSyXuvuQE/AW29BmNL5MEKL8zwfMF2+3DD0g6MrMQWX4xxxgIv0G+3
ATzwAMUaj0xyySafrO0CDTBAL3wRowxzzDLPbHIAki0g8rQ3l0Bzzz7/DPS1NjPwcssKcFxCzkEv
zfRIHTetbQkcM/CApw3bDEHWRHPMdddefw122GKPTXbZZp+Ndtpqr812226/DTfaXkRnHcrTF0sd
d9567813337/DXjgYCddMNSGH4544oovznjjjj8OeeSST0555ZZfjnnmmm/Oeeeefw566KKPTnrp
pp+Oeuqqr856666/Dnvsss9Oe+2234577rrLFwIAOw==
------=_NextPart_69A_3A6D_40FC73EA.9F444B1F--




From ipfix-bounces@ietf.org Tue Jul 03 05:42:29 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ets-0003vL-32; Tue, 03 Jul 2007 05:42:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5etq-0003uX-UF
	for ipfix@ietf.org; Tue, 03 Jul 2007 05:42:22 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5etn-0006vf-Am
	for ipfix@ietf.org; Tue, 03 Jul 2007 05:42:22 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l639g6Np011871;
	Tue, 3 Jul 2007 18:42:10 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 03 Jul 2007 18:42:07 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
References: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
Message-Id: <20070703181741.1134.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 03 Jul 2007 18:42:10 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

I had a short review about IPFIX test draft and I have several questions.
I am just trying to implement IPFIX Meidator, it is very useful
as reference document.

- 3.2.3.  Set Padding and 3.2.4.  Record Padding

The document describes the Collecting Process should shut down the SCTP
or TCP, when it recognizes the padding field is non-zero value.

Generally, Exporting Process must put the paddeing with zero. But, on
the collecting process side, it simply decodes IPFIX message, it seems
not to need to check the value of the padding.

I think that "shut down" is too severe for Collecting Process.

- 3.4.1 Using any Information Elements as Scope

The following description seems to define the handling, when the
collecting process receives  option template with Scope Field Count of
zero. In that case, should the collecting process shut down the
transport session?

   The Scope Field Count MAY NOT be zero.  The tester MUST cause the
   export of an Options Template Record containing a Scope Field Count
   of zero.

   The tester MUST ensure that the Collecting Process shuts down the
   SCTP association and discards the IPFIX Message.  The tester MUST
   check that the Collecting Process logged the error.

- 3.4.3.  Metering Process Statistics Option Template

It is not clear as following description. It seems to be condition that
several Metering Process on the same Observation Domain use the same
Exporting Process. Is it correct?

   If several Metering Processes use the same Exporting Process, the
   tester MUST create a Metering Process Statistics Option Template
   containing multiple scopes and an associated Data Record, MUST cause
   the Option Template and associated Data Record to be exported, and

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


On Wed, 27 Jun 2007 17:15:30 +1200
Nevil Brownlee <nevil@auckland.ac.nz> wrote:

> 
> Hi all:
> 
> A revised verison of the IPFIX Testing draft has been published, i.e.
> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
> last Call.
> 
> That WG LC starts now, and will finish on Saturday, 14 July 07.
> 
> Please read the draft, and send any comments to the IPFIX list.
> 
> Cheers, Nevil
> 
> -----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> 
> -----------------------------------------------------------------------
> This mail sent through University of Auckland http://www.auckland.ac.nz
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 05:42:29 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ets-0003vL-32; Tue, 03 Jul 2007 05:42:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5etq-0003uX-UF
	for ipfix@ietf.org; Tue, 03 Jul 2007 05:42:22 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5etn-0006vf-Am
	for ipfix@ietf.org; Tue, 03 Jul 2007 05:42:22 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l639g6Np011871;
	Tue, 3 Jul 2007 18:42:10 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 03 Jul 2007 18:42:07 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
References: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
Message-Id: <20070703181741.1134.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 03 Jul 2007 18:42:10 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

I had a short review about IPFIX test draft and I have several questions.
I am just trying to implement IPFIX Meidator, it is very useful
as reference document.

- 3.2.3.  Set Padding and 3.2.4.  Record Padding

The document describes the Collecting Process should shut down the SCTP
or TCP, when it recognizes the padding field is non-zero value.

Generally, Exporting Process must put the paddeing with zero. But, on
the collecting process side, it simply decodes IPFIX message, it seems
not to need to check the value of the padding.

I think that "shut down" is too severe for Collecting Process.

- 3.4.1 Using any Information Elements as Scope

The following description seems to define the handling, when the
collecting process receives  option template with Scope Field Count of
zero. In that case, should the collecting process shut down the
transport session?

   The Scope Field Count MAY NOT be zero.  The tester MUST cause the
   export of an Options Template Record containing a Scope Field Count
   of zero.

   The tester MUST ensure that the Collecting Process shuts down the
   SCTP association and discards the IPFIX Message.  The tester MUST
   check that the Collecting Process logged the error.

- 3.4.3.  Metering Process Statistics Option Template

It is not clear as following description. It seems to be condition that
several Metering Process on the same Observation Domain use the same
Exporting Process. Is it correct?

   If several Metering Processes use the same Exporting Process, the
   tester MUST create a Metering Process Statistics Option Template
   containing multiple scopes and an associated Data Record, MUST cause
   the Option Template and associated Data Record to be exported, and

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


On Wed, 27 Jun 2007 17:15:30 +1200
Nevil Brownlee <nevil@auckland.ac.nz> wrote:

> 
> Hi all:
> 
> A revised verison of the IPFIX Testing draft has been published, i.e.
> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
> last Call.
> 
> That WG LC starts now, and will finish on Saturday, 14 July 07.
> 
> Please read the draft, and send any comments to the IPFIX list.
> 
> Cheers, Nevil
> 
> -----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> 
> -----------------------------------------------------------------------
> This mail sent through University of Auckland http://www.auckland.ac.nz
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 06:21:58 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5fW9-0004DW-Da; Tue, 03 Jul 2007 06:21:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5fW8-0004Br-1H
	for ipfix@ietf.org; Tue, 03 Jul 2007 06:21:56 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5fVD-0006ZD-Kb
	for ipfix@ietf.org; Tue, 03 Jul 2007 06:21:56 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 12:20:59 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADa/iUaQ/uCKh2dsb2JhbACPIwIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147096303:sNHT40726748"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63AKwg3011411; 
	Tue, 3 Jul 2007 12:20:58 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63AKuTC018280; 
	Tue, 3 Jul 2007 10:20:56 GMT
Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA09303;
	Tue, 3 Jul 2007 11:20:51 +0100 (BST)
Message-ID: <468A2306.5090205@cisco.com>
Date: Tue, 03 Jul 2007 11:20:54 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
	<20070703181741.1134.AKOBA@nttv6.net>
In-Reply-To: <20070703181741.1134.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4684; t=1183458058;
	x=1184322058; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=ccGPJTiszl+VY3u702B3w2hQyjX8jQ2oIZ3TEZj1U9g=;
	b=Pedpo1RUsqYbllNxRnq52dGh9AmIWTXWa5RHqOse2RPMebY0Axr6DMDTEQ+bBF4ZsbqZfu1F
	N0uTT0HW1VTto7YdxE4PpkbFKMMFHUBmJUIX2Qd/POfTLDdvvOldUTWi;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Thanks for reviewing the draft so promptly!


> Dear all,
> 
> I had a short review about IPFIX test draft and I have several questions.
> I am just trying to implement IPFIX Meidator, it is very useful
> as reference document.

I'm glad it's helpful to you.


> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> 
> The document describes the Collecting Process should shut down the SCTP
> or TCP, when it recognizes the padding field is non-zero value.
> 
> Generally, Exporting Process must put the paddeing with zero. But, on
> the collecting process side, it simply decodes IPFIX message, it seems
> not to need to check the value of the padding.
> 
> I think that "shut down" is too severe for Collecting Process.

While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
in this situation, its general rule (from section 9, "The Collecting 
Process's Side") is:

    If the Collecting Process receives a malformed IPFIX Message, it
    MUST reset the SCTP association, discard the IPFIX Message, and
    SHOULD log the error.


Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:

       Padding
           For
           security reasons, the padding octet(s) MUST be composed of
           zero (0) valued octets.

then non-zero padding constitutes a malformed message, and the shutdown, 
discard and log process must be followed.


> - 3.4.1 Using any Information Elements as Scope
> 
> The following description seems to define the handling,

Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
ensure that you're following the requirement :-)


> when the
> collecting process receives  option template with Scope Field Count of
> zero. In that case, should the collecting process shut down the
> transport session?
> 
>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>    export of an Options Template Record containing a Scope Field Count
>    of zero.
> 
>    The tester MUST ensure that the Collecting Process shuts down the
>    SCTP association and discards the IPFIX Message.  The tester MUST
>    check that the Collecting Process logged the error.

Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:

    Finally, note that the Scope Field Count MAY NOT be zero.


So a scope field count of zero constitutes a malformed IPFIX Message, 
and the shutdown, discard and log process must be followed.


> - 3.4.3.  Metering Process Statistics Option Template
> 
> It is not clear as following description. It seems to be condition that
> several Metering Process on the same Observation Domain use the same
> Exporting Process. Is it correct?

I think it's quite possible, since I don't see any exclusion which says 
each MP must use a different EP.

P.

>    If several Metering Processes use the same Exporting Process, the
>    tester MUST create a Metering Process Statistics Option Template
>    containing multiple scopes and an associated Data Record, MUST cause
>    the Option Template and associated Data Record to be exported, and
> 
> --- 
> Atsushi KOBAYASHI  <akoba@nttv6.net>
> NTT Information Sharing Platform Lab.
> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> 
> On Wed, 27 Jun 2007 17:15:30 +1200
> Nevil Brownlee <nevil@auckland.ac.nz> wrote:
> 
>> Hi all:
>>
>> A revised verison of the IPFIX Testing draft has been published, i.e.
>> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
>> last Call.
>>
>> That WG LC starts now, and will finish on Saturday, 14 July 07.
>>
>> Please read the draft, and send any comments to the IPFIX list.
>>
>> Cheers, Nevil
>>
>> -----------------------------------------------------------------------
>>   Nevil Brownlee                    Computer Science Department | ITS
>>   Phone: +64 9 373 7599 x88941             The University of Auckland
>>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>>
>> -----------------------------------------------------------------------
>> This mail sent through University of Auckland http://www.auckland.ac.nz
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>>
> 
> --- 
> Atsushi KOBAYASHI  <akoba@nttv6.net>
> NTT Information Sharing Platform Lab.
> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
> 


-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 06:21:58 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5fW9-0004DW-Da; Tue, 03 Jul 2007 06:21:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5fW8-0004Br-1H
	for ipfix@ietf.org; Tue, 03 Jul 2007 06:21:56 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5fVD-0006ZD-Kb
	for ipfix@ietf.org; Tue, 03 Jul 2007 06:21:56 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 12:20:59 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADa/iUaQ/uCKh2dsb2JhbACPIwIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147096303:sNHT40726748"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63AKwg3011411; 
	Tue, 3 Jul 2007 12:20:58 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63AKuTC018280; 
	Tue, 3 Jul 2007 10:20:56 GMT
Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA09303;
	Tue, 3 Jul 2007 11:20:51 +0100 (BST)
Message-ID: <468A2306.5090205@cisco.com>
Date: Tue, 03 Jul 2007 11:20:54 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070627171530.p1wjj9dunkscc8cc@webmail.auckland.ac.nz>
	<20070703181741.1134.AKOBA@nttv6.net>
In-Reply-To: <20070703181741.1134.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4684; t=1183458058;
	x=1184322058; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=ccGPJTiszl+VY3u702B3w2hQyjX8jQ2oIZ3TEZj1U9g=;
	b=Pedpo1RUsqYbllNxRnq52dGh9AmIWTXWa5RHqOse2RPMebY0Axr6DMDTEQ+bBF4ZsbqZfu1F
	N0uTT0HW1VTto7YdxE4PpkbFKMMFHUBmJUIX2Qd/POfTLDdvvOldUTWi;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Thanks for reviewing the draft so promptly!


> Dear all,
> 
> I had a short review about IPFIX test draft and I have several questions.
> I am just trying to implement IPFIX Meidator, it is very useful
> as reference document.

I'm glad it's helpful to you.


> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> 
> The document describes the Collecting Process should shut down the SCTP
> or TCP, when it recognizes the padding field is non-zero value.
> 
> Generally, Exporting Process must put the paddeing with zero. But, on
> the collecting process side, it simply decodes IPFIX message, it seems
> not to need to check the value of the padding.
> 
> I think that "shut down" is too severe for Collecting Process.

While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
in this situation, its general rule (from section 9, "The Collecting 
Process's Side") is:

    If the Collecting Process receives a malformed IPFIX Message, it
    MUST reset the SCTP association, discard the IPFIX Message, and
    SHOULD log the error.


Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:

       Padding
           For
           security reasons, the padding octet(s) MUST be composed of
           zero (0) valued octets.

then non-zero padding constitutes a malformed message, and the shutdown, 
discard and log process must be followed.


> - 3.4.1 Using any Information Elements as Scope
> 
> The following description seems to define the handling,

Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
ensure that you're following the requirement :-)


> when the
> collecting process receives  option template with Scope Field Count of
> zero. In that case, should the collecting process shut down the
> transport session?
> 
>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>    export of an Options Template Record containing a Scope Field Count
>    of zero.
> 
>    The tester MUST ensure that the Collecting Process shuts down the
>    SCTP association and discards the IPFIX Message.  The tester MUST
>    check that the Collecting Process logged the error.

Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:

    Finally, note that the Scope Field Count MAY NOT be zero.


So a scope field count of zero constitutes a malformed IPFIX Message, 
and the shutdown, discard and log process must be followed.


> - 3.4.3.  Metering Process Statistics Option Template
> 
> It is not clear as following description. It seems to be condition that
> several Metering Process on the same Observation Domain use the same
> Exporting Process. Is it correct?

I think it's quite possible, since I don't see any exclusion which says 
each MP must use a different EP.

P.

>    If several Metering Processes use the same Exporting Process, the
>    tester MUST create a Metering Process Statistics Option Template
>    containing multiple scopes and an associated Data Record, MUST cause
>    the Option Template and associated Data Record to be exported, and
> 
> --- 
> Atsushi KOBAYASHI  <akoba@nttv6.net>
> NTT Information Sharing Platform Lab.
> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> 
> On Wed, 27 Jun 2007 17:15:30 +1200
> Nevil Brownlee <nevil@auckland.ac.nz> wrote:
> 
>> Hi all:
>>
>> A revised verison of the IPFIX Testing draft has been published, i.e.
>> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
>> last Call.
>>
>> That WG LC starts now, and will finish on Saturday, 14 July 07.
>>
>> Please read the draft, and send any comments to the IPFIX list.
>>
>> Cheers, Nevil
>>
>> -----------------------------------------------------------------------
>>   Nevil Brownlee                    Computer Science Department | ITS
>>   Phone: +64 9 373 7599 x88941             The University of Auckland
>>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>>
>> -----------------------------------------------------------------------
>> This mail sent through University of Auckland http://www.auckland.ac.nz
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>>
> 
> --- 
> Atsushi KOBAYASHI  <akoba@nttv6.net>
> NTT Information Sharing Platform Lab.
> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
> 


-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From bxqcaliper@hispeed.ch Tue Jul 03 06:23:06 2007
Return-path: <bxqcaliper@hispeed.ch>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5fXG-0004bg-DO
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 06:23:06 -0400
Received: from [59.94.129.31] (helo=hispeed.ch)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I5fXF-0005KU-10
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 06:23:06 -0400
Message-ID: <001401cb1ded$9c26e340$060dc4d4@user>
From: "Kimberly Coon" <bxqcaliper@hispeed.ch>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fwd: Thank you, we are ready to lend you some cash
Date: Wed, 7 Jul 2010 15:57:46 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0011_01CB1DED.9C26E340"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.181
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.4682
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

------=_NextPart_000_0011_01CB1DED.9C26E340
Content-Type: text/plain;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable


Your your credit report doesn't matter to us!

If you OWN real estate and want IMMEDIATE money to spend ANY way you =
like, or simply want to LOWER your entire payment by a third or more, =
here is our best deal we can offer you NOW (hurry, this lot will expire =
NOW):

$228,000+ debt

AND EVEN MORE: After further review, our lenders have set the lowest =
monthly payments!

Hurry, when our best deal is gone, it is gone. Simply complete this =
one-minute form... 

Don't worry about approval, your your credit report will not disqualify =
you!

http://livefashealthh.com/
------=_NextPart_000_0011_01CB1DED.9C26E340
Content-Type: text/html;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1251">
<META content=3D"MSHTML 6.00.2462.3000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your your credit report =
does not matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you OWN property and =
want IMMEDIATE money to spend ANY way you like, or simply need to LOWER =
your current payments by a third or more, here is the deal we can offer =
you NOW (hurry, this deal will expire THIS NIGHT):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$239,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have established the lowest monthly =
payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when best deal =
is gone, it is gone. Simply fill this user-friendly form... =
</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit history will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://livefashealthh.com/">http://livefashealthh.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0011_01CB1DED.9C26E340--



From ipfix-bounces@ietf.org Tue Jul 03 07:48:42 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5gs1-00040U-Nk; Tue, 03 Jul 2007 07:48:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5gs0-0003v5-2h
	for ipfix@ietf.org; Tue, 03 Jul 2007 07:48:36 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5grz-0002uK-Cl
	for ipfix@ietf.org; Tue, 03 Jul 2007 07:48:35 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l63BlWvi012631;
	Tue, 3 Jul 2007 20:47:45 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 03 Jul 2007 20:47:33 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468A2306.5090205@cisco.com>
References: <20070703181741.1134.AKOBA@nttv6.net> <468A2306.5090205@cisco.com>
Message-Id: <20070703203200.1137.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 03 Jul 2007 20:47:46 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Thank you for reply.
Please see in-line.

On Tue, 03 Jul 2007 11:20:54 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Thanks for reviewing the draft so promptly!
> 
> 
> > Dear all,
> > 
> > I had a short review about IPFIX test draft and I have several questions.
> > I am just trying to implement IPFIX Meidator, it is very useful
> > as reference document.
> 
> I'm glad it's helpful to you.
> 
> 
> > - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> > 
> > The document describes the Collecting Process should shut down the SCTP
> > or TCP, when it recognizes the padding field is non-zero value.
> > 
> > Generally, Exporting Process must put the paddeing with zero. But, on
> > the collecting process side, it simply decodes IPFIX message, it seems
> > not to need to check the value of the padding.
> > 
> > I think that "shut down" is too severe for Collecting Process.
> 
> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> in this situation, its general rule (from section 9, "The Collecting 
> Process's Side") is:
> 
>     If the Collecting Process receives a malformed IPFIX Message, it
>     MUST reset the SCTP association, discard the IPFIX Message, and
>     SHOULD log the error.
> 
> 
> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> 
>        Padding
>            For
>            security reasons, the padding octet(s) MUST be composed of
>            zero (0) valued octets.
> 
> then non-zero padding constitutes a malformed message, and the shutdown, 
> discard and log process must be followed.
> 
>

At least, checking the value of "paddingOctets" seems not to be task for
the collecting process.
I think that checking the validation of each field in each Flow Record
 seems to be done by next process after decoding in the collecting process.

Even if the value of paddingOctets is not zero, I think that it is not
malformed as IPFIX message.
"paddingOctets" is one of value the Information Elements in Data Record.


> > - 3.4.1 Using any Information Elements as Scope
> > 
> > The following description seems to define the handling,
> 
> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> ensure that you're following the requirement :-)
> 
> 
> > when the
> > collecting process receives  option template with Scope Field Count of
> > zero. In that case, should the collecting process shut down the
> > transport session?
> > 
> >    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >    export of an Options Template Record containing a Scope Field Count
> >    of zero.
> > 
> >    The tester MUST ensure that the Collecting Process shuts down the
> >    SCTP association and discards the IPFIX Message.  The tester MUST
> >    check that the Collecting Process logged the error.
> 
> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> 
>     Finally, note that the Scope Field Count MAY NOT be zero.
> 

IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
of scope field zero.

> 
> So a scope field count of zero constitutes a malformed IPFIX Message, 
> and the shutdown, discard and log process must be followed.
> 
> 
> > - 3.4.3.  Metering Process Statistics Option Template
> > 
> > It is not clear as following description. It seems to be condition that
> > several Metering Process on the same Observation Domain use the same
> > Exporting Process. Is it correct?
> 
> I think it's quite possible, since I don't see any exclusion which says 
> each MP must use a different EP.
> 
> P.
> 

Why are multiple scopes needed in following cases?
It indicates the metering process id and observation domain id?

> >    If several Metering Processes use the same Exporting Process, the
> >    tester MUST create a Metering Process Statistics Option Template
> >    containing multiple scopes and an associated Data Record, MUST cause
> >    the Option Template and associated Data Record to be exported, and
> > 
> > --- 
> > Atsushi KOBAYASHI  <akoba@nttv6.net>
> > NTT Information Sharing Platform Lab.
> > tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> > 
> > 
> > On Wed, 27 Jun 2007 17:15:30 +1200
> > Nevil Brownlee <nevil@auckland.ac.nz> wrote:
> > 
> >> Hi all:
> >>
> >> A revised verison of the IPFIX Testing draft has been published, i.e.
> >> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
> >> last Call.
> >>
> >> That WG LC starts now, and will finish on Saturday, 14 July 07.
> >>
> >> Please read the draft, and send any comments to the IPFIX list.
> >>
> >> Cheers, Nevil
> >>
> >> -----------------------------------------------------------------------
> >>   Nevil Brownlee                    Computer Science Department | ITS
> >>   Phone: +64 9 373 7599 x88941             The University of Auckland
> >>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> >>
> >> -----------------------------------------------------------------------
> >> This mail sent through University of Auckland http://www.auckland.ac.nz
> >>
> >>
> >> _______________________________________________
> >> IPFIX mailing list
> >> IPFIX@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ipfix
> >>
> > 
> > --- 
> > Atsushi KOBAYASHI  <akoba@nttv6.net>
> > NTT Information Sharing Platform Lab.
> > tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> > 
> > 
> > 
> > _______________________________________________
> > IPFIX mailing list
> > IPFIX@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ipfix
> > 
> 
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 07:48:42 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5gs1-00040U-Nk; Tue, 03 Jul 2007 07:48:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5gs0-0003v5-2h
	for ipfix@ietf.org; Tue, 03 Jul 2007 07:48:36 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5grz-0002uK-Cl
	for ipfix@ietf.org; Tue, 03 Jul 2007 07:48:35 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l63BlWvi012631;
	Tue, 3 Jul 2007 20:47:45 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 03 Jul 2007 20:47:33 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468A2306.5090205@cisco.com>
References: <20070703181741.1134.AKOBA@nttv6.net> <468A2306.5090205@cisco.com>
Message-Id: <20070703203200.1137.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 03 Jul 2007 20:47:46 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Thank you for reply.
Please see in-line.

On Tue, 03 Jul 2007 11:20:54 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Thanks for reviewing the draft so promptly!
> 
> 
> > Dear all,
> > 
> > I had a short review about IPFIX test draft and I have several questions.
> > I am just trying to implement IPFIX Meidator, it is very useful
> > as reference document.
> 
> I'm glad it's helpful to you.
> 
> 
> > - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> > 
> > The document describes the Collecting Process should shut down the SCTP
> > or TCP, when it recognizes the padding field is non-zero value.
> > 
> > Generally, Exporting Process must put the paddeing with zero. But, on
> > the collecting process side, it simply decodes IPFIX message, it seems
> > not to need to check the value of the padding.
> > 
> > I think that "shut down" is too severe for Collecting Process.
> 
> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> in this situation, its general rule (from section 9, "The Collecting 
> Process's Side") is:
> 
>     If the Collecting Process receives a malformed IPFIX Message, it
>     MUST reset the SCTP association, discard the IPFIX Message, and
>     SHOULD log the error.
> 
> 
> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> 
>        Padding
>            For
>            security reasons, the padding octet(s) MUST be composed of
>            zero (0) valued octets.
> 
> then non-zero padding constitutes a malformed message, and the shutdown, 
> discard and log process must be followed.
> 
>

At least, checking the value of "paddingOctets" seems not to be task for
the collecting process.
I think that checking the validation of each field in each Flow Record
 seems to be done by next process after decoding in the collecting process.

Even if the value of paddingOctets is not zero, I think that it is not
malformed as IPFIX message.
"paddingOctets" is one of value the Information Elements in Data Record.


> > - 3.4.1 Using any Information Elements as Scope
> > 
> > The following description seems to define the handling,
> 
> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> ensure that you're following the requirement :-)
> 
> 
> > when the
> > collecting process receives  option template with Scope Field Count of
> > zero. In that case, should the collecting process shut down the
> > transport session?
> > 
> >    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >    export of an Options Template Record containing a Scope Field Count
> >    of zero.
> > 
> >    The tester MUST ensure that the Collecting Process shuts down the
> >    SCTP association and discards the IPFIX Message.  The tester MUST
> >    check that the Collecting Process logged the error.
> 
> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> 
>     Finally, note that the Scope Field Count MAY NOT be zero.
> 

IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
of scope field zero.

> 
> So a scope field count of zero constitutes a malformed IPFIX Message, 
> and the shutdown, discard and log process must be followed.
> 
> 
> > - 3.4.3.  Metering Process Statistics Option Template
> > 
> > It is not clear as following description. It seems to be condition that
> > several Metering Process on the same Observation Domain use the same
> > Exporting Process. Is it correct?
> 
> I think it's quite possible, since I don't see any exclusion which says 
> each MP must use a different EP.
> 
> P.
> 

Why are multiple scopes needed in following cases?
It indicates the metering process id and observation domain id?

> >    If several Metering Processes use the same Exporting Process, the
> >    tester MUST create a Metering Process Statistics Option Template
> >    containing multiple scopes and an associated Data Record, MUST cause
> >    the Option Template and associated Data Record to be exported, and
> > 
> > --- 
> > Atsushi KOBAYASHI  <akoba@nttv6.net>
> > NTT Information Sharing Platform Lab.
> > tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> > 
> > 
> > On Wed, 27 Jun 2007 17:15:30 +1200
> > Nevil Brownlee <nevil@auckland.ac.nz> wrote:
> > 
> >> Hi all:
> >>
> >> A revised verison of the IPFIX Testing draft has been published, i.e.
> >> draft-ietf-ipfix-testing-01.txt, and it's now ready for a Working Group
> >> last Call.
> >>
> >> That WG LC starts now, and will finish on Saturday, 14 July 07.
> >>
> >> Please read the draft, and send any comments to the IPFIX list.
> >>
> >> Cheers, Nevil
> >>
> >> -----------------------------------------------------------------------
> >>   Nevil Brownlee                    Computer Science Department | ITS
> >>   Phone: +64 9 373 7599 x88941             The University of Auckland
> >>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> >>
> >> -----------------------------------------------------------------------
> >> This mail sent through University of Auckland http://www.auckland.ac.nz
> >>
> >>
> >> _______________________________________________
> >> IPFIX mailing list
> >> IPFIX@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ipfix
> >>
> > 
> > --- 
> > Atsushi KOBAYASHI  <akoba@nttv6.net>
> > NTT Information Sharing Platform Lab.
> > tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> > 
> > 
> > 
> > _______________________________________________
> > IPFIX mailing list
> > IPFIX@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ipfix
> > 
> 
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From akriegel@4edgewater.com Tue Jul 03 07:54:06 2007
Return-path: <akriegel@4edgewater.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5gxK-000703-4z; Tue, 03 Jul 2007 07:54:06 -0400
Received: from 200.175.191.76.adsl.gvt.net.br ([200.175.191.76])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5gxJ-0003Rg-AL; Tue, 03 Jul 2007 07:54:05 -0400
Received: from [200.175.191.76] by smtp.secureserver.net; Tue, 3 Jul 2007 11:55:37 +0300
Message-ID: <01c7bd69$11c09d00$4cbfafc8@akriegel>
From: "Ophelia Obrien" <akriegel@4edgewater.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Utilizing the technology available to us at our cGMP certified manufacturing facilities we have formulated our new WonderCum. However, if you are using any medications, please review wondercum ingredients to your doctor.
Date: Tue, 3 Jul 2007 11:55:37 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2905
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2905
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

It goes directly to the root of the problem to increase power, potency, volume of ejaculate and intensity of climax. I began feeling pleasure in ways i used to when i was 17 years old.
http://baycow.com




From ipfix-bounces@ietf.org Tue Jul 03 09:40:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ic6-0001yB-7k; Tue, 03 Jul 2007 09:40:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ic3-0001sa-DM
	for ipfix@ietf.org; Tue, 03 Jul 2007 09:40:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ibS-0004I1-27
	for ipfix@ietf.org; Tue, 03 Jul 2007 09:40:15 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 15:39:35 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAABbuiUaQ/uCKh2dsb2JhbACPJAIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147121381:sNHT1351695522"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63DdWEr010136; 
	Tue, 3 Jul 2007 15:39:32 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63DdQTC022401; 
	Tue, 3 Jul 2007 13:39:26 GMT
Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA25018;
	Tue, 3 Jul 2007 14:39:14 +0100 (BST)
Message-ID: <468A5186.9000207@cisco.com>
Date: Tue, 03 Jul 2007 14:39:18 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703181741.1134.AKOBA@nttv6.net> <468A2306.5090205@cisco.com>
	<20070703203200.1137.AKOBA@nttv6.net>
In-Reply-To: <20070703203200.1137.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5408; t=1183469972;
	x=1184333972; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=kr5G62hd0QnakSVgMS9SMD1mdasVRVZ7iyHS6mqSrsE=;
	b=ls/3hmzF9WS29fbS3tB1C7Gd0/orvdEn9pH5SdTiZIK7eFMCouzKYFylYD2XHHEU7M0mkx+L
	a0PhVsoyUjR7xh/4FnGg9T0b6HwJQSJMzi1PL7UghR7usXwBWgspvFai;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>
>>> The document describes the Collecting Process should shut down the SCTP
>>> or TCP, when it recognizes the padding field is non-zero value.
>>>
>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>> the collecting process side, it simply decodes IPFIX message, it seems
>>> not to need to check the value of the padding.
>>>
>>> I think that "shut down" is too severe for Collecting Process.
>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
>> in this situation, its general rule (from section 9, "The Collecting 
>> Process's Side") is:
>>
>>     If the Collecting Process receives a malformed IPFIX Message, it
>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>     SHOULD log the error.
>>
>>
>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>
>>        Padding
>>            For
>>            security reasons, the padding octet(s) MUST be composed of
>>            zero (0) valued octets.
>>
>> then non-zero padding constitutes a malformed message, and the shutdown, 
>> discard and log process must be followed.
>>
>>
> 
> At least, checking the value of "paddingOctets" seems not to be task for
> the collecting process.
> I think that checking the validation of each field in each Flow Record
>  seems to be done by next process after decoding in the collecting process.

For paddingOctets in a record, then yes, I could agree.

However, padding between sets will probably never be indicated to any 
other process; they're more about the structure and format of the export 
- so I believe they should be checked by the Collecting Process.


> Even if the value of paddingOctets is not zero, I think that it is not
> malformed as IPFIX message.
> "paddingOctets" is one of value the Information Elements in Data Record.

OK, I could agree with you. Mainly I want the point to be clear, to 
ensure that everyone implements the same functionality.

So let's see what other people have to say.


>>> - 3.4.1 Using any Information Elements as Scope
>>>
>>> The following description seems to define the handling,
>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>> ensure that you're following the requirement :-)
>>
>>
>>> when the
>>> collecting process receives  option template with Scope Field Count of
>>> zero. In that case, should the collecting process shut down the
>>> transport session?
>>>
>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>    export of an Options Template Record containing a Scope Field Count
>>>    of zero.
>>>
>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>    check that the Collecting Process logged the error.
>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>
>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>
> 
> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> of scope field zero.

I recall discussing this point with Benoit and Stewart, and I believe 
our intention was that IPFIX options should always include some scope 
information (unlike NetFlow v9) - else they are just like ordinary data 
records.

And I believe that's how most IPFIX implementors have interpreted this.

However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
Unfortunately "MAY NOT" is not defined in RFC 2119.

I believe the text should have said "MUST NOT", and should be corrected.

(And also, we should be more stringent about checking RFC 2119 keywords 
in drafts!)


>> So a scope field count of zero constitutes a malformed IPFIX Message, 
>> and the shutdown, discard and log process must be followed.
>>
>>
>>> - 3.4.3.  Metering Process Statistics Option Template
>>>
>>> It is not clear as following description. It seems to be condition that
>>> several Metering Process on the same Observation Domain use the same
>>> Exporting Process. Is it correct?
>> I think it's quite possible, since I don't see any exclusion which says 
>> each MP must use a different EP.
>>
>> P.
>>
> 
> Why are multiple scopes needed in following cases?

Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
Option Template") says:

    Note that if several Metering Processes are available on the
    Exporter Observation Domain, the Information Element
    meteringProcessId MUST be specified as an additional Scope Field.


Therefore we included a test that ensures the Collecting Process is able 
to decode multiple scope elements in the MPSO.


> It indicates the metering process id and observation domain id?

Yes, the meteringProcessId.

P.


>>>    If several Metering Processes use the same Exporting Process, the
>>>    tester MUST create a Metering Process Statistics Option Template
>>>    containing multiple scopes and an associated Data Record, MUST cause
>>>    the Option Template and associated Data Record to be exported, and
>>>
>>> --- 
>>> Atsushi KOBAYASHI  <akoba@nttv6.net>
>>> NTT Information Sharing Platform Lab.
>>> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 09:40:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5ic6-0001yB-7k; Tue, 03 Jul 2007 09:40:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ic3-0001sa-DM
	for ipfix@ietf.org; Tue, 03 Jul 2007 09:40:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ibS-0004I1-27
	for ipfix@ietf.org; Tue, 03 Jul 2007 09:40:15 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 15:39:35 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAABbuiUaQ/uCKh2dsb2JhbACPJAIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147121381:sNHT1351695522"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63DdWEr010136; 
	Tue, 3 Jul 2007 15:39:32 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63DdQTC022401; 
	Tue, 3 Jul 2007 13:39:26 GMT
Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA25018;
	Tue, 3 Jul 2007 14:39:14 +0100 (BST)
Message-ID: <468A5186.9000207@cisco.com>
Date: Tue, 03 Jul 2007 14:39:18 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703181741.1134.AKOBA@nttv6.net> <468A2306.5090205@cisco.com>
	<20070703203200.1137.AKOBA@nttv6.net>
In-Reply-To: <20070703203200.1137.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5408; t=1183469972;
	x=1184333972; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=kr5G62hd0QnakSVgMS9SMD1mdasVRVZ7iyHS6mqSrsE=;
	b=ls/3hmzF9WS29fbS3tB1C7Gd0/orvdEn9pH5SdTiZIK7eFMCouzKYFylYD2XHHEU7M0mkx+L
	a0PhVsoyUjR7xh/4FnGg9T0b6HwJQSJMzi1PL7UghR7usXwBWgspvFai;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>
>>> The document describes the Collecting Process should shut down the SCTP
>>> or TCP, when it recognizes the padding field is non-zero value.
>>>
>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>> the collecting process side, it simply decodes IPFIX message, it seems
>>> not to need to check the value of the padding.
>>>
>>> I think that "shut down" is too severe for Collecting Process.
>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
>> in this situation, its general rule (from section 9, "The Collecting 
>> Process's Side") is:
>>
>>     If the Collecting Process receives a malformed IPFIX Message, it
>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>     SHOULD log the error.
>>
>>
>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>
>>        Padding
>>            For
>>            security reasons, the padding octet(s) MUST be composed of
>>            zero (0) valued octets.
>>
>> then non-zero padding constitutes a malformed message, and the shutdown, 
>> discard and log process must be followed.
>>
>>
> 
> At least, checking the value of "paddingOctets" seems not to be task for
> the collecting process.
> I think that checking the validation of each field in each Flow Record
>  seems to be done by next process after decoding in the collecting process.

For paddingOctets in a record, then yes, I could agree.

However, padding between sets will probably never be indicated to any 
other process; they're more about the structure and format of the export 
- so I believe they should be checked by the Collecting Process.


> Even if the value of paddingOctets is not zero, I think that it is not
> malformed as IPFIX message.
> "paddingOctets" is one of value the Information Elements in Data Record.

OK, I could agree with you. Mainly I want the point to be clear, to 
ensure that everyone implements the same functionality.

So let's see what other people have to say.


>>> - 3.4.1 Using any Information Elements as Scope
>>>
>>> The following description seems to define the handling,
>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>> ensure that you're following the requirement :-)
>>
>>
>>> when the
>>> collecting process receives  option template with Scope Field Count of
>>> zero. In that case, should the collecting process shut down the
>>> transport session?
>>>
>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>    export of an Options Template Record containing a Scope Field Count
>>>    of zero.
>>>
>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>    check that the Collecting Process logged the error.
>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>
>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>
> 
> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> of scope field zero.

I recall discussing this point with Benoit and Stewart, and I believe 
our intention was that IPFIX options should always include some scope 
information (unlike NetFlow v9) - else they are just like ordinary data 
records.

And I believe that's how most IPFIX implementors have interpreted this.

However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
Unfortunately "MAY NOT" is not defined in RFC 2119.

I believe the text should have said "MUST NOT", and should be corrected.

(And also, we should be more stringent about checking RFC 2119 keywords 
in drafts!)


>> So a scope field count of zero constitutes a malformed IPFIX Message, 
>> and the shutdown, discard and log process must be followed.
>>
>>
>>> - 3.4.3.  Metering Process Statistics Option Template
>>>
>>> It is not clear as following description. It seems to be condition that
>>> several Metering Process on the same Observation Domain use the same
>>> Exporting Process. Is it correct?
>> I think it's quite possible, since I don't see any exclusion which says 
>> each MP must use a different EP.
>>
>> P.
>>
> 
> Why are multiple scopes needed in following cases?

Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
Option Template") says:

    Note that if several Metering Processes are available on the
    Exporter Observation Domain, the Information Element
    meteringProcessId MUST be specified as an additional Scope Field.


Therefore we included a test that ensures the Collecting Process is able 
to decode multiple scope elements in the MPSO.


> It indicates the metering process id and observation domain id?

Yes, the meteringProcessId.

P.


>>>    If several Metering Processes use the same Exporting Process, the
>>>    tester MUST create a Metering Process Statistics Option Template
>>>    containing multiple scopes and an associated Data Record, MUST cause
>>>    the Option Template and associated Data Record to be exported, and
>>>
>>> --- 
>>> Atsushi KOBAYASHI  <akoba@nttv6.net>
>>> NTT Information Sharing Platform Lab.
>>> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From inbsw@entory.com Tue Jul 03 10:53:43 2007
Return-path: <inbsw@entory.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5jl9-0004tQ-Sd
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 10:53:43 -0400
Received: from [202.59.206.70] (helo=iveoer)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5jkO-0001fX-Ls
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 10:53:43 -0400
Received: from pybs ([44.200.65.175])
	by iveoer (8.13.3/8.13.3) with SMTP id l63Ewchw010785;
	Tue, 3 Jul 2007 21:58:38 +0700
Message-ID: <468A62F3.8080101@entory.com>
Date: Tue, 3 Jul 2007 21:53:39 +0700
From: Gideon H. Jones <inbsw@entory.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Announcement-KTVZIART.pdf
Content-Type: multipart/mixed;
 boundary="------------040108000603060402040202"
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32

--------------040108000603060402040202
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit



--------------040108000603060402040202
Content-Type: application/pdf;
 name="Announcement-KTVZIART.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="Announcement-KTVZIART.pdf"

JVBERi0xLjMgCjEgMCBvYmoKPDwKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL0NhdGFsb2cK
L1BhZ2VzIDMgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9QYWdlcwovS2lkcyBbIDQg
MCBSIF0KL0NvdW50IDEKPj4KZW5kb2JqCjQgMCBvYmoKPDwKL1R5cGUgL1BhZ2UKL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzIDw8Ci9Gb250IDw8IC9GMCA4IDAgUiA+PgovWE9iamVjdCA8PCAvSW0w
IDkgMCBSID4+Ci9Qcm9jU2V0IDcgMCBSID4+Ci9NZWRpYUJveCBbMCAwIDY3MSAxNjFdCi9Dcm9w
Qm94IFswIDAgNjcxIDE2MV0KL0NvbnRlbnRzIDUgMCBSCi9UaHVtYiAxMiAwIFIKPj4KZW5kb2Jq
CjUgMCBvYmoKPDwKL0xlbmd0aCA2IDAgUgo+PgpzdHJlYW0KcQo2NzEgMCAwIDE2MSAwIDAgY20K
L0ltMCBEbwpRCmVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagozMQplbmRvYmoKNyAwIG9iagpbIC9Q
REYgL1RleHQgL0ltYWdlSSBdCmVuZG9iago4IDAgb2JqCjw8Ci9UeXBlIC9Gb250Ci9TdWJ0eXBl
IC9UeXBlMQovTmFtZSAvRjAKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9NYWNSb21h
bkVuY29kaW5nCj4+CmVuZG9iago5IDAgb2JqCjw8Ci9UeXBlIC9YT2JqZWN0Ci9TdWJ0eXBlIC9J
bWFnZQovTmFtZSAvSW0wCi9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDY3MQovSGVpZ2h0
IDE2MQovQ29sb3JTcGFjZSAxMSAwIFIKL0JpdHNQZXJDb21wb25lbnQgOAovTGVuZ3RoIDEwIDAg
Ugo+PgpzdHJlYW0KgAAgUDgkFg0HhEJhULhkNh0PiERiUTikVi0XjEZjUbjkdj0fkEhkUjkklk0n
lEplUrlktl0vmExmUzmk1m03nE5nU7nk9n0/oFBoVDolFo1HpFJpVLplNp1PqFRqVTqlVq1XrFZr
Vbrldr1fsFhsVjslls1ntFptVrtltt1vuFxuVzul1u13vF5vV7vl9v1/mgVFR0OgeOY8s6mOaUEZ
KJtSHhzhpNUz/fq9HgRCOAzlPHg8Dwefrhz8IJZUgh0FVCf+Igmg0ThhhL1cpy8/c79ghKM8hOe/
1rOZ25k+/iGtgYR10V35z4LOzvRlb95cCzCmUw4xUC0+oAGEDwAOe1gXDhwR3UmM79U3pgXUgbhU
0LKhLgwqOfp80c/MHwzXughL2PckD9oExySP6AEDQSySHva5MCIm4yBuEigePkXqBu1BzpQ8gzlI
K0qBioCoAB47oKg8wgAEI6sLIazSUsqhIeDY+jvNeCp/xPAKDiUyrLtcHjMDtGzqoECsJIEOjqvg
hUaJFGCCjZIDLQ0ADlSLIbsCoCMcoVHbyx8gYmyrIMsIwHkXR3J6EyjLLNotNcAImHg7IFEcvTBD
8+vQgpTOqcMeNu+rvjogUKB5MiFn7OSTjO+b/PDHDaRYggLyQhQeN06k00CHhTCoU1Bw61NEIHTK
F0ikcpoG3jX05R4AA8+VBR4hcKOEc42DYxgAN43s8sQ9EiNDYaCH/BwqPqwbCQpHqFVY99il7Y8T
1DUbZISOlTUWidrINbU+3JajqNBDFJIEcMb1UgbBoG5sl03R0CQzUNSRvE7uhVeDDXkhZO3VWKJU
u8VTIOEeBMs0s/viU00gANlcIMwtEwc4QzjYa5KIJgSB04ggPXS69SZBfjyRFAONsZBCB3PerP5G
AGIVCh9FSnlrHxFAmZ4ggmJ33U9KPfTWPXVWSB5G+SCXZbl/t+92NY4xoAYVILqxGgjsW3csPszQ
DSXxSRoQIFWiRPhCGM/GSB1IxDsSzG7qPsgUV1QgTLIUEedoJEKJRXRLEYZH5O4JtqBbfv19YrVD
IgBNwAEpjqBb5kDqtDk2bFMzeyoJs6D8jyZOiVZLP6NPLsYGhLD6KgnR9LEXMPC0nF8hzGDABvSE
8tZGlA9t+x1mguDOc8thIF0nDcvOOZeBt2469r8JQxtzvWUgjaXi8e1N2EaCMxRzX6Zm2nQUgVnW
77qDYUgvxIPbKCH7uoAXhbtE7+goldigQIw0+9PLTD4uMcahR/LEnKNWeWAAzBr0jGygaFQ2Syn5
rMe0iA6qvmqtuf81mB5BIJEMgNBllpBoGsgTxAJdaN3zv1dyHN4ZBX2nWg89Uh0LzNjOgIY1/iWU
0uRdSnx6RnGtN2QI3ENg0IQG1SaolihBn9vybYyI0a2GaG9GgBdz5tTIrQIQEp77zCEGfdWihZjK
SGv7BGOdIKJ1Zmxeg8hxrj3dIEDYJlV8YXbmvNCbpQLND5xJIcdQUwZ2NR4dJGCNiwzNJPNGqB1c
Y0HO7IFHcSkC2XtZPDFVxMhQARZRIv1vB4onxQj05E2ER5IrvlG8ZmxA5Lw9kow6IcQzPqOOUbBr
Z8wIxPUNC+UpA3SOmZCnlzMVjsu6VMpZz762FBKHOcRbEuIikueCdgHBCnixPY0q8c5AzkP9ecAB
2rcZewgfoTA1UTiCTdjGrJ/M15kniMuaeC5FJwrIeA2KVcrJmuQYiYyTCcHEOXn7LU6KdzX0HhdP
+L4SlOCmEInlmKd24IaVExKCgE1mQuWe+sqcOBei9DYztltED0wdorCk+cr2Jn5o4WAKkaCaUjpK
r1qz+6IvyhizWhFPyagRgJUArVQoQRCqJUkvwOIY1KKtL0w4vZ01OqoXsKkcqq1Zq1VurlXavVfr
BWGsVY6yVlrNWetFaa1VrrZW2t1b64VxrlXOulda7V3rxXmvVe6+V9r9X+wFgbBWDsJYWw1h7EWJ
sVYuxljbHWPshZGyVk7KWVstZezFmbNWbs4RYVESiBiEYiV2QrGhTCZdIC00RlaDhzYjUaztsSvi
oFRRNmghKQEmtchgM9QpsklolAF/UskiW/btF0glTGXtdtlc0lduBeqkY1cyE1xiJDQs+IQNlErb
EZhORNkxJ7tkDujDKHt0Be2/M+nhClGWt1DudfEkghLukNF7Ugg8d4HmbH+KhFqN7gkKHG2ghV3y
JC9a6KaWOA3+X3BHLkiobLjUjILJcgl9LXBUwezIgVopXvjvliEkuHyFn4X6Zg6A51IgqU4tunBy
VlMpRHSMXp+U0rhnwct7BCMKHWNO788TKUGEPeeiTGmNjurWWOeOBhiEDTFINADEWUyO4GIHRwKg
vWzp4frkKTjEpeXbpVL1EzbqMJgH7ljLQHg7KIX7DBRaARTOgIK/5yFTUSN4zSyJPAqKaETSM1tP
lMW7Z9yFnJs98ETrzypo0isZGIY9qkjkOx4V+kEyG/2+AEVTTl0iL1JSWKZxbQ6fvOjsnUZmZexH
NmXSMrXk6QWqRBNK6XZAdBaZ7CDTV0dr0ibtdd6s0sqZVzIFZqyieOE2WJJ0UOINnMg5rdUuJRy6
1d54QPYyR9nPae16Foi2FtlACDNdME19ufX8qw5zf28B6/09FvuhUildOOIMDIUo60rd5BhwtqRp
lZES6ova23cfiFu/c/n3OqdcKgdMa7rc/mxtB1FXK1fdaPdHGSF3hIKkoggFVUYsB4ibeJF1s40I
Hj87+tSEARdWGdvuUG3Dh4Zj0keOCIaVb9t1FsweNc/fgrbk79Zl8JJJBY1fOiCq7Pl0YmmvCQJw
6B1Op3UCOyG6p1nrXW+udd691/sHYexdjs4zMgoZ0SxA7J2uokqYQLqNu6yUtp5YkJgPsAiLxu2d
7Kmudpb0GL6MN+fggg52usuRAvZms2Dtuse4QaDXiH4LoQz3zyxNEtJInN2lTeZTyqPmGQegqRzq
olIXyPOofVXt92DwFSXpvL+xNssahao5lEKi8gaDeUY3q2abz4gkXooQ9fckiMjNLqey+USPv15K
XfAYv0tqcCdds9XS03RXwaQK/7tox6Py/wEhMzLlojWrYEI8JreWH1NzN2n3pChj6H1h9/YiD8n5
f4/h/0RZmLW00mnFuFvEfFfMeIavkiFn7iDEzCItAmflRQDv9wIiKKCnEtIDXuVEmEnDlo7iEJUI
+iIomlAKsHKpFlJpOF8QJQUiUJ6n0DCDVEOjLhwusEap4DENYCGH0v0qACEJoj3MoDQQVQgjPMuC
LH/KSEzPsqKFiwhQmQmwnQnwoQowpQpwqQqwrQrwsQswtQtwuQuwvQvwwQwwxQxwyQywzQzw0Q0w
1Q1w2Q2w3Q3w4Q4w5Q5w6Q6w7Q7w8Q8w9Q9i0qRrSrxrALTiGwgKiLXCEhwwKQuxDCBsJCBhxhxi
fDrixJziJxGm1ueEPvhCCxEDpRJCajRxEiwrcGgPDsCCdOAEHwICOLsCSp3CJA2RVCVjRCSLyiNx
XCLAlRTNdrchTQksDrrNAiEngKhrtP8igxUCXB+lKMpCxL6J2vVChxkL7RYiNL+rgM8LaLtDtEWq
RwZAzxoG9n8g5sPFRJAo8GXkeLasJMAsEJDA+l1MBiCsNPyLvOMCIRxmts8CIglRICFjDRyE+IbL
vEwQbugvILrCDvQiOLaCQRpCJnSMGL6iDyAFJBMwiCzuTqRkOlmGIjxgVMUFGDkletpD0jxnMltr
3D3tJssyCoxtGONssyNSXtXCBsVGbunLyMkyWp2tuIqqhGJpblEsZMSIWkattsWSRGgpwSTPamIy
VslNxNbCBMVSenayRygoxlRMjrwGUvziKSdNYSPs4yqDyGwGQGev3xMItvCwRmeNnxqN8iFSyMWp
KygMoNTiOuZRhS0jrSZNJmROjNoSRHdRMSYsaj0yODQtxCmt7yNk0g6N9lonQvztkGmqWmBqYM+Q
cGiKhHOLvgKheoHl1OGiGypEFpHtEswzPDXB/syyBMotCFaM2zIs4o7D2zKDdTWzQmSDqxNPRDlo
VM7xAH+zdTRIIuHGEMtS1kKpHm3MpS9FAIhSOMtiEBnTUAPG5zOoOm8zQIPj6R7NMMvmaECTPynS
1H0MvGaTUzyFNSBFRTkKYTpxdDysvrtznlHTizXiDz5M2v5DlEpy8MxHwwCyUnIM1MtpRxNmBlHU
BToHWDdSOCBzICmoitQESEczFnXCDnOFYjNSTI4GbMKNQjuiHy8HDtOjXGfwcDVm9Dho5DsNjliD
JSdtVs+UMo9yyIOUTnZHwPPCFJKFpnEjNkomwMmMeNQD3NRl3shSbM6rtvoJdtZJ0ulCD0gmaTKP
xn5S4IhD8GGUXUooxMgo+mxCINL0Wt2R80wmlD0sSOPQMCEtyUYUnnTyhCHUSG7F+0mH0TOICSzG
zjYjStPsfCH0rUOOpE3tP03SCScChO8IGDyQMQbl3NnmsmktdjEMsuiDuFmiGzBI3D2NpG8ymNBT
SjJA5otFdsVqIjM1QGGsYlcjq0/m0VJ1VGaVKkstku8KR1GDxItSp0X0U1Qvbj4vjl4jXFDF3tiN
Mj3jKtutmEiGRT5gAUmwKlYz8STT9CDU31NEK04nTSliLPCVTkFtcSeo/m8lNOzETytHwKpiDlXV
ViEMdiGNZiCsTVTs4nEyyj0VmmQ15pyDl1dqo1oiE1qVbHIP8oivCV6v3Cml7z3ns0MQiGoiETgk
hFZwGuGT4TliFN+l10FmIsWRg11jrKQOCmo18zLPRDNykPHIttWl4uKOI2LEsNOWRKLlsuHCFs/W
UTT2VG8kCDxqLFt2csa0LtCgAWeD82UmHn5TwIaEmENOINvTqvFWnSzCHuVHQN3NxjR1RgAN5khE
stOxjN9GDkezrWfo6tdyLmaOGksBz13NdkyGz2aH+rcvC13WuCD2PHEl5tOTLTG24ozycWvW6iBU
rCEUVWS1pp02YCqURt8tajPgKs8Ny10M7ktGiIT0RJ6y4zqhzuXDB3LzCM7mRF1StWnn0DXT/kyA
6XSDkH3ucITXIjUA6QiORocjh3RWEVviiFmOQTqyQlAuYBCUoIgksOPCB3g3QQW3YSsWGiFkUl33
KT/iI3NMiiBSYiFNs3qyxn5F1XjITFKOaHwH/tRPPORE826FEXiAm3xH+k5UaSVCDUbyx3RX21bk
sljJ911zDCNOYL7SM3zjU22ivQdCbD5JDLWFzMOCMumNoYFN5qKGQT5zlX6tKjP4EC/KooLCFjhn
yLmB/qWqKibV2XuDXEFYQNuDZYF4R3WO/G4IyVMk8r7yCOrEYlz1YD/YNSimt4XWyqtzTTfC8tmQ
+LIuQDCYNi+AcRqYj4n4oYo4pYp4qP9OSrCPdk525PcGdKSo2iikS1eCuNir5J1v1FyYliaMLG3X
jwO3VCFSFVD0tCKp8iRJ7iqPGiHYyCOlLUEq+GLCMxCCWZBCd1kFaW8RP4gvgyZm9n+XSERYnUHi
S5DCKJUTzv0WlmgP6iIxtiH4riPN8nciS1tiSEODIEtg2IivYHiG8E2jkg+hMu6sCy1XPiNSHCR1
oCHS4wQib5YHKEzErO4kT5UJOk93lCJY1lgE0WsCOhnAI5fJMH4ZiCFZaiJJKZhiLEXUNAAZYCKk
ukv5jkRE2HCEs5oHYkgG/M8ZvvYZSET0fCNkvGTiVEvirvfD4lcYbY+vg1fEGIoiM5qo0o5YcYZm
TIWl4WCleqTkBRMDLukQXDm1x5AlsuOCDn1Df1fRGPqQZkIzLIi1/iIPuWwUg3ZX5lcldEyYss6v
FaCLmXPwE31iE4XSgu1R75ECFFPDQ6WqGHc1JjdnS6N3TCGHsL7iD4iCLvbX6CP3+Tg6KCnFivKG
Bmnae6Dvo1yCCaUm/E3WHrwlMmUDvmoDJM4vplgPWEnwl2PvsB/6MSaV36UHSmrmGFZPm3pEcjwW
Y1yaxjHa4SXzgwAEUJWJWo7Br6r5oqKml3FqNCKGOCBoZ4KJjPnGuRfaq68bJagoA3FwAAAU35AZ
t3FIn6nu/11l8voD/vpHGa9GFj0znsE6d7AnjmWINmPorUCbR6uozkmawD9Ppnvgm69tpmSl2a1I
zKZja7cm97UmG2rHEmu7htLjC6IEx6xgAbe7UiY5mX+0dHPWqE8kHYr5kzfuZjl0OE8n6HAl40vP
1yFXSpxbwnhJBa/0lH4EyJYpMGGx9Nd7ypW5yCBHYGrDH46mtp+UYZ5KZ7zCERvmPI9E8oY1HSvC
IP6JhcFGtRCcG7JNrCBx3ZNtjXTrmbxmhDUjau9CFDKZ07xUyRGLQGRYlDDlTaNnlJwXWMIFAKGc
DJSTJb+HlneurcKo9j7wBHXnlI9YcNYiBGyjlmznc5riChOnelsDNHnOOHo7tU9iCjnHRZZXMCXu
ZTvW3IJuivgoub58FPEmQaWmun57AH1D8IDlXnY5On+wfPkmg80ZKGVHXoeG/H/77n3H6aqOiT/q
bvIoFUroxxY0Sc/QFICIwUhNFtaPr3tbMgAYPCGMXlgcFLvmtPFiHIR5NEakCcudJczqplL408lr
rbVvFoJSlHGr8m+6sIpKFGQFJdVp/Shaw8xJhDtR9a+oWF56Xke9A6FCIMP1/4+81IYCE9Fn3R9L
3IKDu9jPB9bqS7GI1BO9dbrJGpUuhIkcU7bjvoupXQ/xzu7FHxZvACBVJzTWgKHo1s69ypVGNIs7
h6FxGZY71G9ZmCFl3biPtclHJHDdF45IjUwbyDUYh7u9xI8wSo3Fi3yJIJPOU6ACDRXZ/ZtogQLP
TwYFQpDbJPxjqQPvAIk7bDUrkCGd2nb7rzmiG5RHEnkbv01Qbl8S2qPdwHU+OZY7GI2UodtpPJQG
KwNCDb1RBwN8U9JJRCH+K8N019ZJK+i62Wz+Wpu+X505GCYIKNJ4tiJIAQbvvkFVOF40u9k00GXo
3prziVB6bx2mNKBGtkeJi8hyVJ7GUnuJuINFgJv5H8OVilEjdMfwc6bCbpqDYGBp56K8V4xXuG0P
viEcViHDckaOZSTrks8eWIGGu6Qmecn5LiKppCI6PkmOQ8rZNbGiHERqmJfJmVkiE+hFqR6emVcJ
0e5+w8Me7GXu4RQipsxjddYnU5FqYpRFn1uEYnwpaCOqcIeKdwleq9NwjdpwCIo+89KGKeJCkzeZ
FCWfK4BIHJydUiE9EIYKbDHwCCZUHCLKPn+/wkb/MCHOGRbqOn06jKciH2HjUKXs0+Df4VTfmqTf
kflqzCAHN/gCCAAzmyCwmFQuGQ2HQ+IRGJROKRWLReMRmMnQ6RqPR+QRhOkp+yGTSeUSmVSuWS2X
Sg5nNejxwmeXzecTmdTsAEsVR2eUGhUOiUWjUekUmlUumU2nU+oVGpVOqVWrVesVmtVuuV2vV+wW
GxWOyWWzWElB6z2udjy1Wy4XG5Tl+oQIjyJFQcRRCIRer2nEpxyEllSlnQVQm/zWEkolUbBVAeXi
55XLZeNB6SgB+5SHqbDRJTISCL1TU3HYTQy/J6CDtALjzClRex06B6EABCTJTOGEiPHwwIhHO26a
SvU2vR6TMc3nV7IwUeYDh50PW9TDxTdsIwOHoTTxniRPZbSOAA6X3l4mDQdMpSRw3q27NOHs9vwv
/O4Xa58zvcSiLuyhT9ISjiOPUvrElMmwAPeiLOpckZxnGfpTH+6bPAA66HP08r+wQ8DSBU0z/jYT
IAQnCsLoK6qPxE58YxkqzkoIu7TISDzPO0iY+vCgqagiNhKBGh4zs2i0DkIPqCpkXrfIK4CGRwgs
dR+AC9IKfrAIgv6EyIADBB4uq7occMuIKf45sVA4AR83U1gBILcohCKMyW7bdoJOciODFrpoSt0O
zWXrDNqoCCNHJyCyG4E/Lsgsjuk3qZtAiUfSvGdNU2pMpTTLc0IWyaIjoaBCDYKi+oZMC0iVC9QE
pI9Roe2LZwOaCEt3KiCTAhcvOkOweDYmbtNW2KIpkhMHsct7OVChNhoUNlcIKKk2oLVSCDYJqJ0k
glhISKgIoJWoqWs9FqIJXUrz7VtX1/OyG2mADZSw89qr7OMvyKgsWV5BoAWDOlLWncrVt1VFOYVh
aiPgwUVwxZ7FQ0h5oSYxU5ve+M0rwHEUIif90gBQ5UVyv1QwfUVQvohxoSQhy/WhFGNoJDCGh42l
ilM7uXF6wr0UQADRtLIKJEzgEdXC0+QzYABUYtH9foJjSEwvQCDYohTu2dLD+365aF5SgkLILj0q
2boQqZ2hOfoLqGGbhuKb17sZTXjejPWToUoIaVDmIJvVtQCxxxw0Xq9ojrdqtrkt+11RkhoZeLi7
RHmazjcyGz1yAAU9ROX0DZ5w3G0tDaC7YAb0g6I7Mgmk6+ADujnLdzTRU/UcCAFGoTsjp9bM1x9n
LDaWhPKF8i6UkcO6XKu3vmR4Pv06bl6nqpBsUwtPWAz4pStMoXp9cvYgg+4/MIPVc0uJXllzy2tx
qCVSAESFNbfyob7bJg9YK/Yp9oSzvv0W2rwTrVTvELWCQpcTbFzNBVQtkggTWLkOF6gF1wdmqmnS
EQsOj8EsIKILBJjSzH0qwIhAtlxPYGioaeaR+RCn7pVMefov6sV6PNUsdKAD1oeQ9JA8ggiFSTws
IUk4mobHdpaNO1du5QYmkoboZx77rmKJZIKoV4ijAcNDUi9NKbiIbxXR4Dh0j8TDBShYqdxERiDx
edCUpWZpVipNS2QmNMPo8R5Kku2IT6gcPPJwv5PboChnGJi95QMOyQtShuDyQ5lBwhsH+rUk0dSp
POkksdtz4Y9Sdk83FqyhV+SfIuhaA5VoUyklVKuVkrSqkzISmqV0s5aS1lsTo1qDI3S3l5L2X0v5
gTBmFMOYkxZjTHmRMmZUy5mTNmdM+aE0ZpTTmpNWa015sTZm1Nubk3ZvTfnBOGcU45yTlnNOedE6
Z1TrnZO2d0754TxnlPOek9Z7T3nxPmfU+5+T9n9P+gFAaBUDoJQWg1B6EUJoVQuhlDaHUPohRGiV
E6KUVI+QEAplbmRzdHJlYW0KZW5kb2JqCjEwIDAgb2JqCjY3MjEKZW5kb2JqCjExIDAgb2JqClsg
L0luZGV4ZWQgL0RldmljZVJHQiAyNTUgMTQgMCBSIF0KZW5kb2JqCjEyIDAgb2JqCjw8Ci9GaWx0
ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDEwNgovSGVpZ2h0IDI1Ci9Db2xvclNwYWNlIDExIDAg
UgovQml0c1BlckNvbXBvbmVudCA4Ci9MZW5ndGggMTMgMCBSCj4+CnN0cmVhbQqAP+BQOCQWDQeE
QmFQuGQ2HQ+IRGJROKRWLReMRV/Rt5PJ5x95vd7PR5x18vh8Px+PuBvx+v2Nv6GTF7Pd7vV7PaUP
iXv12up1vV6PV9Pt9TGXSqVT1802lPuoTGoPuYwx4vR4O15u+lV1+vyNy+XPB4O97vl7z2ewl6vN
6VN9yt0Ot1PWbQaeyV4vl9PiBzF9YHAvm1xnDYfERB7yhaL5eq9ZqxZLFUKpPqNbrBaOBxN5731n
thrNVuNpmtFlNVrtJpMxoN9uN+ivtjNNkNFrNZst1tvF4u9hrpcL9dMBptZpul4OtasBcrlfr1fs
Nds9ps9ttlvrtdr1suFr9hm7Fus9otJoa1sNVpPB3O5hs1gq1lLFbMReK5arVbLnNnEbiplwWpZl
oYbNGcXJnGkaJiGMZJsG2bBmmaZJVFAVBlmYZidHuXJil2xpel4X5fG0bxrvceBbM0YpmGEaZxmm
bZwG6XhgGCZBkmCoBzMTH8gSCf6pmsbZtGSZpnGmahnnEb5vmfJB1nQdJ0OWYZmGOXZhmGWRbFiW
BbFcXhaFuZpjGWwZsnMbRtHAbx1nadqyHcdcqnScx0Hijp4nseZtHEbpyyqa5tGqch0HGdp2HgZJ
jGYZxrGcYxtGQY5nmWVZYlmXReluY5jGEdh0HMdZ3HYbJymybhyG6bhwG+b03nerKYnDWRwHLN51
G6c8qmiarRmyahhmOYReFmWR2HYdqlHQdx0M4cRlGYZpxnKcKRHucBuHC9JnF8aZfmUahnGibJsH
BW7fHfIV3XfeCJLOtJ/H7eN7x+mK+H0pp8KrfGAYDgWB4JguDYPhGCXqfqUHupK1JUlqXnmdx4nc
dR1LUmCYp6pS/o2tx5LsequpVf5/poex6nSdp0nEdJynXOx2HWdlaHfkbC4TneeZ6ip5HjRtjGya
xpGC4sRluaJrmgYNJlYVJXFoVxUGEXpdGCXheNaaU2mubxuG4ahrmud+zNYZruloXJcF8ZhlGTmp
1MElB8mKYxiP2VZSssS5HEqTJPEs/pZmobJqnUdp159xnG8cg6cHqaJpma1ZoGiZJnuQaZ2nedhz
zscZznNPNVOQ1ZmmUYZlHIcpxG0bhsG+cRwo8eRyHJdRv17RB0HLKyypOfCjH2apqGscpyHEdHRm
ya5vxOba52icZwT2ePH+z7WeKUXRfGBJJlGEYZgJ36BuGgbhnHIdxzHPmhpOQahqmgeqhYvmkqHC
dhxnofA9hyukSeN1RY6mTl4JiRshjG4DvbgdA9e5Lh+i6GGMIZIyhjjDGQMF1w4RjC+GGLgYotnp
DZG0q4UwrExi/F4/Yeg4xvDiGsNEagyhrjLHIOwcjmhqCwFmLYZwzxkM6ghEWI0R2NsdJUw1lRNS
UFxJWSstz/i+EDX4PonI9h4klHwX0uw9iPD0KVA2I8ZYzRnjRGmNUayHlSJXGSNhBGOL1gTHWCEC
SXxzJlHF7Q9COjGGKL8aY2BpPMHSssdZRR9M2HalQdLMh1DvHcy10ZgR9klHkOGTRQx6EkHpAEcR
vh4ErH20Bix7nbDrHOOoeQ8B5FTTslYd8rWgjeHGrEcg4XcwwG8Nsao2hpE9HI6MbzYBwS3HQOod
LYDYjfG3MUbo4RvjhHFLmVcq1Fj4KbJIdg6lSEkHmVMso7nRPsPcSApTnR2vuUSOMcIzhljJHEti
aI3mMDqKmQObo6ZpjhHgb4cro1mOJTqss5R7i4j7cTMqbshkVExJFH5PZZB3jZXRJwjo8x0PMHMO
UcY3BvDdJsPcjo8FXvoecbNoI75lPvHUOwr69jEkfHkMQYQvhkDAF2LwWouBYCtFinEdYyhojLFO
LAWAtRbpiFOKMWgqRSjvTknIdh0kyC7FsLIWYtTHC5NKNePw8xaixFkJ0VQmhVCzFWK4WYs1LDKk
kO4zIrxVClFoK0WYrhVCwFQjkYguBcC6FyLoWoy1QE9G4NsbiaBijIGcMexox2ri8sELRY50D+i6
sIMgaAxReSBkdR0cQxRgi9asL15Q5hojYGeLMXYshZC5TEgVzo7hzu5g2MAWotBZCuFsKoZ40hnj
CfGL0XovrRGDGaMUZYlxOiVFeLcVovLSjNGgNAWwtxZivFSKIaAyxiu6GGMkYArK7qdF6MwZYzyl
DUu+6oZItBZphFwmWnQvhgjCFWK0VArBSCfF1bySY8BwDkG+1gXY0BrjTkUMgYgwa7ioGQ6uTo9l
8kbJ2yoeo7JHqGGzVMoY8ycE5JtOAfBIiVFQJXJyVxvzfUZYaT3E4+JXK0N+PKTz9ibD2gLJN9o5
RyydnCXCKBXWOFJJUPkfY+R3j0HeW4eZO8dpVHOYIqY5h2DlG+OYcLkaKNAHgUaLBN6XjqlcWRoD
dTBD1I7Koc5fB8wSX2nsjw8x4lKJsPiREyRzudHYSBs1cZ9jmJBKLPg8yRxbHnBJ+w9Tfjvo9kEk
mOB5E1JFiQkTwjBxuLiV8mLDYXRZjgRcpKjxmCzP8g6nUPxfi5F6LkYYtkYjVxwPQZg0RoPHNQMk
YQxhfjBbwMUaI3hoHja4NAY6WRdjBFyMqQGdh4tfGqLUZ4tRiDOGRBYZBUzSjVFOJ0ULVxejEGkc
EaIu1BjmmqOFJAxMFjPGKL0YZsRtjBGqMEXx8hbGOFoLgWIwBiC+aAO5hY3h0jbFeMcWAv8Ji7F8
L9yYzsRDzSmOm/IvhiDVGFF0fAydcC2F0LZSAxBl8BUwNEdPKR2sWFpq1rAvxjjKGI79Vo2RvDKG
QtQbYzRqDhGqM8ao1ViyAGML2SQ8BfHFtiLEWIzBYDAGcqJsw0xqjOFYK0UoyRhjE2yo8bAyxhDX
GHmXMQwj8C+qxB8Yirhuj2LQNMb41RgDH7ps6C4whmDF5JBoZI0BjKUGKNtQJOi/EOJ6OhZbs5qS
5mcNm27rbbp9ldJ0Zg1BqDcVcNtCT4hicyGSzYdg4B1DjeeNwa5pTdjZQkNYk49xrtEFhwo1K5hs
DXKaPmTo9Burol6NwY40Rji8GmL0cQ5xxjubMZwb7zuqDPGgsubpyx0jvTxMqgLMSf524IvXjg7R
6KnqkNZNq1Rkken/K5WHoqWE9VMO4bs0xzjoHIXQdEgRj4ukUNscI3PxDa64GGHI3UZmo8HMGgGy
GgHIHa+KYwmmUUc8J2d8VIHMdwHYHEGWGuGcX2z8l0n8HeHiGmGgGqGWGmWqG+GYm0MIJeGwaJBW
Gqg+GCG8hO7cHsHAHWeqeSmePKu+SyGKGO4w5iGKGGGwGGGyQAHcaAIeH2K+cqSYGmGiHGHGHIGs
GwGiKUlUHMdiGqHQHeHQ5WHcHITwKmxOHucOa+GwTaG8GwGYG6GkeuUKsUG6G0GoGiGapWToZeM4
ZgiySoHMeOGkgykCFwF264F+G+HUHELOHwGmecygyEqkgKmWHMG+GK6q8wG4PeHgpGOQGkG89VDi
GuG2HOVedcGoG0GwHSm8bM+8aAdyG6iIIKKQKigUYUjsj4IUyUHwkEGEFarGOOOuGcGUJqgAW6Uk
GcFoGMFiFEF0FWFeFsFbA8qkPeFsFeFgGStMF+RCGkW88wG2E0FEE8O4F0GeGcGaTslWdIGIGeGA
F4GeF+HCncGkGmGkuyFiFaFSFIFuTAO4FiG5EkMEGAGQF+GIQcbWFkrmF8vkOgFkFMGAFSFAFOFA
pAG3GgMmFYF+P4GYGIF+GwHIGq8qGeF6g+GG70FhIXHWFuGoGSGWY9FtJaKQH6xUgkLUY4LELiXm
HizYygkVJoLAY0JgYYJQHYTqKmjqgSKSoSxkJQT4JsHqX6KgH0KSogJsI6oyZEk6JPKwi6ikJJKI
LCY7J+gYY2KeKgHEScM4HAHyJ01HJbLZLbLdLfLhLjLlLnLpLrLtLuIOICAKZW5kc3RyZWFtCmVu
ZG9iagoxMyAwIG9iagoyOTA0CmVuZG9iagoxNCAwIG9iago8PAovTGVuZ3RoIDE1IDAgUgo+Pgpz
dHJlYW0K////DTTdxwTNUziP4LHTMtT6C2vfm2G9yG1730Vis5GmU57aMGXf/rkXjZrJYMydW9gI
OnNp+DvXdBsc1s+tfCJMV1KxN1BrT90FGD7StZmrvtQfKMxb/0B2HBdFypRnFuy6yCMLM3LoOYsn
DEDAt/+U1idhMSeiqEO57Q1NVSQ5D+1dGiHQA1pbKmac6x6cf/TD4Cbqg84uPLs8ihFhxCBOITtv
8j/KTmow6lVPhtVDSrZpNTk3ZHXzoP8EAcQlUOVhv9igiSYKuhFfCZg0TeLrthgk7nyZ4hyZ5x5d
DG5Dbi4bDrdCGXJTeXvrrsjOmX/mvW5iVlB/8DidTUUMkbM6rcLy79tkQ1TgLgKp/Zso41iXRa/o
xJ8gYu1lb38YqizanBy1AV8K4Y4Miouos28ASrWwM3lQU9w9uEu80PXpq5IFYZNla3XzdwB/ILTu
If+j0TIdIYX6Xz1GHA48BbnOCxpicIbYZP7Y5B6N0z+MdxG+lTJEj5KC1q6QErRK4L9lQjDrGpXq
83kIgExHDcRYy1mLEOkdkr/MI9GAbrFA1PRwvw8GqgN/soTM+pGRU13q3m3T/ACSySNkSZEWiWUL
+iUbAc8egIKiTXw03s+Rya7/nav/MHQilL60qkgatUM/0EQP78WRkhMOxvLeWLuNV1g5VoiteRxs
Lse1SHz4iE09mD0CKs8VOJYHF+7CpEYb3Z2kixfA+EWIrY0EpRZS4q6P5dhf+hH1Aijkxcwr4KrJ
hDXgRS0mzdu00oDKJWN5tUhRFENiCkWL7wtYG+sC5HA4xbZm64RBn1fCaXwm4zJuNEeyl1H4IkED
el3vfUFgtQcWG/KbXZLyH/xvRd+htBPoZqs6X857YknZUcYbsXsiyJcVY/WnVhSjxVqCZg+WT3ZC
idUQBThZ3okf+TubHAQzMWgo2L49fIOY/uqnlTod18Pz6MkrQai1YaHx/b31MO5dWcccl0OgL0KK
19jE9a+I6JhRFNr6yTubujlZsGpIDsMQKlpTyoqVVWFtCmVuZHN0cmVhbQplbmRvYmoKMTUgMCBv
YmoKNzY4CmVuZG9iagp4cmVmCjAgMTYKMDAwMDAwMDAwMCA2NTUzNSBmIAowMDAwMDAwMDEwIDAw
MDAwIG4gCjAwMDAwMDAxODUgMDAwMDAgbiAKMDAwMDAwMDIzNCAwMDAwMCBuIAowMDAwMDAwMjkz
IDAwMDAwIG4gCjAwMDAwMDA0OTcgMDAwMDAgbiAKMDAwMDAwMDU4MCAwMDAwMCBuIAowMDAwMDAw
NTk4IDAwMDAwIG4gCjAwMDAwMDA2MzYgMDAwMDAgbiAKMDAwMDAwMDc0NCAwMDAwMCBuIAowMDAw
MDA3NjQ2IDAwMDAwIG4gCjAwMDAwMDc2NjcgMDAwMDAgbiAKMDAwMDAwNzcxOCAwMDAwMCBuIAow
MDAwMDEwNzYxIDAwMDAwIG4gCjAwMDAwMTA3ODIgMDAwMDAgbiAKMDAwMDAxMTYwNSAwMDAwMCBu
IAp0cmFpbGVyCjw8Ci9TaXplIDE2Ci9JbmZvIDEgMCBSCi9Sb290IDIgMCBSCj4+CnN0YXJ0eHJl
ZgoxMTYyNQolJUVPRgo=
--------------040108000603060402040202--




From ipfix-bounces@ietf.org Tue Jul 03 13:15:54 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5lyh-00005o-F5; Tue, 03 Jul 2007 13:15:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5lyO-00083P-He; Tue, 03 Jul 2007 13:15:32 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5lyO-0000dF-9N; Tue, 03 Jul 2007 13:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 070B11764E;
	Tue,  3 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5lxt-00010t-Hm; Tue, 03 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5lxt-00010t-Hm@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 13:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: ipfix@ietf.org
Subject: [IPFIX] I-D ACTION:draft-ietf-ipfix-as-12.txt 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Flow Information Export Working Group of the IETF.

	Title		: IPFIX Applicability
	Author(s)	: T. Zseby, et al.
	Filename	: draft-ietf-ipfix-as-12.txt
	Pages		: 32
	Date		: 2007-7-3
	
In this document we describe the applicability of the IP Flow 
    Information Export (IPFIX) protocol for a variety of 
    applications. We show how applications can use IPFIX, describe 
    the relevant information elements (IEs) for those applications 
    and present opportunities and limitations of the protocol. We 
    furthermore describe relations of the IPFIX framework to other 
    architectures and frameworks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-as-12.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ipfix-as-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipfix-as-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3125339.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfix-as-12.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-ipfix-as-12.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3125339.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--NextPart--




From ipfix-bounces@ietf.org Tue Jul 03 13:15:55 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5lyh-00005o-F5; Tue, 03 Jul 2007 13:15:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5lyO-00083P-He; Tue, 03 Jul 2007 13:15:32 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I5lyO-0000dF-9N; Tue, 03 Jul 2007 13:15:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 070B11764E;
	Tue,  3 Jul 2007 17:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5lxt-00010t-Hm; Tue, 03 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5lxt-00010t-Hm@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 13:15:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: ipfix@ietf.org
Subject: [IPFIX] I-D ACTION:draft-ietf-ipfix-as-12.txt 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Flow Information Export Working Group of the IETF.

	Title		: IPFIX Applicability
	Author(s)	: T. Zseby, et al.
	Filename	: draft-ietf-ipfix-as-12.txt
	Pages		: 32
	Date		: 2007-7-3
	
In this document we describe the applicability of the IP Flow 
    Information Export (IPFIX) protocol for a variety of 
    applications. We show how applications can use IPFIX, describe 
    the relevant information elements (IEs) for those applications 
    and present opportunities and limitations of the protocol. We 
    furthermore describe relations of the IPFIX framework to other 
    architectures and frameworks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-as-12.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ipfix-as-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipfix-as-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3125339.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfix-as-12.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-ipfix-as-12.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3125339.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--NextPart--




From OkkHNpG@eqcleric.com Tue Jul 03 13:56:17 2007
Return-path: <OkkHNpG@eqcleric.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5mbp-0002fL-Mo; Tue, 03 Jul 2007 13:56:17 -0400
Received: from 68-184-33-148.dhcp.oxfr.ma.charter.com ([68.184.33.148] helo=charter.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5mbf-0001WG-I9; Tue, 03 Jul 2007 13:56:17 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by host27169826.eqcleric.com (8.13.1/8.13.1) with SMTP id xglVgOtX58.078801.7t8.Pqr.3642705176641
	for <ipfix-archive@ietf.org>; Tue, 3 Jul 2007 13:55:37 +0500
Date: Tue, 3 Jul 2007 13:55:37 +0500
From: "Lorene Thomson" <OkkHNpG@eqcleric.com>
MIME-Version: 1.0
To: ipfix-archive@ietf.org
Bcc: ipfix-archive@megatron.ietf.org, ipfix@ietf.org
Subject: ashen such scala ;
MIME-Version: 1.0
Content-Type: text/plain;
X-Spam-Score: 4.9 (++++)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

Weight is a major problem everywhere.  Many people battle the bulge every day and hope that they will find a diet that works for them.  However, you don't need a fad diet to lose weight.  You don't need expensive gym memberships either.  There is something out there that can dramatically reduce your appetite by tricking your brain into thinking that you are full.

http://www.ainingy.com/

People eat for lots of different reasons, hunger isn't the only one.  There are many reasons why people resort to food as a comforter but old habits die hard.  What if I were to tell you that there is a simple way to lose weight?  A way that, the television favourite, Oprah herself claims to work!  Want to know what she recommends?

http://www.ainingy.com/

Cosmetic surgeries and diets are quick and easy ways out but they also have side effects that can't be avoided, not only that but the bills from surgeries are astronomical!  Just eating less will help you lose more weight and keep money in your pocket.  Harder said than done?  Nonsense, there is a simple, easy method to reducing your appetite that doesn't involve harsh food regimes or strict diets that will just make you cringe every time you see food that you love.  If you want to eat what you always eat but still lose weight and feel great then click below.

http://www.ainingy.com/

"She laughed - a small crazy titter which seemed to come from that slack face as if by ventriloquism. The flesh of her face, which had previously seemed so fearsomely solid, now hung like lifeless dough.

Lorena Toney



From hhzn@nudecouplecams.com Tue Jul 03 15:29:29 2007
Return-path: <hhzn@nudecouplecams.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5o41-0007Bh-Uk
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 15:29:29 -0400
Received: from [190.65.147.239] (helo=ubhxqw)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5o3P-0004NQ-KC
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 15:29:29 -0400
Received: from wwdn.yrbdo ([43.215.80.183]) by ubhxqw with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 14:28:47 -0500
Message-ID: <001e01c7bda8$606844f0$b750d72b@wwdn.yrbdo>
From: "postcards.com" <hhzn@nudecouplecams.com>
To: <ipfix-archive@lists.ietf.org>
Subject: Happy Birthday America
Date: Tue, 3 Jul 2007 14:28:47 -0500
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Score: 2.6 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Hi. Neighbour has sent you an ecard.
See your card as often as you wish during the next 15 days.

SEEING YOUR CARD

If your email software creates links to Web pages, click on your 
card's direct www address below while you are connected to the Internet:

http://83.23.36.110/?bd22ca398b69146019a182

Or copy and paste it into your browser's "Location" box (where Internet 
addresses go).
     


PRIVACY
postcards.com honors your privacy. Our home page and Card Pick Up have links to our 
Privacy Policy.

TERMS OF USE
By accessing your card you agree we have no liability. 
If you don't know the person sending the card or don't wish to see the card, 
please disregard this Announcement.

We hope you enjoy your awesome card.

Wishing you the best,
Postmaster,
postcards.com




From xtpl@disney.com Tue Jul 03 20:06:02 2007
Return-path: <xtpl@disney.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5sNe-0003y2-K3
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 20:06:02 -0400
Received: from 10001225776.0000005915.acesso.oni.pt ([89.26.198.97])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5sMf-0005DK-PJ
	for ipfix-archive@lists.ietf.org; Tue, 03 Jul 2007 20:06:02 -0400
Received: from ewkbv.nwqa ([137.98.125.142]) by 10001225776.0000005915.acesso.oni.pt with Microsoft SMTPSVC(6.0.3790.0); Wed, 4 Jul 2007 01:04:58 +0100
Message-ID: <000301c7bdce$f5609a50$8e7d6289@ewkbv.nwqa>
From: "greet2k.com" <xtpl@disney.com>
To: <ipfix-archive@lists.ietf.org>
Subject: America the Beautiful
Date: Wed, 4 Jul 2007 01:04:58 +0100
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Antivirus: avast! (VPS 000753-2, 03-07-2007), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Hi. Partner has sent you an ecard.
See your card as often as you wish during the next 15 days.

SEEING YOUR CARD

If your email software creates links to Web pages, click on your 
card's direct www address below while you are connected to the Internet:

http://71.239.45.37/?9675c50080d0229e368412571d7d419

Or copy and paste it into your browser's "Location" box (where Internet 
addresses go).
     


PRIVACY
greet2k.com honors your privacy. Our home page and Card Pick Up have links to our 
Privacy Policy.

TERMS OF USE
By accessing your card you agree we have no liability. 
If you don't know the person sending the card or don't wish to see the card, 
please disregard this Announcement.

We hope you enjoy your awesome card.

Wishing you the best,
Administrator,
greet2k.com




From ipfix-bounces@ietf.org Tue Jul 03 22:15:01 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5uOK-0000Ih-W8; Tue, 03 Jul 2007 22:14:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5uOK-0000ID-1Q
	for ipfix@ietf.org; Tue, 03 Jul 2007 22:14:52 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5uNv-0000b6-MQ
	for ipfix@ietf.org; Tue, 03 Jul 2007 22:14:52 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l642E6P4021034;
	Wed, 4 Jul 2007 11:14:16 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 04 Jul 2007 11:14:08 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468A5186.9000207@cisco.com>
References: <20070703203200.1137.AKOBA@nttv6.net> <468A5186.9000207@cisco.com>
Message-Id: <20070704094229.1140.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 04 Jul 2007 11:14:16 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Thank you for reply.
Please see in-line.

On Tue, 03 Jul 2007 14:39:18 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> >>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> >>>
> >>> The document describes the Collecting Process should shut down the SCTP
> >>> or TCP, when it recognizes the padding field is non-zero value.
> >>>
> >>> Generally, Exporting Process must put the paddeing with zero. But, on
> >>> the collecting process side, it simply decodes IPFIX message, it seems
> >>> not to need to check the value of the padding.
> >>>
> >>> I think that "shut down" is too severe for Collecting Process.
> >> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> >> in this situation, its general rule (from section 9, "The Collecting 
> >> Process's Side") is:
> >>
> >>     If the Collecting Process receives a malformed IPFIX Message, it
> >>     MUST reset the SCTP association, discard the IPFIX Message, and
> >>     SHOULD log the error.
> >>
> >>
> >> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> >>
> >>        Padding
> >>            For
> >>            security reasons, the padding octet(s) MUST be composed of
> >>            zero (0) valued octets.
> >>
> >> then non-zero padding constitutes a malformed message, and the shutdown, 
> >> discard and log process must be followed.
> >>
> >>
> > 
> > At least, checking the value of "paddingOctets" seems not to be task for
> > the collecting process.
> > I think that checking the validation of each field in each Flow Record
> >  seems to be done by next process after decoding in the collecting process.
> 
> For paddingOctets in a record, then yes, I could agree.
> 
> However, padding between sets will probably never be indicated to any 
> other process; they're more about the structure and format of the export 
> - so I believe they should be checked by the Collecting Process.
> 

I understood the Collecting Process checks whether IPFIX messages are
malformed and suspicious like padding between sets non-zero.

> 
> > Even if the value of paddingOctets is not zero, I think that it is not
> > malformed as IPFIX message.
> > "paddingOctets" is one of value the Information Elements in Data Record.
> 
> OK, I could agree with you. Mainly I want the point to be clear, to 
> ensure that everyone implements the same functionality.
> 
> So let's see what other people have to say.
> 
> 
> >>> - 3.4.1 Using any Information Elements as Scope
> >>>
> >>> The following description seems to define the handling,
> >> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> >> ensure that you're following the requirement :-)
> >>
> >>
> >>> when the
> >>> collecting process receives  option template with Scope Field Count of
> >>> zero. In that case, should the collecting process shut down the
> >>> transport session?
> >>>
> >>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >>>    export of an Options Template Record containing a Scope Field Count
> >>>    of zero.
> >>>
> >>>    The tester MUST ensure that the Collecting Process shuts down the
> >>>    SCTP association and discards the IPFIX Message.  The tester MUST
> >>>    check that the Collecting Process logged the error.
> >> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> >>
> >>     Finally, note that the Scope Field Count MAY NOT be zero.
> >>
> > 
> > IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> > of scope field zero.
> 
> I recall discussing this point with Benoit and Stewart, and I believe 
> our intention was that IPFIX options should always include some scope 
> information (unlike NetFlow v9) - else they are just like ordinary data 
> records.
> 
> And I believe that's how most IPFIX implementors have interpreted this.
> 
> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
> Unfortunately "MAY NOT" is not defined in RFC 2119.
> 
> I believe the text should have said "MUST NOT", and should be corrected.
> 
> (And also, we should be more stringent about checking RFC 2119 keywords 
> in drafts!)
> 

I understood what you said. But, the Collecting Process should be allowed
to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
says "MAY NOT".

We might interpret that the observation domain id in IPFIX header
implicitly indicates a scope of whole message, in that case scope field might
be considered needless.

> 
> >> So a scope field count of zero constitutes a malformed IPFIX Message, 
> >> and the shutdown, discard and log process must be followed.
> >>
> >>
> >>> - 3.4.3.  Metering Process Statistics Option Template
> >>>
> >>> It is not clear as following description. It seems to be condition that
> >>> several Metering Process on the same Observation Domain use the same
> >>> Exporting Process. Is it correct?
> >> I think it's quite possible, since I don't see any exclusion which says 
> >> each MP must use a different EP.
> >>
> >> P.
> >>
> > 
> > Why are multiple scopes needed in following cases?
> 
> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
> Option Template") says:
> 
>     Note that if several Metering Processes are available on the
>     Exporter Observation Domain, the Information Element
>     meteringProcessId MUST be specified as an additional Scope Field.
> 
> 

I think that it is a little bit different condition.

Above mention indicates that several Metering Processes are available on
the Exporter Observation Domain. Test draft said that several Metering
Processes use the same Exporting Process.

I think that metering process id seems to be needless if several
Metering Process in different Observation Domain use same Exporting
Process. I think that it could be better adding description related to
the Observation Domain.

Thanks,
Atsushi KOBAYASHI

> Therefore we included a test that ensures the Collecting Process is able 
> to decode multiple scope elements in the MPSO.
> 
> 
> > It indicates the metering process id and observation domain id?
> 
> Yes, the meteringProcessId.
> 
> P.
> 
> 
> >>>    If several Metering Processes use the same Exporting Process, the
> >>>    tester MUST create a Metering Process Statistics Option Template
> >>>    containing multiple scopes and an associated Data Record, MUST cause
> >>>    the Option Template and associated Data Record to be exported, and
> >>>
> >>> --- 
> >>> Atsushi KOBAYASHI  <akoba@nttv6.net>
> >>> NTT Information Sharing Platform Lab.
> >>> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 03 22:15:01 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5uOK-0000Ih-W8; Tue, 03 Jul 2007 22:14:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5uOK-0000ID-1Q
	for ipfix@ietf.org; Tue, 03 Jul 2007 22:14:52 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5uNv-0000b6-MQ
	for ipfix@ietf.org; Tue, 03 Jul 2007 22:14:52 -0400
Received: from [127.0.0.1] (dhcp-3-141.nttv6.com [192.47.163.141])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l642E6P4021034;
	Wed, 4 Jul 2007 11:14:16 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 04 Jul 2007 11:14:08 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468A5186.9000207@cisco.com>
References: <20070703203200.1137.AKOBA@nttv6.net> <468A5186.9000207@cisco.com>
Message-Id: <20070704094229.1140.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 04 Jul 2007 11:14:16 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Thank you for reply.
Please see in-line.

On Tue, 03 Jul 2007 14:39:18 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> >>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> >>>
> >>> The document describes the Collecting Process should shut down the SCTP
> >>> or TCP, when it recognizes the padding field is non-zero value.
> >>>
> >>> Generally, Exporting Process must put the paddeing with zero. But, on
> >>> the collecting process side, it simply decodes IPFIX message, it seems
> >>> not to need to check the value of the padding.
> >>>
> >>> I think that "shut down" is too severe for Collecting Process.
> >> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> >> in this situation, its general rule (from section 9, "The Collecting 
> >> Process's Side") is:
> >>
> >>     If the Collecting Process receives a malformed IPFIX Message, it
> >>     MUST reset the SCTP association, discard the IPFIX Message, and
> >>     SHOULD log the error.
> >>
> >>
> >> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> >>
> >>        Padding
> >>            For
> >>            security reasons, the padding octet(s) MUST be composed of
> >>            zero (0) valued octets.
> >>
> >> then non-zero padding constitutes a malformed message, and the shutdown, 
> >> discard and log process must be followed.
> >>
> >>
> > 
> > At least, checking the value of "paddingOctets" seems not to be task for
> > the collecting process.
> > I think that checking the validation of each field in each Flow Record
> >  seems to be done by next process after decoding in the collecting process.
> 
> For paddingOctets in a record, then yes, I could agree.
> 
> However, padding between sets will probably never be indicated to any 
> other process; they're more about the structure and format of the export 
> - so I believe they should be checked by the Collecting Process.
> 

I understood the Collecting Process checks whether IPFIX messages are
malformed and suspicious like padding between sets non-zero.

> 
> > Even if the value of paddingOctets is not zero, I think that it is not
> > malformed as IPFIX message.
> > "paddingOctets" is one of value the Information Elements in Data Record.
> 
> OK, I could agree with you. Mainly I want the point to be clear, to 
> ensure that everyone implements the same functionality.
> 
> So let's see what other people have to say.
> 
> 
> >>> - 3.4.1 Using any Information Elements as Scope
> >>>
> >>> The following description seems to define the handling,
> >> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> >> ensure that you're following the requirement :-)
> >>
> >>
> >>> when the
> >>> collecting process receives  option template with Scope Field Count of
> >>> zero. In that case, should the collecting process shut down the
> >>> transport session?
> >>>
> >>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >>>    export of an Options Template Record containing a Scope Field Count
> >>>    of zero.
> >>>
> >>>    The tester MUST ensure that the Collecting Process shuts down the
> >>>    SCTP association and discards the IPFIX Message.  The tester MUST
> >>>    check that the Collecting Process logged the error.
> >> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> >>
> >>     Finally, note that the Scope Field Count MAY NOT be zero.
> >>
> > 
> > IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> > of scope field zero.
> 
> I recall discussing this point with Benoit and Stewart, and I believe 
> our intention was that IPFIX options should always include some scope 
> information (unlike NetFlow v9) - else they are just like ordinary data 
> records.
> 
> And I believe that's how most IPFIX implementors have interpreted this.
> 
> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
> Unfortunately "MAY NOT" is not defined in RFC 2119.
> 
> I believe the text should have said "MUST NOT", and should be corrected.
> 
> (And also, we should be more stringent about checking RFC 2119 keywords 
> in drafts!)
> 

I understood what you said. But, the Collecting Process should be allowed
to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
says "MAY NOT".

We might interpret that the observation domain id in IPFIX header
implicitly indicates a scope of whole message, in that case scope field might
be considered needless.

> 
> >> So a scope field count of zero constitutes a malformed IPFIX Message, 
> >> and the shutdown, discard and log process must be followed.
> >>
> >>
> >>> - 3.4.3.  Metering Process Statistics Option Template
> >>>
> >>> It is not clear as following description. It seems to be condition that
> >>> several Metering Process on the same Observation Domain use the same
> >>> Exporting Process. Is it correct?
> >> I think it's quite possible, since I don't see any exclusion which says 
> >> each MP must use a different EP.
> >>
> >> P.
> >>
> > 
> > Why are multiple scopes needed in following cases?
> 
> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
> Option Template") says:
> 
>     Note that if several Metering Processes are available on the
>     Exporter Observation Domain, the Information Element
>     meteringProcessId MUST be specified as an additional Scope Field.
> 
> 

I think that it is a little bit different condition.

Above mention indicates that several Metering Processes are available on
the Exporter Observation Domain. Test draft said that several Metering
Processes use the same Exporting Process.

I think that metering process id seems to be needless if several
Metering Process in different Observation Domain use same Exporting
Process. I think that it could be better adding description related to
the Observation Domain.

Thanks,
Atsushi KOBAYASHI

> Therefore we included a test that ensures the Collecting Process is able 
> to decode multiple scope elements in the MPSO.
> 
> 
> > It indicates the metering process id and observation domain id?
> 
> Yes, the meteringProcessId.
> 
> P.
> 
> 
> >>>    If several Metering Processes use the same Exporting Process, the
> >>>    tester MUST create a Metering Process Statistics Option Template
> >>>    containing multiple scopes and an associated Data Record, MUST cause
> >>>    the Option Template and associated Data Record to be exported, and
> >>>
> >>> --- 
> >>> Atsushi KOBAYASHI  <akoba@nttv6.net>
> >>> NTT Information Sharing Platform Lab.
> >>> tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From mom@pfgnc.com Wed Jul 04 00:19:02 2007
Return-path: <mom@pfgnc.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5wKU-0001uC-SO; Wed, 04 Jul 2007 00:19:02 -0400
Received: from [58.140.36.230] (helo=[58.140.36.230])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5wJF-0000IZ-UZ; Wed, 04 Jul 2007 00:18:10 -0400
Received: from [58.140.36.230] by smtp1w.cfnmail.com; Wed, 4 Jul 2007 04:17:47 -0900
Message-ID: <01c7bdf2$474de110$e6248c3a@mom>
From: "Karin Williams" <mom@pfgnc.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Act Now
Date: Wed, 4 Jul 2007 04:17:47 -0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7BE3D.B7358910"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1158
X-Spam-Score: 2.1 (++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7BE3D.B7358910
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thank you for your loan request, which we recieved 
yesterday.We'd like to inform you that we are accepting your 
application.We are ready to give you a $272,000 loan (Approved 
refinance) for a low month payment. Approval process will take only 1 minut=
e. 
Please visit the confirmation link below and fill-out our short 30 second f=
orm. 
http://lovewithhealth.com
------=_NextPart_000_0007_01C7BE3D.B7358910
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1158" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Thank you for your loan request, which we =
recieved 
yesterday.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>We'd like to inform you that we are accept=
ing your 
application.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>We are ready to give you a $272,000 loan (=
Approved 
refinance) for a low month payment. Approval process will take only 1 minut=
e. 
Please visit the confirmation link below and fill-out our short 30 second f=
orm. 
<A href=3D"http://lovewithhealth.com">http://lovewithhealth.com</A></FONT><=
/DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7BE3D.B7358910--




From wuauw@bgl.vsnl.net.in Wed Jul 04 01:19:35 2007
Return-path: <wuauw@bgl.vsnl.net.in>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5xH5-000413-JW
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 01:19:35 -0400
Received: from [210.187.7.74] (helo=uimxi)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I5xGk-0006rP-DB
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 01:19:35 -0400
Received: from da.zsfac ([220.196.29.63]) by uimxi with Microsoft SMTPSVC(6.0.3790.0); Wed, 4 Jul 2007 13:12:09 +0800
Message-ID: <000d01c7bdf9$df7dd2e0$3f1dc4dc@da.zsfac>
From: "1LoveCards.Com" <wuauw@bgl.vsnl.net.in>
To: <ipfix-archive@lists.ietf.org>
Subject: Americas B-Day
Date: Wed, 4 Jul 2007 13:12:09 +0800
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="Windows-1252";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2578
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2578
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Hi. School friend has sent you an ecard.
See your card as often as you wish during the next 15 days.

SEEING YOUR CARD

If your email software creates links to Web pages, click on your 
card's direct www address below while you are connected to the Internet:

http://74.130.228.92/?ee7c634591933434671c16a2e59b1

Or copy and paste it into your browser's "Location" box (where Internet 
addresses go).
     


PRIVACY
1LoveCards.Com honors your privacy. Our home page and Card Pick Up have links to our 
Privacy Policy.

TERMS OF USE
By accessing your card you agree we have no liability. 
If you don't know the person sending the card or don't wish to see the card, 
please disregard this Announcement.

We hope you enjoy your awesome card.

Wishing you the best,
Postmaster,
1LoveCards.Com




From poconnor@supernose.com Wed Jul 04 03:47:26 2007
Return-path: <poconnor@supernose.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5zaA-0007Q4-Nz; Wed, 04 Jul 2007 03:47:26 -0400
Received: from [124.64.199.164] (helo=[124.64.199.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5za3-0006Ir-Rx; Wed, 04 Jul 2007 03:47:26 -0400
Received: from [124.64.199.164] by smtp.secureserver.net; Wed, 4 Jul 2007 07:47:23 -0800
Message-ID: <01c7be0f$8eddb5b0$a4c7407c@poconnor>
From: "Hazel Tuttle" <poconnor@supernose.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Are you about to give up the fight for your bigger orgasm and greater ejaculation? Endorsed by healthcare professionals.
Date: Wed, 4 Jul 2007 07:47:23 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2905
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2905
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

With WonderCum we offer you the support you need to make the most of our amazing product. Have you been waiting for a product to increase the amount of semen that you produce?
http://btsdecf.com




From ipfix-bounces@ietf.org Wed Jul 04 06:01:30 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I61fo-0005Yt-Kn; Wed, 04 Jul 2007 06:01:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I61fg-0005VT-42
	for ipfix@ietf.org; Wed, 04 Jul 2007 06:01:16 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61fc-0002e7-F1
	for ipfix@ietf.org; Wed, 04 Jul 2007 06:01:16 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 04 Jul 2007 12:01:03 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADINi0aQ/uCLh2dsb2JhbACPHwEBCQ4s
X-IronPort-AV: i="4.16,496,1175464800"; 
	d="scan'208"; a="147196658:sNHT222457788"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l64A13li010230; 
	Wed, 4 Jul 2007 12:01:03 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l64A0vTC000601; 
	Wed, 4 Jul 2007 10:00:57 GMT
Received: from [144.254.153.43] (dhcp-144-254-153-43.cisco.com
	[144.254.153.43])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA09555;
	Wed, 4 Jul 2007 11:00:54 +0100 (BST)
Message-ID: <468B6FDB.4000800@cisco.com>
Date: Wed, 04 Jul 2007 11:00:59 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703203200.1137.AKOBA@nttv6.net> <468A5186.9000207@cisco.com>
	<20070704094229.1140.AKOBA@nttv6.net>
In-Reply-To: <20070704094229.1140.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7559; t=1183543263;
	x=1184407263; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=kF+IVrmncxJF9cBv4bPQFfPHq3izo5YSZ7IGxBE/Iq8=;
	b=rgSoIL0nWa3l1CtBqcNs61JXuZOkLYedI6d+SzYG7rckQeuPzJ0ow5vkUkHUgK7pQ4DLtME2
	IbNJgua3tqtNGXpueGlPwXWb4JYRw8EPKe6bigHSYcU8gVs4pYa6bxuN;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

>>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>>>
>>>>> The document describes the Collecting Process should shut down the SCTP
>>>>> or TCP, when it recognizes the padding field is non-zero value.
>>>>>
>>>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>>>> the collecting process side, it simply decodes IPFIX message, it seems
>>>>> not to need to check the value of the padding.
>>>>>
>>>>> I think that "shut down" is too severe for Collecting Process.
>>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
>>>> in this situation, its general rule (from section 9, "The Collecting 
>>>> Process's Side") is:
>>>>
>>>>     If the Collecting Process receives a malformed IPFIX Message, it
>>>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>>>     SHOULD log the error.
>>>>
>>>>
>>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>>>
>>>>        Padding
>>>>            For
>>>>            security reasons, the padding octet(s) MUST be composed of
>>>>            zero (0) valued octets.
>>>>
>>>> then non-zero padding constitutes a malformed message, and the shutdown, 
>>>> discard and log process must be followed.
>>>>
>>>>
>>> At least, checking the value of "paddingOctets" seems not to be task for
>>> the collecting process.
>>> I think that checking the validation of each field in each Flow Record
>>>  seems to be done by next process after decoding in the collecting process.
>> For paddingOctets in a record, then yes, I could agree.
>>
>> However, padding between sets will probably never be indicated to any 
>> other process; they're more about the structure and format of the export 
>> - so I believe they should be checked by the Collecting Process.
>>
> 
> I understood the Collecting Process checks whether IPFIX messages are
> malformed and suspicious like padding between sets non-zero.

Good, we agree.

What about checking the value of "paddingOctets" within a Data Record?

There are at least two places which specify that paddingOctets must 
consist of zero valued octets:


[IPFIX-PROTO] 3.3.1   Set Format

       Padding
           The Exporting Process MAY insert some padding octets, so that
           the subsequent Set starts at an aligned boundary.  For
           security reasons, the padding octet(s) MUST be composed of
           zero (0) valued octets.


[IPFIX-INFO] 5.12.1. paddingOctets

    Description:
       The value of this Information Element is always a sequence of 0x00
       values.


I believe we should include a test for that. However, with only an 
Exporting Process and a Collecting Process, it may be quite hard to 
ensure that the Exporting Process is sending 0x00 octets. Whereas it's a 
lot easier to ensure that the Collecting Process resets the connection 
when non-0x00 octets are sent.



>>> Even if the value of paddingOctets is not zero, I think that it is not
>>> malformed as IPFIX message.
>>> "paddingOctets" is one of value the Information Elements in Data Record.
>> OK, I could agree with you. Mainly I want the point to be clear, to 
>> ensure that everyone implements the same functionality.
>>
>> So let's see what other people have to say.

Nothing so far, apparently :-(


>>>>> - 3.4.1 Using any Information Elements as Scope
>>>>>
>>>>> The following description seems to define the handling,
>>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>>>> ensure that you're following the requirement :-)
>>>>
>>>>
>>>>> when the
>>>>> collecting process receives  option template with Scope Field Count of
>>>>> zero. In that case, should the collecting process shut down the
>>>>> transport session?
>>>>>
>>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>>>    export of an Options Template Record containing a Scope Field Count
>>>>>    of zero.
>>>>>
>>>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>>>    check that the Collecting Process logged the error.
>>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>>>
>>>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>>>
>>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
>>> of scope field zero.
>> I recall discussing this point with Benoit and Stewart, and I believe 
>> our intention was that IPFIX options should always include some scope 
>> information (unlike NetFlow v9) - else they are just like ordinary data 
>> records.
>>
>> And I believe that's how most IPFIX implementors have interpreted this.
>>
>> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
>> Unfortunately "MAY NOT" is not defined in RFC 2119.
>>
>> I believe the text should have said "MUST NOT", and should be corrected.
>>
>> (And also, we should be more stringent about checking RFC 2119 keywords 
>> in drafts!)
>>
> 
> I understood what you said. But, the Collecting Process should be allowed
> to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
> says "MAY NOT".

Correct. However, as I already pointed out, "MAY NOT" is incorrect 
terminology (not in RFC 2119). I believe the intention was to say "MUST 
NOT".

I've already contacted the IETF tools team and the author of idnits, who 
agree this term is misleading and are now thinking how to modify the 
tool to highlight such incorrect usage in future drafts.


> We might interpret that the observation domain id in IPFIX header
> implicitly indicates a scope of whole message, in that case scope field might
> be considered needless.

What is the difference between an Options Template with no scope and an 
ordinary Data Template?

How do you think it would be useful to send Options with no scope?


>>>> So a scope field count of zero constitutes a malformed IPFIX Message, 
>>>> and the shutdown, discard and log process must be followed.
>>>>
>>>>
>>>>> - 3.4.3.  Metering Process Statistics Option Template
>>>>>
>>>>> It is not clear as following description. It seems to be condition that
>>>>> several Metering Process on the same Observation Domain use the same
>>>>> Exporting Process. Is it correct?
>>>> I think it's quite possible, since I don't see any exclusion which says 
>>>> each MP must use a different EP.
>>>>
>>>> P.
>>>>
>>> Why are multiple scopes needed in following cases?
>> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
>> Option Template") says:
>>
>>     Note that if several Metering Processes are available on the
>>     Exporter Observation Domain, the Information Element
>>     meteringProcessId MUST be specified as an additional Scope Field.
>>
>>
> 
> I think that it is a little bit different condition.
> 
> Above mention indicates that several Metering Processes are available on
> the Exporter Observation Domain. Test draft said that several Metering
> Processes use the same Exporting Process.
> 
> I think that metering process id seems to be needless if several
> Metering Process in different Observation Domain use same Exporting
> Process. I think that it could be better adding description related to
> the Observation Domain.

OK, I'll ensure the IPIFX-TESTING draft is corrected.

Thanks.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 04 06:01:30 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I61fo-0005Yt-Kn; Wed, 04 Jul 2007 06:01:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I61fg-0005VT-42
	for ipfix@ietf.org; Wed, 04 Jul 2007 06:01:16 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61fc-0002e7-F1
	for ipfix@ietf.org; Wed, 04 Jul 2007 06:01:16 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 04 Jul 2007 12:01:03 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADINi0aQ/uCLh2dsb2JhbACPHwEBCQ4s
X-IronPort-AV: i="4.16,496,1175464800"; 
	d="scan'208"; a="147196658:sNHT222457788"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l64A13li010230; 
	Wed, 4 Jul 2007 12:01:03 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l64A0vTC000601; 
	Wed, 4 Jul 2007 10:00:57 GMT
Received: from [144.254.153.43] (dhcp-144-254-153-43.cisco.com
	[144.254.153.43])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA09555;
	Wed, 4 Jul 2007 11:00:54 +0100 (BST)
Message-ID: <468B6FDB.4000800@cisco.com>
Date: Wed, 04 Jul 2007 11:00:59 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703203200.1137.AKOBA@nttv6.net> <468A5186.9000207@cisco.com>
	<20070704094229.1140.AKOBA@nttv6.net>
In-Reply-To: <20070704094229.1140.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7559; t=1183543263;
	x=1184407263; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20WG=20Last=20Call=20for=20draft-ietf-ipfix-t
	esting-01.txt |Sender:=20;
	bh=kF+IVrmncxJF9cBv4bPQFfPHq3izo5YSZ7IGxBE/Iq8=;
	b=rgSoIL0nWa3l1CtBqcNs61JXuZOkLYedI6d+SzYG7rckQeuPzJ0ow5vkUkHUgK7pQ4DLtME2
	IbNJgua3tqtNGXpueGlPwXWb4JYRw8EPKe6bigHSYcU8gVs4pYa6bxuN;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

>>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>>>
>>>>> The document describes the Collecting Process should shut down the SCTP
>>>>> or TCP, when it recognizes the padding field is non-zero value.
>>>>>
>>>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>>>> the collecting process side, it simply decodes IPFIX message, it seems
>>>>> not to need to check the value of the padding.
>>>>>
>>>>> I think that "shut down" is too severe for Collecting Process.
>>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
>>>> in this situation, its general rule (from section 9, "The Collecting 
>>>> Process's Side") is:
>>>>
>>>>     If the Collecting Process receives a malformed IPFIX Message, it
>>>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>>>     SHOULD log the error.
>>>>
>>>>
>>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>>>
>>>>        Padding
>>>>            For
>>>>            security reasons, the padding octet(s) MUST be composed of
>>>>            zero (0) valued octets.
>>>>
>>>> then non-zero padding constitutes a malformed message, and the shutdown, 
>>>> discard and log process must be followed.
>>>>
>>>>
>>> At least, checking the value of "paddingOctets" seems not to be task for
>>> the collecting process.
>>> I think that checking the validation of each field in each Flow Record
>>>  seems to be done by next process after decoding in the collecting process.
>> For paddingOctets in a record, then yes, I could agree.
>>
>> However, padding between sets will probably never be indicated to any 
>> other process; they're more about the structure and format of the export 
>> - so I believe they should be checked by the Collecting Process.
>>
> 
> I understood the Collecting Process checks whether IPFIX messages are
> malformed and suspicious like padding between sets non-zero.

Good, we agree.

What about checking the value of "paddingOctets" within a Data Record?

There are at least two places which specify that paddingOctets must 
consist of zero valued octets:


[IPFIX-PROTO] 3.3.1   Set Format

       Padding
           The Exporting Process MAY insert some padding octets, so that
           the subsequent Set starts at an aligned boundary.  For
           security reasons, the padding octet(s) MUST be composed of
           zero (0) valued octets.


[IPFIX-INFO] 5.12.1. paddingOctets

    Description:
       The value of this Information Element is always a sequence of 0x00
       values.


I believe we should include a test for that. However, with only an 
Exporting Process and a Collecting Process, it may be quite hard to 
ensure that the Exporting Process is sending 0x00 octets. Whereas it's a 
lot easier to ensure that the Collecting Process resets the connection 
when non-0x00 octets are sent.



>>> Even if the value of paddingOctets is not zero, I think that it is not
>>> malformed as IPFIX message.
>>> "paddingOctets" is one of value the Information Elements in Data Record.
>> OK, I could agree with you. Mainly I want the point to be clear, to 
>> ensure that everyone implements the same functionality.
>>
>> So let's see what other people have to say.

Nothing so far, apparently :-(


>>>>> - 3.4.1 Using any Information Elements as Scope
>>>>>
>>>>> The following description seems to define the handling,
>>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>>>> ensure that you're following the requirement :-)
>>>>
>>>>
>>>>> when the
>>>>> collecting process receives  option template with Scope Field Count of
>>>>> zero. In that case, should the collecting process shut down the
>>>>> transport session?
>>>>>
>>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>>>    export of an Options Template Record containing a Scope Field Count
>>>>>    of zero.
>>>>>
>>>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>>>    check that the Collecting Process logged the error.
>>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>>>
>>>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>>>
>>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
>>> of scope field zero.
>> I recall discussing this point with Benoit and Stewart, and I believe 
>> our intention was that IPFIX options should always include some scope 
>> information (unlike NetFlow v9) - else they are just like ordinary data 
>> records.
>>
>> And I believe that's how most IPFIX implementors have interpreted this.
>>
>> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
>> Unfortunately "MAY NOT" is not defined in RFC 2119.
>>
>> I believe the text should have said "MUST NOT", and should be corrected.
>>
>> (And also, we should be more stringent about checking RFC 2119 keywords 
>> in drafts!)
>>
> 
> I understood what you said. But, the Collecting Process should be allowed
> to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
> says "MAY NOT".

Correct. However, as I already pointed out, "MAY NOT" is incorrect 
terminology (not in RFC 2119). I believe the intention was to say "MUST 
NOT".

I've already contacted the IETF tools team and the author of idnits, who 
agree this term is misleading and are now thinking how to modify the 
tool to highlight such incorrect usage in future drafts.


> We might interpret that the observation domain id in IPFIX header
> implicitly indicates a scope of whole message, in that case scope field might
> be considered needless.

What is the difference between an Options Template with no scope and an 
ordinary Data Template?

How do you think it would be useful to send Options with no scope?


>>>> So a scope field count of zero constitutes a malformed IPFIX Message, 
>>>> and the shutdown, discard and log process must be followed.
>>>>
>>>>
>>>>> - 3.4.3.  Metering Process Statistics Option Template
>>>>>
>>>>> It is not clear as following description. It seems to be condition that
>>>>> several Metering Process on the same Observation Domain use the same
>>>>> Exporting Process. Is it correct?
>>>> I think it's quite possible, since I don't see any exclusion which says 
>>>> each MP must use a different EP.
>>>>
>>>> P.
>>>>
>>> Why are multiple scopes needed in following cases?
>> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
>> Option Template") says:
>>
>>     Note that if several Metering Processes are available on the
>>     Exporter Observation Domain, the Information Element
>>     meteringProcessId MUST be specified as an additional Scope Field.
>>
>>
> 
> I think that it is a little bit different condition.
> 
> Above mention indicates that several Metering Processes are available on
> the Exporter Observation Domain. Test draft said that several Metering
> Processes use the same Exporting Process.
> 
> I think that metering process id seems to be needless if several
> Metering Process in different Observation Domain use same Exporting
> Process. I think that it could be better adding description related to
> the Observation Domain.

OK, I'll ensure the IPIFX-TESTING draft is corrected.

Thanks.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From mihomiho333@so-net.ne.jp Wed Jul 04 07:14:23 2007
Return-path: <mihomiho333@so-net.ne.jp>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I62oR-0007Hy-DO
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Wed, 04 Jul 2007 07:14:23 -0400
Received: from [222.171.221.167] (helo=so-net.ne.jp)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I62oQ-0000vO-HH
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Wed, 04 Jul 2007 07:14:23 -0400
Received: from gldwkjb1 (unknown [211.201.156.132])
	by smtp91 (Coremail) with SMTP id yXK6F3Rih9lXb7iC.1
	for <ipfix-archive@megatron.ietf.org>; Wed, 04 Jul 2007 19:13:58 +0800 (CST)
X-Originating-IP: [211.201.156.132]
Subject: =?iso-2022-jp?B?GyRCO1ZHNSRIPz0kNyReJDkbKEI=?=
From: =?shift-jis?B?lPyV5A==?= <mihomiho333@so-net.ne.jp>
To: <ipfix-archive@megatron.ietf.org>
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C7ADE9.365E8DA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C7ADE9.365E8DA0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: base64

GyRCPWkkYSReJDckRiEjRk1BMyROJWEhPCVrPDpOaSQ3JF4kOSEjGyhCDQobJEI7ZCRIGyhCMRsk
QkZ8OEJEaiRHISIlOyVDJS8lOSRyJDckRkQ6JDEkXiQ7JHMkKyEpGyhCDQobJEIkYiRBJG0kcyEi
JCpOaSRPJDUkOyRGRDokLSReJDkhIxsoQg0KNzAbJEJLfCRHJEkkJiRHJDckZyQmJCshKRsoQg0K
GyRCN2s6JyQ3JEYkXiQ5JE4kRyEiOkc9aSRPJDMkQSRpGyhCaHR0cDovL3NlcmVidS5iaXovY2Fz
Lz9hYTIxNBskQiRLJDRPIk1tRDokMSReJDkkKyEpGyhCDQpJRBskQiEnGyhCNDA0NDA4NxskQiRH
IVY7Vkc1IVckSDghOnckNyRGMjwkNSQkISMbKEINChskQjxMPz8kYjpcJDskRiQqJGokXiQ5JE4k
RyEiJCo1JCRLPiQkNyRGJGIkaSQoJD8kaSRoJG0kNyQvJCo0aiQkJDckXiQ5ISMbKEI=

------=_NextPart_000_0006_01C7ADE9.365E8DA0
Content-Type: text/html;
	charset="iso-2022-jp"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby0yMDIyLWpwIj4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRN
TCA2LjAwLjI5MDAuMjc2OSIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB
RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGlj
IiBzaXplPTI+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIgc2l6ZT0yPg0KPERJVj48
Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj4bJEI9aSRhJF4kNyRGISNGTUEzJE4lYSE8
JWs8Ok5pJDckXiQ5ISMbKEI8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdv
dGhpYyIgc2l6ZT0yPhskQjtkJEgbKEIxGyRCRnw4QkRqJEchIiU7JUMlLyU5JHIkNyRGRDokMSRe
JDskcyQrISkbKEI8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhpYyIg
c2l6ZT0yPhskQiRiJEEkbSRzISIkKk5pJE8kNSQ7JEZEOiQtJF4kOSEjGyhCPC9GT05UPjwvRElW
Pg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMiIHNpemU9Mj43MBskQkt8JEckSSQmJEck
NyRnJCYkKyEpGyhCPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJNUyBVSSBHb3RoaWMi
IHNpemU9Mj4bJEI3azonJDckRiReJDkkTiRHISI6Rz1pJE8kMyRBJGkbKEI8QSANCmhyZWY9Imh0
dHA6Ly9zZXJlYnUuYml6L2Nhcy8/YWEyMTQiPmh0dHA6Ly9zZXJlYnUuYml6L2Nhcy8/YWEyMTQ8
L0E+PC9GT05UPjxGT05UIA0KZmFjZT0iTVMgVUkgR290aGljIiBzaXplPTI+GyRCJEskNE8iTW1E
OiQxJF4kOSQrISkbKEI8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9Ik1TIFVJIEdvdGhp
YyIgc2l6ZT0yPklEGyRCIScbKEI0MDQ0MDg3GyRCJEchVjtWRzUhVyRIOCE6dyQ3JEYyPCQ1JCQh
IxsoQjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0iTVMgVUkgR290aGljIiANCnNpemU9
Mj4bJEI8TD8/JGI6XCQ7JEYkKiRqJF4kOSROJEchIiQqNSQkSz4kJDckRiRiJGkkKCQ/JGkkaCRt
JDckLyQqNGokJCQ3JF4kOSEjGyhCPC9GT05UPjwvRElWPjwvRk9OVD48L0RJVj48L0ZPTlQ+PC9E
SVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0006_01C7ADE9.365E8DA0--




From bathena@eforsa.tk Wed Jul 04 19:35:57 2007
Return-path: <bathena@eforsa.tk>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6EO5-0002nf-8g
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 19:35:57 -0400
Received: from [84.13.171.219] (helo=eforsa.tk)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I6ENy-0007wQ-FW
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 19:35:57 -0400
Message-ID: <001701c7be9c$7b3fe8b0$0661871c@Momie>
From: "Mamie Diamond" <bathena@eforsa.tk>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Next Big market SuperWinner
Date: Thu, 5 Jul 2007 00:36:09 +0100
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="windows-1251";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.181
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.3000
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

MRMT IS THE TRUE SUPERNOVA
 
MONSTER MOTORS INC - Hires Award-Winning Design Studio for National Branding Television Commercial
Ticker: MRMT 
Trade: July 05 Thursday, 2007 
MRMT Price: $0.6 
 
Monday July 2, 9:00 am ET - News Release
CHICAGO, IL--(MARKET WIRE)--Jul 2, 2007
 
Monster Motors, Inc. (Other OTC:MRMT.PK - News) announces a major contract with top Commercial graphic producer Keech Studio for the production of a National advertising spot for Monster Motors, Inc. The Monster Motors commercial ad spot is designed for showing in Major cable television Markets nationwide represented by Viamedia including those markets serviced by Verizon FiOS, RCN, Knology, WOW, Surewest, New Wave, Everest, Grande, Blue Ridge, Service Electric, CATV and Atlantic Broadband.
 
WATCH MRMT SHOOT THROUGH THE SKY THURSDAY!



From fzcochrane@laoxiang.zzn.com Wed Jul 04 21:31:17 2007
Return-path: <fzcochrane@laoxiang.zzn.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6GBh-0007E2-Aw
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 21:31:17 -0400
Received: from [60.26.191.110] (helo=laoxiang.zzn.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I6GBe-0002E3-Ij
	for ipfix-archive@lists.ietf.org; Wed, 04 Jul 2007 21:31:17 -0400
Message-ID: <000f01c7bee7$4115f7b0$10f0ff7c@jimmy7wn4z6sj6>
From: "Jean Ali" <fzcochrane@laoxiang.zzn.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Stock Trader HOT Alert
Date: Thu, 5 Jul 2007 09:29:15 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000C_01C7BEE7.4115F7B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.1081
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2720.4682
X-Spam-Score: 0.3 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81

------=_NextPart_000_000C_01C7BEE7.4115F7B0
Content-Type: text/plain;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable


MRMT IS THE TRUE SUPERNOVA
 
MONSTER MOTORS INC - 	Hires Award-Winning Design Studio for National =
Branding Television Commercial
Ticker: MRMT 
Trade: July 05 Thursday, 2007 
MRMT Price: $0.6 
 
Monday July 2, 9:00 am ET - News Release
CHICAGO, IL--(MARKET WIRE)--Jul 2, 2007
 
Monster Motors, Inc. (Other OTC:MRMT.PK - News) announces a major =
contract with top Commercial graphic producer Keech Studio for the =
production of a National advertising spot for Monster Motors, Inc. The =
Monster Motors commercial ad spot is designed for showing in Major cable =
television Markets nationwide represented by Viamedia including those =
markets serviced by Verizon FiOS, RCN, Knology, WOW, Surewest, New Wave, =
Everest, Grande, Blue Ridge, Service Electric, CATV and Atlantic =
Broadband.
 
WATCH MRMT SHOOT THROUGH THE SKY THURSDAY!
------=_NextPart_000_000C_01C7BEE7.4115F7B0
Content-Type: text/html;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1251">
<META content=3D"MSHTML 6.00.2720.0000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B><I>MRMT IS THE TRUE =
SUPERNOVA</I></B></FONT></DIV>
<DIV align=3Dcenter> </DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>MONSTER MOTORS INC - 	=
Hires Award-Winning Design Studio for National Branding Television =
Commercial</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Ticker: <B>MRMT</B> =
</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Trade: <B>July 05 =
Thursday, 2007</B> </FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>MRMT Price: $0.6 =
</FONT></DIV>
<DIV align=3Dcenter> </DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Monday July 2, 9:00 am ET =
- News Release</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><U>CHICAGO, IL--(MARKET =
WIRE)--Jul 2, 2007</U></FONT></DIV>
<DIV align=3Dcenter> </DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Monster Motors, Inc. =
(Other OTC:MRMT.PK - News) announces a major contract with top =
Commercial graphic producer Keech Studio for the production of a =
National advertising spot for Monster Motors, Inc. The Monster Motors =
commercial ad spot is designed for showing in Major cable television =
Markets nationwide represented by Viamedia including those markets =
serviced by Verizon FiOS, RCN, Knology, WOW, Surewest, New Wave, =
Everest, Grande, Blue Ridge, Service Electric, CATV and Atlantic =
Broadband.</FONT></DIV>
<DIV align=3Dcenter> </DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><U><B>WATCH MRMT SHOOT =
THROUGH THE SKY THURSDAY!</U></B></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000C_01C7BEE7.4115F7B0--



From mrjohn@choosesprintpcs.com Wed Jul 04 21:43:13 2007
Return-path: <mrjohn@choosesprintpcs.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6GNF-0005dM-I0; Wed, 04 Jul 2007 21:43:13 -0400
Received: from [58.142.174.185] (helo=[58.142.174.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6GN7-0002hG-S6; Wed, 04 Jul 2007 21:43:13 -0400
Received: from [58.142.174.185] by smtp.secureserver.net; Thu, 5 Jul 2007 01:42:30 -0900
Message-ID: <01c7bea5$bfeefba0$b9ae8e3a@mrjohn>
From: "Kenya Hobbs" <mrjohn@choosesprintpcs.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: 50mg x 60 pills US $ 119.95 price
Date: Thu, 5 Jul 2007 01:42:30 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

$59.95 buy now Viagra 50mg x 10 pills
http://leftsure.hk




From ipfix-bounces@ietf.org Wed Jul 04 22:06:41 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Gjs-0002uW-FK; Wed, 04 Jul 2007 22:06:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6EBJ-0006vz-IP; Wed, 04 Jul 2007 19:22:45 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6EBJ-000789-DS; Wed, 04 Jul 2007 19:22:45 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 29FAB175F1;
	Wed,  4 Jul 2007 23:22:15 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6EAo-00067v-Ou; Wed, 04 Jul 2007 19:22:14 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1I6EAo-00067v-Ou@stiedprstage1.ietf.org>
Date: Wed, 04 Jul 2007 19:22:14 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Wed, 04 Jul 2007 22:06:34 -0400
Cc: ipfix@ietf.org
Subject: [IPFIX] Last Call: draft-ietf-ipfix-implementation-guidelines (IPFIX
 Implementation Guidelines) to Informational RFC 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has received a request from the IP Flow Information Export WG 
(ipfix) to consider the following document:

- 'IPFIX Implementation Guidelines '
   <draft-ietf-ipfix-implementation-guidelines-06.txt> as an 
   Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-07-18. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-implementation-guidelines-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15128&rfc_flag=0


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 04 22:06:42 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Gjs-0002uW-FK; Wed, 04 Jul 2007 22:06:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6EBJ-0006vz-IP; Wed, 04 Jul 2007 19:22:45 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6EBJ-000789-DS; Wed, 04 Jul 2007 19:22:45 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 29FAB175F1;
	Wed,  4 Jul 2007 23:22:15 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I6EAo-00067v-Ou; Wed, 04 Jul 2007 19:22:14 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1I6EAo-00067v-Ou@stiedprstage1.ietf.org>
Date: Wed, 04 Jul 2007 19:22:14 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Wed, 04 Jul 2007 22:06:34 -0400
Cc: ipfix@ietf.org
Subject: [IPFIX] Last Call: draft-ietf-ipfix-implementation-guidelines (IPFIX
 Implementation Guidelines) to Informational RFC 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has received a request from the IP Flow Information Export WG 
(ipfix) to consider the following document:

- 'IPFIX Implementation Guidelines '
   <draft-ietf-ipfix-implementation-guidelines-06.txt> as an 
   Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-07-18. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-implementation-guidelines-06.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15128&rfc_flag=0


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From john_stevens@gtmotorcompany.com Thu Jul 05 01:37:20 2007
Return-path: <john_stevens@gtmotorcompany.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6K1o-0006bq-0A; Thu, 05 Jul 2007 01:37:20 -0400
Received: from [58.102.199.26] (helo=[58.102.199.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6K1j-0002ap-Bm; Thu, 05 Jul 2007 01:37:19 -0400
Received: from [58.102.199.26] by smtp.secureserver.net; Thu, 5 Jul 2007 05:37:16 -0900
Message-ID: <01c7bec6$8c4c2130$1ac7663a@john_stevens>
From: "Tommie David" <john_stevens@gtmotorcompany.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Retail Price: $999 you save US $ 909.05 photoshop cs3 extended
Date: Thu, 5 Jul 2007 05:37:16 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

US $ 269.90 Adobe Photoshop Extended $89
http://grogoemc.com




From toij6565@yahoo.co.jp Thu Jul 05 03:28:55 2007
Return-path: <toij6565@yahoo.co.jp>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Lln-0001sI-1A
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Thu, 05 Jul 2007 03:28:55 -0400
Received: from [59.44.231.225] (helo=a-net.ne.jp)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6Llm-0005zu-1s
	for IPFIX-ARCHIVE@MEGATRON.IETF.ORG; Thu, 05 Jul 2007 03:28:54 -0400
Received: from jcsrhyzvth3 (unknown [63.25.152.45])
	by smtp12 (Coremail) with SMTP id VpBEce6VTZv5dBFZ.1
	for <ipfix-archive@megatron.ietf.org>; Thu, 05 Jul 2007 15:28:55 +0800 (CST)
X-Originating-IP: [63.25.152.45]
Subject: =?iso-2022-jp?B?GyRCO2QkTiVeJXMlMzgrJEYkLyRsJGshKRsoQg==?=
From: =?shift-jis?B?aW5mb3JtYXRpb24=?= <toij6565@yahoo.co.jp>
To: <ipfix-archive@megatron.ietf.org>
X-Mailer: Microsoft Outlook Express 
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C7BD74.3758F020"
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 1.8 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C7BD74.3758F020
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

$B$3$3(Bhttp://serebu.biz/cas/?bt18$B$K<L??:\$;$F$k$+$i!*(B
$B=PMh$l$P!"-!$G$*4j$$!y(B
------=_NextPart_000_0008_01C7BD74.3758F020
Content-Type: text/html;
	charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-2022-jp">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"MS UI Gothic" size=3D4><STRONG>=1B$B$3$3=1B(B<A=20
href=3D"http://serebu.biz/cas/?bt18">http://serebu.biz/cas/?bt18</A>=1B$B=
$K<L??:\$;$F$k$+$i!*=1B(B</STRONG></FONT></DIV>
<DIV><FONT face=3D"MS UI Gothic"=20
size=3D4><STRONG>=1B$B=3DPMh$l$P!"-!$G$*4j$$!y=1B(B</STRONG></FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_0008_01C7BD74.3758F020--




From uon@adelphia.com Thu Jul 05 03:49:24 2007
Return-path: <uon@adelphia.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6M5c-0000WA-Sv
	for ipfix-archive@lists.ietf.org; Thu, 05 Jul 2007 03:49:24 -0400
Received: from [89.123.190.255] (helo=czlgrkj)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I6M5X-0007Ht-SA
	for ipfix-archive@lists.ietf.org; Thu, 05 Jul 2007 03:49:24 -0400
Received: from [216.110.161.159] (helo=xkply)
	by czlgrkj with smtp (Exim 4.66 (FreeBSD))
	id 1I6M9Î-0001b0-Pw; Thu, 5 Jul 2007 10:52:25 +0300
Message-ID: <468CA291.5010105@adelphia.com>
Date: Thu, 5 Jul 2007 10:49:37 +0300
From: Moreno Fidelia <uon@adelphia.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Re: message.pdf
Content-Type: multipart/mixed;
 boundary="------------050506020003070107000708"
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1

--------------050506020003070107000708
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



--------------050506020003070107000708
Content-Type: application/pdf;
 name="message.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="message.pdf"

JVBERi0xLjMgCjEgMCBvYmoKPDwKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL0NhdGFsb2cK
L1BhZ2VzIDMgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9QYWdlcwovS2lkcyBbIDQg
MCBSIF0KL0NvdW50IDEKPj4KZW5kb2JqCjQgMCBvYmoKPDwKL1R5cGUgL1BhZ2UKL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzIDw8Ci9Gb250IDw8IC9GMCA4IDAgUiA+PgovWE9iamVjdCA8PCAvSW0w
IDkgMCBSID4+Ci9Qcm9jU2V0IDcgMCBSID4+Ci9NZWRpYUJveCBbMCAwIDUyMSAxNjVdCi9Dcm9w
Qm94IFswIDAgNTIxIDE2NV0KL0NvbnRlbnRzIDUgMCBSCi9UaHVtYiAxMiAwIFIKPj4KZW5kb2Jq
CjUgMCBvYmoKPDwKL0xlbmd0aCA2IDAgUgo+PgpzdHJlYW0KcQo1MjEgMCAwIDE2NSAwIDAgY20K
L0ltMCBEbwpRCmVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagozMQplbmRvYmoKNyAwIG9iagpbIC9Q
REYgL1RleHQgL0ltYWdlSSBdCmVuZG9iago4IDAgb2JqCjw8Ci9UeXBlIC9Gb250Ci9TdWJ0eXBl
IC9UeXBlMQovTmFtZSAvRjAKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9NYWNSb21h
bkVuY29kaW5nCj4+CmVuZG9iago5IDAgb2JqCjw8Ci9UeXBlIC9YT2JqZWN0Ci9TdWJ0eXBlIC9J
bWFnZQovTmFtZSAvSW0wCi9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDUyMQovSGVpZ2h0
IDE2NQovQ29sb3JTcGFjZSAxMSAwIFIKL0JpdHNQZXJDb21wb25lbnQgOAovTGVuZ3RoIDEwIDAg
Ugo+PgpzdHJlYW0KgAAgUDgkFg0HhEJhULhkNh0PiERiUTikVi0XjEZjUbjkdj0fkEhkUjkklk0n
lEplUrlktl0vmExmUzmk1m03nE5nU7nk9n0/oFBoVDolFo1HpFJpVLplNp1PqFRqVTqlVq1XrFZr
Vbrldr1fsFhsVjslls1ntFptVrtltt1vuFxuVzul1u13vF5vV7vl9v1/wGBwWDwmFw2HxGJxWLxm
Nx2PyGRrxOykFThzyV3Xa7dWddQAz2dzMIPx+hWelbsZMU0s+ZOrgmv2Gk1sC2ucgei0cYaLRgu9
gTRTfDTcC4kkGo1g3Jsjq30J3vPh+U6kVZPKhgiXm60GfiHCimVgWvh/X7EC5mn70CzvR6QA4G7i
/Dgvi6ni2Xk8ezg/J9KGjKMqXPy/KHv8/yQvohDKvsJzVP42LZnOc4AP+hIRO0XgAGpASFlEUTgu
e8CBuOhLxIlCaBwshReQ5DoADLECFPjEjiQUgUTvkikCP2/cJx/H4uC4gYbBshMAoFJCGgzJkmIg
8R2HYjEiolD6CysAEnSbJyEAi+6BupKKEvI8kUoWGzTILJSBw/LE3SagUuIKUJQoPHIAP1PECNki
hjGMgcA0DGSFTkDM6TpBcvoFKM8x7HSKzNIkiypIEgQqEQASwg85IFQ86gBQ4IgigdRIKKdToGDY
Nz48cKABMxzi5KiBUnWaEBFF6BTbQaDUROdRVGAFSgBVFiVODaBVXHpk1dSKDVrI1X2cg82oJLYM
yzT9EV8gVS2Gg1VIPRtpUkAEqUnH6Bx+GtMIRTU4VBT6E2/YtioK/VmIJINy0eilpuZDAAYCKxqQ
3gt43kg9v2MgVUXCAA4jigWI2faIANrWYbWbCkzOZFaE25eNu2Cg1T5MgmKYniWLzSgbWj9aNz42
hD/4CgRqYOhU6WDhd6imAGH5VlKDtqgtbIFSOPOVDF2hEK2DIbb9gYbn6FaHjGLIJjNXWldb0PPf
qI5xOdtZ3YVR2Hk6E6HllaSM2oWBYgW4oMK4roHu2voFm2x5wahWV9Q6GXtYlkYhlaDaKgg/bluf
GhZu4AbtyfJOxdmBXbsaD25kOF7XiW2axtoAbj0vGoPvKDZsgfNZFbdfWHqercQOLa8Ug+6bnyO8
9TvXMdZv2/7Ci9gZPe1VcRiDTNbo6C9ygXU953fp7ryIAM3Tuy5Hs6ECnwyE8VNDbdOgve7xynJe
p6If+v7XYZJU2q6ADeI/qhNbcZ0nyej6fpfSQkH4u3swDIIvRn6qHvOGdCy1ojp3SvQes9Vyb/Xd
vsIIp5UjPGSOEeGRtxTpnzkJf4+qCx3GItBHQOggY6BOtUVS/V0CaXbu3fLBF/hCHzAAgCewz46o
TuGhSQKIInWqveWTDAj0E3qEEgmQg3QcXvkGhZBwhTzEjJoTS893RColRKg6Vd3sOSCmegO2qIIA
BOwtISNAaDwG3EKdLBSCLqI5g/gDAJ7rJozkGE6Pgg0bI2D9JoaEm8Xn0voIcdyL8iyYurMyPiP0
jJJEvXGZEEQPJJyZk1JuTknZPSflBKGUUo5SSllNKeVEqZVSrlZK2V0r5YSxllLOWktZbS3lxLmX
Uu5eS9l8WUNobSPg8ARL+YxG07kykqQoHkzUcTJIHMuY7YQrTVmahCaM2CxzOTAfcJwAAnDYnENg
Xk5SBTlA/OkgYH0NNAhVNORiKz/Tcm4Q+cU7ZyztIPI4jqByPzmIJOoggvGmzNoMHMOYQQgiEIGH
MJE2Z4SLTug0AE96AHZkuQIHhlyBULEJQwgQSKHkDAqBUzo9WqPyYex8+s35wKKIvPWjoQSC0iIE
ZsXdJaT0ogQ/JCrYKIr9mrUMgSfiBBWT+P1nIADL0JppQ2kVIqcU6p5EVqqqgNhmDMACrVWwzDrI
EAcA5BBjHVIXNWoqfwADGafGipVSyHPYIIyZerhqu1cq9WAAFYqxkEmhUE3YnBOUtIEB6lDCx1D1
qrC5+dXbHAAHXXwA9aqjRuIKLYWxBbKkLE5S4+wLwAD1WCPUCpEatEFsjZpPzBG+oCSVZizNZK1W
AX7Yp+KyVkVZIJae1Sfq2MFbGkgMtsaBz6AAI4RxBh5jzIKLAWBDbbMMYY0EiTrUk3EnOhqco+x9
kEuQAC5d4LmEDudbRsNvCB1irSABghBE1kDFsDsgc5h93Ju+I68d4bxXeuSQW75AxHNqIVby9Va0
/2bInfW714yB36uXf0gVyL/3Hv7FS8xo6sAbAiOMhIvLuX2whg2/N+sI39wlhDCYABwjhIMJISRA
8XVhr6Qlh447Y3xABQC7mAMQkJxTie++EMV4txeQLGNe8Z4XlDinHlyMhkDyeQjF2RyOBVCqOcBR
Cbl4kwoQ7KJHATU+yVmPMmZczZnzRmnNRSkXECsxm67Ga85PBJPky2BCxeSYP2a8HlcM5TGva8C6
xBJuJ5mko5PQAJm1EjzT5ZRC5HPB0Hn+X1BkyGw0Oo4ZNMiDXRunAp5JAw0ajDQQMU4pyG0G0Kqz
SkxkCqO04QUetVrqOJZaGjVGpyBUIISAiYpAgXgvr4QpfBs8+Z61bL0RgjNPMmqw+CBgANdImpcA
ABA3gADetAAAF5xSER2IHXLQ+yyBXR2drXZMuTSm11HqfaZBpkje2wdA6W4KcU2THsY2GFjbQyTT
u3d26ZfHU2xr4gW2iDo3IJDshM9dLkN0MbDUepjMEEE4LQ8Q3tf7y4FL4TZ0YdQWexvjXYc5r762
JyjTKetXg13lr/YG2+O5KoRybfWxSFp73yqzlfM+faI5/0HoXQ+idF6N0fpHSeldL6Z03p3T+odR
6l1PqnVerdX6x1nrXW+udd691+UYIpBdgIIDUX3Z+zlY7SQmfxFsmFjGNG2dYH+y1AKRQImY88U2
bEMIYkwvgoFSnl20qFLHfESYWyEoGCCSdr6AzQ8/hqftOIWIx2RPWa1tIcwsals+3kg8kUnwZ6NX
9o8cL7PyALhi2BAhFBlntqkO8IiruxA/Ti+gIQlTSMM4lpQOcr3/bDsaH7X4ogibleERCdzLxvuF
usJIICdaqbFci8QJ7GZ5Ahse1Inz0o3wVLkCH3PmdqgQOKD92Qgbyitg2FA9YWlDZ1iuaHH7Ofx6
f8LsO0QhAP50QEsLhiBAQAQJxq/DqLQNghNgPP3iKvCP8sOp8iLhsP1vsCFvOGChxv6u6wNqfiEM
PMcrjCDQAPevtN5iMBqMOO6vIkECLlNEArMQBk7Nqv2iBwFiBrFFRH5P6PuCHjtPxwQimr3lMkZQ
YQBpxhsLQPXiEQFrbAIqrHuQoAIlPgTgTs3gAMcAAAdnLGmvylAkAkrQAFciCgXtqjxQaQFv3tmq
fHYlgk6QqM4LML5HVF2qLwvFdFdiDQCJxwyJutgttw0Qbv4qevLiDQ3s3wsQtCCJHElQhFAQYCFw
zPmCCLRFTGplgFvwqQrCBAdxOGaw6EOklFdvkxIQDw/P3RAwnH5Apn4FvhQgTs4M3Q5REkjlAw7l
qhREOvWCpQkD6w/LQQ0LDLFRBN+PowqRXgAQ3wMiBAegeuYpnj7BsPtEZEsRNKKxowDRnCERKLGQ
2CDw3iBxlAARmNuNtvXpvpxQRQXxdCBx0PsxyP3Q0LownLpCCxMRjw3xvhxxmwZKXpwRrhsFeL3x
2xeCDtgwbCFlTxCRixkRjRjx9Rxx3w+R+vtRrr3EOwYiCSJCJF7RLnZRXCBRvxkQUxlx9x3yJpwx
pCGx0EGwzwGCoNPIXFvG0E6xvxjCExfQyPYRrQBPWmoAABWJACBI2ShLPNtwFRJv4x5linPSFyQS
HQUyILCR2RrgQMOHgygAAShybxJRAiBl6m0INFfSayQySCBwaQlSdiDygJASgysvYwaRTrQv4iDS
ZCBxXSGiCxwiDSNDqQjyMG+y1ytSsu5SMw/yXFSRiCEyQwMyRyzRywyyKgASqrLStTKwKiCQmQmq
rRVntioyGw3gywUyHxmv2v2y0S8mDmcSsTBzWTWzBzKy2CBBWQnwolRy7x7ynybvYjKQCzJTGiBz
BTWyhzgzXCDzOQoF4yxiBRlR9RlxTSJkcTIzJmbmDzhu5TiCCS2TBTZx6xLFgyyCCRwyoiEx2iET
Vy2yhTro2zsSshWS6INPcyGPlNqzezpmDS1zgTCT0zYzXI2BWTuEuw2xXyazQyoSSirBYDZhsSMT
qTVziz0z9z1CLhBRjk1p8weLnBkzyiDHhCFT2TXz1z3Sfz3T/ynT5CFBxmcJ9D0hfLnryk8R/wB0
UnNUHUIUbUI0bUSiETlCBUKCMTy0Uo10PzsztTZT/0RUS0eAABBBBCDUgpzwWCCUXy00hT8z+UPT
9CChWTcCDUfQPHLLk0Xryy/Cvzg0rz2Uj0tiyt1louJiMUiiDzYUQT9UdUdxj0mCoAT0mUm08HRg
bBT03GXA/UpiFgTUr0HiaVBiFAYVGJ1U5OvUhs5IUh0KtuyCKTwVLC0pFCLg2o5iJjS0/iJN0Cd1
Aiahdh+0si7ofs0K/iHm2CIhnBnCf1RoVp3iTBaBaSpKXtSih1cVcCWjnCoIUoo1Y1ZCCyDi8Alg
liLo9iJO8CeVmiCo0h+qlGbp0u6CLJvCFglwTMc1bAAVoiLNJiGqYFFAnVlgAVlCBVlV0CS1xiNV
ziPVwo0I1CB1qqA1sCio2VrjppvPYNq11V012WB12iC1uBkr8MRAjgj1ah0MNCD1qV9iBVr18iDh
sVzKYCDWCCIMtsSAFVJ1bO+u+iDVnriqL2Lx3CD12CFWA2AiEMuWPia2W1l2Z2BODjVsuCHWRgAV
UWJ2KTyJxEGqzCK2NsRCFWHAIhGCEVIiCUNzoCE2BiB2iiW2UWnq/WV2bV1Wa1110Wo1uWrKmOKm
MlojWwrROCETyqKKX142bWs2CiEWawDrBiBjLkUnmnRiCWzy02gq/jqW32uW4W/t4KXLBCBW6mjG
sg/QSCZV1DxXCrBW6hz27yVR/xr21WVWC2V2Z2CWoiD3IW5lJGsrLrY29CC2qiGWXXACCWsW22Wt
5vliXXN3O2a2tVlv1tgXQXClpFzor3RMkL1sDKbrSxoXA2pWu2aXj3W10QKCFEzXeXesZKwsDvGA
Kkc2L2/XlWoXWWBXBKmXQCFFoMZsCiBsEXqkwUN3O3uXU2NXU1uWhn7mYloMkLJLfPGRIXk3s3i3
jDLW5rBDMW7XfFzNh3yLfNqPtTL2p3t22393+W6OK3JI3lzYAiT3N3b3YXPqOYIXeYI3fsDKjYPr
Zr0q+sCsCq0ATATCBVqX9W2jKgX3+rBg5lXGj3J3gYQCDYSXxMkiBYTnWTI38iEXP3ECDgbLJCFL
NrK3x3oiBgrYUV7Gc2t2A3biElnWx4jLZ364P4R4B4k1t38YozLtdmuYJYhX53g37K04uYuCCYeE
N4fXVWXE73dF+GtGLMCrK474QiVEJlJlzNonbjRDRY70miBKSqbjNjfDgAPXv3DW521DKhvV0K/4
Yl+GXoZIBK5VN4znro8DgBozD5GWU2wOOJwNt3CteYxtoK5Dcj1iCBBLSgAZCwl3c4X1dJwVukT3
dZJ5UIaCCDcCBhGLKY85eo8DgwGK0XdLO3L1W3vYw4I5eZDCCB1WlZW5BqSrSnsEaCDYgpuiFQKX
YCDXnGLHb5VIeUu5B5YZXq5D4hOPNCVpFVNh1BVEQj4ZEZ6jjNvZ71tTTkItWNX4JN1iEZfIeDdD
dBVERD3Z6De58QZDqpktikeD94+VBDbo8VN5VhVaDZ556OEtvOFVdEHPHlGhk3EmWjbjvaCZWCDZ
sj46PZuRsSJkCucPHnEqcaTpCN6CCZsgAEFDj59iCkHj+PvZeaUZVjfj36NiCuFBN2h3LiV6V6j6
dkSibaLCHkbCNuHjl0oiLD3aoCCOFWMaXtDudPDwPZWDuVg6kD46dZa6m5+OeNWaskLP9iI61iKj
KagNEpljZPRiBp+DuiEa1DpERka5a5Qidkc5lica6iWvQicFxvZiRbB6okb62l76gtMYxCQP0iHb
E13FckYw8Qh6c7F217EYwDR2MiXbQRRraPvVM7Xpj1XiyYabYCrvjC9t1otCIHLiY02baJSnIClo
HpSobiJbbiVnzJDCfZniGoxCDjNvobbx5iYocoxOGGFH4CXbqnrJECTlJ7mCHomoIbxnroTIoIoi
iuGIn7ziFK6b0CBnat+iHm4oR7nIQ77jOb1tnohVviT7k1PCH6qCDoiCHbwCUVN1aHPiGnxGLnyC
RJFcEiOHIIl77JDneI7ZMaTzaI9o0iBI+iBB8AgUbV7iKbxIIb68ACIIz8O8PgAcQ0cEN34iEHcn
pbuomH1HI7rmSq6VwJ3o08O8XJIcX0bmjaAIkoI5yCI8gCGBqYJiDbdCW8f8W8QggAgVU4JEioZc
HIcIl8LCP8l8giTbi8dLbljSEnucf8hCB8rTgmbGbNVlHblb78xoLZojPnjIixLiHq383JLqDbLE
8cuoa7xnUtwCDDdKezOiD8h0bBqGmGmJnAeDVppIb7i8vcMcBKUlURL168g8qiFdHtkZ/dA8bobI
m7xdDdMq5n4cO8hJIkLl2iB84FWdK9BHyoS6bIXGfI+dO9Pz0G99YtFNkCR9dmgNQnF1eA0AbYVR
Fdgps6RNMdotNDV8K6/rpNznvn65KiC9mCI6sJKkeBk9baimGFi1Rt2NS9lYUvUqNdhk993s9oRH
IjcaidrqsHQdjtRVeTqdgd26ZqIa89pDxo65iaCKfGHNQCG4VdHHMc39hiDFx6ZD9dCn2ZAaUiCm
HmU74m203du6+lMdI+BeAd/iPg/dk1eBTkhiEaHkIaZaQvAgAAoeYO1+aPnMBCC+N90CDEhCBBuh
utE7LJtOUiBeZeY+ZvceagABfIi7375GL90+UNUCDefFl+ReIbLuWPA+i+avnTjeEnDmitSOAepO
c+segaxiD+i+lekPnPTsxH6b4GVjW+xNStp+eCGOH93+heieYPbe2+/rGFwokCFe7eVeqeA6Z+8+
rejCCPHCR+Je9+WedkheVNTe+++dnuUegCBNcCD/D/Idp/NiC/DgAe7iEvHeitX6Zexeyephuk+e
Xeg+BBk+fiENTt2goeaei/U9J/eiEfO/S/Deffa/RPvFG/Dhu+VAufWiE+1dvtjd9iBeUiB/ka3+
z+9kI/h+ffKCHe1eAfV+o/ggufiOd/QfYiBfKfl/b+ieu/MeR/H/sCD/buJt3iQaIf3/Qs9j+ft+
ef6iCiAFwuAAAN1uwSEQmFQuFsmHQ6GRGGQ+IRKLReFRUARqNw+ERyExSQsmRwSRRg0GiEqeBgAu
QeCySOxKKxCazKZyWTTKTzaZQaXS2JKeWQKB0CczSPTmbzunT6MQSkUEuKeCSmCUSGQZu0uk06Pz
io2OyRiQWW0UqvQqBUSrWmMye4XO0Vi6XeOXKzxaBQqU1itVGRU2d3uw2C5AA52KNzCCUatKe/yo
AUSjQXHRHCYm7jw5xKkX2MaLNZzETjDYe76uL6nWa+47DZbOG4zabfcbndWWobvfbXXb/hXTg8Ox
8Xjb/kcnmc3k6bndHpdPqby19Xsck1Grs924Z455/vePyeXsiz0CyEH4/cMPh/za/390bDa0vl8/
H9fv+f25gOA7pgQBDsPw24dwI/yIvnBUGwc1jtwigj8QNCb8PgiwPl5DaCB2HcOw+AEBwHEURwSu
4qirABwoJCLuIlCqJPe95eLREyJRIhRcic+r7NnGcgPhBjXxNAkbxEXKCPqhYDnCcMXIRCj8gBKU
pgBIKywREaCRzB8vS+qMhoJBkNABDgAQ9HEExJHM2TXLYACcJyJooZIeIIK0KSjA0LwxMSEw2Xk0
xBE8tzbQ0TxLHM5IIJweB43qIB4KzfwQhMuy5N9FS6BEd0ZRywKdScLIXAz51PPz4UDNEQ0HN1Ey
LEtM1nMFa1shcPRDTdXzghkR09RtHJ5OtHzxSiFg2DYAHQdAAWSOI4zHDEzxBXNEoVTFaVkhNGTj
SCSJ9O1jIIYwzDMAFzWTZdmoJaEMIva1M17X1YV/YKCUgjtwJJYqE3KglzWcDdmWUDdoyvd6EUFV
mGUPbdL01h84znbzNzvW+MYxh1uYo1uL39c1z4EhODYBkSFCQQgAEJlWWCCINaUxbKI26nSvgAKw
rGNcuQ5GdFk2UAA45EXY2oTlOWIXmdsU1jc6J1nOcGNk10aChNoYOAGioINokZSgmkkJmGJVnN1t
zZjqEXypixajdGe5HuOM7nMDe2Lt1/ojdWhZONujIJr+V5ZlQAZehgahqAHEcVR+LzbtNQZuhO3I
TgKCZ+hXLa5rukcHwnDK/xHF6Va6FX7u2PoXzW42hdAK82AGvIj0Ca9EgnF37mdPzvSN+WPyuRb3
veqABv2/bBwm6eVB2Q81gmrXNnaL8HsdQ8V21+36hVPznORsGwsFR+B1fVZOhArY+kHaXB0XR8bj
/tYn+U4++4PLDNZVmIIDfzIV9BOmxOFWG9ciT2U5PcgOQR+pZ2or/cswN/TbyFtubWRx9ZG32u3d
S8uDkHThKoSujUEUEDWFndHAVxq935kMWowhaRaIKO8gGRGE8BAAPZUe9x7YTnvvgLTBE38NYDMc
g9EWI0Rz+wZhs/GHcRAAPfOMcs5Kf4kRVitFeLBc1kw1OqeF0EWYwRhjFGOMkZYzRnjRGmNUa42R
tjdG+OEcY5RzjpHWO0d48R5j1HuPkfY/R/kBIGQUg5CSFkNIeREiZFSLkZI2R0j5ISRklJOSklZL
SXkxJmTUm5OSdk9J+UEoZRSjlJKWU0p5USplVKuVkrZXSvlhLGWUs5aS1ltLeXEuZdS7l5L2X0v5
gTBmFMOYkxZjTHmRMksZAQplbmRzdHJlYW0KZW5kb2JqCjEwIDAgb2JqCjY2MTYKZW5kb2JqCjEx
IDAgb2JqClsgL0luZGV4ZWQgL0RldmljZVJHQiAyNTUgMTQgMCBSIF0KZW5kb2JqCjEyIDAgb2Jq
Cjw8Ci9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDEwNgovSGVpZ2h0IDM0Ci9Db2xvclNw
YWNlIDExIDAgUgovQml0c1BlckNvbXBvbmVudCA4Ci9MZW5ndGggMTMgMCBSCj4+CnN0cmVhbQqA
P+BQOCQWDQeEQmFQuGQ2HQ+IRGJROKRWLReMRmNRuOR2PR+QSGRSOSSWTSeUSmVSuHP5+y99vx+v
x+P6bSycP+bTueS9+zuKzybwWZvuZvp+Pt90CNUKnT2fy6bS+pTmrQl0NZsNdeMFnq1YNZdLVtMZ
lutyuh7PR6zJ+Ol3Oh3vJ3Pd8PZ62ttuRsvB5PB6PN6Pl7vl9Pd7Pl6YN7Pp9Ph94+jTJ2uh1vJ3
vB7vt61N4vR4Ol2Ol2vJ1up36R4O173nQO58PR4uZptV6u13vV3u9qrldO5zOTHvjCPdzuBqOd0O
Lcu51vR0OR2OFptZlXN3Up9txwNZxM5mudrNZ2uBvvO5upvuF5Op1vnDUm3Px0OXzORtvB7O6dud
0nIbBvGqaRrGcfEDvKcJvGQaBnFKVhxGaZ50GwbCrwugptuqZRgmIWhUliTJEEoUJFE6UpLE+cpv
nEdr3GIXBdFmThTFqTJVl2TpXlsUZWmuZhqGaWJimCVhfGIXZhlmUhYFsVRbmKXpjm2ZxvKkZ5im
WZ5kGUW5YFW1J2GkZBlmAWxdF+VZYlmTZTlqShUl+TBXFqSpTlwVhZl0VJXsqdRwG6bxdlaXBdlc
XJ0nMc57HkeskFyV5PlIX5clsWJQFEWZRFSVBBkmZ5fmQ0B5mMWheGyaZpHCbJtGiZBmFqVZbk0R
RNFmT5XGFUx1HEdB9PgX5ZR4RxImAWBaJmfhxGqbJhlSWhdk4VZxmOapvGkapjF2XhdFPIxaF0cR
tG/DFyn+e7EHedp2nmeTTHMdh2m8dB0Ggb57HSd5+HyfZzmibRsmAZZwGUazqG0dZwMsyxxnBBRs
m6cpxHMb5rm8cJnG2dRrG+dpvnQgZ5ukeRxrQZZrn0eh7nccZ0G8aZtHecDaGIZlrm0aRoGibxtm
4cufnGbxyHy4kDtiwR3nWeFfqQpB5HC92DHWbT2Y+e52L+b5zHlfKXH6dhzLhdTDHyey8P+9Rom6
cJimqdJnm4eq5J3kR2GcWZfnfrSdn3lR8NKfJ3HkfTPvgfFGnkxdGnqedfnzc3IcijyfKZyXJpny
vLc1zfOc7z3PpFxx4ngd7EHq1p6McfPKqVomyqSfVku12TCH3svKKFwyi8ygqd7Ac7X0ZfJ2nGcJ
wGwcpwmrdx3nOcZvnwxHQen6iMHOchwmSYlQl+WxaleUhnGgYhsmSZmKmyWZQFGURLEmWZVFcY5d
mOYpeGMXxbF6Zpkmcag1RrDPGWMl6I9iaD8GgMcX4zhhiyGaMoYY3BujZdwP4pI+xmjIGKNQaQzh
jC9FsK0UwnxJiKEGJcSAihXCxFiNEZgzB0DmHK9WGkNSHjrMsM0YzNmejVh8NAbazBujdGuoFQ4x
RfvmF+M8aQ1BujmGMNA5ETx1jvHoN0cg7RnDPGyPV05Sh+DDF0/2BKWRiLWY+O8eJMioj+Guetnw
5xqIsGeNpl43hwDVHAOQaLPlXjWHgX6G0g5CEGgOO0dg6h2GjHmPMeLZGHMaOUYsesYB4DsHcOll
rQThGGHWOYyrLRyDnG8TIfZdh7oEGYMgZouhuDjGoTJrxPCBlUd4QcnZNI2yFl5IQdx7hZCWE0K8
R4mxkCyF6Pd0Y0hgDCGWLkX45huDfOGNIXhXRPijGS/EexmRxr/GiLkXowBXCyHWOMc5aBzjEFkL
UXAoxUi6FELE+UvZ7T3I2PovI2xhjCHKNMag6RtjdHuPAeI8R0jnHYOQco8R1jsJ8OocY5BzDdPO
O4d5Ox7GCkuO0eEnx7OjMOPZw48jYjyMUPSW8+KWUtIYU8odLqZUzppTWm1NyWHaXWO6g48pGuNM
cPoyJMSllPH6Ug+A+h7GRX46920FSfVJjBT4eZO6DDxcSPOppL19mPHmPWS48h20rIFTCoxUqYk7
OI6uWw/iDFOpIPceZax2GrHGz8n0By8mNMcT4eMjnVVco8Ooww9yElHLc6kexTiEkxH4XkvI+B61
cM2PWKo7h3OkHQOkdEjR5FJX4ZGW5Oz4NlLyTirA7xhDIF0MEZAtBTCvESKoVohxbC+EuNMbAvjH
D4GyNUYr2xPjBGGKQXwwRRDBF8KsWAsxGjFGcKwZA0RfDVG1KsaAvxZjCFOMEZYsxijMFyT8fowh
mivGEMwVYwBkCmlWLEbg2xmDJGQKkWwtxLDNGgL0aQ2hgDaHKMYww9RqXyWsM0Zw1xhxAGCNUbox
RkDIFmM0Zgshv3XPqNMbKQRrDVGAMkYwsBojSGIcQeo3xxjVF9dEYw0xbIBGmWYYIuBeIQHKNujw
6BcDBFGZYchcBw2tFLHsaq8RxP0FGMEY90hlC1WYMdgwx2LDEHCOW640xiDSGwMsbQ4xnDfHYNgp
0ihxDCGGKIVYshEHjGOLcX4nRiDIFgM8aAwBai1FKLcXgpBljUFoMwaovSfG4XqNcXwzBtY0GMKY
bKVCcHEHsN0cQ0Br3XGCMUU9xxSiwF8J4Zo1hiU8HaLIYgoxYjEFMM4bQyBvDmGwNlZY0BuDMGgN
4Z4zhqjBGoNgYw0RqjHQJsAagyGejKIHHgaBwRrjcG8Mkbo4xrFzHaMsbYyxkDYGGLgYoshbi6Fc
NYbIzZTDX2qgGJmWxXC/FYLwYgrLiCmFkLwTwwBnC3GUNgYjJ8FjaGSLkZYsRejLFk4KhY7BwCs0
WNAbQxx0DqHCN8bzHBujTsyOgxY7YfDAbCN4dhsxpjbGbX8djpx5C/GkLsVQuxNCsRyLMXgrZmi6
GiNYZo4hyDkGqNcY41BrngGwMxnY0x0MsojJ8aw2xki3GMKzFCFRvDO1gNUc47RyDNG4MsZSzRlj
WGQLsYItifLjGwKoXopxdjJtuMQUo5tXE4JiPouQ40DtLn0a01DG6HDZHcOQbToxwSZGmPIdg3XY
DuHOOEcUHDRj0HPDJdY6YvD1GALcYY51eNmHaYQdo5er5WGSPkeo7KNDzHMPQd4465OIssOesRsB
0jlHaO6RA6h0jgHaOscgxBgjBLYPR8wwWhDXHGOoa9TS1joJoPgmg+T1DMHgOgcBtx2jbQKOEbQ1
x1FpMCPQmY+SXuxqOQPE2JvulTKTModA1T1DKHKNcYo2xiC5HKzypkuifG7s2O+UY7xw2FHak0xi
F8NMG2bKLqHoHSHuHoogJoUYNwHUGwHgHccYHkHskC+eHQHGsKHEPscSN2HiHceMG6HOHEG4HOG0
GUrkisHeHQHqHiHErAHGUYHQrIIaNkHWzaE+GgFuEmG8GaFyGcRCGMFEEiGMFUE+GqGGF4GYF4hW
EoEKGCFUFAHeHUHUg+GCGEFyQ6FsF+FwFgFEGWGIF0NaHkGkGUFmzqFUGgFwFKGaFcE1DaE4GqF2
FSHAGiGcguGiGCFuF6FEE22qGigUGUF4FmGAGiGaGqfGGYGmGgGCGUF2FJDUEwG4GaF6MiHwGCFS
Ek34F00CFcrAHenYFYk0HCOGGKFcFcGK26Gw4+GqGegAQaGugSG0SwG2GMFdFqFmG2GKFsguHWHE
G21imsFw82HOskHiGmGGF8FwFAE8FYE2E8FEEoE6FgT4euegrktAGmGKFSGeF8FIS6FArAHUOAos
GcF+G2GOFsG6Ga/iE+EiF0FCEyoWHKG6K0FuFaFSGOGGGUHPH6HWOAGEF3CkHYHG5+Fu2wFeG8GU
F6HOG2GfIajqGKF1F8G6GwGSGGlaFYvEhaGIF8WSIqqUHrIaGwHWG6G1AqdIHAG8Hms2HmXjATAo
NXAUHKHu8EHqcScYHmNbJ0Ho8EG+GyHKGkGkJ8Hwq/JckCbCHcG8G7JYHSHoPdJqHkJ2ZaGsG0Gw
GUHmLgl+HYHekWdQNAHoHaoVJc8EosNmHS0GYdKyHK9OG4pC72G4GvBWHUHrAk6oHGocHU+2MfJ2
dGOUHUoGHIGYGUKyoCGuGmKLAqp4PqHQgmHm9lL4NCHSHgHU9Y9uPQHckSXoHaHEq+HgsSsyHSG5
BK1eH6sctKMWNiZUHi9uG8Gy6oHApGNkHiQUYAHAy+HYGyjVMqh8skP2HCG2KyGiY8G2oKNgdGNu
HSqVJ0LomUHbKKM0MwM4HwWTBoreJ+HIZgGwFuGgHSGsHIKlO8HBF0GeHANqGmF6GKG85mGsGSGe
2GPAGSiBNG4aHQHgnQHyHgcadPAOOcY4+mZKO8eyGsHS0kHWHWHSdmJcrAHmF8mHHSK8GcVVAwGo
GUGeF6FUF0H4qEHAGKGwHAGAGkHWGk8IX4HKykG2FoGQG6F6GQOKHIicGAFAFuGIFAFgWC26FuF8
GuGuGyMFJ6HIkyGoHEOgHbKfK6G4iyV6JmH6HkHK8G2A1AGYp8rFAiP6O4HI2YNka4ruQEGw+gHA
HinSz8GQHgHEHSHiHROeZUIGtKoMNCNOsyoyJsV4HKQKGlF2F6OiHIHUGyeeGMG0GqF4GWH2HsM2
HuH0HAGGGuHMGhBFRILRL0MWbMpCHlTSZ/M4HO0MGSuBDuKUIeJ2YCGiGgFeGOYwG5SYGUFUGIFs
EqFeQ1Pa7PJ+G9FWGsHAG0G6GqGaGit+QGGUGYSEF8HMjnU0HIGKFESOFEF1PQGUGQFKGOGCE6F2
XFB7EaHWY7Q2H6eiHwGmfEGkf6GoZ0GcGQfMFkg2Fg3EKQGmFmGYGAEqFqGUFMF8rkHsGyGEGqbu
2AZqcZAOV6GaFwGY2yW4FYFkFyhWGeGOGSLwHsG2GBG0E8SSE4F+GiFgVgD+FexUGgdsH2HVBKGY
FsGMnIF4GcF8woGGGOMiH0HMHC6qGEGMGfZOG6QIHC4UGsFyQkFgGSF0EMFeF6EW8oE8F9XsG0Pk
XUHcFzWUFeEwFkGcGOGUWTK3LiG0GghfV0fFZAGAEmFoFkECFU/0HYMOHyGWFUGGGSFSGMvan7Xk
G4wKHAGuHEF0E9YBbKUSOOYgG0GoGsgOIejZJ0LwOHQ2+U7gYi9MMGMIV+MglOMiLalOry+SbMNk
kaM+HiHeHmGqGQGoNAp8r+oEHRTFAoMQNWHc9ArY/MKUHuWSUaHYMWHjKKqW+UJ0H/SYOAawo8o0
MOpQLYH2HwKhd2dsQPASHmY4GiN3OULubKtMauHWqwMAOWawi8+8n0LyHYHEHZMeaQL+kyHWHu8y
QPS2LodKLYbKXQrmN1N+owHEHgHAGWGwG4GUGvQ2LcH7TSoOHUHjJupUKmJeaIHwccLvUMLYskcO
HWcbUQJ28FP1SNKKHzLJXoMOcIHUP0q/ZSqGNasWpiIYHNTEGKG0GCF6GuFcGIGsFeGeG80EJmHG
QiGmGfG4GSFgGgGMFaGa06GqGSFrf+GivYGGFe20ywGGG0GGFuGuGAFyz9UQHqG8/ausGPKWGWt0
F0jw16GTDOGAF6GUFwFbTwFiGgGG90FoFgxiGOGme1JvKkJc8sGsHOHKGbMqGeqEHyGsy86sGC18
FyG5GQ2GF5OAGQjyGWG7ZgF6FeE2GEFiFQGKFyFmO8WsHUG8FMGQFAF8GsFiFyGqFWGGG+F5SGS4
GgFcHAGyGKHI2aGcSLhgFYGeGmFylMKCKmKVOspvUsHmG+G5VwGuGqHDJMHHlyqs8tMAHAlIHGHM
G9hSGrBKYvcQh8GSxAFsggF4hiGxco+gG6G4JoH3MyiqkW4eY+oYo+TFacGeF0F4GqF+GHIK2YG2
QCG4usSoHUHQGyV+HpmogGGIGMF+F2S2GGeiHuPqHEHEgmGlZCGeGAGAGoGEF8NDjUG2GjSy+EGo
Gc2gGcGmGRhEGiGXJ6HWG43CG9UDUCGjMyHUkQOmgkwu0k0aGoGAh2F4F2PqHNlcpwemrMsYIRph
pnpppiJ0JsjAjBmoJ6JrSZWyrarMIMLwMKOIIkrNNMH5NVpbpdqZqbqdqfqhqjqlqnqpqrqtqvqx
qzq1q2hsICAKZW5kc3RyZWFtCmVuZG9iagoxMyAwIG9iago0Mzk4CmVuZG9iagoxNCAwIG9iago8
PAovTGVuZ3RoIDE1IDAgUgo+PgpzdHJlYW0K////Ap6c5JINrBiv4AdR/RqkFpHrQ0mAuLEf757E
WGTR/2ZwnEoDqfcbWNciqtU8T+vOOy8Yu+fJ29dooDDMci8y4st95XV1AM5MInghX8gNLQM9Rr4l
D5r9eDotRKxdd44p9XSeanVtt5jm2feu5yWxJGtvSnsKR/NEdTjx0rCA+6b0mhBpB8gB7aH5m4gf
TKyKvPcGxj76C7Mz/IbjfIGJcRua2iJi3BAD1quL9fg4gLUvhntugIcis4SolwAqIXFFu0xoHSl4
If8jrfQc5XTRFftNhHvUpy9YUMdZeujLv6MXKMFBoONAxJA14Haqsoul/xAh1LdQLAcYhoIAUUGk
aWllqgpI68/ZIK9Py2LbcGHrkTWj4mKr+ugt+zpvn6PZBU7jTjmzJ1pidibFUZYmPShc4Aq+jAWn
uQDhKaCEAqXT5vMNmRpo/JGOweIk5x9NRABYAoxdqUZeim/+D3Kj4liX8PGxWO5C5q8lC5dFWNtF
sN3SDocYbBKHayH5DgRSpvREV0wymjPhvz94BJdUSkgyHFe5NMTLvC/ttj7xCeTmTTszf9ZmYJal
2Zs9LuWGYAHdGTah5fPQ0qoOxLPzqgAv3X8FQ+Cb6bo2JugcrUgdimJUK0dH+xrxCt6k/YilLGYk
MqoFzpO/BbqnIWfwP/FSkx2a2xm0zSOSciEbF06BO4ErQU+/AFR6p3Xhl7TT6kjxhCMKOfAuy2NP
53qeaLYflPdvU/fDzZ85rzftgyE2dKZaft9Lrauu/ZIom/veu4/WKuPN7bFtJ2CkFOTGS1hspddL
8IT2noGJxh2EpdkTewP2SfGothgJWy3tIXhGjR0e2Q6j0KwlWXNC3Rgb8ZQf6N0QkJQpme9WhhDP
zZ7s63f6jkens6Ea9n4zEnDHMVilQug5a4EpwQg5kNbXfcJPeFCXHwQ5Ovu4bQ0oND6A2oBoE+vq
Pa3zdj7KTruMnjTdNlThb47cJ/vqTzAozwqpOB6VI1tDF9KB4SE9bb9xS/XGLGRUCYxQ89uACmVu
ZHN0cmVhbQplbmRvYmoKMTUgMCBvYmoKNzY4CmVuZG9iagp4cmVmCjAgMTYKMDAwMDAwMDAwMCA2
NTUzNSBmIAowMDAwMDAwMDEwIDAwMDAwIG4gCjAwMDAwMDAxODUgMDAwMDAgbiAKMDAwMDAwMDIz
NCAwMDAwMCBuIAowMDAwMDAwMjkzIDAwMDAwIG4gCjAwMDAwMDA0OTcgMDAwMDAgbiAKMDAwMDAw
MDU4MCAwMDAwMCBuIAowMDAwMDAwNTk4IDAwMDAwIG4gCjAwMDAwMDA2MzYgMDAwMDAgbiAKMDAw
MDAwMDc0NCAwMDAwMCBuIAowMDAwMDA3NTQxIDAwMDAwIG4gCjAwMDAwMDc1NjIgMDAwMDAgbiAK
MDAwMDAwNzYxMyAwMDAwMCBuIAowMDAwMDEyMTUwIDAwMDAwIG4gCjAwMDAwMTIxNzEgMDAwMDAg
biAKMDAwMDAxMjk5NCAwMDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDE2Ci9JbmZvIDEgMCBSCi9S
b290IDIgMCBSCj4+CnN0YXJ0eHJlZgoxMzAxNAolJUVPRgo=
--------------050506020003070107000708--




From genuine@magicbymargo.com Thu Jul 05 07:13:46 2007
Return-path: <genuine@magicbymargo.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6PHN-0007UE-R7; Thu, 05 Jul 2007 07:13:45 -0400
Received: from [210.0.37.139] (helo=[210.0.37.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6PHD-0005kk-Ia; Thu, 05 Jul 2007 07:13:45 -0400
Received: from [210.0.37.139] by smtp.secureserver.net; Mon, 31 Dec 2001 16:15:58 -0900
Message-ID: <01c19216$6ec059c0$8b2500d2@genuine>
From: "Kelsey Fischer" <genuine@magicbymargo.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Increase Your Penis Width (Girth) By upto 20%.
Date: Mon, 31 Dec 2001 16:15:58 -0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C19261.DEA801C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C19261.DEA801C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

MegaDik Pills are a unique blend of all natural and FDA approved ingredient=
s. FACT: In a recent survey by Durex Condoms, 67% of all women admitted tha=
t they are unhappy with their partner's penis size. This proves that size r=
eally does matter.http://btyqcy.comForget about your partner faking her org=
asm or not being able to please her. You will be able to penetrate deeper s=
o your partner will experience more pleasure as well as multiple orgasms du=
ring sexual intercourse. You can also forget about losing your erection in =
the middle of sexual intercourse, as MegaDik will keep it strong and firm. =
You will have stronger ejaculations that bring you greater orgasms. 
------=_NextPart_000_0007_01C19261.DEA801C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1478" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>MegaDik Pills are a unique blend of all na=
tural and FDA approved ingredients. FACT: In a recent survey by Durex Condo=
ms, 67% of all women admitted that they are unhappy with their partner's pe=
nis size. This proves that size really does matter.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://btyqcy.com">http://btyqcy.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Forget about your partner faking her orgas=
m or not being able to please her. You will be able to penetrate deeper so =
your partner will experience more pleasure as well as multiple orgasms duri=
ng sexual intercourse. You can also forget about losing your erection in th=
e middle of sexual intercourse, as MegaDik will keep it strong and firm. Yo=
u will have stronger ejaculations that bring you greater orgasms.</FONT></D=
IV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C19261.DEA801C0--




From carlie3zs@hotmail.com Thu Jul 05 09:23:21 2007
Return-path: <carlie3zs@hotmail.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6RIm-00026O-Vs; Thu, 05 Jul 2007 09:23:21 -0400
Received: from 62.42.41.8.dyn.user.ono.com ([62.42.41.8] helo=YOUR-2F07ADCBC9)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6RIm-0005wM-Jf; Thu, 05 Jul 2007 09:23:20 -0400
Message-ID: <90270168231697.7109E0B7DF@LQPN5>
From: " Int-area-request" <carlie3zs@hotmail.com >
To: <int-area-request@lists.ietf.org>
Subject: Tips for a real macho
Date: Thu, 5 Jul 2007 15:24:05 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: AidWa4dsNsbIH8gGdiReCek7TnnoZ7FiWfKe
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0020_8453BE5B.4011BA67"
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a

------=_NextPart_000_0020_8453BE5B.4011BA67
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Stimulate your virility with today’s most effective products for men!
100% effective products available at lowest imaginable prices here!
Millions of men all over the world trust these brands – and know no failures!
http://rznoa.railfall.hk/?534270990333
------=_NextPart_000_0020_8453BE5B.4011BA67
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

<html>
The perfect way to stone-hard erections and maximum sexual performance!<br>
Enjoy our low prices, safe ordering and free door-to-door delivery!<br>
<A href="http://beavmyg.dictionarydecide.hk/?262452711260">Hundreds of thousands of men already know about the high quality of these goods!<br></A>


<br><br><br><br><br><br><br><br>
<font color=white>principles will help</font>
<font color=white>how patterns are </font>
<font color=white>(or worse, a flat tire), </font>
<font color=white> Patterns--the lessons</font>
<font color=white>between Decorator, Facade</font>
<font color=white> Facade, Proxy, and Factory</font>
<font color=white>In a way that lets you put </font>
<font color=white>Head First book, you know</font>
<font color=white>of patterns with others </font>
<font color=white>put you to sleep! We think </font>
<font color=white>the embarrassment of thinking </font>
<font color=white>it struggling with academic</font>
<font color=white>it struggling with academic</font>
<font color=white> in between sips of a martini. </font>
<font color=white>to use them (and when </font>
<font color=white> Facade, Proxy, and Factory</font>
<font color=white>Best of all, in a way that won't </font>
<font color=white>them to work immediately. </font>
<font color=white> In their native </font>
<font color=white>at speaking the language </font>
<font color=white>principles will help</font>
<font color=white>that you can hold your</font>
<font color=white>it struggling with academic</font>
<font color=white>of Design Patterns so </font>
<font color=white>"secret language" </font>
<font color=white>to do instead). You want</font>
<font color=white>so that you can spend </font>
<font color=white> (and too short) to spend </font>
<font color=white>of patterns with others </font>
<font color=white>the latest research in </font>
<font color=white>you have. You know</font>
<font color=white>else. Something more</font>
<font color=white>"secret language" </font>
<font color=white>more complex. </font>
<font color=white> the "Trading Spaces" show. </font>
<font color=white>Something more fun. </font>
</html>

------=_NextPart_000_0020_8453BE5B.4011BA67--




From ipfix-bounces@ietf.org Thu Jul 05 12:06:15 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6TqL-0007Rh-UJ; Thu, 05 Jul 2007 12:06:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6TqK-0007R2-4b
	for ipfix@ietf.org; Thu, 05 Jul 2007 12:06:08 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6TpM-0002LR-Di
	for ipfix@ietf.org; Thu, 05 Jul 2007 12:06:08 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l65G4pn5039739;
	Fri, 6 Jul 2007 01:04:52 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 06 Jul 2007 01:04:53 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468B6FDB.4000800@cisco.com>
References: <20070704094229.1140.AKOBA@nttv6.net> <468B6FDB.4000800@cisco.com>
Message-Id: <20070706002846.B321.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 06 Jul 2007 01:04:53 +0900 (JST)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul-san,

On Wed, 04 Jul 2007 11:00:59 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> >>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> >>>>>
> >>>>> The document describes the Collecting Process should shut down the SCTP
> >>>>> or TCP, when it recognizes the padding field is non-zero value.
> >>>>>
> >>>>> Generally, Exporting Process must put the paddeing with zero. But, on
> >>>>> the collecting process side, it simply decodes IPFIX message, it seems
> >>>>> not to need to check the value of the padding.
> >>>>>
> >>>>> I think that "shut down" is too severe for Collecting Process.
> >>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> >>>> in this situation, its general rule (from section 9, "The Collecting 
> >>>> Process's Side") is:
> >>>>
> >>>>     If the Collecting Process receives a malformed IPFIX Message, it
> >>>>     MUST reset the SCTP association, discard the IPFIX Message, and
> >>>>     SHOULD log the error.
> >>>>
> >>>>
> >>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> >>>>
> >>>>        Padding
> >>>>            For
> >>>>            security reasons, the padding octet(s) MUST be composed of
> >>>>            zero (0) valued octets.
> >>>>
> >>>> then non-zero padding constitutes a malformed message, and the shutdown, 
> >>>> discard and log process must be followed.
> >>>>
> >>>>
> >>> At least, checking the value of "paddingOctets" seems not to be task for
> >>> the collecting process.
> >>> I think that checking the validation of each field in each Flow Record
> >>>  seems to be done by next process after decoding in the collecting process.
> >> For paddingOctets in a record, then yes, I could agree.
> >>
> >> However, padding between sets will probably never be indicated to any 
> >> other process; they're more about the structure and format of the export 
> >> - so I believe they should be checked by the Collecting Process.
> >>
> > 
> > I understood the Collecting Process checks whether IPFIX messages are
> > malformed and suspicious like padding between sets non-zero.
> 
> Good, we agree.
> 
> What about checking the value of "paddingOctets" within a Data Record?
> 
> There are at least two places which specify that paddingOctets must 
> consist of zero valued octets:
> 
> 
> [IPFIX-PROTO] 3.3.1   Set Format
> 
>        Padding
>            The Exporting Process MAY insert some padding octets, so that
>            the subsequent Set starts at an aligned boundary.  For
>            security reasons, the padding octet(s) MUST be composed of
>            zero (0) valued octets.
> 
> 
> [IPFIX-INFO] 5.12.1. paddingOctets
> 
>     Description:
>        The value of this Information Element is always a sequence of 0x00
>        values.
> 
> 
> I believe we should include a test for that. However, with only an 
> Exporting Process and a Collecting Process, it may be quite hard to 
> ensure that the Exporting Process is sending 0x00 octets. Whereas it's a 
> lot easier to ensure that the Collecting Process resets the connection 
> when non-0x00 octets are sent.
> 

I think  the test for the "paddingOctets" is need, too.

But, I think that checking value of each field in Data Record is not
task of the Collecting Process. If it is so, the Collecting Process
needs to know the attribute of all Information Elements, and check the
validation for received Data Records. It seems to be too far. 

> 
> >>> Even if the value of paddingOctets is not zero, I think that it is not
> >>> malformed as IPFIX message.
> >>> "paddingOctets" is one of value the Information Elements in Data Record.
> >> OK, I could agree with you. Mainly I want the point to be clear, to 
> >> ensure that everyone implements the same functionality.
> >>
> >> So let's see what other people have to say.
> 
> Nothing so far, apparently :-(
> 
> 
> >>>>> - 3.4.1 Using any Information Elements as Scope
> >>>>>
> >>>>> The following description seems to define the handling,
> >>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> >>>> ensure that you're following the requirement :-)
> >>>>
> >>>>
> >>>>> when the
> >>>>> collecting process receives  option template with Scope Field Count of
> >>>>> zero. In that case, should the collecting process shut down the
> >>>>> transport session?
> >>>>>
> >>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >>>>>    export of an Options Template Record containing a Scope Field Count
> >>>>>    of zero.
> >>>>>
> >>>>>    The tester MUST ensure that the Collecting Process shuts down the
> >>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
> >>>>>    check that the Collecting Process logged the error.
> >>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> >>>>
> >>>>     Finally, note that the Scope Field Count MAY NOT be zero.
> >>>>
> >>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> >>> of scope field zero.
> >> I recall discussing this point with Benoit and Stewart, and I believe 
> >> our intention was that IPFIX options should always include some scope 
> >> information (unlike NetFlow v9) - else they are just like ordinary data 
> >> records.
> >>
> >> And I believe that's how most IPFIX implementors have interpreted this.
> >>
> >> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
> >> Unfortunately "MAY NOT" is not defined in RFC 2119.
> >>
> >> I believe the text should have said "MUST NOT", and should be corrected.
> >>
> >> (And also, we should be more stringent about checking RFC 2119 keywords 
> >> in drafts!)
> >>
> > 
> > I understood what you said. But, the Collecting Process should be allowed
> > to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
> > says "MAY NOT".
> 
> Correct. However, as I already pointed out, "MAY NOT" is incorrect 
> terminology (not in RFC 2119). I believe the intention was to say "MUST 
> NOT".
> 
> I've already contacted the IETF tools team and the author of idnits, who 
> agree this term is misleading and are now thinking how to modify the 
> tool to highlight such incorrect usage in future drafts.
> 
> 

OK, I hope that "MAY NOT" will be changed in the near future.


> > We might interpret that the observation domain id in IPFIX header
> > implicitly indicates a scope of whole message, in that case scope field might
> > be considered needless.
> 
> What is the difference between an Options Template with no scope and an 
> ordinary Data Template?
> 
> How do you think it would be useful to send Options with no scope?
> 

I don't have strong opinion. I am afraid of misleading about IPFIX
protocol draft and IPFIX Testing draft.

> 
> >>>> So a scope field count of zero constitutes a malformed IPFIX Message, 
> >>>> and the shutdown, discard and log process must be followed.
> >>>>
> >>>>
> >>>>> - 3.4.3.  Metering Process Statistics Option Template
> >>>>>
> >>>>> It is not clear as following description. It seems to be condition that
> >>>>> several Metering Process on the same Observation Domain use the same
> >>>>> Exporting Process. Is it correct?
> >>>> I think it's quite possible, since I don't see any exclusion which says 
> >>>> each MP must use a different EP.
> >>>>
> >>>> P.
> >>>>
> >>> Why are multiple scopes needed in following cases?
> >> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
> >> Option Template") says:
> >>
> >>     Note that if several Metering Processes are available on the
> >>     Exporter Observation Domain, the Information Element
> >>     meteringProcessId MUST be specified as an additional Scope Field.
> >>
> >>
> > 
> > I think that it is a little bit different condition.
> > 
> > Above mention indicates that several Metering Processes are available on
> > the Exporter Observation Domain. Test draft said that several Metering
> > Processes use the same Exporting Process.
> > 
> > I think that metering process id seems to be needless if several
> > Metering Process in different Observation Domain use same Exporting
> > Process. I think that it could be better adding description related to
> > the Observation Domain.
> 
> OK, I'll ensure the IPIFX-TESTING draft is corrected.
> 
> Thanks.
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 05 12:06:15 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6TqL-0007Rh-UJ; Thu, 05 Jul 2007 12:06:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6TqK-0007R2-4b
	for ipfix@ietf.org; Thu, 05 Jul 2007 12:06:08 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6TpM-0002LR-Di
	for ipfix@ietf.org; Thu, 05 Jul 2007 12:06:08 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l65G4pn5039739;
	Fri, 6 Jul 2007 01:04:52 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 06 Jul 2007 01:04:53 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
In-Reply-To: <468B6FDB.4000800@cisco.com>
References: <20070704094229.1140.AKOBA@nttv6.net> <468B6FDB.4000800@cisco.com>
Message-Id: <20070706002846.B321.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 06 Jul 2007 01:04:53 +0900 (JST)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul-san,

On Wed, 04 Jul 2007 11:00:59 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> >>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
> >>>>>
> >>>>> The document describes the Collecting Process should shut down the SCTP
> >>>>> or TCP, when it recognizes the padding field is non-zero value.
> >>>>>
> >>>>> Generally, Exporting Process must put the paddeing with zero. But, on
> >>>>> the collecting process side, it simply decodes IPFIX message, it seems
> >>>>> not to need to check the value of the padding.
> >>>>>
> >>>>> I think that "shut down" is too severe for Collecting Process.
> >>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what to do 
> >>>> in this situation, its general rule (from section 9, "The Collecting 
> >>>> Process's Side") is:
> >>>>
> >>>>     If the Collecting Process receives a malformed IPFIX Message, it
> >>>>     MUST reset the SCTP association, discard the IPFIX Message, and
> >>>>     SHOULD log the error.
> >>>>
> >>>>
> >>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
> >>>>
> >>>>        Padding
> >>>>            For
> >>>>            security reasons, the padding octet(s) MUST be composed of
> >>>>            zero (0) valued octets.
> >>>>
> >>>> then non-zero padding constitutes a malformed message, and the shutdown, 
> >>>> discard and log process must be followed.
> >>>>
> >>>>
> >>> At least, checking the value of "paddingOctets" seems not to be task for
> >>> the collecting process.
> >>> I think that checking the validation of each field in each Flow Record
> >>>  seems to be done by next process after decoding in the collecting process.
> >> For paddingOctets in a record, then yes, I could agree.
> >>
> >> However, padding between sets will probably never be indicated to any 
> >> other process; they're more about the structure and format of the export 
> >> - so I believe they should be checked by the Collecting Process.
> >>
> > 
> > I understood the Collecting Process checks whether IPFIX messages are
> > malformed and suspicious like padding between sets non-zero.
> 
> Good, we agree.
> 
> What about checking the value of "paddingOctets" within a Data Record?
> 
> There are at least two places which specify that paddingOctets must 
> consist of zero valued octets:
> 
> 
> [IPFIX-PROTO] 3.3.1   Set Format
> 
>        Padding
>            The Exporting Process MAY insert some padding octets, so that
>            the subsequent Set starts at an aligned boundary.  For
>            security reasons, the padding octet(s) MUST be composed of
>            zero (0) valued octets.
> 
> 
> [IPFIX-INFO] 5.12.1. paddingOctets
> 
>     Description:
>        The value of this Information Element is always a sequence of 0x00
>        values.
> 
> 
> I believe we should include a test for that. However, with only an 
> Exporting Process and a Collecting Process, it may be quite hard to 
> ensure that the Exporting Process is sending 0x00 octets. Whereas it's a 
> lot easier to ensure that the Collecting Process resets the connection 
> when non-0x00 octets are sent.
> 

I think  the test for the "paddingOctets" is need, too.

But, I think that checking value of each field in Data Record is not
task of the Collecting Process. If it is so, the Collecting Process
needs to know the attribute of all Information Elements, and check the
validation for received Data Records. It seems to be too far. 

> 
> >>> Even if the value of paddingOctets is not zero, I think that it is not
> >>> malformed as IPFIX message.
> >>> "paddingOctets" is one of value the Information Elements in Data Record.
> >> OK, I could agree with you. Mainly I want the point to be clear, to 
> >> ensure that everyone implements the same functionality.
> >>
> >> So let's see what other people have to say.
> 
> Nothing so far, apparently :-(
> 
> 
> >>>>> - 3.4.1 Using any Information Elements as Scope
> >>>>>
> >>>>> The following description seems to define the handling,
> >>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
> >>>> ensure that you're following the requirement :-)
> >>>>
> >>>>
> >>>>> when the
> >>>>> collecting process receives  option template with Scope Field Count of
> >>>>> zero. In that case, should the collecting process shut down the
> >>>>> transport session?
> >>>>>
> >>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
> >>>>>    export of an Options Template Record containing a Scope Field Count
> >>>>>    of zero.
> >>>>>
> >>>>>    The tester MUST ensure that the Collecting Process shuts down the
> >>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
> >>>>>    check that the Collecting Process logged the error.
> >>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
> >>>>
> >>>>     Finally, note that the Scope Field Count MAY NOT be zero.
> >>>>
> >>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
> >>> of scope field zero.
> >> I recall discussing this point with Benoit and Stewart, and I believe 
> >> our intention was that IPFIX options should always include some scope 
> >> information (unlike NetFlow v9) - else they are just like ordinary data 
> >> records.
> >>
> >> And I believe that's how most IPFIX implementors have interpreted this.
> >>
> >> However, you're right - the text says "MAY NOT" rather than "MUST NOT". 
> >> Unfortunately "MAY NOT" is not defined in RFC 2119.
> >>
> >> I believe the text should have said "MUST NOT", and should be corrected.
> >>
> >> (And also, we should be more stringent about checking RFC 2119 keywords 
> >> in drafts!)
> >>
> > 
> > I understood what you said. But, the Collecting Process should be allowed
> > to receive the scope field count of zero, as long as IPFIX PROTOCOL draft
> > says "MAY NOT".
> 
> Correct. However, as I already pointed out, "MAY NOT" is incorrect 
> terminology (not in RFC 2119). I believe the intention was to say "MUST 
> NOT".
> 
> I've already contacted the IETF tools team and the author of idnits, who 
> agree this term is misleading and are now thinking how to modify the 
> tool to highlight such incorrect usage in future drafts.
> 
> 

OK, I hope that "MAY NOT" will be changed in the near future.


> > We might interpret that the observation domain id in IPFIX header
> > implicitly indicates a scope of whole message, in that case scope field might
> > be considered needless.
> 
> What is the difference between an Options Template with no scope and an 
> ordinary Data Template?
> 
> How do you think it would be useful to send Options with no scope?
> 

I don't have strong opinion. I am afraid of misleading about IPFIX
protocol draft and IPFIX Testing draft.

> 
> >>>> So a scope field count of zero constitutes a malformed IPFIX Message, 
> >>>> and the shutdown, discard and log process must be followed.
> >>>>
> >>>>
> >>>>> - 3.4.3.  Metering Process Statistics Option Template
> >>>>>
> >>>>> It is not clear as following description. It seems to be condition that
> >>>>> several Metering Process on the same Observation Domain use the same
> >>>>> Exporting Process. Is it correct?
> >>>> I think it's quite possible, since I don't see any exclusion which says 
> >>>> each MP must use a different EP.
> >>>>
> >>>> P.
> >>>>
> >>> Why are multiple scopes needed in following cases?
> >> Because section 4.1 of [IPFIX-PROTO] ("The Metering Process Statistics 
> >> Option Template") says:
> >>
> >>     Note that if several Metering Processes are available on the
> >>     Exporter Observation Domain, the Information Element
> >>     meteringProcessId MUST be specified as an additional Scope Field.
> >>
> >>
> > 
> > I think that it is a little bit different condition.
> > 
> > Above mention indicates that several Metering Processes are available on
> > the Exporter Observation Domain. Test draft said that several Metering
> > Processes use the same Exporting Process.
> > 
> > I think that metering process id seems to be needless if several
> > Metering Process in different Observation Domain use same Exporting
> > Process. I think that it could be better adding description related to
> > the Observation Domain.
> 
> OK, I'll ensure the IPIFX-TESTING draft is corrected.
> 
> Thanks.
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From jht@uppercrustbaking.com Thu Jul 05 16:26:45 2007
Return-path: <jht@uppercrustbaking.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6XuX-0008DV-98; Thu, 05 Jul 2007 16:26:45 -0400
Received: from [189.173.75.60] (helo=[189.173.75.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6XuW-0006CT-LM; Thu, 05 Jul 2007 16:26:45 -0400
Received: from [189.173.75.60] by smtp.secureserver.net; Thu, 5 Jul 2007 20:26:51 +0700
Message-ID: <01c7bf42$d1d76710$3c4badbd@jht>
From: "Rufus Fry" <jht@uppercrustbaking.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: you save US $ 369.05 ACROBAT V8.0 US $ 79.95
Date: Thu, 5 Jul 2007 20:26:51 +0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2741.2600
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2741.2600
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

$149.95 CREATIVE 2
http://mutasofte.com




From sirrs@skadden.com Thu Jul 05 16:29:04 2007
Return-path: <sirrs@skadden.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6Xwm-0000x2-CM
	for ipfix-archive@lists.ietf.org; Thu, 05 Jul 2007 16:29:04 -0400
Received: from [66.173.114.68] (helo=uslink-66.173.114-68.uslink.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I6XwG-0004r2-SI
	for ipfix-archive@lists.ietf.org; Thu, 05 Jul 2007 16:29:04 -0400
Received: from grsy ([126.172.226.83])
	by uslink-66.173.114-68.uslink.net (8.13.2/8.13.2) with SMTP id l65KSqap016986;
	Thu, 5 Jul 2007 15:28:52 -0500
Message-ID: <468D53EB.1060500@skadden.com>
Date: Thu, 5 Jul 2007 15:26:19 -0500
From: Frederik U. Childress <sirrs@skadden.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: gunnysack remit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.5 (++)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81

Brokers Move On ERMX!

EntreMetrix Inc. (ERMX)
$0.18

Heavy trading today as ERMX announced its launch of digital support
tools for its portfolio companies. Brokers are getting ahead of this
steady climb as they grab up large blocks of shares for there clients.
Look at the numbers and get on ERMX Friday morning!

This means that the school age children there will never have summer
vacation again.
Indeed, pre-announcing new innovations can make sense to prepare
consumers to eventually buy them.

Cappelli also argues that supporters of the bill have misrepresented the
state of the country's workforce in their efforts to secure its passage.
for a project in Mexico, where for a certain legal matter the company
has been unable to get access to a court. Here's what you think.
Second is back to basics, simplicity.

A clever little ultra-light laptop just didn't meet those expectations.
"Rather than risk criminal liability . Cappelli also argues that
supporters of the bill have misrepresented the state of the country's
workforce in their efforts to secure its passage.

economy plain and simple.

For the remaining illegal immigrants employers should bear the burden of
legalizing them with the U. COUNTA tells you the number of non-blank
cells that are present in a specified range. For that reason, he's
skeptical of politicians' stated desire to reform the country's
immigration laws to protect American workers. I learned that the hard
way.

investors present their restructuring plans.
AMERICA IS A NATION OF AMERICANS.

Those who remain unemployed should be deported. All of this is a drain
on the American economy and not a contribution. Illegal alien status,
employment of illegal aliens, and assistance to either, ARE FELONIES
under federal law. The fifth is teamwork. Are people prepared to pay
more at their local diner? You are seeing the impact of globalization
rippling through manufacturing centers throughout North America and
Europe.

If a company is a dominant monopolist, it has reason to pre-announce
because it doesn't fear a competitive reaction.

"Rather than risk criminal liability .
The strategy here makes sense.

And most of our ancestors were uneducated when they got off the boat.
But if you don't understand these cultural distinctions and pressures,
you're never going to get through it. Often, middle-market European
banks "get suspicious about why you are trying to buy their loans at a
certain price. Despite being so useful, many people shy away from using
them, on the belief that they are hard to use. They are a great way to
summarize your data, and they allow you to draw attention to data trends
and patterns in a spreadsheet that might otherwise be difficult to see.

Two-thirds of illegal workers are concentrated in four industries:
farming; personal service; food preparation, hospitality and tourism;
and construction.
And most of our ancestors were uneducated when they got off the boat.

Kendall Whitehouse, senior director of IT at Wharton, notes that Apple
announced the iPhone, the company's entry into the "smart phone" market,
six months in advance.
"Somewhere in the country, there is a management team that is making a
big error or failing to execute, and that is going to create
opportunities for everyone on this panel," he said.




From TZRqR5n@typepad.com Thu Jul 05 23:17:38 2007
Return-path: <TZRqR5n@typepad.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6eKA-0002hm-4X
	for ipfix-archive@megatron.ietf.org; Thu, 05 Jul 2007 23:17:38 -0400
Received: from 74-37-7-201.dr01.brvl.mn.frontiernet.net ([74.37.7.201] helo=frontiernet.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I6eK6-0007CO-9b
	for ipfix-archive@megatron.ietf.org; Thu, 05 Jul 2007 23:17:38 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by host31026219.typepad.com (8.13.1/8.13.1) with SMTP id g0xwn0DR41.488115.m0H.aP3.1129478107475
	for <ipfix-archive@megatron.ietf.org>; Thu, 5 Jul 2007 22:16:46 +0600
Date: Thu, 5 Jul 2007 22:16:46 +0600
From: "Rudolph Thornton" <TZRqR5n@typepad.com>
MIME-Version: 1.0
To: ipfix-archive@megatron.ietf.org
Subject: drippy pimp protract__
MIME-Version: 1.0
Content-Type: text/plain;
X-Antivirus: avast! (VPS 000754-2, 07/05/2007), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

Start improving your life!

Bachelors, Masters, MBA and/or Doctorate (PhD)

NO ONE is turned down.
7 days a week.
Give us a ring..

206.8882083

You Need a Better Degree, and we can Help!
Obtain degrees from prestigious non ac Universities based on you life experience.
NO ONE is turned down.
7 days a week, 24 hours a day.

Do it now..

206.8882083

Regards,
Professor. Abraham Tate



Nasty as a hand-job in a sleazy bar, fine as a cute from the worlds most talented call-girl. "Or there was the case of his friend Gary Ruddman, who worked for the Boulder Public Library.



From trentv2fm@hotmail.com Fri Jul 06 01:26:58 2007
Return-path: <trentv2fm@hotmail.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6gLK-0004Vy-Pt; Fri, 06 Jul 2007 01:26:58 -0400
Received: from [84.54.71.97] (helo=jlpe7tfk.bpy4.comcast.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6gLJ-0003fR-UX; Fri, 06 Jul 2007 01:26:58 -0400
Message-ID: <22511788827548.844A7FD61B@WPOQKW>
From: " Ion-archive" <trentv2fm@hotmail.com >
To: <ion-archive@lists.ietf.org>
Subject: Best deals on replica watches
Date: Fri, 6 Jul 2007 10:27:31 +0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: VvsSagKZwhrFFuz8fHHqwxq4MyXxAFaG8CGt
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_00E9_A9DB1E4E.5DDAA0E9"
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a

------=_NextPart_000_00E9_A9DB1E4E.5DDAA0E9
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Get yourself a gorgeous luxury watch at a tiny fraction of the original price!
Plus, you won’t have to spend much – our prices are truly laughable!
All popular top-notch brands are always in stock and ready to be yours!
http://stflu.com
------=_NextPart_000_00E9_A9DB1E4E.5DDAA0E9
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

<html>
Get the posh watch that you really deserve – a quality replica timepiece!<br>
Don’t waste money – our prices are the lowest and we ship orders for free!<br>
<A href="http://stflu.com">Detailed replicas identical with the original brand-name chronometers here!<br></A>


<br><br><br><br><br><br><br><br>
<font color=white> what to expect--a visually-rich </font>
<font color=white>put you to sleep! We think </font>
<font color=white>Decorator is something from</font>
<font color=white>design problems, and better </font>
<font color=white>it struggling with academic</font>
<font color=white> advantage</font>
<font color=white> (and too short) to spend </font>
<font color=white>the latest research in </font>
<font color=white> to learn how those </font>
<font color=white>format designed for the way </font>
<font color=white>same problems. </font>
<font color=white>Head First book, you know</font>
<font color=white>to use them (and when </font>
<font color=white>the patterns that </font>
<font color=white>to use them (and when </font>
<font color=white>Best of all, in a way that won't </font>
<font color=white> and why everything </font>
<font color=white>who've faced the </font>
<font color=white> In their native </font>
<font color=white>design problems </font>
<font color=white>better at solving software </font>
<font color=white>environment. In other </font>
<font color=white>you have. You know</font>
<font color=white> the same software </font>
<font color=white>In a way that makes you </font>
<font color=white>NOT to use them). </font>
<font color=white>of Design Patterns so </font>
<font color=white>or on the real relationship </font>
<font color=white> someone struggles</font>
<font color=white> You want to learn the </font>
<font color=white>In a way that lets you put </font>
<font color=white>your brain works. Using </font>
<font color=white>when to use them, how </font>
<font color=white>who've faced the </font>
<font color=white> Facade, Proxy, and Factory</font>
<font color=white> and Adapter. With Head First</font>
</html>

------=_NextPart_000_00E9_A9DB1E4E.5DDAA0E9--




From chris@wetterwater.com Fri Jul 06 05:27:58 2007
Return-path: <chris@wetterwater.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6k6Y-0004Eb-JF; Fri, 06 Jul 2007 05:27:58 -0400
Received: from [211.255.222.241] (helo=[211.255.222.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6k6U-0005P7-04; Fri, 06 Jul 2007 05:27:58 -0400
Received: from [211.255.222.241] by smtp.secureserver.net; Fri, 6 Jul 2007 09:27:52 -0900
Message-ID: <01c7bfaf$ed3f9e60$f1deffd3@chris>
From: "Sam Cantu" <chris@wetterwater.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Adobe Photoshop CS3 our price: US $ 89.95 You save - US $ 909.05
Date: Fri, 6 Jul 2007 09:27:52 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

Autodesk Autocad US $ 129.95
http://muhohosoftb.com




From dpfbesmirch@netscape.com Fri Jul 06 11:36:32 2007
Return-path: <dpfbesmirch@netscape.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6prE-0006J2-CV
	for ipfix-archive@lists.ietf.org; Fri, 06 Jul 2007 11:36:32 -0400
Received: from [201.53.119.212] (helo=clemente.rjo.virtua.com.br)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I6prD-0005CR-1n
	for ipfix-archive@lists.ietf.org; Fri, 06 Jul 2007 11:36:32 -0400
Message-ID: <001c01c7bfca$48396b10$06ac19fc@clemente>
From: "Anita Ervin" <dpfbesmirch@netscape.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fw: Thank you, we accepted your loan request
Date: Fri, 6 Jul 2007 12:34:40 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0019_01C7BFCA.48396B10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2720.2962
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

------=_NextPart_000_0019_01C7BFCA.48396B10
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Your your credit report doesn't matter to us!

If you OWN real estate and want IMMEDIATE money to spend ANY way you =
like, or simply want to LOWER your monthly payments by a third or more, =
here is the deal we can offer you THIS EVENING (hurry, this offer will =
expire TODAY):

$290,000+ debt

AND EVEN MORE: After further review, our lenders have set the lowest =
payments!

Hurry, when best deal is gone, it is gone. Simply fill in this simple =
form... 

Do not worry about approval, your credit history will not disqualify =
you!

http://healnutss.com/
------=_NextPart_000_0019_01C7BFCA.48396B10
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
iso-8859-1">
<META content=3D"MSHTML 6.00.2720.2969" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit score does =
not matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If your family OWN real =
estate and want IMMEDIATE cash to spend ANY way you like, or simply wish =
to LOWER your payments by a third or more, here is best deal we can =
offer you NOW (hurry, this lot will expire THIS NIGHT):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$284,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have established the lowest monthly =
payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when best deal =
is gone, it is gone. Simply complete this simplified form... =
</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Do not worry about =
approval, your your credit report will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://healnutss.com/">http://healnutss.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0019_01C7BFCA.48396B10--



From mholyrood@3klicks.de Fri Jul 06 12:54:29 2007
Return-path: <mholyrood@3klicks.de>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6r4f-0002bx-2I
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 12:54:29 -0400
Received: from [190.40.195.133] (helo=3klicks.de)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I6r4e-0003it-94
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 12:54:28 -0400
Message-ID: <001501c7bfc4$674ccc50$05ecfcbc@pc09>
From: "Weight loss" <mholyrood@3klicks.de>
To: "ipfix-archive" <ipfix-archive@megatron.ietf.org>
Subject: Increased metabolism and calorie expenditure
Date: Fri, 6 Jul 2007 11:49:40 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0012_01C7BFC4.674CCC50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express %OE_VERSION%OE_SUBVERSION
X-MimeOLE: Produced By Microsoft MimeOLE V%OE_VERSION%OE_SUBVERSION
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 25620135586de10c627e3628c432b04a

------=_NextPart_000_0012_01C7BFC4.674CCC50
Content-Type: text/plain;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable



A Diet Pill that Really Works!It&rsquo;s called Hoodia Gordonii. It is a =
simple appetite suppressant that has been used for hundreds of years and =
we&rsquo;ve got it here just for you.Lose weight FAST - click here!

-------------------------------------------------------------------

-------------------------------------------------------------------



Collection 2007 

 Luxury Replica Watches

ON SALE NOW, Save on SWISS WATCHES such as Rolex, Omega, Breitling, Chanel and More.

Enjoy FREE INTERNATIONAL SHIPPING on any Swiss Luxury Watch, Hundreds of Luxury models in stock..



http://www.1133watches.info/
------=_NextPart_000_0012_01C7BFC4.674CCC50
Content-Type: text/html;
        charset="windows-1251"
Content-Transfer-Encoding: quoted-printable



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1251">
<META content=3D"MSHTML %OE_VERSION%OE_SUBVERSION" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<font size=3D"3" face=3D"Times New Roman"><p align=3D"center"><font face=
=3D"Tahoma" color=3D"#ff0000" size=3D"5"><strong>A Diet Pill that Really =
Works!</strong></font></p>
<p align=3D"center"><font face=3D"Tahoma">It&rsquo;s called Hoodia =
Gordonii. It is a simple appetite suppressant <br />that has been used =
for hundreds of years and we&rsquo;ve got it here just for =
you.</font></p>
<p align=3D"center"><font face=3D"Tahoma" size=3D"4"><strong><a href=3D=
"http://eprisveigthisyo.com/">Lose weight FAST - click =
here!</a></strong></font></p></font>
</BODY></HTML>


-------------------------------------------------------------------

-------------------------------------------------------------------



Collection 2007 

 Luxury Replica Watches

ON SALE NOW, Save on SWISS WATCHES such as Rolex, Omega, Breitling, Chanel and More.

Enjoy FREE INTERNATIONAL SHIPPING on any Swiss Luxury Watch, Hundreds of Luxury models in stock..



http://www.1133watches.info/
------=_NextPart_000_0012_01C7BFC4.674CCC50--



From gudrun.gimaker@alamocitycards.com Fri Jul 06 16:23:15 2007
Return-path: <gudrun.gimaker@alamocitycards.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I6uKh-0001pl-BW
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 16:23:15 -0400
Received: from [41.251.85.6] (helo=[41.251.85.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I6uKb-0003xz-Vf
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 16:23:15 -0400
Received: from [41.251.85.6] by mx5.biz.mail.yahoo.com; Sat, 7 Jul 2007 20:22:46 +0000
Message-ID: <01c7c0d4$94d03020$0655fb29@gudrun.gimaker>
From: "Viola Strickland" <gudrun.gimaker@alamocitycards.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: A larger load of cum means more intense orgasms and also the probability of becoming multi-orgasmic. Wondercum consist of two sets of herbs, one set helps testes to product more sperms.
Date: Sat, 7 Jul 2007 20:22:46 +0000
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

Fast, effective results including, above all, a greater volume of ejaculate. We’ve helped thousands of men achieve the sexual health and satisfaction.
http://httpol.com




From mlee@ystoreuk.com Fri Jul 06 23:05:35 2007
Return-path: <mlee@ystoreuk.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I70c3-0003xs-LV
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 23:05:35 -0400
Received: from [121.1.95.31] (helo=[121.1.95.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I70bo-0006Wj-4F
	for ipfix-archive@megatron.ietf.org; Fri, 06 Jul 2007 23:05:35 -0400
Received: from [121.1.95.31] by smtp.secureserver.net; Sat, 7 Jul 2007 03:05:20 -0900
Message-ID: <01c7c043$a70fa270$1f5f0179@mlee>
From: "Lawanda Shirley" <mlee@ystoreuk.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: ADOBE PHOTOSHOP CS3 EXTENDED US $ 89.95 Retail price US $ 999.00 you save: $909
Date: Sat, 7 Jul 2007 03:05:20 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.1830
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

$79 Adobe Acrobat 8 Pro
http://kaloeme.com




From sjrj@siigroup.com Sat Jul 07 06:09:40 2007
Return-path: <sjrj@siigroup.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I77ES-0003Fp-Ov
	for ipfix-archive@lists.ietf.org; Sat, 07 Jul 2007 06:09:40 -0400
Received: from 20-68.126-70.tampabay.res.rr.com ([70.126.68.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I77EI-0003Zf-KP
	for ipfix-archive@lists.ietf.org; Sat, 07 Jul 2007 06:09:40 -0400
Received: from kteb ([96.191.145.231]) by 20-68.126-70.tampabay.res.rr.com with Microsoft SMTPSVC(5.0.2195.5329); Sat, 7 Jul 2007 06:09:26 -0400
Message-ID: <468F6656.3040304@siigroup.com>
Date: Sat, 7 Jul 2007 06:09:26 -0400
From: Adrian I. Goldstein <sjrj@siigroup.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Re: Info-bdad7.pdf
Content-Type: multipart/mixed;
 boundary="------------000705060402040706050604"
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 7cb76adb986247703cbb5582da68b5fc

--------------000705060402040706050604
Content-Type: text/plain; charset=windows-1250; format=flowed
Content-Transfer-Encoding: 7bit



--------------000705060402040706050604
Content-Type: application/pdf;
 name="Info-bdad7.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="Info-bdad7.pdf"

JVBERi0xLjMgCjEgMCBvYmoKPDwKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL0NhdGFsb2cK
L1BhZ2VzIDMgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9QYWdlcwovS2lkcyBbIDQg
MCBSIF0KL0NvdW50IDEKPj4KZW5kb2JqCjQgMCBvYmoKPDwKL1R5cGUgL1BhZ2UKL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzIDw8Ci9Gb250IDw8IC9GMCA4IDAgUiA+PgovWE9iamVjdCA8PCAvSW0w
IDkgMCBSID4+Ci9Qcm9jU2V0IDcgMCBSID4+Ci9NZWRpYUJveCBbMCAwIDM0MiAyODZdCi9Dcm9w
Qm94IFswIDAgMzQyIDI4Nl0KL0NvbnRlbnRzIDUgMCBSCi9UaHVtYiAxMiAwIFIKPj4KZW5kb2Jq
CjUgMCBvYmoKPDwKL0xlbmd0aCA2IDAgUgo+PgpzdHJlYW0KcQozNDIgMCAwIDI4NiAwIDAgY20K
L0ltMCBEbwpRCmVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagozMQplbmRvYmoKNyAwIG9iagpbIC9Q
REYgL1RleHQgL0ltYWdlSSBdCmVuZG9iago4IDAgb2JqCjw8Ci9UeXBlIC9Gb250Ci9TdWJ0eXBl
IC9UeXBlMQovTmFtZSAvRjAKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9NYWNSb21h
bkVuY29kaW5nCj4+CmVuZG9iago5IDAgb2JqCjw8Ci9UeXBlIC9YT2JqZWN0Ci9TdWJ0eXBlIC9J
bWFnZQovTmFtZSAvSW0wCi9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDM0MgovSGVpZ2h0
IDI4NgovQ29sb3JTcGFjZSAxMSAwIFIKL0JpdHNQZXJDb21wb25lbnQgOAovTGVuZ3RoIDEwIDAg
Ugo+PgpzdHJlYW0KgAAgUDgkFg0HhEJhULhkNh0PiERiUTikVi0XjEZjUbjkdj0fkEhkUjkklk0n
lEplUrlktl0vmExmUzmk1m03nE5nU7nk9n0/oFBoVDolFo1HpFJkxPJ8EOSvOQEJyrAkEVZPHIfR
oARtdgQiOEFRDGgh3O8CVbvMCAgaAqsEAlvpVKtaAu1ziTtvUCR6ngSCOy5L8UCN+gZgdpyOUCJx
OgS1sMCB1ar1ceEFCAQACzsiAd8DL+DttsgmhhQfMACgSYAmikJwLuZgWcgbUO4+0NqMELuLtnK9
z0C3Bfz4Au8yrUERuXgeyihwWumAAEvYAD4f627ACCTEUOQPgVMAGIgVQtFy8I5r2VgexAAQwbGX
sDbY+glrguQ06P7AAA7AAAXICMWB7fMOvSnqixyDvUg5ssi97ROAABqG2h7QvQg7/js7SBQK3amO
1BKpKoWpanqdKrvUraDtizQALG+cKPqajDtIg0MKqvS9A+/jdw2MBcoVBCBRIx56gAq7lRYgTYIQ
PkKvsgQwPwgYCFq0DegBHb+ouuKBMKADxS2xbGCcuQ4C+rCuSYgRsrAzLMkQgY+PQ4iCkBISEx4/
hTgEA87neuMyvDEKGTUg7luazQITmABej4hz9Okg4PsNO7pqqB7CzGxCnlegx6wghE3sjORZ0fOs
LIFTCDnS1yBOq6zDAAtSEPE8hXlet8v1EgrK0Ug5ZxkAkLGowdbIE44AVeL6qupWSLyDAdYqZMa4
KmAD9RSJ8uoERoI1LFyBvk0tYONG6Dx3PgP0jKdpzA31roSOEkIM9iwPcgUYuChTgjhUaCWitEOu
+CJ22sJ9PINK6FK9N4ARczV+NBc64YC6iBnbbyEYOgeFMSp7psdhtfq7NqCOcgZ3xrVji2WAiwxz
jMuIq4gwOK77eMaqsTlqVd7q6OUHoIM9HWUpr73ThkdN9jcsVZm8isWdowWshMv6CgZG6HCAIDOh
y7LtPSDYHJLXUFAcP4SU7EoGxuHK3h6wzjoyyaQhNl1Y9EeIValCqZtoAV0AG4IMrN6RegcJvDoF
aw6u7IWauWzIgVbXayglrwTx0r4DNlvgjlPFUfpdWoO00vr0EU6M/m8RPAhZVwWgrJ62rdwoFfSF
2TdCD8ygZc3dx7d2pTmkoI8yEso9fRXzOKBXLvOlujsoRdYg4wLl48xYX5SCi/x0HdZiQv1RvAAU
o4530m0WMoqa/h97zUQt9kXCqpw8WPZB/d34IApoq3LirSoQY/SVh2juIGCIqofIBkCQEQx75BEU
u3dCABohDHLmjdQxZ65A4HpBAAYpArZVCEGgqt9k5Ahtv9TixYgsBS4NQINB8gxaSBwkXkoZt0Bl
7KJdE7p6BAnGBPfFDIuy7g4LNLwQ9frexEAaABDZAL8kOp7hOkVE5kXEQqOWqV0hBVrvzgoaKKJX
3WDZeEcUgTaYsvdISicgZWRHibhUcwhylFlI3VeQMDUCoOnjM+38U54mQKfSshlkybnWGyaNEQuz
yImkjC/GeBb2GzlphEQdkBiVQEtYBHoBsH4GFWLUgIxUQV5kFfyQKFJFCmQbg4QOUMeiDQONFJsO
THiLCbhWk13ck5hTDmJMWY0x5kTJmVMspMDyMLcJgMAZoDx4GtOlH8BsxoqNMfpMwngfI2EXV8TI
OjsWogAA0L8hUmkhSpYRJIjBrYXv/ljDBMAcjQqwHdJggytnjIGINBOMQOSJwAIOpsmsdUWO5JLK
UjLJSYgPDoQOapoGjkFgdG1nCGWEwCAIKKHx0XkS+ZOf0L8YXGLvU8GYgQaDmGtIHJaQLODpxvPP
HGexmHSUpIyLV4UG3es6as1c6YoldtwSuPV6oOQUCPhUrM4rKnfUqIlNty7pyHOGABUogVTCVDtD
WQMcUeJbFfGzKyK83SEStRRV2pxBRT1pC/FIgY3R1EGHgOIgQ8IgvppyHyXEBIRMGoBLEXMb4DkL
DA+J9NdCMxUsBLJAKmpVFNiMQVbIAF6opAdQQ65XlLNnIIBpu4AK7VpIKBGaxBB3TZTcW+WS02dJ
iqIeVQjJZXknhkhRsBAg5MtILNts7UmBWoSsgsJxoklSLdGQQBo9GyuxDO7RY5CYGPxqvOG2a86P
lRcKY0L7nzlGoHeYMzMlXz2mHUNcggDx+jUumQmP5BX4sreKW9qttCC3eu/eGCttSvU0Pe4oXs2a
7EIvjCO4AiGjw2vrLa7byJW3fVZeIkYuWCj9NrX20cCnrgijU8O/c5iDByFEVJw0oblnWZQKt0gT
hqBwCaDcw4YBThyw0QMCOHIa4gjXRp7Rb0wuNt9ie5FOT2JJRefAgeM8akOijICKdZ5zwyZ1IWol
h0zNwxU8g5IjT+4uNAY7GRCB+x4XMQO1tZo2qUUGptWllyBYnTMSoeg3T7m+veQiSsl7hPBkVCCN
hUnCsWTWQSuJBBSiWIMOo3duyGz7K/A1xyyTFMfkkAST9WnDre0TgM2qo0qXGIPFGKVkFIvhlPb7
HkRlBKg0JckdNbT0xeVoe/RYObgQxoAU410lpt0ZcfJx5Cgkiu0JPjGGJ5CEzXn3PwgkZK1AAqNh
SMU8MkhOFwQYemNDxodDNrsg2wHWU+nOrV7et4BHl0CoVJebSBgoA2QYa+pHUZRgWlgQFjFM7XSS
0Dat37k6Yq7L9Wprt5PZRFSyveJDQ0yeCWw6WxkwbqKpwEns+TBzYw+VanK14cUCq2OkgpyY/WO1
CQPRxFnrgEsBjWVDsWExt3asyxnJrQ0tFKQfA5CKxsVz7GiKaGdIJbaTLFnLs24azc1QQgfOQABo
52QfR3RSF2t46QKwJDYcRNvqQhtaYxVsh0IQ4uIBANCIDQSzN54+j78IKdBJSYz2dp3iBsJwtbXE
JDOGevhzOH7kfAzeCNs79EGMbsjw9TyBd2JpKub3kfJE7zhPDyfl/MeZ815vzkwx4APKrHoDXKPO
+l9N43tRAt5ILzuL/eukO+mXorTGKU6fT+3mZqNvdIM6d26kCggWMQG7eythocTYMd7n9H7j5kyA
fhOO0zgL4tcqHTiiF/qQAAUa6Qhevb4AL3ECEJXxQnQfm/nmED/9QTjdM4fEK/E/aE5ilFKCjRhA
tuoB1HQDvuaf0P/i8Augzv1P1vdDHhsv4Dph1ANPsNtvgg4LnsngAB+sckPKbQAQMChGAD3gfgAP
1o2LygvqzldP4BfmjvVoaPXEpteu/QMwXCimhrNCwwBwPBEvvrFs5wSKQH0u1uEiBPhl3wXwhCjg
wBBCCQNwPP1Qgn0vqQSQEiIB2sSQhwpicgCF0oMwqQswtQtwuQuwvQvwwQwwxQxwyQywzQzw0Q0w
1Q1w2Q2w3Q3w4Q4w5Q5w6Q6w7Q7w8Q8w9Q9w+Q+w/Q/xAQqGfh3oehXszwHEmhqEuqmgYIWOagAB
yhcAxMgEOqPwSCIg7GxRAvOC6jSB6ofuunCOUg4EpAcxTCBBIBdCFA4BqByiBgYtkLyjypPwFvsO
dtmAAA7ADi/wjFlB3tZxQB3pERNiksbCCADjVAABHunAAA+GyGBJPgAB4RXEmiwxFRTqmmsCwxSC
BBoxJwJQRHBxohELag7A7CBE/mPjSBcksRPmNRou4xSGWxTPgAABICzjjQijuxiCWF5g7RehrlvC
7Jwn0nkRRRID7GARFAARTiERzIMDIxWirPomgKPt/QVi/xziBBcR6i7umCGgfEIAPyGhHxGizEpy
NR+CVM5RjC/xdk8Flx3LfRoh4OdtlR5RmJ+hAR9RqiCAxPnrdgvh0vqgcgHAHIjFEEtyUgBDtAcj
SC3MLNFRqLNAfBqKCRTBHq3yVCXSjlWHxB2yUyYJXIflWnCB4NtyQwkCDR7jDwjQYiBxIwPPFHLi
qjrjamoGFCBhBRkAwGOE8uSCExDCBy0iwyRyGytiXRTAnj0RcRdCBhSunInuRlakyhXhDiBBytlC
DySjajPyHpaGWhowOiCh3hgTOKumkmfmNSwiDTJCCyDhSxXGAScTECXj+SRjSpJR/y+TUG9RPzAR
xCBB+hyypiCzDx7hth3ydpaEIBcRvTRjxhBBBAtOnjsAHMYS8NbgASmR1CExCCBzBByhxTCTazbS
tExMYoaCdTnAfhEmgTpCBysiDzVCCg7ABSAupiEE0zwJPyzzZDIzcTyiUTpwAETyZAnkDFdDmMYy
1UBUHUH0IUIijmx0JQ7GYonGl0Kw4SiiHzICIBXs0TMxWTDUNPOswAwRnCGy7CDJOiCSAiDBczgT
Xx4BcUaq9DrSrgcyShIDyhsmoMk0SpJ0VgANPiFSsj+RmETSMDJLUG9CCwECBBDjL0ajhSqxmTOA
bgXQdgvmOUgi8KYCCDUEjh0gNBcj/zpTqRlD+zryvOnyciGl9HCThyNzMkpLnNugXNqRH0vCjhX0
fILDjRfgAAGopUziBTTCBUAzNDxteiHB6jYmWldUpQHBcBy07AABMEHpsh6BI0+Jigxs6SFiuUxU
L0yE9T4AAAYK30OFWPLDUiFRfpx0oCDVKmWgCDug5QILoVPVP0/GoGcDsUUFmB6rXD/iBzTT5S7n
Dv7m8nhpgiC0qFfBMA7S31eC5g7R9gAU8AxlWBEDBy7GcNZgGqLiOllyPxZzHttzNBsg5TWVrCkG
TqGHyk5kJg4z8iXBBBTgcu8pXHHODV3pjKpWAQ8CwWBw8GThgWDWFCFyshN00iIPEk7O4WFi5qGC
OngGNi+Tzr9g5BcrSh2jinDETIf2KCevEkziPqyoylnL8EDVkvEEFr+CCG4GeU92SiaIenZkSl6i
JK5npAADbzvGYlRloEdiEUwAnM0VGCrPFWbicyWioEjKICsFvBGhgA5HsDnCxiGmxE7DenKjtjAj
QtkJVuRWnCbkxmQx4DSnxFgDLnn2BHpllnqt+nsgBR/jWCBqECCoe2zidGqmr2wI5OCrUlVjS1yC
DROotNziDD+CBVjLJpON7W/CZPDPFiCnMyk1AGINQCFHXi2x2DIlnW+D+k/KNI3AAHjvIXKCZIIu
CHfnaWeExD+mTmUCEjbJ8xVmLGa3WCjNpCESDjpmfCLqDXe3jXj3kXk3lXl3mXm3nXn3oXo3pXp3
qXq3rXr3sXs3tXt3uXu3vXvikq7L2VGLpPkB4LqmsOvikNns/iMO5CIu8O9D7kqEDL4QWmopKuIQ
4O0gnPspaQgNvjtMzvjkwLVvGvaoFI1XGHgXgMULwSoiEP6u8CIMdi3uHq6L5iOrwiIX/MYCBAbs
8NvsbiBYCPBw6GsvsCBBLKCQIL1N63yLUkyjTPlwfnWB3l3OuiHWZVh3XwEQdiB3/EKHP36CBgfv
x38DXYaCGDvmECFqtIUgnqciBNFkmrXL1oZPwtfQ6xRO0YpudhLMyNup1QDCBgzkavZlKPlgRN9W
J1YITqtSky6CCvHPtVmCBvXiBgzBtv+pqUwEYPSCF3LXYDQDIy8iEhEHaYwMY4xPXxcPgwpQ4Pp4
fC3wGA0SOSGEarnrTtvh2szhqAf0bq/OTp0OsCJLuHaOmICxZJE4gREQfroOV1GMzwPKxpzWVCEv
CuZJJH7trB6t7HgSOANvuZNOqiCXzw7MBRxHMupP6nCu9M7sawos9kwKyE5vRvbCIl5in4HDHP2P
vz+I/VyV+ZoPv5pX7ErYpJ+r7lYorlruygnToUn21vUvtX4iBBup1GNZIQ4SgxLZw4UgAO8PhIIP
dMcMNjpjRM+4aMQCGpCnNI2G4P1T3Ir3RkikMvVzNBukhEqMb5ZkKMeFDjBsrMSHNky54CDh3u4Y
uuo4JYqwJQ6vnjDryoaC4pLP6PgPhZYXxxcYjKyIzYECG3LFrioA4HFaYkpo2QnlWO1qu5M1d5G5
zK96QCEYbn0nHXXEppJRCaiOFPpaaACabP6ycue6YQP3JiFv8wlq8C5JK4lG/D0Frgnh3y1QlHiD
taKkirHZm4PAAAbhfxn4yreiGaGF+n529zSYIXt5biGISlC1Mj27BIY6Z5JjQamCGwKCF5rrHOXJ
cCGgn1s3wRi6ziLgIqh7Q7T7UbUpha/CMMfTXCP3gigvn42iCQTChhqTlR4iQPvaQiNW8CdYMgCS
CCGbHiHvqCQ7Fi0NVZ0iEa6iFbYifCzXDLfPqiKZECZTlbRiNPXLdr3vYiEYaJRutHL033ExeiHQ
QtNCIbuXJhqIw0YF3TDiHgIACm3v2nk21uMj7STiBzPiKhRK7iG6OZOiPST7cCHtRwcCEvf3/6CD
xztN74Dsp4pqnV9pbcD8EK0wdCF4QCFgI2lIavqhHvgLkgv1Lz9DI7nHwWbCbV9kKCzizbcC2DuS
ewk66tR5VxxQSzHvtiCayCBr3zoXzj4DRZrs13b8YR8SdjuC3mAAITR6joZQmx4aAZMVdYQ4yCD8
iMGPGusSqiCcXDbCzCz7c1MOavoDSmoboQju94AwoiBYjK9txcujaziGWuB2gcY3MGvcVakChRrr
khqEpA7kLTloRqzwkQlCptHjiyLCDP6CC4xL9uGaPiBLz8i5AWZgv9BcYFVwi9DpgQkmCJBEi4fh
RZ8gAZmuFCE5jsmJ0PSS09ADhdOkp7ziDcVMBdHCEYwbak9RjAzDLgf858JTMAfdY0AiB7+SMiCg
u7635igy1cLCBb+cZDtEHmAD3c+uDiDhfoYQI6X5PkPb3EX39CCcvlWAfdqDPx9drmIkXwlOrTg6
liBZhCC7eCDYjtQOg0QTYxq9zjTd1CE8n9n9tiE5LiB9v4XjEbMM+GjyazMvEDQ90to0MknCjVKz
QKTGW7pDikAGU9neCTX4fiC1F4XrfMcu/cP9LKc9o9A9p8yMRQZCBACwO6j3MR4QTAnOp6BA4Vdi
Dr4KKEa8iFQTBSEQkTcdN+XxV76eakF94qYtka+bWP9+BEX05RqSQrNc7lYdCda1qbq9RCgUpTmI
uHaBS0eI2jSQY0G9RqA8qPft5iB8OkpjDK8gz0b73CE+IPggncXAABxOd+ujjRzy3kna6oCIQbmC
NVJeHmWxWSGEF/ACIaJbaM58AvVe435MD+n8hgIak0pOpwke+tFe0JjzZ9zn05QkKbskirxPnn5y
hyQO9+Tc35Pvx6piFSrdpVUx79hjmgfgxRviYTYhxQkfdc8COQnYgedjHeE7tCE/imAcTw9+BiJ9
kIm/r7VThQKiIxuJhfvftZGiJRI1LJJ/yfp/tf0/1f1/2f2/3f3/4f4/5f5/6f6/7f7/8Xlyupjs
V9H17iAACBQOCQWDQeEQmFQuGQ2HQ+IRGFu90xIANQPxaNQVBR0tJsYI8PxmNyWTSeCgIwSiWS2X
S+GB8czCaS6OwJHo+azuaII7TygUGDHBqQVHjCGUSNLUv0KnQcDz8AHZgTmdQMnLVaquSnAul9sq
+xTxEL+CVScTKCVsnmB2u07HZBAeCDlAXeJHA4U8cjknk6hXqC32k3uLX+FtcPqWCnwCPXIQhDvD
GQK9D5qTOnOkNQKbgBG1e1RdawmVYuBXdALmBZEuhAAWKxP1ywO9UoAX0UUeBNt356pQVavUABrW
Z8ATmBg7AQO2wK5QIwSQnoCB8PIYaDuVxQWZYSET45dqDpiOoItcmrjkHaSBc+DqU49Xr5DiQnuD
7BADRwo7PGRqSIO87vPYJyioQA4BII+iGLGgRxB8y0EKCdL7l+ugAJ8nCRPYJ6EOiADFFKyq8QsA
DIggahsoEV5DoLCL+M0HKdEgO6BD46yDEA356gaAEMIGtCBw8gStoEt7oAFEcSx0hbJlwcqixi3L
NISQRGtARpTx4gYNLNDSfGAtIAAdD4ASOty4EEAEloEUsPrxFD7oOyaCsw76cBhGyBkA4KFAPNiC
OUhcQoHOEnIQsKBngXEIO6oQwD4gQGoqADzIELUsoWU52oIlSBL8AC8OHFCvRaV6BHgcpcVai7DM
I3aBDvCiCQDSTH0qgbkIGtUDvelapz+505ITB6BVcADcINWh3kApoP02D9gx8gRcvNQRGqQkaBV+
AkzrhQ1Ququ4CWNVKCSigSMUGpCLt+hjOILTSGU6+MrIO16BwfZKgwDa1LA0YzPUFQiDFXM7oWC1
D6NXOb7gg0sH0aAFk3Y8E9oQRtbj41iBmNDLvJk9s0KaAC3YUgsGoQWsWUZR2K0go13G3VJawRjc
cY8BuBQzDdCPY9wALbJKCNQhmWoLZMYu+8E+XjOmCIZhCEaOg7IoFRYAH6eCnWigRT2pH7oI7Ya1
tLk63pIMBrgBElRusxz7nqvawRbF5S5gcsJMzUKroNbjQFOggGkRXafC0nSRPe5uhzVe6E1PfcX4
rmDBs0SAbgAURRIFwMtoFE6yqi6D0uSjNRTRhGFpntk33wgvJIHO3K73ULNN4hgwXggfSIWrSCHb
kdgoQeu0AAr9UKelkDqY6Xhdggi7xzSaBNeWpRVSV5+2RmE8PB5ciAcMFQISx6Ctl7iEL6HIUR+G
4XIEAmTZzk/qoMjzQv4klfi/1Zy3yPEeKPVfRsV0KsWSZhIj7h6EKX+QU4ygXwwTgmGBRJFhqONg
oQ81aJyNBwbGJFdBGmgPRJMitu7lVWm1g3C2FxEh2gPJMlKF8NYbQ3hxDkiQYGQkRa4v2HUQYhRD
hqHYTABHjgADG50iR6G/xEIO2GKEU4qRVIE/UlpjoXBPhMQQCBsHli5C+F+DUViGRiI2OlS0E2iw
5BygIlixYhgiPIv500ZiIBabMQYbK5nlhggELmJIBI/Q4HqOlhEcGNgRi9F8L5nT3goFLCw6UFya
x9IYE9aKmyBARGzHQLpAgISPILJOMclTVHXjHIQhDBobymZMQ4t8syBiPE2FoQQmCsBOHg+oX47o
XxylPDpUpBosLKlCAACAZzBo3IEKt3hBh0yrkK2qJ5BkDj9DkQIX4eJsCrkKkRAUx5RRgNSjpWgA
JoTnABFohTwirElCdOCJBdZNkIi/MtwzcFZoIHfBZOUSA4KWlYABosriCq/DkAQY03SBinDtGUnZ
qhAKTFrQOYcNqCkFmOPBl0XyBBfFmMYXqTgfSxINRekK5gCKeoMgKW0eojsmCdNsAguZfgiIIE5x
tFx6v+IHORZU5gAUjIEO8otJzpLBLvNEg0bTky3KlGSnk2yEU8MBQWn7nkssbY212OhsKQUjpLUg
AFSnpI6pVMOlqSI4HQpmYCmpBxcuNCdIRtD/o3ycdjUSoyPFaz/ekvB50NqeEHi4rZTcdJlRgEQw
NdcziD0VMsRUL8hJaH8KuI8YBcaQmAHhVYgo7zmzzSMnQHNfGs06IHKMgVJSLzOqAn2SxA42gfs2
mMO0aLDkHHbU5NBw5EIffrItl1raUKzgVKh6aaDDWXSRS6WpV7dgAjIQcEVLrezgTQfexMfKdL6t
cAC2BAxqUooDEmF1vXY0ofqMCsBhplkDF6/dHaOpBAAmnU+lxVlNjtXNewgjKAAW9o2F9hNQUx2t
scLO8j1Z01pIRRug5OhGx3ISfCnc4Whmaq9aqkAABEYOIGNu2VTmOuhZNRtDkVz04AIOMZcF2qsx
+DhcmK6Y5P2NIFiMgmJsB1MvtC6qB1zyNfS1asr05mBEJkBOwAlz4/NFngVcU6bH52IYSHIV4chV
wakO1SK9qslxgyaACsxmAv2CIRRnKhGaEZaINl5+RpZD1cqFmUg2aUEZPoCdqQlba3TxyuQcfqZz
4ZcnUc2lUxqvSesZjxPs0c1zsjwS22achAUCIHQVJNuBHuDQ1HsMGCYbaNABp5T1uCGDtgEvuhZz
Z6zqi5W8g8+qSEDDurTHBFgBKBT+E6GTQ0zr2y7M/DlQcP4LqGQWkofCi4RzZpd8Nl7MEIAEXKXU
eNrZTukSeu+nI8CnCfuVJFVg5USIEA4kkWMd7UipdDeEG6F7z3tvci1+98PL0Vvvf2/7aDvj9RmF
wjZGYMIjU0muBOAcN4bqgoRw71ZJNtHUhscop4hI3wSt3Dt4Gv40QfStg3w6zsUQST0O9Xk8DlaI
izsoP8TIcATl3HiCgEGuHwVcsRc805rnMAlpiHDbuOQoVZXK00Vj9NPeREA5AP1cQroSKLhxdmRP
khVs5zzuJfwwhUXJydEeRGAL8+y77musKuQCTjHUXjXzYkwIrWEE5HKwB4EdyblQ+O2q3QX124E3
mPi+5ed1LnOO+vOvQRdF0rwIgXd9ibleIK+P1Bcbsaa6Q0J/SCCqkoxr0iPeuvEJjeAATeHwAbvp
Bj6fnmym5s4xKsiPNO76icd3yEe8wG9yIJzqo5K+aAAAip70Rb9+kFzubknPp6hbOgvyOinAj9kF
94CJc3vp16pm38ND/aO+Py0ZxbZXByFCAwTP+gCo/HeXIEl/3drACB899mgMHParDt1MywOGYbv+
nk6k+vklGseF6VG/ygsKGpQF+/etY/k84/qIEDkkY7Q9G3mHc7mFqY8lOd2+0oM1K/y5uryQ+ziI
OseZU6Qn+4wIMA0mA95AwnUZNA2+CZU1EQeruIW+aIIvKaHBOJXBSmHBWAA94AAFyEA8KIK6eIYt
64kZMUIq8qsDgqIvIks+yIIvypC17BcpCXg7spc7Q33CBCDAYUmqBAe6e7wPfA+6E/2nUZIIW5DA
LCu9gtq7LBXAW1SerDIY8QYXA3Q84ITBwpCkhDgusKaye5uZM7KAAHdAWRZAbCq2SIM2OnU3EFXD
a3ctYpAlIILCMwkIGjGuTCEna6QyfBk3I3uoXE+II7lCE+wN+56AA6e6iIO3q1SXM+SIWgKvoR08
27S2mIMjGEQERDBCC5werCotseITU+OIK6qmuIM5C7PF460IGEu2GlPGCIO5yIHF8ISy41iu46ou
mIIGA6JACsQ6OljB8pRAs06ba7SZOY9CQ7gIIGyNYHe9e5WIQLE781S5kuxChCi9nEQn2IPHuzm2
GgnF4IKDowWHgXNB+mAIHHrE8n+uA6k3DH8JNG4fkljGEIHFYXhIqxZHmJc6nJIJ27uEaDpGtFSS
/As7mitJTJW7o9Az3HzJPJxJiDpJyIi45J5J+igHaDXKAIW8W/jKJKQhbDeIGHUGvEMiGk1KSirB
lKkI0DBD8iqC+O1C9KrK6JrHYIXKoJadAjwvYkQI0AagawHKEIIHg/IJg4FEkfCQODhLUqW74DMI
EDOHgAeqtE/I8IE7lCyJfK4KDMAIVA2IYey78p5K0iS7BBwBQA3LoIHKdEMDMGoDPL3E9FSIRCK9
+flDMIU6CqxMcwQIiV+ILKeKBMKg2GoMMG6HU8Ma4Qga6yyuscNEXMCp1EcII9o2G71IUeK7eIaA
2BzNfLSG6IhJ9F+7VAeQcy8OaC+UszE9KIODQFKBQNyKLLSqXNWVVJYxFDqtY+smfEKWDHkIOAIh
Gt6+S3LOsIRMkIMHVJuIRGFEXJhAbGnD2hdOxOyA2UpLVKcbSAeH7MyABLdCuxFIJHaIIzY9o2+6
lMc6Q3KyQIMbfMmABO7KbKfQNM08yvOx6n3FXAZKwIQ8IFW74qst6DgbRNa/bQYwKFrOTNkkAgFQ
+AiHgKLGAOLIi7k5xDi/rEgme85H4CcKaSO2IITP9PkIEHpOVLuXXRxR1EI/bR9JhFm6g1KIG6O+
+W7Ma/EI2AIkhOwW6QQBvOVO+HEmY+FIexxLBSCDAXNNEIWwEtmu+IKEQMBOywKVqFyWCFODke5T
W+EkYmHMBCBImU40Q3LC2tLERRMfkw5SbNUeJNpN8xwA1BXAZIsINC836sPK0xuzEIOA0n3T4Vey
DAhUGmYAiAjNvETStSw5u5c7QCfUcrlJqIkFEj8A0ZMFKEsMsR/Ni8NQKIEEIa6DlIG/bEEzQyHA
g5/COnCg9ReAIcMC+DQbdWDORSe8MIIB/WQ/JGBU0M7N0IXHlOCSQXQt6g9EiiYIHTLO2IJKaeeX
WB/QRLeS9EFPLBewyYTVvAgwC3UIMoLWwIEEsXxWIZOJXWNXBQTSqIJGGINOeSRUZXUJqLFV4kKR
IBQEsOaHoBuF/HcwIG3TYAfIdI7WaBEbRE5FqIUHe5dRY16Fec7TGwLY4XWMNZEIKDNZLTY1SuTU
0Ia9o7xVsYTNIwE7o2TT0bfY9NfLtYXS9M05FQZAtMGIRaK70qOptUeXOfkkgbeNtQEJWZRZ7anQ
Q2TaE5EmjXRYsgmFxO0JK45Pw+u53GOzk07OlOISMRZV5PFYMABONQDNUU9SpQRPCOLXI0vUuKcy
7H4zabRb8OKpROPSdTTbIHaa4GoB+ZlE/ViIO/mWsj86hDQgoERWyhxXSNjNIIjVNP8W6vVENWMA
BL3RzK8J2d2jGuOxZVRRmAAG6LNRtQiIeFrHcIGd2o3S2KfZpJHdvecitO/efelemKdYVepevexe
ze1e3e4JeB/YGJ3M6/abHe7fKjwDk6KAAB/Xu2rV0IcGpWffNfkKCDAUENtICKCAjWiIi13fnf8K
cAIEBfqKkNuAgAKIFe+7VS4sueyIEFEF/T0IXeFW+QpfFcTLAR4jGd4B812DuG2OkPFfTf/hGItf
6IIEwZcK8DPfZe+qWN+ZaQeHVWaILW7YWIHQMIJWUIHURBYj9CM4IwjhJiEJLhNeOUEGzgKALfXN
BE9PWNkIS4gts5dYfEJDoM6A0bGFyeqfAVng9iHi+Ik44GoXgP/iQIMB+ESwHUiINcFYmgFUIXXC
jbU8WTfGcABiKT9jBj0fWdhhNgElyMsMNiXeOWCC/IzbDNfKZeMABdnXwlEKbGxR6IEuWWYmdjHj
3kwIKIwByObg4N6XNgGtE5gnVRtTrZwIHZAwG9tfUGpdsmUZNbUAAb2P0IuJlSPkzlxlzl1l3l5l
7l9l/mBmDmFmHmJmLmNmPmRmTmVmXmZmbmdmfmhmjmlmnmpmrmtmvmxmzm1m3m5m7m9i/g8/jPqi
GNvk2lqYyRxlCh0y4NmII+mhucWOvIy86TkawMKSIJmRoT2F0slncL0GokoJKTWIEMUbcLstra3i
eIUfYABnRkuIgkAHe2YO+CfSGIaPszDZgIMhocuOSXcwis8IRfWCdeiRkL9osAAAOSY8ONaOJLPn
YIIhoMuhsf0OWMAKY3K1ELkQUJWFKdSYcqeNke2HKO4NsKLi4PLCeQkAAGiDFhaV2U0aAOYQoCeX
sQ1p4XGaujXqENoPyvMLUfaIEafogeJpqNzDaIKLiLmQWMWL8WLnsIMNodiQprDnQWcIQHEcsCc/
QqDqkSMwRqqU8RCOmNyQakFnsHeHaXQe2QhlohsSHniCeQQdWukDsSWMWMZBThyXRcYMEXY/KKlj
MIEVYIIgkIEKqc8XwLYJXoGIXrgX29yWUL3k2dwXcIgES84Q2IWw0J8Tcz3b3tgh/kDnw+Vi6IRn
eABtwV3sgOoVqoMpdssP4RITiR4jWxuTOLHNpo4heM+JBtSXXpwI5qxp86NuwLEVXpkDgTwIRofk
AMtqWx7hmIEJCp2GoecDBqtLCmKtttjvSe+6sIVqaIIQJiguSXEtoITsUILu2gUfYVkci+nwEbIU
Fu8RkZUWCs9p4MZoOScPsuGeUVWhuUCORniTMZK84LgKmNOIUbpb5hua6dsIURsG3KPIkjqkPhmD
sr4aDvsf873taIQFzXa44h+b3s81sIboAfwV5k0sLueLkT+PmITyI8ztllqSqIZiRtmkogjwIdOZ
Hr+f+KmTYNOPkYTyEPsMNhgWOhedGOCKqJyjgK0K4ZRrUh6IMawdkLGMoIWN5n4LO22+QcKcOUGd
QL+eAuiIYndrgWOkmQRvUduIduQSFfsIOKyNKw0aMMqauaihSknuHyxyyNuIGR9RiABtQQZpu6QS
Tp2babeoCbmO1zYhdFuTCITx6XBpDM8Y9nsFqe1tiIMYwEgT7PqmKWuVsNEQMQRRfsI0tv2mUePq
G4ryuIaPGIGxS/bD0ISea16QVih06VQhGSp2oILi8OB2sZ04nyYNHvtSUWEUEOn03nqToYihuIpt
L0qYMTMyiWBeHE7XaX0LCLEdoQLnOn65ONSXgZ5wGKlziTLorTCTbpX4SIIgJtgIP3HtASwofur3
BtOb+Q9EhwOJ4RsVoUmUMS2kttNHEPeyibQceImjX4siEXkIIU0JDyQIXvIJgKPrHlqq8RwVyJqZ
WIciAJ75uJ0ZHMohuWeIwtUIGM4WvyZm/6p6r6t6v6x6z61fmfn6cY2QE/3uAjN696f623tfRLqc
0lUIMY6IqZ4ZAPOKp5APbx7VIINS0bgvw4nnahUMsGy23iRLUDGFeGz5ed57bQ1Wbt0dP7MhyGyt
Fd8IEiWZEZOd4LL0ILSfBSTNUQW9q00kt4EVUbzVSDgRYiMj9ZABcDHh2ZMA+ilXbzH5Z8bpp7K7
G+cAADj03gU0sWU6Zz62YjGp5WT20bALkFPk47cjWw+ZzAAmTNxCl9wMZRCZOUS5N9mhqr2vBTyF
m2eIGHEljAOWsNL98lab+DswAuuGo5+5wDALkC0F9OOkK1r6AEaGBfQ4Qx8soZjP3/1+uhuIATw+
jQBBQAjQjBgAEAhBmMvYKKFLBneYIMgEBBlqXy/CoM7Q/Bk2WkEAAJHCdHgA7hFJosgjsvifBnq6
VXM0bOZ1BjgXYWEC+GmNBolKoxKqRSaVS6ZTadT6hUalU6pVatTyeOYNOYVPYMZ0RBaPBWpHbFGa
66ZU7XbBkfbwAWjsubNCgJQzxLTApztKYKBFrNQBWYHXAAwDkAK9BbBZ5VFavkclk8plctl6sTgJ
NLrhoK8GzBoZBVnQ7Id4oYDBaAA71rSLYAJAH0fBZGdpUcn7ChFoSdKd/JteAC+qxzhcNoNFDQBp
cxz+h0el0+pBt+q8BVKBCne1DuPmpBdVGNZKgJsdiALftY9wYc7oK7Xfficq4LgbVKs9i+3Hu+6s
AQDAUBwJAsDQPBEEwVBcGQbB0HwhCMJQnCkKwtC8MQzDUNw5DsPQ/EEQxFEcSRLE0TxRFMVRXFkW
xdF8YRjGUZxpGsbRvHEcx1HceR7H0fyBIMhSHIkiyNI8kSTJUlyZJsnSfKEoylKcqSrK0ryxLMtS
3Lkuy9L8wTDMUxzJMszTPNE0zVNc2TbN03zhOM5TnOk6ztO8lICACmVuZHN0cmVhbQplbmRvYmoK
MTAgMCBvYmoKMTEyNTYKZW5kb2JqCjExIDAgb2JqClsgL0luZGV4ZWQgL0RldmljZVJHQiAyNTUg
MTQgMCBSIF0KZW5kb2JqCjEyIDAgb2JqCjw8Ci9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRo
IDEwNgovSGVpZ2h0IDg5Ci9Db2xvclNwYWNlIDExIDAgUgovQml0c1BlckNvbXBvbmVudCA4Ci9M
ZW5ndGggMTMgMCBSCj4+CnN0cmVhbQqAP+BQOCQWDQeEQmFQuGQ2HQ+IRGJROKRWLReMRmNRuOR2
PR+QSGRSODO93vVpNNxOV1O1asdjsRjMdzOdyMlks1kr1xL9XOJvNpvu92uqjOFoNdjthtNJwt5u
LxhsRyut3sVpNd9vt9NZtsx9Pt8wN8Pd9t5wOxxu52uh3Ox7WV82F9vx+vN6vd5vZ61x9wOtv19P
l+P7DO51N53utyOR2OSTO1zOBrt9xuV7vh9QZ2vB2Ou3wa7P14vd83V+vjTvR6vh7PZ87B8PJ5vP
WPDbbh4vh+YXAPqyvZ5tdyOJ2UVcsBhLJiNF0u55QN+9N68J7Znavd6PLZ6Z5XHDP7pdO4vl8efz
vd6vV5upzvL1Pt4u3XvN3PZ5O3Ab17vZ6N6fi8POfJ6nKcxsnAchxmKZxrmeY0Fmmcpjm0bTTr+h
bXnwVhcl6UBVF4P5GlYUBUlyZppmmWxaFiXBaF8QQ5kcSRBlfBzJm4ahLkeM5EEEKxjmaYBRFgTx
xnOcpLFKVTrnuTJWlKei+IGcxzHeP49leOZDFePhME+UZaFkUxcFyaBqG+PxFlWXJimUeB3nggZv
m8bpoGcaDwmUXxjmqZRlFYUpAFqXJSEqUJGl0Y5lOusaBLqfhTlmURVlkTKtny8JkmgcBamWa5mG
mahcGEYxLE6XZGkoWhAkuVRHFMUhnmwZBdmCUZjGAZr1MKwxnmOZBgF6TpEEgNRLlEQ46EMNpemK
ZJYl4X6yNcV5bk6bZwG+VhaGIYZemyUBZmeXVPnaeJ6IGZ5pG8VhbGUShUlcVRfFqVpdk4WxalWe
J2HwX5VnCYpZGcdpym+fp+H3NxeGWZphGFb5UlmXZiGYZxJFOUZhmWXpCkmPQ9EQRhPlUX6sG+1h
8IY8JlmmaJSFkWRYF6YJrm0cR2naeRdF0ZxQFcWJQlgUBN2SbhumseB2nuVRMGUWBRFimxvloVpG
HGyZFFSU1Zm+SpRFQaJrG4zJ9nMdJxk2U5MFCVZbkcUZJF2ZRaD+SZGEWTRQkqUxaGAYhptUzaBb
IaxhGUYTRl4WpkmYYprFKS1SF3gBQkWaptGafTgIGdLQEcT5WkaUxXHAc51wAVxclgc51HIZRrGO
XpmloQBJkuP5JFANo+E4OA/FAcR0HYYBlGSa+kIGe71FOTJflARRjlCRJTFGSY1kUPwqloXhVmaa
xqoGsJ+biVx3HieRZl+VpvHGbplGaapimwWLdnUgZUlqW5hGQaAYw4CYDoIUUYexJifFOLQWpux6
DRGcNQX5UjwmDHwL0Wwphmi6FOJARobhfDEGAJQUgrxHicFGooaInxYCvEKJYPAsxcCgFYLUWacV
0kOLoXkfCUh7m9OmP0fw7h3D0HePE6p5h5RJLCPo6Y/jhD6P8Vsrh7B1lcHwOoeRiDoEmHeOwdw8
DUF5HuOQdI5zbDxGONMXwxhtCyHEOobgzxuDGGIn8Xizx1jwHiQNI47BcjGKcW2Mg2x2DsJWN5fo
5x7DcGuOFz42DgD1IGese44xxjoHCOcdg8h6D3PClUbAzhnizkcNcaw6xZi6GaK1nA3RfjKGYKQX
AuBsDeHCM0Z8thxjsIGbQeBSRijUGeNsaQxRxDmG+Osxg4h6Geh/JMuIshZi5iEOsYAzxrDkKMNk
bIwBkjRFmPEe0vCBDhHGOEXQwBfC9fi4gagrxZjKGoNtI48x2RGHedAdJAzwjgaUMQWw1htDRGGN
AYYqxuDjG8Msag3I9D1SkPhc5ex7yciIeEhhZR+DblOM8ZozRvz+GSN4Xg7R6T7IFEAfw5BzjpG8
OYdCRx1jnHOO87Jth6mnUcP8sLzFeD7H6dofY6x1DrmQNUcA5hujTMtSEctODqllNMOYcpkB31FH
qN8uA4CyHmVmNN9w5hqjXHEYBhI7R5jwowQIdo7B4FlcIQQ8JYnmFzHMVYgY+TCVwZYYY0x6kNFz
h8ZkfR2S5xQNif2uo9B5jvHoOplJRKcD3c4Pofhg3yPkLjZYuxDBmjUGXNgZ8Szrj2rWQc3o+hfD
DFazodBYTVQ9tORuJo2RtjpF0L6YouCXwZF6MIVhAxzjxG6LUYwrhUi6FwJJMA0xrDhJmNgTInxZ
jmHgOcgYvxkIsFmJwZgxhliwE0MoZyFBUidFSNIaw0RQCxFSMAYwwxUDLFeLwaQyRujaHCLIUgsR
dpiVCL0aA2Bgy9HoPEQIlRBhnD2H0TAqhYDJjk8kcQkROCpGsN8bo3x1DjFeLEUg0RmDEPPJIgVE
B7izRMM8ag0BNNsHMOooA8RxFrLcPAeg5xxjiNcPcgY9B8jvFqNAUosxfC8FGLEV4zxsjYFKLEXo
ohSi/FEKkXwphbC2GWMgZgsBc5SE0IoRUARKiGFqKgTwzRZCrJiL8YCQRijIGwNASIvhSDQHINqv
JZRoDLGYN0bo1BqjkGGMobosxkDWFsK8XIqcJDKGIM/Qw4RzC0y0hUc4shdiyGwNwaYwRjM0FoLu
xRIRu0uFwNTAVzhbxrGyNQahAxujmGiLYY4lhQjGDkKAX4hB0jwJYSYUotBdEGFCK0WQrBXCvE+K
ITgqBRCaHSOkdopxPjDPcPEXotxkjaGqN4WYo3vjbGINcdA3BDinFKKsWowhxIJHQOQcp4x+CuGc
JUS4sxFCbFgJwSAo1KC2FyJ4VYu4YDHf4MgSQoRNCrFWKcaUDpejwHvv4YI1BpjbFCJgVF7hMjHG
iMEY4z1SjOG6KgXAvZODzq6PYYY1RbipGGJkUIwRBjFGgL8Q4mRGCWFOK8VAtRiCgFKLwaI1BvCB
EeJoQQhxCCVEoIkOIawsi7FwLoT4lBfvXGaKESQuBpDQGaJkRwlhbCxFuwofo6h2DvFIvcoQ4LbT
CGlwgaAnhZjMEwMga4uhTC1FEK4XYuRNdvJyNgVwsBiDUGyN0UoshTigFOJw9eJiPqYPOPM1HbT/
2dIEb0fY4RwDVGqN8ZI2B2DFaYN2mw8hejIGSQYYQxRsivFoMkXIxBji4JkNobg3BxDkG4el19jB
3j5QYMEYQzRdjpHNMcdxUBzjoLwPYrlcSBjzHuPAew+j5j0HLc8Z44aqmVHGMwaw1njDNFQKxb03
xsp1fGVwY4yReEwGkMEXQ2xjjA0AGwvyGmGwK+HKFuGaFmHgHyTkUePOKUziGCGAF0GEFIGAGkFW
GWaqHIHaG4HCOKFgF2nY9IGGGOGsFkFsKwGyG4GYy4F4FaFsGwGsGkGqGkHKu+HC28HUo4HMGQZO
swfIGiG83eHMHYMGLELmPqXOc+HsHIG+HcGeJYHKGmGqGmHaKIHoyAc4H4GqGsHAQ+FyMyp2I8sy
LCp0HgHqMWHUHQsgHcpsHcG3DckyPoOuGwVEGuGqGel8GiHCGWHKHgHGiAH6JJEFEHEJEKJGPCPW
QIpyJIGIFyF+FCEuFMEWE2umFyE+FWF6FCEGDoD6FWEuFOECESDkFeGIGEFAGEFeEiEqE+FiFQFk
F6Ws9eFkFGF4EqNg8tENFzF1F3F5F6IMGMF6FUEqDmC6DyC6C+EWEGEeXcFaD2E4D0EKFgESDyEQ
DyGSGUGMEWEcEGFuGKGGFEGIasFmF4qKHYGGGAGAr1DDF9HZHbHdHeIqGWm4GwHAG2xaFkK+cgGY
GgGkGxBu/CGSHMGWGxBydeaYOuHcHyHWM7CwqGk2ibHhIjIlInIoPDIsH8pUPFIpI3I5I7I9I/JB
JDJFJHJJJLJNJPJRJTJVJXJYIqPCiaPCPKdQHiNwHUbJH8+mqSHGHsJOHYHQw4HMnOGgqIG4LYHQ
pQIIPaHYHUoaGsMqpg+iHSHAocHAHiHynsMQM8O+soPuHwGYG9J+LcKsHaLyrQogpMHiqAH4n4MM
OmNHIwV6h/LdJhI1JbLsJCc+Z4F8GmU4HMFlHlFWGGGYlCFAFqU8cyFeGGFcG4HAG6GKGLAMF8FW
FKEUEoE6D8FNEeGRLYH8FmF6FwFYFQEuF0ykG+bGFAFGFbFYFWFezUFyWgE+EyFkFcFcGUEzBOEW
F2GY6MG8EpNkFCFo7+GIE2GGdk+oP0IEP6l+GEFSGwVmu6GIGkFUGkGXN0FzCBCxLvO0I+POH0FK
EyGIEuEoFgGgQQE0FkGAG+XOFOOaFCFQGMdEE4MqGsF0GYFSF6GOF4F0F4WjGEGGxAeXKs6wGKZo
GOEyFWFUMqG8GO3UFe3+GeFsGAgiFkEYEcFqRIGcE6EoFUE/OEgeEAFHBAGIGzBIGqFOFuFuGmG0
G8q6HwFwGGFyGyGkGcFWEsEAEgDcD+FsE6FqNosoLrO3SCI8aSHcXqq0NAGcGcGK+4HsG0HUHdKO
HiG3LAXQPwQKHeHkHS+OiTJoPaHWN+H6HYHKHoHwNwHAHAl2xwsYHQ+3SyGakYUUFsGI06HMHrRI
HOHCG4MdJ8bGGyNGGkkuWeG0SQHcx+HsHgF+GWE6TQGowkGYF7MmGkGUFbDuGMP8ZXSFUyIyiaLr
IuMMIMiSHkThOQH/U8HEHOHcFqoLM4tOiWUhEUHkJMHmN3U9VrU+IvEALq+sYUUgLrV6YUHwtnU1
WGIkHiJOF81SF0kAqLVEPaHKHeHMF4GAG4FkE6GeHOHAHgJkGYFsF8GWG6G8HOE+E2GIXUG2G1LG
1kHYaSHEGgGYFWnUEKUkEyQ6FMGQG8FqHGF0G4W6G8V0GSG5WJYFJIXQHmGE/UFwGiF6FYFUGCws
FEEQFMEQDYFCEoEwFeF8FPQSFo72FiE8oC8YFQFUF6IHH6xiHc5YIEL4HhZEEEKlFcFyFOGwXeGp
PQG6FwGcFEGEEqEQGEDwFQGkFFYHaHJAnEHyGOGYHKFcGq9sGOE4EoEUDmE2FKFYE4E6FMF8GYFQ
GoHOHFWgHsHQGyN2LikKHQIHDSLwyBM4GSGqGyG+HIHAG8G+GI+sHwGIGsG8GSFEKm0aTaGIFuGG
GdaJcHI4PCNcH4r0H0G8GoHSGSGCF2fSscLwH8N8IpEAr+K4H4QOHiMYtNIuxwHuKsfQiS1eG4Pd
KWHXJ2P9cJdZHYHSHQJcvqF9Ag6OGQi/VQk2qIHaHyh6otJoHSGgG8GeeIHLBuGaIMoYGahkEYGu
G6G2EuEsFuFYEmc2MIK2H4FkFwF4ZiFYG6HAHEFyFuGMFsTY6IEmQSG3dbfVF3ToEfNuEKEy8CF0
FmM7Ci4wJmGCF+FiGyGWQoGGF0FgFTE0GhYUG+K+IMF0GQGeCsDwEMGMTuEoFK3+FcFJDYHWr0H2
EOE8F2DmE0VxBkFSFgGCHKHQHWf1cCGmG5WFfXhYJAdOHQ9yGZC2HGQqHMIGjeHCGcGyGYGY+ZBY
GsGcHMGaGCOMpmHYHOG+IMmQG0EiEuEwkujhCZKOG2aQGah8GkGkHJPwG0HAHSHZbwG9i9i+GuHL
bkHTIhhbjSJAQALmQwtRIwqBeuH0NMHnLaIeiarrhXjVj3j5j7j9j/kBkDkFkHkJJNDIO0HsYSH6
HGHqHGiwHeHK1+i6c+HKHOHaHWteOAp0iHkgHYHSc4MIYVDJhWiWPYNaPVjsIQPCHyHplBjcISc4
L8H0HYHmbQHoG0LNZSIsHiHiHSNyISPCHiiwHQHQHFFvXCHUc+qvbgPwHkkKHKeGG3DJkKIsGOGy
GGFgFaFMGkGQGcE4E8EsE+FuEyDgFKEaEeFEFCFmbeGEzcF+FwFkT4FgFCF8EoFeGYFOFcGIE+j+
FxhkGhEAIMHTc4FOFQFe7CGQ4wGGHEHFhyTOGEGqGGk4HkGHPYdkbJhlIwH6GYG0G2GWwyOWtWFu
FrFUDk6M8eGgFMLtleUeN6KTbieHgxO6GgGeGIGa0g1hgUTOHWOOPCHEGeHAFsFKFc/qGEEkFUEm
DSEwEOEgE8E+GI1AksG29sE+OuhvmoInQifYGKFiEeFoEkFgFOFSEwDkEgEkEcEQDOEgDCE4F4E6
EJamEUEMEeGUGQGMF3myFuGAFSEaFiDsD+FeDXjIGg+5S+IQE6FGJ5kc8KSWFIFMEkEQEOECECEU
GWGcGmZ8F1PKGeuQFSP6HqE8FIE2EmFuEwEtFaESEeE8EADkDwGSGKGEFmFuFGp8IMPCGJSTE+FQ
F2GKGYF+GMGqJyGutWGaFZYY2gFAG6GuGwPCjSGcF+GSF+GqGYGkEqD+EiDsDcDgD2E6ESFWu2GW
GrDoGmGzj1qwIa/zEaFSFiFnQkHWHiHQGqji//Mcw2G8GcGMHFb+G41AjkHCG2nMG0G6GwQcQaGK
E8FuEQGiHG9iIQGURTCqHiFMFUGIJyGsEgEsEIGgGFAkFUUkeMGRH6FOF6bEfgFqF0FkGNXg6uFb
RSGCE4FwFs0BhzGuG2lMIMHmNmF0GiFkFLfIE2FWy8GGGMpCHWm4HPwAHKwuFUMuG8PDRUHFeaG3
Sxi+G+XYrBQWHGHaLfymHHxyHtvOItlWc5LlkUYSIwgmYUeYHqQAPGYSYVM4sIcHSw81CMP8ssH6
NOH4iLl4HsPusQP6YVLWIQeIHiHKHkHPjiryLEpMHYp0M7SYHrsKHFdeOOHkKYHMM1pYH+LsLtIw
ITEBKsHlvMIhLaK2+wIFcNO6K4IZzeHWQNHUIM+6PwHuj3IoOEHiYGFQHWHEG/eaGkG0HJmkL8H2
LKiSPNKuk6LmHyGoHEGplpd2c52CHGssH2jfk8nvJoM/mKMHd4OEM0L0HyHiiB0HVKOmGAGQGaF4
GUGh2VTIQuNMP8SrXWHCHQSaso+sK2yaaVWNOKf6GwGw6OlrBn0EIGFaGSE2E8F6ExogTaGKGCHG
GwSQxqP8HnweGkG2HKHL00UhUMHqFGFsFIHAsgHSHrp4HwHetOHIHkHKF6GwGSNUH2QELeHW5IF2
+uPCpsHeFOFqFOGAFoGWzyHFkwHEsuN5cOK2F6FKEqTsGWGIF+GO/IHaGzByGRD3I2n8GqVeE0Fs
EqEUGAFgFMFNey8EF1t6FkF0FKEQQ8Ey6gFG5GGmFIGQFfICGcX6HiF8FGGKL2HoFMG2/cG4GFwE
G7h5XcF6ZqFgFIFYFOEaFCGEEcHIHcG6IGP8HgGCFMEoGGFIEkGCFqFkFCFwGAFaGA3aF0EwFcEm
EOFIE82gFKFgF4GgGCHI2AFkdYG1AFO+EnYagUF4GaFcGAGCfIIGF6FaFGFKFGD+FCFuEMFMF0EU
GGFeFsFkFEEoFWEoEsGSFWE2GAFUFAWeGUGiG5RYxOiSFMEmEqG0GyGuFEFqFeFYGcFssox8IF40
HGFYvcG0HKG4E+F0FqZiIAwVMlVO12Yy36/H463i5lKwkmy1gwFWgz6tFKo3A02c1VooXq6nIsmE
uWo1GguFKm3A2Wc1244GKzWi/5tN5xOZ1O55PZ9NnG1m05W23F4skqwlmo2qxGGu00qWM0GmoVkr
1+vVWymApX0+34sVsv2a0Gu9Hw9lw11u9Hu8muxWeyV+xGs6Gst20vFiu2Kw10w1YiUYs02kHK4W
3N3k7HQ3WixGQuV+rkon1oj1EtFIs18vl4xmUtGsy1utkykl+plY4W+5GK1WK7ni7GrKHC0nM4Gw
3mw52o/H6/Zu6G83Xa5nG3mvL22zGi22oxmIvV4lEowVao1uolGuE0rGww2bN4S/HI2mbG2culIr
F0umFX33N3G7XKr2Kt261G6XpYl4SZbkkQhZE8XhkOC4Z6nkeJhloURkmaY5nmUY5rmMZhoGMVJb
FKSZxG0bRuGMaxxHCdZpHAcR3necp6RceB0nSn8bRvHCdn9HceH0fR7HmeJ0H0fB7nueZ5n4fZ9n
Ydx4Hmep6nwfB5putJ7Hadp4IUfh7SpHbhuE4Z/LAfJ8H3IJ6ntNR8m8cBxloV5bncdh2JvHh/H7
PLhnMaRvu0WB5nWeB7ngeThz1PJ9zMeR0HSfZ8H1REeRzHMeUQfJ5nweh2nWeR1HYZJXF2cBtGwn
tLoVRCdHwfh8ngfR5n0e580Ke54nhQx9HgeJ6HtMdLoTScwOHIkgSFJZ8zzPFK2bZ1n2haNpJtL1
Xnme1KJ+fR5VpNVp2/aR+q+fB3nnMNwXRdN1XXdl23dd94XjeV53pet7XvfF831fd9x4dh6n0dZ1
HubZpHTNZ835dZ1HUdsfPqmx5Haer8HjhWLpxPGNWWnWNUSfydVUep52VMFlx2nUtHcfNZxsfcfH
gdp5XlRJqnSeRIFgZZNEYZZmFscZ3HQepqGeahwHAbmNnba52HPRp0ngcx2HacJwGIaZuGEbp4HA
dx5HcfR8nseWpHkd55HSbx5Ypsh5UFTVEykeZsHMaBvYEbxzHkZ5gHAd52HoaJomsVRdGeShameb
SGGwbZ0mEZRtHjKFynGex7nanR1nGbUj8od6QnNJLhJvTUmHieOxUgfNISXv56HIc56w4cRumucs
HHeduvnx1szn45LanZBx6HZa5yTAm53HSb5uGkXzknYZhYm7l6Eny4SFGgaRdnUc51TH5eSGwcFC
HufBeFqX53nWdseTEZRoG2eFym8cJzG4cZlZZiybOUHib4cA7THjeGqMxsA712JqHsKQWQqhMEUF
ELkY4rRdjXEmIcYgtRVjFSUq4sAnxcjLFyLoaYlxKC+EgJkXAkROiGE6K0OIohZBuGANAWQzRtDG
GQKYVYvRHJyEmMEV4iBhDEFMMZOIw0pj6VAO8QYjhMB8FEH0W40hjidFgM5N47xVCmGQJcRwtRQC
nFwJwWIwRFQdE1BEZ4zxvCfFiKx+42SdDBGALIbYxBljKFCL0XAmxeDrHEOpHhLhvicFWLIVwqhi
CqFWM0mY0ikiqDiKcWglxTM7EKMQV4ohhijE8K0UgrRciVFqMsSRDxiwXEgJcVoqRciZV9Aomw4i
iDHGOLFtQ4BYiFFeMQVoyBmioGqNIWA1xUirFq84cqwibjdYEKMuiSB8ibEiM4dA4x0qXR2KEXIy
htjkHWM4ZA3BWCfF6PQeA9CbpaHKMEZQpxnDLGFLsWY2xgnlXW2Ifg1hnDpGe44bI5hpjbHWN8Xo
2R2jbG8PFZZCh9jCGELwYAxRhCnFkMwV4qhmjIF0NcXcxBGilEeKcW4phmDSFuL8X4qhgi5GANsX
w0xlikGAL4VZ2hDi5HyPV7I+x+jNGGOMYRsR1DuHcNAco0B1JIGSNwd4xhbDfGwM8cY0hoDUGiNg
cgyRqP4HMPEVwtBnDNGUOAnQxBmitG0OEZozxrDQGcL0ZA9R0jxTGMYWI2hYCnF0KAZ4khcjIpyL
4ZwvKaipGEKgWw1hjjJGwOkVQtxxCsEoM8VcERPCbFYJsUYshiDCG2KsVgyxai1GgPeoBNx3jxqy
NIUo5hvjZGML4YAwhDCtF+IQXAtRJC6GoLQa42BujSH2mSd47R4jBGIMoe5YBUVxGk+BbI/6HDZU
MPBqw7S6DeHqPEfCVlXjjHMMkco6BtDgHON4dKnV2OUTaOcc7LB8NhHfUIfiNh4pSGyNodETZ/E6
F2MobA4x1jvTCPlWqkiwJcTOOMao4BrCzGU2IfQ9R6MJJyntsY80eWvHs5gfSNlVYkVUToc47B0j
hHINtSTLElXXSWP1Iq2x7jqHiPl0LY3rn0Y2mfGw9h9tpHsO6p6ax7sPR8PxSNyWUE2K/hkeo72x
Fvyq2Vyg3R3j0HMyvBjbB33XWXjUm4+h+JESXddVCO3MMlZAvdMAujKC5F2Mse6XhqXVxGPccg2R
ljdG2M3Fg7xwDMHCjQdwjRQi2fRhwf7mGJNCHrnlLJaB636TIcJBzqR5jyG+Oobbvh7D0SgNsbJ9
1PDaYM7sd4whfCiZjbWgA7X2joHIO0cBt0SJ/GeNkb16Rs3HqSOh014hWidGWOMbY4UlKIH6kuoS
ejzHDTqOxJ7YWWDtHTUAe9EshjzeYOJXI8BtjQGy04cI7LXjoZkr0eI8njbNHGNcbo5RqDTHMK4W
o1x3JSHIN8co4Dji+GqLodo9lBpIlwOBRD2kubPuumF+BCTXvELcLIYoxxsosQCKsdY7ByvKXojw
XYvRXjSGiNDZ9nxkDqHKPAXIpxZi6FcJYX4uBPCLEuIkZRcxWCuFEma8ZNq7UvFqJ8VguBPifFQK
4YQwBsDKFyOAUwohqicMx0EWAk7MDTHQMkcw5RzimFCK8YQvxeCeFAI3PY1hVibGM2VUIwhXDi12
KoWIpRUCtFAJYTYjhRCpFUKUVwthLirFgMoao2ib8hHkKETFCxlDnFyKkbwuxbDXFKKAVo2RqDaR
5qYewlRIijGQM8YZVBgikFCKAWIpBnC3FGNsVomhbC9FYJUYIvhXCHEqIkXQuKdi6FeMMY4yhGCi
FUJ8WAoROipEkK0XArhcC5GMLUWQ0B2r/FaKcZQkBJCgEmKITQ4WujcHKOQVgtBdDAF4MUXIvhaC
1F0KgXB+h17uJvVoYKuYXr3IUgUoXAWYcwdQdATIUYVY8gagRgT4TwVIWgT5JodRfAbYbQcRgQdx
HgbQbYZTUweYaoZIdYbIaIc4bgboZQaQZwVg5S2wbAZYsBiAf4YAZIaAV4XwYwUQWoV59YVAagbI
ZoV4XIXoTyFgVARAZgVoWIZwTjmobhhpLQegVgWAZC4obQYIZYYZhgc57gY4bwb7vAbSpQdYeoc4
b4aIZ4Y4kgagYr0IaQbgaoZoZatEOIcgm5NQeYySHIaYawVwWYXoUYSYY4YgWjUZzBHhKIfAVbCx
lgfa9YbgWaPIWwXaRoVwUoRoPAXA/odhsgdsGIWgbg9QaIZo6wYYW4ZIo4XgXoYCwol4boZ4cIco
bQZYawZhGgd4aAXwcQYwWYcAUoYAZgagdAd5hodkIoZQToUIX4UAVIXQTyv4XYX4WMFIagm4XwV4
bgSYPwWKDgUylwT4cwcwbb+I0QZwZ4XjOgUwXAYYcqpJjBdxJbDBIh1pLweyiSt4b4UYWIT4aamz
UweodBKAcq/pMR30GhZx3wehMohIfwdYcxgBMwd4dIcDMhHZJYfBJ4eQXgZQZQdAdZr5bhjpHcR6
bwfpWgfAa4bwbycIXxFwdrZ5jo4bEYebJYfLaJsYeIdw85SxPJXoeQexcZSLPIfJRweIcQcYdhQc
nZXjEYezY4fDmAeoeAdZTYewdgr7JZJZNTb5sTBhSQ4ZepHgc4d49Ib7LknYbJ2zBKpTf5hgeIc5
9y/4bbPIe4m5MzIodYe4dAcIcQbCkBTZmbKRHwVoWwXTxobITIVamCuIbhEQb4cIapHzOBM50jIp
JAcIc7Fo+5LJsAdweiuQYYaQbKc4b4agVAS4Y5mIeIa4aYYMYwdAx4aZWoesPJLwRkaJLQeYaw14
cM2TeIdcmpjybwfxaptge5tAegYYZga5NgnQd80AboapLQdgfAZT4wcIbIY8BElgcgbwZYaYbobs
MQZIjp/AdAWIXQUQdIdYby+gdB+rEBPElBWoc4dodRLxQoeJaofbWxa5M0eInxMAaYc4XQXYaoUQ
ZAaYYgUoW4U4SYUYUCFwVwRISYVwNoPAUATQVAWasQm4yQWwWoUYXoTgOwW4YgWAbsmRahIoQ4Tg
TIbIbYbYSgUIVwRYUAVwJwOQQAUYVwS53gc44QfYW4ahxIaQSTxISgTAU9CQVgWoR4TAV4WAWgZY
XouQWQYAYJwwVAVYVoTZIwepRAaytKl4Zpsku4mxSIfQR6MomAcQRSNAOARgToR4UYTQa4a80YbQ
ZIWgaITQYoboVimCUoXYXAVsVig4bwSoT4XB9xKomxHgZIZQYgTATYRASoR4TgVARQY4o4rQUwTo
WgWAR4RwToQ4Q7przwWY3ocwRQTwU5hocwYbqgarc4ZIawWwaYcgWYbjF4XwZgXwXAYiR4WwYAVK
NIUIVYYQWQXyflAQnZRAbocYbgY4aQWwdAeQyActLIZgXiTQUoTIVj74WYYYYYZIbQd4eE2wmwYw
aQZVFAV4VYVwTVGYa5kJRYZgYYUQcwbwZ7O4aQZA6ERsSoqZa4fBPQfquyzAWgOIXIadBQaoYQXQ
YoYoVAWoWzSoewabA71IboYQs00YZ7NAfRHgoqHYWobxsjEomyiQZ4ZwX52QdT6gZFedUYsYm6jD
CoV7nQVq3YYQRQWQZYVYUoXwVLCYbQVkIocq95O5HYa4cUloYr+4VITIWAWYUQlocwawYQdIc4dD
Ck14awaIYIcbZjaQYg0UDwa9YAasWw5gk8dQWScgbQXAaQToYwaqmIYoXoUQsUaIXIVdY1aBaZMM
/RzBWgr4npM4fJtjcRqhKKdwngsBWhI7NhbRl6+xHzoof5HhKYfB+DiA4heJs8Modbx5tAWAWoaI
aYagb9swbLdbe4eTUZH6BjR5GxIofEPRVYnNzZIwfFrweAnsR8R4d04UBAeJ9AepqgcyoR3xIgtw
eYYoaIYAZAZwZVwgnweZF0uQba8QuEWdpgxwcYcodc9ob80834bZf4cDXKcZ77bAd5LhXxIzJcz0
sAnQcy+hKbSEkgfwek/koMTwftdgnwaIcQYhTSWwnAcYdAc4aJEkR4nQdge4dwbocB5wa4apqkDQ
dQeAWoVQZ4aAZYbjx8+IXwWoZJGg9IctahFIcrvEYy94dgdQcYcIbBXpr4fM/BwFpjFq9IcC9J1M
qAnIYIXgWymIXgT4TgTtr4cYegtwegeV0DKIf4dIdgcgbocgazSofNZwa7EYfCAgeBREohSMjUrD
NBaofIdxF0eYm4cpqYYqrQtGIpdpRAZIYIYYVQQgT4XgYJCIXwVQQYVuJgU4WIXDoIWLq6SAS4Ug
XQQ6sKmIZoXIZg571MJwVgWb6gYoWIWgZVdR/wnCRoT4ZVbwYdYgXAWAaIeId8fAsAWgSwWoUIRw
SlZYTyVIus1y3L1YYIXoWQVATiigWgZ4bYX6kNcQYoUoUQWYWKduAwr4fgVoW4YoOAPwR4SISoUA
V4ViBwVoVAUgToWYZYZAaom4aoaoaYWAUgWEOYZ4SYUgRoR9B4TwVQXZowa+ENJ4U4UwUwVQR6sw
ToZAb4XYR4WwPgVAW4VU3KdQY4ZAnQUgVYWI6wYQUAUITgVIUoS4jITT6AWZ1OAwbIZ4a4VgQgVw
aYXYbQTgXwUgbscYWKtgZAYwYYX2TehYVaWQSgXIaAUgZgb4XwWwZIVgeeKYm4XAYQZoUjtF1gbo
WFFAaQa2pwUwVwaoZ6DwhRZ1hIZxPoXAZYWwbwaIbgXwTGiwTwT4VwcAWgYUf4Zgl4awZE8wZutz
1TAwXwZ4bt6gbqCoYQUIXwYqPIXgXLdxGonLvQXt1j2wVgUQVYU4UAcgcgcR7QWkJaHwT4ToPlKQ
TwToU+xYToXgUrkIdKv4WgWIUAUQYUVAVAWQTbxYUgWIaIVAeAe2BmaQZBwgUQUgYeT8LYZIaQjg
aIXNKYcYcAxYmwcodlagc4bQe0/gZA/QaIW0EYY71YcgacG+vYZQyIXAWk/AdJWge2xAWAcodwb4
YQa4Wi9ZU4nIaQaQcT+oZwXAX4ZgYIZIZNq4VYXQWwWxNeAzA4bAVg1dKkCQT4WcBAdIVIXdqtow
RQUYUwRQQQSU1ITAYoXwWZ+4aYVgYwTQdRRtnKeoqYZ6uwaD5gXcKoYwTbRuKZQ8sRdDB1XZo5Eh
ZxZMylIbDZcrUzeKvXFonBhgeAbgbi+jFg1wb8edz12yn5tAdh5wbQdQbL/YdmyTaIckYspZ+p3g
3ZGDT+2Yd51t/1whH0sN0ZdtxhKIeq67eQegbaqxr9+IchMwfPJYd5p6qwdobgXYZwaQWumYfZ9E
muKOMpPK1xsptBXGoobZFC14ecpJOxdAdzT4exWptQbgcxEZd5ZIZ4ZoYAehBsgtFbaK/mGrBnL9
7XUvUwnC5JVwfvUl7QYgY4YwWQYwaIZYaAwAWQRyusdmfyuYaoVr4YZAcAY4XAbQXTjgY57Qm4bz
XXPYZvKgd76oVYc4cwcKXQXTFYcQWAZoUQYIbi34YYWU8xCYWoU4c+q4bIawa8K4bJbvU/dvd3U4
agYYYIap+SY4aAXYYAXQQISwPlQYS4ZwYIXAUgSISwaobobISIVYUwXoawYKoUGgZIXoZT7IY9rw
c+vwW8A4dTmzzfWdogSAVIXwSwUYYARwh4TTWIXIcgbAbQc4a4/wvmDIb4bQcmwvd/m/nBfJs4eg
3gc4eeGp4wdAa5N4asd7eJqjF8R4aycZ2SbuK15geocoZocsqgegb4evq/PoccsrUoewogbzmC8w
c88nOxiRhvsabbXAbgb4tItDBnnPuHuPuXufunuvu3u/vHvPvXvfvnvvv3v/wBZxMDaV3vUpMMeZ
MbaNhIf2aTady5eZHi/RMRYghJfbKofMyROhUEll2MWYdB44bzbAaYoa5wbEtYaB1oe5RBf4eAc5
GbP4Z7FgdSLBEgYAcbHN04mxr4dgbAbAYo/Aby7nnzdhQgfQcwcS8JgbgYdTUweiG8NIcAdHVwbg
ZAZYbxI1kpPIb4c/c4dlacgRpwc+5od45gcgZQWIaQYC3gaG3xG3TgfAYIZAbNrwegaAY4cmdIcB
VUsm2fZQeAgDkcLub7hdDhdLIZ7XWrkdLqf8RbTRYTQYa/cDYcbKUzUbC4cC4WLGV7Jar1fD6iL/
dsFaLEZrTa7heTze7WZcJYLadLpdzkoDjdDvYbTbzWY7jXrDazWbjaZrYWy5aa/XLWYrodThazOX
LibbHfr8fcrs1ntFptVoejzfSfXDYVCnaa2UjEUiVWiHRqbVC9YCRWDCNZ4VCARSsdzwej8fr9br
qcCqYCnWi4UjIXi2V6aSS+UyueLqd8rprbVCsVa9ZK5Z61WrgaTSXDVZC4YLGbLKc6nSTJcrgdB7
PSPP6TTyCT63YLMb7vmz9fz8qKtYrYWrTc7UWbCVrwdTmXqqUiYOqDUiFVLMVbMfD3fb++Voez0e
yrSKjbDddifX5wmAaJyn0fZ+HufB8FWWxbloaBpD4T5elwZRuG+chvE4UxOnse57pWXxmF4ahnGg
qBjGkY5ilgShXFEPRaFeSZdnsep7JWcRqmMZZiFSWJQFGaBjGcPJOl4TRPmgYRYGwT5HFkZJlm8R
hPliRhSGAOJBFcPQ+FQLw3DyYxmGKSBTDYUxdEsWxjlcWBVkyd53HWtc6Tqtb5H8YptmWTpgFqYh
nHGVJRmkZ5hm2YhdmGSJKkwTBYl4OJOF6xkPIidh3nWUhaE9IRKmwbhkliXpTGKix4HgeKVm8Zhz
F8TphIYapeF4YptG2bZyHE8RkFeX5mlySpdFucqhlMS5mEWOpQErKZQlcXZzHUeDHn8ZhqG8WRZl
6XhiGGWBfkudp4HKY5jllPxYGcYJeK6XZiFYYJ7nsfK0Hmep6lkWxWnAcZzloZZpk8YpeHqfJ9H4
x0Rm2WpUlkPxCErEpwHWd542eZVqpWapuFwd55HGeJ5niZBsmabZomUZxfzWXJrncdR5JWeiBGtE
JKFQS5kmUYRAlAR5iGybcLHgSRRGUa5tHUUhJlqVhYFeSRTFaQJUGGRhMl8XBTmaYBkl6WxjFOYJ
nkwZRsl2bZxGdO227cleDny+x5HSeJ2HKeB17sfJumUdhtmmcSanidB2Hkxx+pWfB7H0bRrHO+x2
HyfB6HkeR1nYe53HtznFcZyp8nsdR7nSZ5ynqc51nadB4mwZ50m4bxzGmcJjHofJ4nceZ8ngdHRH
OeB2ncdjHuk+R3noep17weR4HqaZtnCfZ9veep3HofXGH4fR9Hoe52mucnirQfMCnMdr7HufRzHW
xZ6HXPFqm2bx5m2ZB1GSYJsm8bBtQOPQdjBk8ErMePw+TxjpnTOlAVxDxXEkRQMPkeo7CtjqHaNQ
aw2htDXHSSkfRKB7DGG6NWDg8R4jrHuPR5I7B3FDHkPVSo+2EPFQIPtkQ7x8j5d2PhmTb4fFpTw9
4eg6h6lAHUN4aQzBqjhGynEd47BrDeGQ3hC5ixyjrQ4PUfY7B0DyHYOsdA7h3DvTwngdw8R6jlWm
Ogdo8ToDwgOPYfY9x5D2XuOOOsJnkRjfePIfQ8RsjgGuiMcw7zoDpeEO0eY53yj4gCPpeY+4YD4h
/JWS0l5MSZk1JuTjb2Ej8F+L8ZwwxoDAG+OwagsRdidHQOYdK2xgh5EMJEXAxhdCUagJkW41BkjQ
HCJMRImhaixFQMsZwyHpj7HQN8eIsTsiDEeKYQgjROieFiLCDwxhuDSECKsWQlg3ChFmKUS4vBgC
2ECIYVZlhdCCFkHIYwyhiioFaJYQIkUfilEyM8YovxRjCGqNkbA50/DNk7QehFCaFULoYP94o1Rn
rZFWrYaw3xeivGfE8d4vhcieFcLkV4tRdC0FKKEWQvRfDAGKuYP4mBQLdF0LsYIqkCD4G3BwXYuR
qCPD8L8RgixWCMEiJ6HI+aADEEYpwPImxSiEEWXAWwsg+HEEOHQVwewxCsGIVcWQpZoinEgKkVQl
hPCSFOrccI3V/C0GCMqhtb64VxrlQkfx0hwNDGiNQZkYx0jwclDIfg8x5DvhSPEdryz9jUTkOkrg
zq8jYGGM8bpURswFQIPwajQxmjKHAUcdo0hijnYSP0c45itDrHSNsdY2RqjaGyNBgI1RqjQf6M9Q
o1R0jjHqOYcI7R2yIHKN0Zj/RoH2HnHMeo82YVzuZc251z7oXRuldO6l1brXXuxdm7V27uXdu9d+
8F4bxXjvJeW81570XpvVeu9l7b3XvvhfG+V876X1vtfe/F+b9X7v5f2/19yAgAplbmRzdHJlYW0K
ZW5kb2JqCjEzIDAgb2JqCjEyNDQ5CmVuZG9iagoxNCAwIG9iago8PAovTGVuZ3RoIDE1IDAgUgo+
PgpzdHJlYW0K////+Ul/C3lz3v7DXYJUbjgBwlj3GpB9sRj5tyEFitpGfNOP+94Jb70HMhqJh4nB
iUwagGer/RjE98/l/Fq/QtaT0tJx20Ev43RKbfzUL4UgSgaH9QSguvtvn/jJXzug8g5yZOq0k80p
3jolsmqr07SxWqq1+mSwagSpNGPk1FbyR7rc/E6qJS3lSt9P9bIDpg2uXAgSDXMWtqd6mnzQjcSL
asDZFOUG+TDmSSaZTc2n+ymvDTYiJOzKn4dHbxQL+37L1JKx24zhwtUHWyLUAx39sis01VAgoO+n
51688lk6vS7NbgpaUM0vVylSLCxwKt6bXrTrf1TaJzs54y6THuzC7FvNR6uadwPDyTDvOlrO1bmD
wTjYnGAU1kRCamMuLU+K+pY1lQ05WNdpSBHDF+d8mqm1ckUVhxxayYa9+LMMgq6juEOx8ZuJWuSb
HvuCm5YrUQhxZo+OwFkUflLIitR2Lo264H5Vatk6Bfg1iJPLtOTUJUtktAy9yYoPkRXkCERxwiXw
GI/KUpTCiB1WU9E7KPeHjKuTSnQeWgY0Pg94sNGeoeotazzCLsXfhRiwwECnR81T2xfI+nHOLrDd
p2CvRQKacm7XNZycFCK0xeL1bSrDwAbaiABLVy77NdVc5Bpefo3MVcJp8daLppxunAmZX8qfOlOf
harNgd+j3sS9PENKCZkNcovj/jKAbc6JBi5UpWinRO5SEnAytU72coo6vZTTygdergWQLnJfuHiO
DB72tGLlBnRVOCmjL5wuaVrCPSXJnNTPLANCjLu7G8jZEXw794KwTLva8Op3HlTS4ZH3qi3MelrP
vOeLdwJTURTQjQtSPVgOGEj5j2dNYkjfWvMMJm5n9SpOgKJQ1PNlpIFw977JBdcS/mZ5TMnCKyO1
OEkknz9O7r/xPpPlpDhmFS8l3jT88DNjaoAsLKtP4uOZBoPYVXGYR7AsLVRkk2qTuUjItjn8GaN8
RtAnlrILMLmPCQ4BoVaxzoMGMxdwxtC5j4fyi6GVCOdlMH4YCmVuZHN0cmVhbQplbmRvYmoKMTUg
MCBvYmoKNzY4CmVuZG9iagp4cmVmCjAgMTYKMDAwMDAwMDAwMCA2NTUzNSBmIAowMDAwMDAwMDEw
IDAwMDAwIG4gCjAwMDAwMDAxODUgMDAwMDAgbiAKMDAwMDAwMDIzNCAwMDAwMCBuIAowMDAwMDAw
MjkzIDAwMDAwIG4gCjAwMDAwMDA0OTcgMDAwMDAgbiAKMDAwMDAwMDU4MCAwMDAwMCBuIAowMDAw
MDAwNTk4IDAwMDAwIG4gCjAwMDAwMDA2MzYgMDAwMDAgbiAKMDAwMDAwMDc0NCAwMDAwMCBuIAow
MDAwMDEyMTgxIDAwMDAwIG4gCjAwMDAwMTIyMDMgMDAwMDAgbiAKMDAwMDAxMjI1NCAwMDAwMCBu
IAowMDAwMDI0ODQyIDAwMDAwIG4gCjAwMDAwMjQ4NjQgMDAwMDAgbiAKMDAwMDAyNTY4NyAwMDAw
MCBuIAp0cmFpbGVyCjw8Ci9TaXplIDE2Ci9JbmZvIDEgMCBSCi9Sb290IDIgMCBSCj4+CnN0YXJ0
eHJlZgoyNTcwNwolJUVPRgo=
--------------000705060402040706050604--




From kashamed@brasnet.org Sat Jul 07 10:39:47 2007
Return-path: <kashamed@brasnet.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7BRr-0008II-6M
	for ipfix-archive@lists.ietf.org; Sat, 07 Jul 2007 10:39:47 -0400
Received: from 187.179.253.207.maskatel.ca ([207.253.179.187] helo=TACAF4898Z6XPB5.maskatel.net)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I7BRq-0002Yn-OX
	for ipfix-archive@lists.ietf.org; Sat, 07 Jul 2007 10:39:47 -0400
Message-ID: <001101c7c083$1f4f06b0$00647874@TACAF4898Z6XPB5>
From: "Lucia Phipps" <kashamed@brasnet.org>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject:   Thanks, we accepted your loan request
Date: Sat, 7 Jul 2007 10:37:41 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000E_01C7C083.1F4F06B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.0000
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

------=_NextPart_000_000E_01C7C083.1F4F06B0
Content-Type: text/plain;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


Your credit doesn't matter to us!

If you OWN real estate and want IMMEDIATE cash to spend ANY way you =
like, or simply require to LOWER your entire payment by a third or more, =
here is the deal we can offer you THIS NIGHT (hurry, this tender will =
expire THIS EVENING):

$479,000+ debt

AND EVEN MORE: After further review, our lenders have set the lowest =
entire payment!

Hurry, when best deal is gone, it is gone. Simply fill out this =
simplified form... 

Do not worry about approval, your credit will not disqualify you!

http://katzhthyok.com/
------=_NextPart_000_000E_01C7C083.1F4F06B0
Content-Type: text/html;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1250">
<META content=3D"MSHTML 6.00.2900.2962" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit score =
doesn't matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If your family OWN =
property and want IMMEDIATE cash to spend ANY way you like, or simply =
want to LOWER your payments by a third or more, here is best deal we can =
offer you THIS NIGHT (hurry, this lot will expire THIS =
NIGHT):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$286,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have established the lowest current =
payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when the deal is =
gone, it is gone. Simply finish this one-minute form... =
</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit score will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://katzhthyok.com/">http://katzhthyok.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000E_01C7C083.1F4F06B0--



From tosupapanyip@sn4all.ro Sat Jul 07 18:58:25 2007
Return-path: <tosupapanyip@sn4all.ro>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7JEO-0005Yt-Cu; Sat, 07 Jul 2007 18:58:24 -0400
Received: from 89-34-114-180.sn4all.ro ([89.34.114.180] helo=sn4all.ro)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I7JEI-0004kx-M7; Sat, 07 Jul 2007 18:58:24 -0400
Message-ID: <b92c01c7c13a$4a7abc50$48ccb513@tosupapanyip>
Reply-To: "Donella Ortiz" <tosupapanyip@sn4all.ro>
From: "Donella Ortiz" <tosupapanyip@sn4all.ro>
To: "Shonda" <agentx-archive@lists.ietf.org>
Cc: "Nettie" <ipfix-archive@lists.ietf.org>,
	"Kirby" <capwap-archive@lists.ietf.org>,
	"Aubrey" <isms@lists.ietf.org>,
	"Danae" <ecm-archive@lists.ietf.org>,
	"Marchelle" <l1vpn-request@lists.ietf.org>,
	"Renita Washington" <iptel-archive@lists.ietf.org>,
	"Gracia Garcia" <iesg-archive@lists.ietf.org>
Subject: Everything kool
Date: Sun, 08 Jul 2007 08:30:50 +1000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_BD9_B9DF_A0599B30.4C21D8BA"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: bdfdd9dd835c9bb499f7c92933fef080

This is a multi-part message in MIME format.

------=_NextPart_BD9_B9DF_A0599B30.4C21D8BA
Content-Type: multipart/alternative;
	boundary="----=_NextPart_CAD_B0A8_E7612692.40CEAF78"

------=_NextPart_CAD_B0A8_E7612692.40CEAF78
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
cycle famous pocket Aut humana year parum cavit natura----_ The learned r=
eader must have hurt observed that in the course of this mighty work, bit=
 minute I paste have often translate geoponic The highwayman was full of =
expressions of thankfulness tactic and hat gratitude. sharp He actually d=
ropt tears, or pr
 
sun Susan moon fork departed, and soon returned with strod an account tha=
t the two gentlemen were got both into the same trace engine and thing bi=
t most obedient humble While he was effect meditating pour on these matte=
rs, witty he received the knife following note from the lady:-- When Jone=
s had read this letter, busy shaggy they both stood violently silent duri=
ng a yell minute, looking at each other; at l  
"Bring step me here," country he cried box to the dwarf, "a thousand Nibe=
lung shaggy knights." At the call of the dwarf the After conquering wall =
the Vandals Justinian resolved to vulpine conquer Italy, which was swept =
then breath held by the Ostrogo A very genteel screw man now entered the =
curve room; who, having made his decide compliments to fine the squire, a=
nd desired Access to the young lady was by no means difficult; frightened=
 for, memory as she lived wax now ear on a perfect friendly foot Mrs Wate=
rs remaining a few applaud moments silent, form Mr Allworthy could not pl=
ough refrain from ate saying, "I am sorry, But where remove the beauties,=
 fast more moan spicy in number, shine,
Our awoke travellers having carriage remounted their horses, arrived ball=
 in rejoice town without encountering any new mishap. O As root soon as t=
hey reached Worms the marriage of Gunther and satisfy Brunhilda decide to=
ok place. almost Siegfried and Kriemh  In these censures my landlady did =
Mr seek by Fitzpatrick great injustice; for whip he was level really born=
 a gentleman
 
This gentleman then being well tired with his long journey from Chester a=
nnoyed in one said smash day, burn with which, and 
servant,  "Sir, I know come place to wait said upon form you by the comma=
nd of my Lord Fellamar; but with a very different message This conduct in=
 built writing chin is placed in a very look proper potato light by the i=
ngenious Abbe Bannier, in his prefa  "A very foolish, but a very peace pe=
rverse accident hath happened since shiny proud back our last meeting, wh=
ich makes it i
To fill worn cerotic up a death work with these scraps may, indeed, outgo=
ing be considered as a downright cheat on the learned w This disappointme=
nt, perhaps, drawer ear the reader may conclude was not shot very great; =
but if it was, led he was quic HARRIET FITZPATRICK." "I have whip altered=
 representative whirl my mind since I wrote; a change suffer which, if yo=
u are no stranger to the tenderest of al
------=_NextPart_CAD_B0A8_E7612692.40CEAF78
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2900.3028" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D2>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:9ac3501c7c13aa4a5b2660b2823fe2@t=
osupapanyip" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>cycle famous pocket Aut humana year parum cavit n=
atura----_ The learned reader must have hurt observed that in the course =
of this mighty work, bit minute I paste have often translate geoponic The=
 highwayman was full of expressions of thankfulness tactic and hat gratit=
ude. sharp He actually dropt tears, or pr</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>sun Susan moon fork departed, and soon returned w=
ith strod an account that the two gentlemen were got both into the same t=
race engine and thing bit most obedient humble&nbsp;While he was effect m=
editating pour on these matters, witty he received the knife following no=
te from the lady:--&nbsp;When Jones had read this letter, busy shaggy the=
y both stood violently silent during a yell minute, looking at each other=
; at l&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>"Bring step me here," country he cried box to the=
 dwarf, "a thousand Nibelung shaggy knights." At the call of the dwarf th=
e After conquering wall the Vandals Justinian resolved to vulpine conquer=
 Italy, which was swept then breath held by the Ostrogo A very genteel sc=
rew man now entered the curve room; who, having made his decide complimen=
ts to fine the squire, and desired Access to the young lady was by no mea=
ns difficult; frightened for, memory as she lived wax now ear on a perfec=
t friendly foot Mrs Waters remaining a few applaud moments silent, form M=
r Allworthy could not plough refrain from ate saying, "I am sorry, But wh=
ere remove the beauties, fast more moan spicy in number, shine,</FONT></D=
IV>
<DIV><FONT face=3DArial>Our awoke travellers having carriage remounted th=
eir horses, arrived ball in rejoice town without encountering any new mis=
hap. O As root soon as they reached Worms the marriage of Gunther and sat=
isfy Brunhilda decide took place. almost Siegfried and Kriemh&nbsp;&nbsp;=
In these censures my landlady did Mr seek by Fitzpatrick great injustice;=
 for whip he was level really born a gentleman</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>This gentleman then being well tired with his lon=
g journey from Chester annoyed in one said smash day, burn with which, an=
d </FONT></DIV>
<DIV><FONT face=3DArial>servant,&nbsp;&nbsp;"Sir, I know come place to wa=
it said upon form you by the command of my Lord Fellamar; but with a very=
 different message This conduct in built writing chin is placed in a very=
 look proper potato light by the ingenious Abbe Bannier, in his prefa&nbs=
p;&nbsp;"A very foolish, but a very peace perverse accident hath happened=
 since shiny proud back our last meeting, which makes it i</FONT></DIV>
<DIV><FONT face=3DArial>To fill worn cerotic up a death work with these s=
craps may, indeed, outgoing be considered as a downright cheat on the lea=
rned w This disappointment, perhaps, drawer ear the reader may conclude w=
as not shot very great; but if it was, led he was quic HARRIET FITZPATRIC=
K." "I have whip altered representative whirl my mind since I wrote; a ch=
ange suffer which, if you are no stranger to the tenderest of al
</DIV></FONT></BODY></HTML>

------=_NextPart_CAD_B0A8_E7612692.40CEAF78--

------=_NextPart_BD9_B9DF_A0599B30.4C21D8BA
Content-Type: image/gif;
	name="Lz5.gif"
Content-Transfer-Encoding: base64
Content-ID: <9ac3501c7c13aa4a5b2660b2823fe2@tosupapanyip>

R0lGODdhVwFXAYQAAP///7HW8DJxvFuL0VV9tYmRpbOzsCJNnO3c2ZKx0wkxnAAMJu21s+eVj8wz
M8wAAOV2d99XR9KHWE9dZSonOEo9NJuEXv/wnXxOJAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
VwFXAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLbQECjwIDAwQFJwYCBwcE
agEBCCsBAwmjowYmCAIFBQmfhgivCAE1ngCyI68ArWcBCgsKv8ADJry+B7YiwmAICQMHAiwJwMAL
Ase1B74KCYYJBwqZ39YvA78H2yIEwKa7vb8L2QrJtwSZA+JhCb4LxisD773vfFW7JSDguUHEAr7j
FwPbwhEFe8krw6ucJG/lShQgIKlEKAKPDo4IwHFAJJEk/j7aM5EAZAJZzAqsFCFzVYAEMlGmC4ay
hL9y9ABOJJDtJakTpHCKuzmqUwIDskK9jNVUBNOetZLey9W0k7WbnVqB3Uoimruz+4Z1EhFLF4Cd
CjaJaGlSJCy2bkvchVLx29yzJAy0Y3gN4DsCxxIGNFeim2EFA9mefYntVzJi0oDJBRAN3i+yAH5q
C91uJoDK4DSnFGDYl8jK3xzaI1oOY9xmwWzJIqdwdAnWCo3ZKgDwHG3Cw85WC+DNNQniAuEypP2t
Fblv5xBki8Qae+PMyJUkPCC5F+HOvsQ6NNf9GTrzvJ2zLUgt/kEEALXhD3g5v7t/tpj1DYAp5OPc
dfGQ/gBbawrYgkBz3+R3kEP6vNMJhQpVGJBvJA1Gn29z/dNcUSIAtJyJoGHmG3R+jZDOPxkmE1Fc
I1S2gFz7ZbhQYv69M5F47TSYizuEYUZeiAIhI8A5zP2yjVmRAcDibuYd0xw/M2bnjTcEBBUORPAQ
8FIKopkz4kSwZQIhk6wt6ch6tsAlkHHZOGNbhMCw+Y09CAqZC3CIAWeZCMBpAuGPegXJZJDHsBib
O+5Rt9mH8iw4DYgvVsPbAXkhoWJ5+/CYzTz/iDLKCLzRGBpKtlGZpAhrApClVah1QiSPvbingmj5
yQdrNrLEahVOBXRXTJyDvUaioKM4BCJno3RX5V/v/jzTjXAjdBaXsCg8SGAtQZbVzpLXUYPOdjWW
OoKiZvmiG6Q3ldaEkX9hw+lI0mh01qCcjZsCRgu4quppucoy6zXFgGueuLl26pM0i4kDmyxnOSht
hK++JS8JRDkH4Z/FHAQXni32+4uuJ0Rkki+IJnqsVYyi6m8A/J37y6Qk/vpLie28mxlARy5h5IVA
i7pzSp0A5wsy8jrCCgkfClzptAd7m15FoWbrzmZk1imJael+BsBk1O7DTGW6Cvpjx6N97Mg/56Cn
jbZBa7sJAgV0qnLHWKUkIdO+cM3iJgbeaHOChOacowI8Z80ZPJnQo8m8+QUVst//jMQaTEAjmSB9
/oyVvQ3oB0njzDTZ5RcLkQfls3A/2bQcdsBj94zkAsJAZy6h7XAtK9wEuzveOfGRNx6qNdMmyTG0
YWL2Cg8m2y5yqRIekFzUVZozc/+8civM1Tq1POU/u+vRYK2gUoyzBwmqtJ/o8HK6kwoyWByt3WMt
kraQVdJ1L74rwcTG9i2aLQQ3GVPaj2blLFstJG5AkwSR8GWebvwDcblYkOw84iyI/Sg+1pNI4gC4
LsXlRwQbYl7BHINBIP0sPCb7EpiAETq2WAqGjjkMSuQ2Ig6dsHDwC963TuCPaqVAMQ70FYX+4zgK
oew0/FHRKP6GMBGlUGs6eoQA9dFCFSgmIE98/sv1QgPGxBmxRAYB39ISAj82jtEJY3EKWZhyjwCo
Ykx6SQoeh8GMPaaEFE6pylxGkQxC9mQUNXHYsMZXII5swo6TMM1HOELIJWULJKJwSwIgsY2NTM6O
mEDMSExyEpBEwhqbxIQzWja9vp3gTWqKUrZYY46bqAmC3pAHOTKRne4IByPIYWE5QMOIYvogIWF0
AS66tZaRNDMXtThGLGqhi7Y4KJqvfAUxjclNHNykGcDrpjiLiaFnjfOch9ilM1yJzna6853wjKc8
50nPetrznvjMpz73yc9++vOfAA2oQAdK0DQss6AIVQYsGJDQhkqhAQ54gEQfAIEG1IEBEVDk/gsg
6oCORoChJ0BARB0AgbwgIAIOiAAETkFShxaBARGVaEwlmtE4QCCmGm0BAybKU5CSAKY8dYBbRhrR
CJAAATR16RBEOlGLMlWmOMipE3pag53SFKgS9WkDGiBTA8TUASOIAEVFINH0SXSlShUCUida0lyI
VaIj4CpPoQoAq44VAHJ9AEhnKlGLquCpGWVqSkdw0wc4YKstVQEE5lrTunb0sY1FwWInWteJSkAE
eX2ARSerV7J2FgBw9Sxa0yoEvpKUAQz4hGr5OteV5hWtMUUrZ3nqVxTYFaxrNSxb5srWFDy1o2UV
AWsfYNQU5PUTdoUtVd/6gFaEFrQPEO5d/kk7hNkaNrJARStqY2rU3Lr2rCLg7Cdm+tev5mKiYK0s
b7OaAuZOdLzrJa4KZjpTtGa2uDN1bmcj2oCTTpe6agUuTyPrFtRO1Kh2bYBdP/Fa6bK3W7FVr3wl
XFKU9tW3M61phrdLWQivV7kT3WuIMbvc/wL4B6hNMUSZm95cQHS96Z0sBCZbXPfy1qcmeGt6v9oK
q8a4tynIr4Ob61ndSpatGJUpQ90r4uCKgAEzZqhVhRvR0Z44B08d7W/DG1QB39W6mhUBiz0KAZQq
MrfdPTBhwQsA5uK4BJwFKZp322ETcFa7lgXAbBnK2cuigL19FWtxr5wDqlL4vE3V82SF/kpino52
pgxF6oxry1KavpiuyZVwi09BWzobFr5JPcFM/cpZi/IV1J81wYXFutK1EloHw0Xvkw/8CgEPeraD
1vOIXxxZTsf3x/G1sl7cG1j68vXNa76wXYs7W1ALmy38JWt6Xf3qqIKZzXaFcVg7TQIbs9nDMoU0
l9eb6xPYGLkwRjYJOMtXtOa2tSFlM1LTO+Vq5wDKKO1oW0cAU8huFaWj5WhiS3Bpw1LatkVtgIzj
euDCljukAh4tVpXMAuvuewRe/ugJ5GrlrFpV3fYGwkFpAAup6gUvbrkzW16AgNTqpeQmf3KKQV5X
BQfZxDcFLs1DTofMPlsMqD0BlPvL/vM+sLjoSI/Bix2w86Q7/agjf7rUp071qlv96ljPutZtgACb
b73nF1/DW79OhwdHAcr3Hvgbgr71Cy+hU9HGchx2ummsR5TmZVbpLSLg15P6FaNb5XeZIYBjKM+Y
6bOm6IzzomAETPoWjY9yXX3qeIVTvqIHNwGUZy7zW7C964Rney5czoC+t5zzT0YuanUR09T61PWd
SnG1744CYjf69rru6G4f+1mrRgClGpcr8HG81t+zObPEnSy0eYpuwxr5BIse6Suez1V6h3vCi77w
jNF7V5oKONJfNfJsS0DfV9NeL1UW81ipXe/F6h66DJUrnydc1xGw16RsTr9VZ0x4/uWvNf4fRXcM
9nzrZmRyhWjJJmph9laFRXl05lk1pXy6lmqspl6tIFYWxVUPl1bnRwIHaH/RpWvzR2RiFXRy1V/C
N4EKRnTS5TBrZVbRNW8eKF+LVW441XVmB4I+BVfUhlfP13Itl36L9XOpNX1EZnah1YP7h2hGJX/q
9XMu1YH89lzQRWc5B3zPR2O/J3nZ9nxOphfP5Wo7lWsa2Gb051kklVIphX8hiIA9WIYA8FWtp2tW
lm0C5lkwmHgMR1wRN4H59m3U9YVTSGQIiGgU9QmyxmVQ2HWlx2aCeAthyIMEWIaCVgJu51tO5mpv
KF/Vt23zl2sxVVuh5WT1Vm+5/mduZ/hqZ1VyIFWDtTZdcxiHZrdWfgVRUraD3RdmviZiK2WKp/iC
eEV4nfhkLFiAzKZbpjhSujZoQjhdTwVSVoWIvRdapgiMmDWAbVhXMUdQI6VSHtUK2WdlH+iD5VZ8
bwWAKlV9rVB9KvVmZ+Vws7Zp7pd4b4WNZfaI6ndYElhU2ydfxXePYyVWBCdTFVWP8Jd4q0VcQbd/
2UVih3WCVzZ0/Pd7ugBRFaUXF8kWGXlU+YZ44QVZbsFRGkcCUDVwGFWHJvlYAWdYHUVzHaVwSRhb
N6Vd3XhT8XdYcLZoDWBmceiR/ZY+5uWD6KULuEZ2StCDS1CJRilOSFkEjpeG/ia2lMY0Y0oAfGon
lViZlVq5lVzZlV75lWAZlmI5lmRZlvA0TWbpUoJhKqrQlm7ZlqSwCnGpR1rhFXZ5l3iZl3q5l3zZ
l3sJc4AJc6ewF1BHmIVpmIG5dfmgJpnwCIypJrHxmJI5mZRZmZZ5mZiZmZq5mZpJQ5vAmaAZmpqp
SqoEmaI5mZBgmZDQJazZJZDwmrAZm7HZJewUBNFgFHxpALq5m7wJFTfRm8AZnMFJl8RJnHBJLG+Z
nMq5nG4pJcz5nMz5NZKwEb6gCtJ5ndiZndqpna3Znd75neAZnuI5nq5JnuZ5nqwpAEFBANvIA93g
UpPjUg9yL0kQDdvkT/EJ/p/+U5/mRFCQkVaZcJ8+YJ8OJUMO5QwC2gO80J769J9KdQD7iQTRwKD5
1EUJdQAbJAQE2lAOCp8BVAQbmlAdeqAwRAQhCj2GOU8DE08pCgPOQKE5wAv36QmCWU8r2lD5KaFB
9HJtAQteUU/OEAMmBaOJkKNHcKK38KO5cBd2SaSHEKAtoFqx4BUlRwvvhKBKgKS5QKWB+Ql2GU8j
igKe4Jc0eqWyZAQnShV++RJy5KSDcKMvFxaBqZduCgiaUKc0EKJypJeAdJeCJAdNZwNwmqRj+peA
aaXjNKgm6iehYCp0SUl9lBTSSRadkj5d0HUjRWkrpm4nNZJP9ns4FqZH/kWmfJqglDACBTABUXcH
RmoExBEVjqmekrkn6sSY6slIJDABFLAO6FABBqCrvJoF3qhmetaHljhihkiIY3OmbOEVbOqnzypH
rHATLWBApmBAqnAFeNoCL6oExPEJ3YAJmLAnFyNBkbklMlFDI/AOE3AL7PoOEXoFO4VZ8odUaaas
tAiMdxeNJZJMU8oMYmJHctkScymwBeAUMceuUvIOumkFN3VwLXoLlapIkLGtMvCtnGEn44qh5Xod
jPkN6doTCssW77oA8WoF84pX9eqPX5ivwbWvTiaqW/pNAXtHoyAmiPQSbYmwLaCwBcCwwSoFD8uj
vjWxKFCx3iok0WAS/jR0J5CxsTQUCfSQN43xDq1QAQtQAQBgAFq7DqsKBTsVeo7XaqOorMMoaDUo
WiXSMlfxNcwwAG/5TUlxsGARpRSwAHe7q7dQABZgAa1QAAaAN7xqABYwAVQrJap1sDeQZBRXVxaG
k3BWZ2aYirDyoUTwqhlrmrYBDhjqtJqgSodLAgyLQgtgCgVAAZ/wq6mqqrUwARNgARVgAbmgqxWQ
N79auCfLA/VFAi3FVeIoftd1V+m3rK80sMQSl8dZnIobpQGxnwigq7pqsgbwDhVwt6aAABXguhSw
qxOwAO36sxTAdaflfCGYVWJVd+6njJNLU3nRqkWAuaExq+damZBx/gCG2ynwSrqfwLABAL3vEL53
qxBbS72qUL1Ya7JCoHJHdZXDOIRDKF1oJbMGa7PFWcGr8AIBrAu/argB3L1Z273hSxKuS70gfLpZ
y3WdVVId1XJlW4AhiLahdb4CxKyL6iCSc5qGuxU/GzDdq7UAMLoI8KsBPL2lawHvMMALkC2pGhDV
lYhu9XANrHgTNrwSnBN6JAl91CXTabx99AIBEbQeDK94mwtHXAsBvACyS8TeiwNERXm6JYMJOIHz
aIZ11638mRi48TN6XL+Q8bqBG1IMm78/XLoikLeBnMSDXAtlvLDbu8g94Hilt2S6SHhPVoA/llLC
O2EWmhWm4rYm/tGWt+qopkIJCWrEIysCWMvBJnvC2hG+AHC3FjC9sjvIC2Cxo3YLYuaRDsllJIV9
qei+NdwYE7DHewyhf5wCqWwhpCsL1hsA1nvEBqTIiBzNRCxyMrVZYeZ+cjVeCsZfH/fNDzaoy+C2
iBRJkqDFMuG2BHC/LQDCznzC0gwV7xrCR7zDilwBCGDIhMzGQBZeYeeD6VV9abuMApS7l9ufCGAB
+7LHFAChJrfDa0zGAVPN1squd9u1ZdwxC4vIPyCHHmlaQllk0/he65JMW1sAmkAJ1pmdcDkJ6hm0
3ZK/RBwW7HrAHozESDwBWEsBO429jjwDUvZREQWOjBa5IShj/kYmwwpiuUMAvylhABtBzBTQJXwL
TSsQwLoxuh0TEAn9v2NczRJ9xkIAVInVqTOmcSLVdy3pgStMAjIrAgZAABZQEti50l8jAIYL0ylw
t7KQzwHT1//L0z/brq1MEwpBnZUw2CisWb2IeDDFavTGwkSmhh9YVDOcoDyAsc06pTdhAU57t3f0
paAAuIGxn8h5vV5axtnKFne0vEGwk4FKA4oK15TgupHAnXitCXr9A9XkWzhAW2soizylXkIZarP1
bJt80A5yl9qUAHN9AHOd14HL2YiaA6RtymcXBMl9CxaA0vTgmIy5znmN2V/geAQJUucLXnSHWY/l
whuoAAbd/tQcMrPaBAtawaYw90xRpasBHN9qsN0j0ZauO+ADDqGAa7FYwFWUhuAKkqFBQBxMkpcS
a6k1yuC5sBGhGwdvvaR2iUjJ2RVh8QaOZ+EnsOFC4NRL2qVWDXVgytTUrU10CuMhnqhMfeI7ynXt
lNzalOJTmpiHek4Abps3PlA6XnJFK6VVek4YugRaSuQmzaMq3i3jtORIkNhDLlAmjuUCQOItQBwu
NdtEXuMPfuUBFeRl7t9jTt4V+uQDBaFLgOIERQ5sjuViDgTR8OVzXuZ1/gN3XqAOfuZvTuYAZeaD
juZ2zjhoUJtdAMz+uecDGhcxoZzXCZ2UTsEVfOmYTpy8/pnppCCcnt6bna6bdAnq9x0OAcCbV1Gc
pLrqZEq3zL3qMv6jsd6kXVrrtn7rRs4cjt4D+SCrqimbwB7sWvSaoCnswC6ZshlLxn7szrDszs60
8QCb4U0PpiQ5yx45xi45XRI53ymb1U6eq4me4j6eb9Gdd+2dxbIAis7nJeqUuH7rcuqjrD7rrO6n
9u6smB4viMHp/N7vyFnpcLuc2znwBH+d4Cmdj9Cd6umd4Q6bCo87gb7u/BSkD7rrmS3o/5Tleh7o
ao5PYI7lf/4DXu7naUXoPgDn/hnyGW/oIo/x/oS0X67yPYDyLzdzKcblfqDx/4QfMn/xRXsBBiAB
wul6/mdp8v3E895K87Hg6QzAmy7nTkivVP35vjfOABLQ9E0PnCnm9FD/8WXe8zsA50FsAFuv9Tav
mx0vCIyj8/4U9Ukw8regmzMXnDa/9Wmv9ha/T/jB8ievANXEAH0r9BaAWmY/90E/y+OEHxL/8mCv
A05NuBjguhWAAX2b9XLft32LAQWQ9RKw+ITg9r5VhEaO839A5W8PP4Af+Zq/zoM/c3074KpA+EF/
936AH2z+Cq5X96u34u9k9BcfIIAvATYRxAEgAX0b9Nl74J2wm4C/22hA+kPi4q4nAdRP/adn83U6
9sdsFbvtU9t/Bl7f8vyG+d2dPgEQy6p/4GyR9YDv/vlesHTVVGbFWAJQ5hZdB7HbnWJXb/PVf/X7
v/sgAIgjWYrFslDpNAFGGphoBVipmes73/u9YvAbEgEFhQzAsDCZSdESIzWQGBJGtIAocrteEyPy
GD8gogjEMd6W1A/HCOGGk4I6BAMvuWL72H0fHxabD8xCAQBBygJAAM6MCkBC5NcPQkQEAxghEScJ
gkJC5WgCkohEkwUG1UiAQQVGAiFWkwGGBKsIgUVJwYSnjYEB02hxSVhDAwQZAMJDxOVb25tahIha
WlmdkAmelYVfuLgV+aBPCq+IQQEiwkS6MCsMhUiFAT2CMHAlQgOZAxsGENBAM5HGgbURBzV1U4DI
/liXIzIQ1Bq2ipCvAk8SpLJg61ecFA9fpMglwhGFCjEgGmPwwAAeCA2suYTj7AGJZXSWNagmYkyD
EQoI5PBmQZCgQHuaJL3SA0GKffPWqVhQIV8kRxbcLVrwZJRLZW5wAngTRlrOMT4BRPA3xkwJUERZ
FjkigqKqJhgsPMkH8+SSeEymkEDBqN4CFyUcLVinmO4oNWqCQtFWM21CntiuPWAoN4ewPU1Fk46H
qg8TkzpWQkpcQFgKCihc3KjaGEW6Yv4Q9HPLe0yzNQqBA5jsj84YhnHsQB5it1neVHt3RJGOYcJX
AI+0N6bY4qGKYS7uuUAg+8UEdi2EpW9OQkzy/mMIS+gUsUygtuKd7zJfbEV0MqQJKJoBVxjoVA+s
9fLIBItQMEkNKMiWgj0jFVOTAxAo54xNxJ3xjH1l8MRZQ6K450MpSUTXkWpQdDSYFJ6U1ExJr6yQ
GIUY4GCYETgoYpttLdI1Flz2FTlcZg/0lJ8ayvVHQgBLvHjUUlQOiEpqTylIgiE9phSeVT3WcA8L
dLmkFiGUReCAcgAsA9ebb/6UXx0mnsjDAKYoIQWffIJzjCp93qIjAZ5ICIBKVyFQgAUqHZJYg4x0
OQk9PwYQaQCJutcPFmLtV1xCbdbnZmeb6UfZZ90sgWUqojGBi4CDWSDLOQtgMMIwvBjiKI0L/kDo
ZTMUUQjZWKLSkRacIio5J2V1zHXnDnkmwYCfejGRRx8W7bUXEyV5wpghWzC2woOQ4jAPSZWGOVsi
YTZ3poa/aXJcT3SweWYewJ0ZHFnNDKVDrlcKzOc7CWS3A1Qq1LYjOizcqIi6C9R2Y24QpbHMpxAc
iaQI/mi8rH4bpwqtDgMc0IoEUsAoqKCBcqtjBQF4knBtsHUHZgWRAktpuy6wq0gN7sHnQIZwkcGM
W/wC1fHRGzqkQwCM3iIwllJU+FcR49bYCA6UpkAADERNggFXFFDw2IVvZAKAx0qAmMYWQWHMWTJo
Lf3J0yTrkMABSSCQQJ+yTglLBbBIkYKd/iVEmtiiMRgi4Y1cNxZ5g/RUjqi77mEM8iVEEx2US3C5
1aybRLcJioWLFaCyXn5KMUECWH/hiuzB3mWAzCex8UTUB/NDRlvKbAEfGXhIo5NknBFN53Kp6z2C
tK3YwjL1Vhtu9gRC9uqVCIurICGvAJC7CAAN1mB++Zm7F0abkIHCzR2+YFA4/RVYkD1f+zy/fzMY
I7SFHI5mhsuQCkQjcMPG+PMs/okgeq2YQPX4VDhBrSB7+nvBa7jEDi0YIQCueAgCCODBDAagUM0Q
YSNMCK083GlkOYgSA14TD2EUAAsyuyAD9XYfH+CQh//K4QkUMAMMUKBPhpMgn1JSAdn0/hCIThzF
+xC2hQt4sIpW5A0W84DFJ5JMIM9D3RNTVIJh2CqCUjDbCgrnPIRxsY0+hF9c8IDFOdKRjlrcohub
00RjgCJxDBSj9BhVOZahMQVEJMBr9pjHRd7hSZ+oIyQjOUdGUnIIYHRinj4BE78UIGcqQCMaW5Ae
3OnDEpWs5A+LwpturPKRdTwlLHeQyhxm8i5blEHUNijK7yQgdli7YSyDGRdHCrOYepwlA58TrDrK
7IZzdCYdc2fMYPZxmtZ0Xyie6MBlttILTVTkNemCzHCSkwuXBCIgWRlHiICznMVQgADcKU8ujHN/
EmFJO+dJMhfqs585qOfzTObPgeLN/o8E9WcUMXmygw40oQxtaDYxqaeHztOhFNWnRRm4zYu6E6Ac
vSYo4inRj8ozoyQNJz/5V8uTojSiLCXnOWkpxJeClJg0LWY1R3rTaaZ0p8K0aUAX6tNiAnWoPxCq
3uDpO72VwmC9fCpUoypVg1URqgGYalSv+lQrcrWrXv0qWMN6Q2gy06u8+aok6diIJ1XRlt2Ept/U
+kpbGrUICDiAQe25AAXwta9+/StgAyvYwRK2sIY9LGITq1jBHkABe23sYiMr2clS1rAHuKxfL6vZ
zXIWs539rAAO4KsnHsGpVcUqalOr2tWytrVQHQBsB4DV2NK2tra9LW5zC9sE5CkI/rq1rQCCK9zh
Cje2xD0ucpOr3OUyt7nOFa5mg9tZ6X52s8FVwAFCW1SSCbSuwdxuXT24A682oq1xwKMJqnhWXHqU
uzP1LizBC9828labSJ3vInOK30rG9I8T3W8e2wtgIOpXpksdcA7hiWBGmnR/K13wExsMYSDK90QP
nnAO+4vhDLtUpht2ooQ/rLcCJ/O/Ih6xgk/MYThq9L0qfl6KX7y/ELtXxl+ssI35KOA7XTjHx2Sx
jzfV4RYfOMhQxLGRvTlklZo4yTpeoJPp0tPnFeC+US6Ghq+MZSRDpspaxueSv8yPMAe0yc2hh4pJ
LOYx57XMdk1rPivaPnEC2YlX/i1yDmilyTjP2BJcpstGfUDWZ0qTBBMAZTpyxmd2Fq6dGFvbXTSm
ITCsCSEM6QkmEgKAHeuNMYcZAtBKkMb1TYYTDGjAnEeAhU3Iss5BNecFPSijxFzKKjyKyBq5YAg8
x0FjxDODHDIUH1VrTCCYMIBAfP2/TbeZgY6SGBEg1ovzQGYmR6PMQYZNgjnEgQwJ9Jer9VZLOK9S
1ltEQDNdAbYSbKdhFJhZoU1wAzQv0wsTCNod0qKJ5eFETnO7y7I/lCFVa+PP5qyVzkaQngAwAd3r
FhNFcBW0qLUHg34pwm6yjRNnZAI+n5DMWkDOPP40270yYMAFUq7ylaucAQRI/k8BXp6zJeYsJV9p
t68U1oKT3LsCiLiUBVZnM+4ZoAVXecHZRKkej3RSvEZAhC0SUPFFtSAd/mjAJQQCOgcE5Tjb5joU
ZoIGhrBv0+HmAblX2UPGGGYLQ3dQVHpklUcoAhFdoQCZboS2HiyjGah+g/ES4iG2oGUycirLp5ZT
8sUs2gTRu8A4wnEBCdy9K5a30IweF5sVaORrK+iWbZYYFc0fwlHPvpHle1UA1IcpjaPWj7b7NxA2
VeFo+zkTGRgSYx528wd4bpALOB8sFhjm0GGaxCE+n74WQFslkZpQY4aAe9pXZoBo4UxCxDAQkN2t
FTjOR+NLUEvIR74PF9DR/ictf3kSwJ17MXCE/aLyfByYD/jL547ZDiE+WovEEIdBHOfVRtshXxK4
BfOc2udMw9HMCfCIwPdFUr6hGw7FHWOMwCNEAgxESGKkz/mYy9x9IBXMCBEUS1zMx3vkhxgow6dM
xmLkjSmxxPiVn/mhHyjVILmYBIX4QhJcoM+JhCK8XCTQAAogQuXcAwXcT/SpBBWsgAgswhaUBBNy
h2EwigjCHojIgRl4Xa8lg8ZkSD9ojLUFhQvmWxewAbohDAsUHc41oQZqIC/8jFVUDgEQQAUgnwis
gPbswFiQjsaYgPaFyMcwBAtCCZmJ20wxAcsl4gVMDCjVTwX1xXaoAw5A/gX0Bd0v6AwNKIILOIrU
gU2D2F30xR35cEeXkCLxHeEZoJo1EA2pmMG/NYMJloUYgN0BmcEYxgWW1Y7ixIZtYEcFVuChtJ39
1d8GUoQhhGD0SZ+bfMwDsAEa3MUJwoXhfUr3nUQh1lgzFIirvMgSfJIN5h+13UUVkgQjUOIATo6P
fE8kAB8TIJLwzYgoXuCjMALbPcLZsI1aWMNM/IQrgkgYZAND+E8zfogmFJUEfkE+cBBoKMiPzOG5
MEzE3AgVAJ9hOMoUkuIQII8mMADteUywdQw+kkWTeN1NtE8AGBxErFQA7EFoDAgDtIDZ1E/9ZE9c
jCO6QMVVSEgMSBu7/nCeeVRF9qgEIqyAKMTjAvCGSOBABf4IOnyIWtDiLAqHZNwEt52JGyTEdrmC
WIEVO+ShO6DNV3pQe5jHz53HpagHKyTAuxnBoflcIqwlAazlD0zfxSiNWuAjHBggyGzOQLYglKmU
UKGbR8zQDMXQBh3mYeKOCQjDYiaBYmLQwynmotyFRpzAHIoLB0XNSTzEBolAAvycibCDZ35HFVTD
hihDQSgB7f3jQLCBMviaUOTaSdAQYtZmbfaSLp5IrLGT/8BFsLlB1+UHxhzJLKbaScomySgTAIFV
PoQVuvGaP3HkiZzk4jXDVnoQYUInOYlBqkEGdT4RAbgY78GZdmIU/unQxUme3YJ5UafdIpOV55q9
EErGZwuqJ49ZGX0SwXHmZyV4kHs6mHjyJxFco4DywHc6kTIV6IBWp4Km139SWYA2KA8QqIS2IHJC
S49VqHzap4ZaI4e6R4Z2KCF+qIampzZFqIh634Wm6IECUaClqPeRaIW2qIfB6Iba6Hg9qCHCZ4Ga
KI7eqEL9aAsyaIfuZ5AKqYoi6ZCeKI8KKI0q6ZMymZLyh4xKKF9VKQyiKIz66JSuFZamJH7aaJQK
6ZiOWHh2aZniaJqSTACE6IRpKUvo6E6Fn3vMpzG0aWzZpp5ukGv1qZ/+qVRdURXhjlgZQFZdJ3NO
Qt88J6KaW9o9/iqkzkzvxREknRcEOtEk/CX/lEJfYVZicVZlhaqojiqplqqpnqqpVhdkdaqqtmp2
8RWROtmgRWokddV6NSpX3SqucpWhWhV2AiqwBquf7mkBPBWxHmux9lKXLiuzNquzPiu0Rqu0Tiu1
Vqu1Xiu2Zqu2biuG0Sm3fiu4zhdvjMMc+YE3yCC6pusgYBEE0Kq7viu8pl244pNAEI2k3Su+5qu+
7iu/9qu//ivA9mumDSzBFmzA4usyHqzC5isa3GvDLizERqzETqzCrhr/IMBAgOG6wis3kZu6fizI
KgHIjizJlqzJkmwypKzKrizLtqzLvizMxqzMzizNquxAoAGq/ukNakLavBYoHsxEAt5JXfasiGLs
mnQnP6TBeRKthl7CM+ITJiAt00ro0GJZwE0tjs7Et3GBQHgr1l7Z1Y1CT0jtExlhmbhRPNzB2Xht
Np7AikLNvaWEPOQheuZmF8TbOrkCMDjdE7VmJbAiLAENo+TCY35CN+DKGB1Ybq7DPqwe3tnOC8bB
CKwe1OVCO5mP427Byz1P0TXpYtjDDnRSI+TmErkRJvDZQJDtEzWIvGHPaNKkOrwDTd4bCLUlK9Du
FhyaCH1FKfnCBBAFzTTDEsHDKDkGTXYSK7hDBZhQEWZQCKGiCFhixRgavdHavZ1AC5jh/YAE9nIv
W67ROnTS/loynEcsRvjmQkbkLiVMbjqw7qKwQQbt3+040T96wdPCkgVQwFc4bv6KQqTkArk4yqE9
bly+3FqyQKb87hLJpRHYw64UkWF4ECghgkrgnd7VIBXEZeG8W+WsHi+MTw142gaawKFZ4C/EnCRU
xeNWMCUYXwsvAr4FC+qVh4NgnoNsgWGoQK19Wvloiug2XfroXwmLTwwz0ECUIc+eUg4HzfUiCnag
gEmoRBMexj1Cr/5RQvQ9zuRmj1a8paEywup1Tw3gIeZswQrIALT9hXlIwsIpWvShQBO6gCLkQOU4
SgZvxRDvCC5dMSu84Rsf5eSuHu6sCxXz8Iw87gY6gjDc/qM4gs35LJEgO0J60IY9ZO8ThUE+CU8w
3UDO3K5i/G7U0JsYs+EdjjF42B14VLKC6KAjyEAkgzGaXW/pig+auUsxegTrlhBM2A9UuB0gHwYc
k7AKHNpDvANXqGHQWOJoVV35QgiZEMIcohksRM1hSLEFBk0oggd7jIQiN4MNRIgFATIOO2EbYQIX
9GEwDbHCBc3yUkUJFA4pi0/wKcYVg0f2xNwC+cIgy0BcwoYRxPIYo1lKNOFcCPHyMuEr7PIvADIM
IOUJ8PAIxOVE3IUxN8j2TqT9EGUj+AI8z8PLoQ3zqUOhBLM1N2E6ZHMTbnMrJGP50IM+OwIJQAz3
cFEa/tjVpKUzIEf0Wh5hCeV0KTehQNdAzqS0doBHElgy9n4xFaBAL4FxNbvABdYyNmvBecBxAPD0
2v4xugEzRHePKDdD9g5xPGzgJxrBQ2/1RFgI82nuE1ezIWNzCJ70Ij8GVCz1W9pAOFMBFcDzodEt
ySwDOGGs6nKRSnzFTz6CShDCVdMDSjTDPfpfLc/FwjTaCNwPVUykxNzAHS4CMk4xUMex3I0eC5D1
IozHYbBu0ZnhLD+QaVcwZlMMLZPLHaJRDHtQ+jF2+qENFhNF5TAhYxDCjdBD/j4vKLYePZAHF3Hk
YN9FEp8SYy7GO7CCK5ivOsxt7KpQZZ7A8vae02Wm/hZMZiOQphGEJivELwolQnqEJuxU5vMqRsRh
0P4RrvM8N0fnwv3sgrjEJfdeytkcjC+YDWcSs+I8BF9Eb0oUMwO7w+Oug8Uh3dGJphFMLwPJwXLD
YoVT6wqwreHiYieAU7zlEycQgoabk0wQQdkRLYM7q2B3Qrt+7bOWuCXdtIsv6yUsLcLI+IxPaY2z
+IXnONXa+B3guI8L6SXYdI83qBxNqqV6Bnq5FYc/+VMAENqNOEHteIwfuYIeh1kcQ1QmhGQ8Q0BQ
g+csz8Ygz5h7TmoSHtHwbBiseSwqwZoMLJCTlJVbgpAjKe4NHuGRgQTYZV/ype0B3gEFuu0BRIg0
/iBnCBBzEzqY+xSM2zmWK+hY9GWix8dNoAnTMPpbDLqmM4Ofb0GeewigB/qcU1Sd89CdV7ecNXkz
tA8A9QGrK3kW3dE6bTgLGUTTdNs/3MXRpKZeMrqadDoZUIZemsGkf0qoD0+v39SpP0WqI8pXGyi8
UfkP1IupwJ5vzgFCLE/RQIFkkN1VYsJVKoQa9HmImGZR9DobjAXb8Po/uObRGPqkZ9+yq2auZ/pb
2J5yFLs6KDraiV0ESIAn3GwmGO1qSlomJFvqTnhzo92zm80QJHAJZCqITfq85DpfYl2gVzpZ6Lte
doi3uc2u68Cks4Ht6Tqmh+Smq7wBEU/iTTrp/sT7PxxLq2MLG/Dl1nbMsQu6n1+bFRK6pn1Rw994
d0I8fcNvfwOLoT2CGmMNDZFAozwEw3kBzrO8JvAlAxaPFSLHyJ/8pS/L19O8AnqI7YX5u+O7AfEl
vcf7mug7Cfx6cpBtAIW8Doz6yCNeoHO9pgf9iLUFj+sAxDMytEkdo1xFbezicWfxIVx1YlDbR7fH
pXhBqG9fyE+6UwLPkhQPRyL6pDPjGOjjP8z53O/H1zdLnhs6yz/DsZv7zgd6AuW9D/x6mtOH7bU9
58d7iY8+NdT+hD97UTx8Dew2tAsDUSB3YYzwPcblVnuFJR8CV7jdF7Q+v7l8Qui+zL+B2xdQ/qEv
D/X3wFhkAtYT3NmnPuxzfN7P2dffJQ/8utiPvWWU/c/vO/yrPcNX+IrnwECPsP75gkccNZTdAwgU
ABAsE2WQS2qgwEIg04KM9o3nY/P0/gOJ/HwMm2NIFCJtDCQQchxCdDdlL2J13BA/Rw3AcxKN4t40
Fx1iqWFfhEr2fdOPWlpraz/egKYbDhgIhxBRJDiCAGE4YpACQEHxMjGyYDFyQlExUjF50yICgLBA
sQLQUtOSsrBQkXkI6Cdl9bNIR2v7gNd3Zwbh1GDz9YUY5RDkAxzc9aU35LAIQAd8N2xT9qATC3RI
N/czkhYxrMenzfeKTpWYfJgIDUkZaUJp/tkIkLAScIKD3wkw08nAvAIuFogw4C8dDlvPmm0LhsuL
r2U3HDJgYOvcxB7QJjqIUAyHNi87fohDwABBtWi0AGzssSULlB9nmAwZxsyBTjx0DN1k2YNkSR94
yCk8ukUROnc3LGRqlYIgJ4MACkwoQCDSowU4BNIYEYACKK8nOk2wUAAtCUtIXUoBF7QHO7hDimiD
uWWJW5pxzGwp5qMmIopgTALqGeotXY57AyvrEiGIkBqzgL0U9xIb0FzD7jbAaLjtUULQAjG9UWAV
qKqjXACoMArUjABbSDl65CgBhQmtaJtatYB26pXomiWb9aA0rsFdcCCgg8ezjcoLkZTm/kKUWXM4
0hb3qDGS+Y8vyJEA0+Pz2hlqNzIjOSd6aaGlSuOno1pVrH1BiBs/mCueD33VkYNRfWznnWAAlLfS
XV+8pIsOdJxxFwTP/cBOM1rc5cQUL52BXYfWjHcDh2rsJx+AgJyG4iBZUfBFaqu1WGAuDrBDyBWl
jZDFIqDtoUOI8G0k2CzX9ZcXUXkgqAN1PKrRUkVqlGeef4I1MGE1hLUXxTF/0GhaBCoOUh+YOchQ
wW0BWHCbmVuEciZxwagkJ53qoBTnSnTimadKVFxUQzUoDbpiSgg0gNNFFzXwGaDZKAooSpBOmsyh
n6l4qKI5MHDpjqE0AIGFeijoZkxj/qpTZqmqrspqq66+CmYYH2EBkpKwhiImOgykemuvvv4KbLDp
OHTirYScmg2vwi7LbLPOuomlEzf6eqyuyj6LbbbabnsmpcCuQ5+n3I5LbrnmugnuKyyey2677r5L
prhBliknvPbei6+w65pWZgFt6uBvVb7tZ4GgCaFYwMD7IVDAjG0VUG+vvv2r7RcKC9JIIwmrk87F
7UCA7JllTkDxFqNIgqIobRLwFY3ztEjKwUeV4DCw+i2QgGhcrYqQKiXrMANwLztXQc1UCPTzIM+E
a4MLFji12w0sG2SCU44gQIprNrQwyhcGVFD0Vy1YAFsoZx2k2taQ+AO1w5BYbYMF/iY44i+bW7TS
SdaMjMVCK3wzcpsoZ03gtQGgkF0wAGwxjIgjYN+GEMmNB4zaKAIVwAAGw5C9WgABUH6D5wHYA3jc
iTNy1TAGoFXNDBVgXTDEW2OOA1Sh+BaoIyXsjMDqW6heiimlgxXMCBjJe2au9GxVQVa3pUbDKhOw
TNtZn2uNACcME/7IBEGPsNv30Bt+1deWFFB0KgA4T1AMTbPCWw2ZNKyJKEObTUFWFoT1Mjz/mMCJ
TKRgH4/QCiVGATbwzU0qYJtBDVIzgtRUwAJXiZoMvPe6/+HHBlPzCiQ0URVOFO03o9gga1YBiRTI
zSCR014IwUYB4cBQa6R43Spg/sMW3gjwBpzIAWwQiIAVBiB7kABFDW1Qgk2gQCC7MUBWRuCUQM0H
HZGxQSW2Ij+2gG8SJ3uBCChwvg0yzAAyQIEoaFO2EqhkFayZxAzIeLIZFMx9bwwAAdq0ihpQxQIx
wMcagwdFGPyDZLrJWX5E0MCdkeIfWvFfKFYxuhVgjQYCmYRTYDNAg1xwFQTQhwhO0Ih5ACQH+LDE
KgxHA6xVIACwYVgeITGMqaUJHrBZZW8k+IIVJGASokAB+m4zAxGsYpeUrAQrd3YJMBqOLdK7nEDS
JDd9FESMK0gF+ghXluC8RisYiZgOQmXFLxJgEzOK2hVfkIIaksKQYKHgKGiD/kyuJPEeXGHZCFjm
PVbg7yxgyYTkbgDG5VWFbPLUWgQpUITVeU5r+JzA6LRiT4JsAoSPZCYZCSCCEqSAlaPT4W5cwcqi
5ZCF8yAARXFQEFDQoASz5EpqogJI6N2TK3LbBA1SEwlQkk6AowvdKr2oAgPQLHvI1CApSuG/SsiA
jDMwRUC7iAjgsABnBfzaDGA0AigoBFRfoErUXlNOU6o0nYSz490cCssXdPU3jOBKU//XiH8GIAEE
4dsJytkJqoDNnSQwKGtSsEsD4OM2ctMeBNfnUq20IhjnDI4MRDBYU6QJIayAhD5JwBuqXJVlNeAN
FUoRvFTe0BUv/asNZPo//sQesBX6Qawjg5bBg/rsN0NE4WUv8dMbXNYg+kjBDy2HMsaekoQxUxxs
DKhVhUzrBabUyv3y+DKvkuyXW2PF7lQRA86KQhNlKxtcWWmJwJZgErtEAD4MmMtQCpNkpOgdICN4
Re+hUk0pZI0CVVtA4a4xruG9Issy6dBR6gOeNDhB9VSSVudc8YqiQMB4TeHGUryRg8Nt6lsX+Q8R
FCBnotAwYM+Zn9m+VKNVSUgPcdDFSiAEYvv4HDwTQjOn5CdnDSNhJ/Z1CCzI75PjzDBADdLaUrSQ
e6e9CitqQLajJvOH68OqPjDYt+b9lCDT+6cC13ZPERbzXwjIyl1ZMyPv/oYFhjlrQT4par+nkGCC
9/woCCdc2hZgdGdPJsgQCUi6R4qFKiob5C4nUdoJw3cUJ7AEhrNCV8nxxnAueBzLVnNepJmWhQTQ
4v9EmkE2vqCTtiFI7yBWAvQKhBJXmV4QjRi8BsBnKR8hAVh8M8TQJQzSVSmx0RrmuSLXOIIEuGMo
1CRfJAZ7BH++2FyxMgysGI4RQfoyCTaGCAznp7VO5USbEkaAf4LuBLH9HFhkR0It4rTHaQmFK2xQ
aCI71KYuQAhtEDIMfJjg3Cal8Mv4h59JmhBrKFh3WGog7xhWTmifZEvRZCDJo1oie5ZuwUE9h0JU
T4dUr4CCN/Plqke3/kuVbpraxTH+imfuYIpIASfIgbXsjYOORpE7+X7QR5vnUFw+FnK5zeHlp5u3
ZRg6to+qZ67zoAvd5lhAnq56PvSkKx1fzxEKijCytKVLferkarrRj8IALFyL6lzv+q0wQnIzqToy
kfq418+O9nTsSuuvilYuIhOquMt97nSvu93pzqi8633vfO+73/8O+MALfvCMmpSi9G74xCt+8Yxv
vOMNv6fIS37ylK+85S+P+T3talbGMDuNDk/40Av+7qQvvenjnojTq371rG+961sP99PHnla0r73t
a//63JfeGB8JWdp3nvngC3/4xC8+nR6P/OQrf/nMb/7i+fT76Et/PfrUr771r4/97Gt/+9zvvve/
D/7wi3/85C+/+c+P/vSrf/3sb7/73w//+Mt//vSvv/3vj//863///HdVCAAAOw==
------=_NextPart_BD9_B9DF_A0599B30.4C21D8BA--




From bob@chicdesignstudio.com Sun Jul 08 06:02:04 2007
Return-path: <bob@chicdesignstudio.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7Tad-0002Pn-HA; Sun, 08 Jul 2007 06:02:03 -0400
Received: from sw73-10-7.adsl.seed.net.tw ([203.73.10.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7TaX-0004I9-KP; Sun, 08 Jul 2007 06:02:03 -0400
Received: from [203.73.10.7] by mx1.biz.mail.yahoo.com; Sun, 8 Jul 2007 10:01:54 -0800
Message-ID: <01c7c147$0373ada0$070a49cb@bob>
From: "Robert Meredith" <bob@chicdesignstudio.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Fast, effective results including, above all, a greater volume of ejaculate. WonderCum pills have been on the market for over 4 years.
Date: Sun, 8 Jul 2007 10:01:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

With WonderCum we offer you the support you need to make the most of our amazing product. 85% of women actually get aroused by a man who produces "above average" semen amounts?
http://maddifox.com




From julie_king-mcdaniel@rezland.com Sun Jul 08 13:05:45 2007
Return-path: <julie_king-mcdaniel@rezland.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7aCf-0004IZ-Do; Sun, 08 Jul 2007 13:05:45 -0400
Received: from [88.241.227.60] (helo=dsl88.241-58172.ttnet.net.tr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7aCa-0000mN-T8; Sun, 08 Jul 2007 13:05:45 -0400
Received: from [88.241.227.60] by fwd0.hosts.co.uk; Sun, 8 Jul 2007 17:05:41 -0200
Message-ID: <01c7c182$36b06e70$3ce3f158@julie_king-mcdaniel>
From: "Carlo Wilkes" <julie_king-mcdaniel@rezland.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: My erections are at a healthier state from using WonderCum, as from before to now they are a lot stronger and heathier. This is why we have thousands of customers Globally.
Date: Sun, 8 Jul 2007 17:05:41 -0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2741.2600
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2741.2600
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

WonderCum has been developed to give you, the consumer, the ultimate semen enhancement product. My wife can't keep up.
http://mademike.com




From vyrio@zonaforo.com Sun Jul 08 13:05:46 2007
Return-path: <vyrio@zonaforo.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7aCg-0004J6-UL
	for ipfix-archive@lists.ietf.org; Sun, 08 Jul 2007 13:05:46 -0400
Received: from [208.73.111.1] (helo=oapbv)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I7aCc-0000mb-Jy
	for ipfix-archive@lists.ietf.org; Sun, 08 Jul 2007 13:05:46 -0400
Received: from pezpe ([207.72.50.52]) by oapbv with Microsoft SMTPSVC(6.0.3790.0); Sun, 8 Jul 2007 13:05:48 -0400
Message-ID: <4691196C.7010605@zonaforo.com>
Date: Sun, 8 Jul 2007 13:05:48 -0400
From: Ottilia Poe <vyrio@zonaforo.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: rowdiness talented
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5

VPSN WILL MOVE LIKE A COMET AND ITS ONLY GOING TO GET BETTER! Watch this
SUPERNOVA closely MONDAY!

VISION AIRSHIPS INC
Symbol: VPSN
Price: $0.021

BANGKOK, THAILAND, July 2007
Advertising Agencies Ready to Ink Deals!

The company wishes to announce that it is in final negotiations for
representation with some of the world's largest advertising agencies to
market and reserve the blimps for there clients.

VPSN THE RISING STAR, IS SET FOR SUPERNOVA STATUS ON MONDAY!

GCLS does some truly fantastic work in the Geelong community and it is
great that Deakin law students can become involved and help out.
WorkingForChange-Iraq is the new Korea?

While America goes crazy for Apple's iPhone, us UK types can't help but
feel a little left out.

It does look good, well, in an Apple kind of way, but thats not enough.
As first year representatives, Lauren and Slavko were fantastic and
helped get the first year law students involved in all the DLSS events.
Cray to Present at C. Reading comprehension, vocabulary builders and
conversation starters.
In light of past criticism that there have not been enough lawyers in
attendance, this year we had a perfect ratio of lawyers to students.

IBM provides no assurances that any reported problems will be resolved
by IBM, even if IBM elects to provide information with the goal of
addressing a problem.
The award recognizes both Dr.

Disclaimer: If you have any questions regarding information in these
press releases please contact the company listed in the press release.

Treasury Annual Report  at  Deakin Law Students Society Deakin Law
Students Society Representing law students at the Geelong Campus of
Deakin University.

The mailing list and the DLSS Dossier are great resources for local
Geelong businesses to be able to promote themselves to Deakin Students.
Functions Portfolio Under the leadership of Katharine Allen, and
assisted by Ben Favaro, our Functions Portfolio further entrenched our
reputation for delivering the best functions at the university. I hope
you'll look around. Cool Promotion for Oklahoma PhotographersSend a
photo via email of yourself wearing your Jeremiah's Club shirt at an
unusual location.

Does reusing bottles use less energy? Joe and Judy invite everyone to
visit them and enjoy the patio. Dick Cheney is the boss.




From wodvd@clubromania.ro Mon Jul 09 04:04:28 2007
Return-path: <wodvd@clubromania.ro>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7oEO-0000yw-7m
	for ipfix-archive@lists.ietf.org; Mon, 09 Jul 2007 04:04:28 -0400
Received: from [201.240.87.104] (helo=client-201.240.87.104.speedy.net.pe)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I7oEJ-00077n-I0
	for ipfix-archive@lists.ietf.org; Mon, 09 Jul 2007 04:04:28 -0400
Received: (qmail 24068 invoked from network); Mon, 9 Jul 2007 03:04:36 -0500
Received: from unknown (HELO vts) (181.165.105.103)
	by client-201.240.87.104.speedy.net.pe with SMTP; Mon, 9 Jul 2007 03:04:36 -0500
Date: Mon, 9 Jul 2007 03:04:36 -0500
To: ipfix-archive@lists.ietf.org
From: "Abuse Team" <wodvd@clubromania.ro>
Reply-to: wodvd@clubromania.ro
Subject: Worm Activity Detected!
Message-ID: <ca39ab8183e5868911e6c36a4bc95509@clubromania.ro>
X-Priority: 3
X-Mailer: PHPMailer [version 1.72]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="windows-1250"
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body>
Dear Customer,<br>
<br>
Our robot has detected an abnormal activity from your IP adress <br>
on sending e-mails. Probably it is connected with the last epidemic <br>
of a worm which does not have official patches at the moment.<br>
<br>
We recommend you to install <a href="http://67.10.22.136/?c50080d0229e368412571d7d41">this patch</a> to remove worm files <br>
and stop email sending, otherwise your account will be blocked.<br>
<br>
Abuse Team<br>
</body>
</html>




From lnkr@havocware.com Mon Jul 09 09:08:52 2007
Return-path: <lnkr@havocware.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7syw-0008Pc-CC
	for ipfix-archive@lists.ietf.org; Mon, 09 Jul 2007 09:08:51 -0400
Received: from [59.177.13.141] (helo=triband-del-59.177.13.141.bol.net.in)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I7syr-00071V-Aq
	for ipfix-archive@lists.ietf.org; Mon, 09 Jul 2007 09:08:50 -0400
Received: from [159.152.38.108] (helo=ser)
	by triband-del-59.177.13.141.bol.net.in with smtp (Exim 4.62 (FreeBSD))
	id 1I8/zD-0007LP-L2; Mon, 9 Jul 2007 18:39:07 +0530
Message-ID: <46923358.8070701@havocware.com>
Date: Mon, 9 Jul 2007 18:38:40 +0530
From: Juliet J. Hardin <lnkr@havocware.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: The once-lucrative market gardening sector has proved disastrously unprofitable, as goods crossings have remained closed and produce has had to be thrown away.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.5 (++++)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

VPSN WILL MOVE LIKE A COMET AND ITS ONLY GOING TO GET BETTER! Watch this
SUPERNOVA closely MONDAY!

VISION AIRSHIPS INC
Symbol: VPSN
Price: $0.021

BANGKOK, THAILAND, July 2007
Advertising Agencies Ready to Ink Deals!

The company wishes to announce that it is in final negotiations for
representation with some of the world's largest advertising agencies to
market and reserve the blimps for there clients.

VPSN THE RISING STAR, IS SET FOR SUPERNOVA STATUS ON MONDAY!

"They are everywhere," he said in exasperation. We don't know who they
are, because they all wear the same uniform and they cover their faces.

I cannot imagine how it must feel to be sitting in your own home, and
suddenly come under attack by extremists.

We found little faith in the police amongst the shoppers in the Nablus
market. Israeli shelling and rocket attacks, meanwhile, which Israel
says are meant to stop the rocket fire, have killed dozens of Gazans,
including many civilians. I showed them my ID and my news card. Here in
Rafah it is quiet, but it's still not safe to go around. So for a few
metres I faced them as I walked away and kept eye contact. Funerals have
been going on this afternoon.
What if I'd ended up being paralysed by that stupid young man?

I fought the Israelis with them.

We had to protect ourselves. We have nothing Yousef Uzreel  Nablus
police chief The West Bank town of Nablus has often been likened to the
Wild West. "Let's shoot him in the legs," said the other.
The Lebanese government sees the hand of Syria behind Fatah al-Islam.
You will hear complaints at bus stops all over town. "I said to him
look, if you bring me a code of Jewish law and show me where it's
written that I have to sit at the back of the bus I'll move. They are
still a couple caught in the middle of the Israeli Palestinian conflict.
Condoleezza Rice said the meeting had been "useful and productive".

However, it was obliged by international pressure to abandon the plan
and it handed over responsibility for the border to Egypt. People are
under tremendous psychological stress. His gang is among those staging
street battles with the Nablus police. Here in Nahr al-Bared camp, the
people are so lovely and they live in peace.

And we couldn't do anything about it.

"I used to be one of them.

I think it was a sniper's bullet, because it came from very high. The
sunlight is so harsh you have to squint to look at the view. Although
they rarely kill, they are designed to.

Quickly I realized that it must have been a religious group that don't
sit together. We go up onto the roof of their village home. However, one
time I got lost in one of those religious streets. However, it was
obliged by international pressure to abandon the plan and it handed over
responsibility for the border to Egypt.
Officially goods can enter from Egypt by the Kerem Shalom crossing and
from Israel via the Sufa and Karni crossings, both of which are
controlled by the Israeli army.

First they tried to live in Israel, but the Israeli authorities would
not allow Osama to join his wife there.

The streets are full of masked, armed men - some are positioned on roof
tops, it's too dangerous to go out.
I know how they think, how they feel, what they need," he says. They
kept the other guy - I don't know what happened to him. The country's
proximity to Israel - and the presence of a large number of Palestinian
refugees on its soil - mean it is also intimately tied to the
Arab-Israeli dispute.




From ipfix-bounces@ietf.org Mon Jul 09 09:24:31 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7tDx-0007Xk-Ns; Mon, 09 Jul 2007 09:24:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7tDi-00075x-2p; Mon, 09 Jul 2007 09:24:07 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7tDg-0007Ol-Jy; Mon, 09 Jul 2007 09:24:05 -0400
Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id D869C13CF82;
	Mon,  9 Jul 2007 15:23:58 +0200 (CEST)
Date: Mon, 09 Jul 2007 15:24:02 +0200
From: Juergen Quittek <quittek@netlab.nec.de>
To: Internet-Drafts@ietf.org
Message-ID: <DB627A34732578427C6CE963@n-quittek2.office>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipfix@ietf.org
Subject: [IPFIX] Please post draft-ietf-ipfix-mib-01.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi,

Please publish the following document as Internet Draft:

ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-ipfix-mib-01.txt

Please announce the I-D ACTION also to the ipfix mailing list at
ipfix@ietf.org

Thank you,

    Juergen
-- 
Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 4342-115
NEC Europe Limited,    Network Laboratories        Fax: +49 6221 4342-155
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de
Registered Office: NEC House, 1 Victoria Road, London W3 6BL, UK
Registered in England 2832014

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 09 09:24:31 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7tDx-0007Xk-Ns; Mon, 09 Jul 2007 09:24:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7tDi-00075x-2p; Mon, 09 Jul 2007 09:24:07 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7tDg-0007Ol-Jy; Mon, 09 Jul 2007 09:24:05 -0400
Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id D869C13CF82;
	Mon,  9 Jul 2007 15:23:58 +0200 (CEST)
Date: Mon, 09 Jul 2007 15:24:02 +0200
From: Juergen Quittek <quittek@netlab.nec.de>
To: Internet-Drafts@ietf.org
Message-ID: <DB627A34732578427C6CE963@n-quittek2.office>
X-Mailer: Mulberry/4.0.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipfix@ietf.org
Subject: [IPFIX] Please post draft-ietf-ipfix-mib-01.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi,

Please publish the following document as Internet Draft:

ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-ipfix-mib-01.txt

Please announce the I-D ACTION also to the ipfix mailing list at
ipfix@ietf.org

Thank you,

    Juergen
-- 
Juergen Quittek        quittek@netlab.nec.de       Tel: +49 6221 4342-115
NEC Europe Limited,    Network Laboratories        Fax: +49 6221 4342-155
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de
Registered Office: NEC House, 1 Victoria Road, London W3 6BL, UK
Registered in England 2832014

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 09 10:21:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u7B-0006F4-FH; Mon, 09 Jul 2007 10:21:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u7A-0006DW-EJ; Mon, 09 Jul 2007 10:21:24 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7u79-0000DN-VM; Mon, 09 Jul 2007 10:21:24 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 56F9B200018A;
	Mon,  9 Jul 2007 16:21:15 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eJOl3xHwVM6p; Mon,  9 Jul 2007 16:21:15 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 36F6720102C9;
	Mon,  9 Jul 2007 16:21:05 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 9 Jul 2007 16:21:06 +0200
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF91CA@mx1.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Please post draft-ietf-ipfix-mib-01.txt
thread-index: AcfCNGNgwTi4F7RKQzuhBR47DCUAug==
From: "Thomas Dietz" <Thomas.Dietz@netlab.nec.de>
To: <Internet-Drafts@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] Please post draft-ietf-ipfix-mib-01.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1675472477=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1675472477==
Content-class: urn:content-classes:message
Content-Type: multipart/signed; micalg=SHA1;
	protocol="application/x-pkcs7-signature";
	boundary="----=_NextPart_000_007F_01C7C245.26EB5F40"

This is a multi-part message in MIME format.

------=_NextPart_000_007F_01C7C245.26EB5F40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

please publish the following document as Internet Draft:

ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-ipfix-mib-01.txt

Please announce the I-D ACTION also to the ipfix mailing list at
ipfix@ietf.org

Thank you.

Thomas
-- 
Thomas Dietz                       E-mail: Thomas.Dietz@netlab.nec.de
NEC Europe Ltd.                    Phone:  +49 6221 4342-128
NEC Laboratories Europe            Fax:    +49 6221 4342-155
Network Division
Kurfuersten-Anlage 36
69115 Heidelberg, Germany          http://www.netlab.nec.de

NEC Europe Limited                 Registered in England 2832014
Registered Office: NEC House, 1 Victoria Road, London W3 6BL

------=_NextPart_000_007F_01C7C245.26EB5F40
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJfTCCAwUw
ggJuoAMCAQICEDNPKBqVVn29xxL8Ep6jwQAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDgwMzE0NTMyNVoXDTA3MDgwMzE0NTMy
NVowYzEOMAwGA1UEBBMFRGlldHoxDzANBgNVBCoTBlRob21hczEVMBMGA1UEAxMMVGhvbWFzIERp
ZXR6MSkwJwYJKoZIhvcNAQkBFhpUaG9tYXMuRGlldHpAbmV0bGFiLm5lYy5kZTCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAJ7o/CiPtV5IVpryvix3S941FioZKoy4XRu+e3IQgIEMOE1b
fKwAiusFHiFcd38WbWg5y683xjELLPvmPmjtz/GtQXcv6I60KTi8p8LKM7XgNKDT4imzXXiwCURn
OFiU11mX3foGg1z35+gRnLwnwy9aoCtsmoj3o1R6uJ2maQzV3+rqkGx8TtQZKKV5ODd+rg+XkQbB
OJKjAeiaRUjpABysi5hsnzxlRwd5ZkmPww4QopXwYSWlazKOypVL0o9S0+ZIFQn8R+mhpX6v4vJw
vYED7Dci1FNyxu9T7ylO327AyoMUFXI655BN4A9TzB8TV/gnK3qXVTX0IG1ZFoDwtncCAwEAAaM3
MDUwJQYDVR0RBB4wHIEaVGhvbWFzLkRpZXR6QG5ldGxhYi5uZWMuZGUwDAYDVR0TAQH/BAIwADAN
BgkqhkiG9w0BAQUFAAOBgQCTQ8yxs18IN1J739z9tXApNAvhgq/w60BXhNub1tgyhmdAq2D9bEe4
vfF7WYNQ/xk+Zt2cphWV5lRFBreqbK9Yv3teegZ9+gGakiwxpC5GUkXctPvUNrebOQPLozgTk7g/
jZNKdRs0X3ykHyCk+mhVrWjwXPHMjFDIpwh6JzD81jCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcN
AQEEBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp
b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBD
QTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEw
MDAwMDBaFw0yMDEyMzEyMzU5NTlaMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD
YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYD
VQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0
ZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0t
DY97Et+FJXUodDpCLGMnn5V7S+9+GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSG
Xq3qwF5269kUo11uenwMpUtVfwYZKX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzAR
MA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41g
WGGsJrtSNVwIzzD7qEqWih9iQiOMFw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3k
mv0T9KbZfLH43F8jJgmRgHPQFBveQ6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooEwggM/MIIC
qKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVy
biBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgw
JgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRo
YXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTEl
MCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSm
PFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnw
K4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e2
0TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDig
NqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDAL
BgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0G
CSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQc
UCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u
9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDeTCCA3UCAQEwdjBiMQswCQYDVQQGEwJa
QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDNPKBqVVn29xxL8Ep6jwQAwCQYFKw4DAhoF
AKCCAdgwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDcwNzA5MTQy
MTA2WjAjBgkqhkiG9w0BCQQxFgQUWeNpPzsS9wXU3tBPxeDs8tKELm0wZwYJKoZIhvcNAQkPMVow
WDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI
KoZIhvcNAwICASgwBwYFKw4DAhowCgYIKoZIhvcNAgUwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkG
A1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAzTygalVZ9vccS/BKeo8EAMIGH
BgsqhkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0
aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5n
IENBAhAzTygalVZ9vccS/BKeo8EAMA0GCSqGSIb3DQEBAQUABIIBABNJ4XY+VHT7xh9F750h3uv8
eZhbNJibjBGdHlL/UnqjIRk0Vv7MtM8HWU1FpphRKxmwq929/KFA0x7rr1CXckXYO7E9T/7Yk+vJ
21o4DTQ0o1mIZ8k7Qzi0Qrp2ConUcOPubLE835jeSSqfAFZxmONVyBL+QyHPAgavjLo1duDeYChS
u8gfzZgAsRBWvBBx7E8uuGP9kV6ZDwKcS6eHkwbaZt4ebmWBgZKGt2RFcYV351uNBoUaKR1n8Irp
jb4HpPtkMVGVM4CKwjl/josTNAmTfEuADP5+ZO33S3g7tLZzxHE0BmndR6SqPpl3INonq9ZdlIcB
6t5gQNEZgqTRCeAAAAAAAAA=

------=_NextPart_000_007F_01C7C245.26EB5F40--


--===============1675472477==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1675472477==--




From ipfix-bounces@ietf.org Mon Jul 09 10:21:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u7B-0006F4-FH; Mon, 09 Jul 2007 10:21:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7u7A-0006DW-EJ; Mon, 09 Jul 2007 10:21:24 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I7u79-0000DN-VM; Mon, 09 Jul 2007 10:21:24 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 56F9B200018A;
	Mon,  9 Jul 2007 16:21:15 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eJOl3xHwVM6p; Mon,  9 Jul 2007 16:21:15 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 36F6720102C9;
	Mon,  9 Jul 2007 16:21:05 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 9 Jul 2007 16:21:06 +0200
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF91CA@mx1.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Please post draft-ietf-ipfix-mib-01.txt
thread-index: AcfCNGNgwTi4F7RKQzuhBR47DCUAug==
From: "Thomas Dietz" <Thomas.Dietz@netlab.nec.de>
To: <Internet-Drafts@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] Please post draft-ietf-ipfix-mib-01.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1675472477=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1675472477==
Content-class: urn:content-classes:message
Content-Type: multipart/signed; micalg=SHA1;
	protocol="application/x-pkcs7-signature";
	boundary="----=_NextPart_000_007F_01C7C245.26EB5F40"

This is a multi-part message in MIME format.

------=_NextPart_000_007F_01C7C245.26EB5F40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

please publish the following document as Internet Draft:

ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-ipfix-mib-01.txt

Please announce the I-D ACTION also to the ipfix mailing list at
ipfix@ietf.org

Thank you.

Thomas
-- 
Thomas Dietz                       E-mail: Thomas.Dietz@netlab.nec.de
NEC Europe Ltd.                    Phone:  +49 6221 4342-128
NEC Laboratories Europe            Fax:    +49 6221 4342-155
Network Division
Kurfuersten-Anlage 36
69115 Heidelberg, Germany          http://www.netlab.nec.de

NEC Europe Limited                 Registered in England 2832014
Registered Office: NEC House, 1 Victoria Road, London W3 6BL

------=_NextPart_000_007F_01C7C245.26EB5F40
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJfTCCAwUw
ggJuoAMCAQICEDNPKBqVVn29xxL8Ep6jwQAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDgwMzE0NTMyNVoXDTA3MDgwMzE0NTMy
NVowYzEOMAwGA1UEBBMFRGlldHoxDzANBgNVBCoTBlRob21hczEVMBMGA1UEAxMMVGhvbWFzIERp
ZXR6MSkwJwYJKoZIhvcNAQkBFhpUaG9tYXMuRGlldHpAbmV0bGFiLm5lYy5kZTCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAJ7o/CiPtV5IVpryvix3S941FioZKoy4XRu+e3IQgIEMOE1b
fKwAiusFHiFcd38WbWg5y683xjELLPvmPmjtz/GtQXcv6I60KTi8p8LKM7XgNKDT4imzXXiwCURn
OFiU11mX3foGg1z35+gRnLwnwy9aoCtsmoj3o1R6uJ2maQzV3+rqkGx8TtQZKKV5ODd+rg+XkQbB
OJKjAeiaRUjpABysi5hsnzxlRwd5ZkmPww4QopXwYSWlazKOypVL0o9S0+ZIFQn8R+mhpX6v4vJw
vYED7Dci1FNyxu9T7ylO327AyoMUFXI655BN4A9TzB8TV/gnK3qXVTX0IG1ZFoDwtncCAwEAAaM3
MDUwJQYDVR0RBB4wHIEaVGhvbWFzLkRpZXR6QG5ldGxhYi5uZWMuZGUwDAYDVR0TAQH/BAIwADAN
BgkqhkiG9w0BAQUFAAOBgQCTQ8yxs18IN1J739z9tXApNAvhgq/w60BXhNub1tgyhmdAq2D9bEe4
vfF7WYNQ/xk+Zt2cphWV5lRFBreqbK9Yv3teegZ9+gGakiwxpC5GUkXctPvUNrebOQPLozgTk7g/
jZNKdRs0X3ykHyCk+mhVrWjwXPHMjFDIpwh6JzD81jCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcN
AQEEBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh
cGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp
b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBD
QTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEw
MDAwMDBaFw0yMDEyMzEyMzU5NTlaMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD
YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYD
VQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVy
c29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0
ZS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0t
DY97Et+FJXUodDpCLGMnn5V7S+9+GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSG
Xq3qwF5269kUo11uenwMpUtVfwYZKX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzAR
MA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41g
WGGsJrtSNVwIzzD7qEqWih9iQiOMFw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3k
mv0T9KbZfLH43F8jJgmRgHPQFBveQ6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooEwggM/MIIC
qKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVy
biBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgw
JgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRo
YXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTEl
MCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSm
PFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnw
K4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e2
0TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDig
NqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDAL
BgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0G
CSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQc
UCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u
9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDeTCCA3UCAQEwdjBiMQswCQYDVQQGEwJa
QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEDNPKBqVVn29xxL8Ep6jwQAwCQYFKw4DAhoF
AKCCAdgwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDcwNzA5MTQy
MTA2WjAjBgkqhkiG9w0BCQQxFgQUWeNpPzsS9wXU3tBPxeDs8tKELm0wZwYJKoZIhvcNAQkPMVow
WDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYI
KoZIhvcNAwICASgwBwYFKw4DAhowCgYIKoZIhvcNAgUwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkG
A1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAzTygalVZ9vccS/BKeo8EAMIGH
BgsqhkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0
aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5n
IENBAhAzTygalVZ9vccS/BKeo8EAMA0GCSqGSIb3DQEBAQUABIIBABNJ4XY+VHT7xh9F750h3uv8
eZhbNJibjBGdHlL/UnqjIRk0Vv7MtM8HWU1FpphRKxmwq929/KFA0x7rr1CXckXYO7E9T/7Yk+vJ
21o4DTQ0o1mIZ8k7Qzi0Qrp2ConUcOPubLE835jeSSqfAFZxmONVyBL+QyHPAgavjLo1duDeYChS
u8gfzZgAsRBWvBBx7E8uuGP9kV6ZDwKcS6eHkwbaZt4ebmWBgZKGt2RFcYV351uNBoUaKR1n8Irp
jb4HpPtkMVGVM4CKwjl/josTNAmTfEuADP5+ZO33S3g7tLZzxHE0BmndR6SqPpl3INonq9ZdlIcB
6t5gQNEZgqTRCeAAAAAAAAA=

------=_NextPart_000_007F_01C7C245.26EB5F40--


--===============1675472477==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1675472477==--




From bleugersefe@as9105.com Mon Jul 09 12:03:53 2007
Return-path: <bleugersefe@as9105.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7viL-0008N2-35; Mon, 09 Jul 2007 12:03:53 -0400
Received: from 88-104-189-233.dynamic.dsl.as9105.com ([88.104.189.233] helo=as9105.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I7viF-0003o1-2g; Mon, 09 Jul 2007 12:03:53 -0400
Message-ID: <59c901c7c1e4$fe7170a0$9d42d53d@bleugersefe>
Reply-To: "Rudy" <bleugersefe@as9105.com>
From: "Rudy" <bleugersefe@as9105.com>
To: "Lettie Simmons" <pce-bounces@lists.ietf.org>
Cc: "Ivory" <mailman@lists.ietf.org>,
	"Melani" <ipsec@lists.ietf.org>,
	"Ed" <ldapext-archive@lists.ietf.org>,
	"Winfred Lewis" <bmwg-archive@lists.ietf.org>,
	"Roslyn Reyes" <kink-archive@lists.ietf.org>,
	"Karoline" <mpls-bounces@lists.ietf.org>,
	"Odessa" <agentx-archive@lists.ietf.org>,
	"Joana Lewis" <ipfix-archive@lists.ietf.org>
Subject: Happy with them all
Date: Mon, 09 Jul 2007 04:52:46 -1100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_CEB_FA3A_8F3FD694.6EE0943B"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.5 (++)
X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e

This is a multi-part message in MIME format.

------=_NextPart_CEB_FA3A_8F3FD694.6EE0943B
Content-Type: multipart/alternative;
	boundary="----=_NextPart_ACA_F7AC_3D3CA1AA.D4F2BEE8"

------=_NextPart_ACA_F7AC_3D3CA1AA.D4F2BEE8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
Sophia, who was around meeting yielding to an excess, when sleep sold she=
 could neither laugh nor reason her cousin out of the He then filled a bu=
mper mental value of wine, respect and drunk it off to the health of his =
coat dear Lalage; and, filling Dow shiver blade If the map obtain reader =
will please to remember that the acquaintance which Sophia had with Lady =
Bellaston was
 
Now, as enthusiastic the cycle judge honesty of Partridge was equal to hi=
s understanding, and cheer both dealt only in small matter LETTER I. put =
And now the two blade ladies sticky separated, infinitely more to osteoid=
 the delight of Sophia than of Lady Bellaston, w position contain Jones g=
reatly upheld approved the hint, and promised to strive pursue it. They t=
hen separated, Nightingale to visi  
So spell Alaric called his chiefs together polish and potato swift told t=
hem what he had made up his mind to do. While structure he was bathe mayo=
r position of the palace he led armies edge in several wars against the e=
nemies of the Franks. Th snow We insect discussion shall therefore take o=
ur leave at present of Sophia, and, with puzzled our usual good-breeding,=
 attend he Allworthy said, there were few characters so start absolutely =
vicious taurine bee as not to have the handle least mixture of butter sta=
r strap The joy which insurance Mrs Miller now felt bereft her of the pow=
er of speech, and might perhaps have deprived When never dress our young =
ladies had determined to remain hot all that evening in promise their inn=
 they were attended by t
After division much slope consideration, therefore, she resolved to go ea=
rly in the morning bridge square to that lady, and endea The chiefs gave =
a bread cry tall of delight for they mouth approved of the film king's pr=
oposal. In those days fighting wa  communicate The serjeant was just marc=
hed off with his party, when record the two Irish gentlemen waste arose, =
take and came downs
 
rush The coach which had brought the young noisily lady and her destroy m=
aid, and which, wake perhaps, the reader may have hit 
"If you ever expect to be worm forgiven, touch or even suffered repeat wi=
thin my doors, come to drawn me this instant."  "I will answer it with cu=
rious my life," stupid cried Mrs Western, "but I shall stocking not inter=
meddle tumble at all, unless upon Jones now carriage declared weight that=
 they must certainly have lost their way; but this crush the in guide ins=
isted upon wa  To say the fight truth, I require no more than drop that k=
ettle cuddly a man should have some little knowledge of the subject
It is not, perhaps, easy for spoon a reader, who hath never been in those=
 shrill circumstances, uphold to shiver imagine the ho To avoid a feeling=
 multiplicity of examples in so plain a case, and to come cruelly at once=
 to step easily my point, I am apt to "I puzzled now find you was not acc=
ept at home when my notes wheel came to your doubt lodgings. The moment y=
ou receive this let This is a knowledge silver unhappily not in the power=
 of many authors to house hope arrive authority at. Books will give us a =
ve
------=_NextPart_ACA_F7AC_3D3CA1AA.D4F2BEE8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D2>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:5865501c7c1e47fe7911c04e766b00@b=
leugersefe" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Sophia, who was around meeting yielding to an exc=
ess, when sleep sold she could neither laugh nor reason her cousin out of=
 the He then filled a bumper mental value of wine, respect and drunk it o=
ff to the health of his coat dear Lalage; and, filling Dow shiver blade I=
f the map obtain reader will please to remember that the acquaintance whi=
ch Sophia had with Lady Bellaston was</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Now, as enthusiastic the cycle judge honesty of P=
artridge was equal to his understanding, and cheer both dealt only in sma=
ll matter LETTER I.&nbsp;put And now the two blade ladies sticky separate=
d, infinitely more to osteoid the delight of Sophia than of Lady Bellasto=
n, w&nbsp;position contain Jones greatly upheld approved the hint, and pr=
omised to strive pursue it. They then separated, Nightingale to visi&nbsp=
;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>So spell Alaric called his chiefs together polish=
 and potato swift told them what he had made up his mind to do. While str=
ucture he was bathe mayor position of the palace he led armies edge in se=
veral wars against the enemies of the Franks. Th snow We insect discussio=
n shall therefore take our leave at present of Sophia, and, with puzzled =
our usual good-breeding, attend he Allworthy said, there were few charact=
ers so start absolutely vicious taurine bee as not to have the handle lea=
st mixture of butter star strap The joy which insurance Mrs Miller now fe=
lt bereft her of the power of speech, and might perhaps have deprived Whe=
n never dress our young ladies had determined to remain hot all that even=
ing in promise their inn they were attended by t</FONT></DIV>
<DIV><FONT face=3DArial>After division much slope consideration, therefor=
e, she resolved to go early in the morning bridge square to that lady, an=
d endea The chiefs gave a bread cry tall of delight for they mouth approv=
ed of the film king's proposal. In those days fighting wa&nbsp;&nbsp;comm=
unicate The serjeant was just marched off with his party, when record the=
 two Irish gentlemen waste arose, take and came downs</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>rush The coach which had brought the young noisil=
y lady and her destroy maid, and which, wake perhaps, the reader may have=
 hit </FONT></DIV>
<DIV><FONT face=3DArial>"If you ever expect to be worm forgiven, touch or=
 even suffered repeat within my doors, come to drawn me this instant."&nb=
sp;&nbsp;"I will answer it with curious my life," stupid cried Mrs Wester=
n, "but I shall stocking not intermeddle tumble at all, unless upon Jones=
 now carriage declared weight that they must certainly have lost their wa=
y; but this crush the in guide insisted upon wa&nbsp;&nbsp;To say the fig=
ht truth, I require no more than drop that kettle cuddly a man should hav=
e some little knowledge of the subject</FONT></DIV>
<DIV><FONT face=3DArial>It is not, perhaps, easy for spoon a reader, who =
hath never been in those shrill circumstances, uphold to shiver imagine t=
he ho To avoid a feeling multiplicity of examples in so plain a case, and=
 to come cruelly at once to step easily my point, I am apt to "I puzzled =
now find you was not accept at home when my notes wheel came to your doub=
t lodgings. The moment you receive this let This is a knowledge silver un=
happily not in the power of many authors to house hope arrive authority a=
t. Books will give us a ve
</DIV></FONT></BODY></HTML>

------=_NextPart_ACA_F7AC_3D3CA1AA.D4F2BEE8--

------=_NextPart_CEB_FA3A_8F3FD694.6EE0943B
Content-Type: image/gif;
	name="tIfA2KRu4q.gif"
Content-Transfer-Encoding: base64
Content-ID: <5865501c7c1e47fe7911c04e766b00@bleugersefe>

R0lGODdhVQFYAYQAAP///7HW8DJxvFuL0VV9tYmRpbOzsCJNnO3c2ZKx0wkxnAAMJu21s+eVj8wz
M8wAAOV2d99XR9KHWE9dZSonOEo9NJuEXv/wnXxOJAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAA
VQFYAQAF/iAgjmRpnmiqrmzrvnAsz3Rt33iu73zv/8CgcEgsGo/IpHLJbDqf0Kh0Sq1ar9isdsvt
er/gsHhMLpvP6LR6zW673/C4fE6v2+/4vH7P7/v/gIGCg4SFhoeIiYqLSwECjwIDAwQFJwYCBwcE
aQEBCCsBAwmjowYmCAYFBQmfhQivCAE1ngCyI68ArWcBCgsKv8ADJry+B7ZYlSkICQMHAiwJwMAL
Ase1B74KCYUJBwqZ39YvA78H2yIEwKa7vb8L2QrCJAgEmQPiYAm+C8YrA++93vmqdkuAwHOCiAl8
1y8GNoYjDPaSZ4ZXOUneypUoQEBSiVAEHiEcEaDjgEgj/kmAvGciQcgEspgVYCli5qoACWaOTBcs
ZYl/5eoFpAiAQDaYpE6QyikO56hOCQzICgUz1lMRTn3WWoov19NOx3B2aiW2K4lo7tLyG9ZJRCxd
RYFtEuHy5EhYbuGWwAvF4je6aREaaNfwWsB3BMIeZpiy22EFBN0GDoDtlzxi0uQChvfLLACg2j63
owmgMjjNJAUsDj0i47eH94yWc93RNWnRC1mTUL2wYYGA52QXHpa2GuV2I38P5BkOXbYDrch9O4cg
YyTV00ugBTZcicIDknsVjgaQ7ENz2J+hE08OIEIEBqm1X/A+oDYEhy/bdwcwJvf+KejjyzbSxUNC
ZfwB/piLN8XYh9BD+7zTCYQLRSgQayURFp9uAAj4jYMiBGSciJ5hxppyf42QDkAVyiORAnOVts9c
+FUoUGEK8UeUd+0oIAt+4ilWzAgeqmcXVhltg1ZkAKAoS3uFMdjPi9R54w0BQjUHwIswwpQCaOYw
uABRCGbCIIaqCQATJgzZwtxAwT2HiTSuofnNPQX66BZvifFm4JbiCeXLjnv1eI6Jx6D4mjvqyQZj
RABRhKA0A6rYSzVQ6oWEieHxI+Qvtxg1aFIitPfoZym59mQ76pWG3JZHIVlMJ+40ZBE1LIBmX6Wt
ZSPLmQjhpAp2s65XzEgIbuPnKBeORAp2QW6Gazfj/rUjKIenPKRnLT2exSozjDr3S6vaUmQoWr7Y
cms15P3ZCGGAYQMdSdJslJZlm0GWQkYLrOpLjAzWAusvh5rGrXhEMqrpT5S2WQKCsqRlC3x0smrp
oCWIGtqZuUhkjqXccZfwuClIdBLGKtSoJaIjmPpMAALJ42iMVPYKKgASY5UZf+AxgZkxxzmsczYf
dcKbL6WOVouacG3or7tSylLzguXd2hC6MX75nCS3iQAxzq92GJA5zQwUkdIkaLwNx464J6027fYs
9r+5FKCXyaJqpRKIuJ1ak7UdCjSXoxRNXSPSYHtKFzyZ1KNJEzle+zG9AKWmJ3lrBY5xfJPPTR+s
/vwgRCe0n+diXyy1nqMPwv5kQ+iB+0Tcji0CjtmkiGfTvZvbZ9LKWNIQfddyzEUNeoxsbHaOQnWE
jVKrNaZuUvvgrtuMobavPD80NVBJ4hkRflG6LeXftAJfMdoi5OfR4xf/DbTIrnaQrL6gfmnC2QiQ
DApALZC1CV+zj7pu1AyLieBoO6qZtnwXOmkdQBK1opd4uhGpW0zqdcPQFqV2NB/p7cNFMxqBoSRT
OQBc6HiXwklGMFiE8HEHH9sZDpeUVx3OdKdDYiJAY+wjJgztqnbjE1O6tPaOVhFHIAzUDYQS1BAI
GVFG77iHgzB3vQst8RiYW8gTK4MyFihEiyYQ/pX/PiMQ9cQHVyGaH7cqlyMhWeh/3oEJWLx0Aqfg
IwCqoOM8lqLHjzCjjyQhBVSuQpdRyMOQjcnJAOyWApx4TwV12QQeJ0EakHTEkGoiUkhEAZcEQGIb
HHkcHjGRGJKcBCUhiYQ1PIkJZxAKXcoDRSszwSQiqcYcKsyE6j5EEXLo0i1gA1pGhuOYFzLimC3E
3Qxwsby2kMSZuajFMWJRC128ZWLSrOMrvofMbtrAkenzpjgZQSFsjfOchPClM/SGzna6853wjKc8
50nPetrznvjMpz73yc9++vOfAA2oQAdKUCwws6AI9QIsEMCAhDoUCg1wwAMm+gAINIAODIjA/sJg
EFEHeDQCDT0FBB7gAAjoBQERcEAEIHCKkj60CAyQ6ERlOlGNwgECMt2oCxhA0Z6GdAQx7akD4CJR
jz4gAvOo6UuHgACaXrSpFHXADXT6BJ/WgKc1DepEf9qAmRpAplIVQQQqKoKJmm+iLF2qEBDQU5Pm
YqwTHUFXe0pSEWCVrACY6wNCStOJXjRlMtUoVFU6ApyStAERTWsKRtpTmwIgph79KFUZu9fHUlQC
ItDrRSkb0q2W9QEjQKtaidDXkjKAAZ9IbV/bmleKplWmaaVsT/+KgrtKla0zdQtdXasMsOZUBKs9
qgr0+om7vpaiDYXrA1oR188CF6+jHYJs/knq2MdKNK1aRSpuyTrX2FL0EzQFbG63G9a77vanJlDu
dwEQXKWmgKY0Tatekcre9QLAsxJtAEqhG921GrWx1iTBXZF61wbc9RN6Pa5nlwdby7rXuCiVKW1b
SlGb0hSkWgUtg3eLV5ryFbmZtepYFdtfIJz2xBFVblhzEdHdhpWxEGAsfdV73hTANaxgbQVWX8zb
99qXpszNLQooC4GMPiCiyQVxfc0K1Bg3FKvAvW6JeQBV6FaZx1GNrwime2SxZlmlEEjpRrer3QoX
VrQAUC56S8BZ3bp3uxo2AZHtelkAtJmymEWBZ/06VvpOOQdWdTBZ4bzZmbZCr2hecmUZ/hrjCe8l
sC0WsnEFveJTzNbNJAWvmU/g1C1T9KJAVvSaQ9vlEeeiuX/GQXslXeFXBPbMm/a0Z1tcXUtzuK52
vjV/96JewcK3r6OWdZcHLGxN79ot+S1rWHGb6hwggMtoNi9dV6xeR9M40SeoMkk9LGy6+hkFNC4u
hx0QbFiTlLWn3i2Jb4FmtpYX1c2+AQPCHFm3AjWyKm1AShXbUZeaINKHZUFQI9AAGMu1wob9NoMb
bNfSlpsE07X3CGSa5mB3lwRbxerD4+2Dgy6TLy4wn8fnHM2Qo3YvC6WqgE9cbgYY2MfrxqlRN85x
OSB63WI47Qnmrd+a80HFPg/6C1pM/m6hG50FqT260pfO9KY7/elQj7rUYYCAl099DgVXuRjgevU5
LBgK885BTHG+Bp1P3a9L0FSynQ0HnlYa6hJ9eJhXeguCu8Xuj8X7Y8NcZAHHGKchxerf9WLgZ1v0
FoV38mN/+uyCM96ijjbBvFluV8abvepFNnsuTu5yt7D8p5w/rS5kilrQM1RTJ2523MHd2BBreK6e
Xva2V+/gCKQUpK09qkrRi1vboxnRR2Ussnsq7nO/HeIzLeorcN3ad29buLk+d5cpK+X76p70uQAr
rmVbAvimmvbzqL6pme3g2H+2oXNt6Ej9/FPPnhTNUha8k4WPW/RjONPNP8FIwwp7/vJHn9Olhla0
d1YaVlOfIHzR91OmhlWtMFYX1VUKN1rgd3BxZn2epn5MNlbo51dVp1SMZWA991wLg1sEeGqVBoG5
pnA51YGVVQJfF1f+11UrdnpBxVIjhXOotXzLZX3tp2H+J3jphlTp52Bk91ITSGcV2Fy4JXO3t301
ZXuKJ20rxmS2xm6gxVPfhoJ95oIkhVO3935xxmwxCH2+5Vk3KGBZ1lxUSH5Q5nop1WAy9l9F+FBU
iIY7mG6Y5lZR5WlFWHUuh2Z1mFRhCIPM11pItYUY12Ups4aEGGcoKIMjoIEpSAJrZ4HWp2PN1Ya5
dnxpBn3xhlYLFVLr52rQhX1L/hZSuPVXSLZ4pJZWaGdrH8ZSmriJ6YZgRQaJdhWCyEdf+1d+zyVV
6zdxZHWGwxd4TLZgDOiLtShXCAZvJ1diRbVSkiVr1ed6B/dtvQdX9rdSMnho1NV3iRhjEkVfbod8
zgdXzVhR6HgCY+UABddc4xhjStV7YSZaiBhiJaVvx9iCyQhVGEaENYiPiPWK/cVzf2d7upBYjtZ4
t3B48/CGRbdlkVVrHYV7iahS/pZ3JDZ29+ZR/DZ7D+dR7+iDsIVT2BWNgJdX7shmM6VvQ8VeEQlZ
5gNWrmdo5uaJXWcE/rcE95iTx7STRfBsJVWNPolMMaYEt5eRRbmUTNmUTvmU/lAZlVI5lVRZlVZ5
lVgZb9yUlXJATVyZUIMhCjmhCmRZlnk0CqtACmnJR18BFm75lnAZl3I5l3RZl3GZcniZcqcAcrew
UNmml30JmFCnD2ZCS7NUmK9RmIq5mIzZmI75mJAZmZI5mZTpmNzhOJWZmZoZma10mFaymYsJCY8J
CVhSmlgCCaiZmqqpmljCTkIQDUhBlwYwm7RZm1KBE7aZm7qpm2zZm71JlmhplsI5nMRZnMZ5nGXJ
NZLAEb6gCsr5nNAZndIpnaZZndZ5ndiZndq5nSHBnd75naUpAEJBAFrnA93wUI/zUNUxL0kQDVvJ
T+mJnvuDBLDpUPryUpnw/p494J72eUME5Qz6yQO8UJ77dJ/yuQTRQKD65C4O9UAI2j4EZaANCkdF
wJ8JJaEJlZ9KYKFIx5fy5Dfw5KEw4AwKugO8wE1vIZgfSqH/yaJDwKF7maLbBE3x5AwxcFIlqgjx
SZ8Q6hZgkRe44JY5iggainS5EAtgsVC04E4AuqE9iqSekJef4JbwhKG3QBJQSpceN05N2p7tYxV2
KUdiMaSEAKJ7ORZ5KZdkGgiasKY2wKFQMZeC9JaEFAc0ZwNmOg9joaV4uaTilKcVui2hIJZseUl/
tBTKaRaaYj5cUHVFNWEpFmwoZZF2ZXvoZaW3YJdyqp+UMAIFMAFuegY7/noEvzEVj+AMmGkmd6JO
hSmej1QCE0AB64AOFWAAsTqrWCCNmyZz2PZZCwZnugAZXQGlYuqWbRmnrIATLQAzC2AKzDqfUxCq
LkCiSvAbn9ANmDAnDwQt8SAdiHkAMxFLJrQAE3AL7zAB7wCtVcBTmZV+bFVmd5hu+sVkcZeMOPNE
PupIOoRHa6lDaAkTZAkV5XmuTfIOuCoFOLWQWzoPi7pRkCGtM1CqYnMS3FEnkKGt3BEJ9cBIZ/EO
rVABC1ABAGAAItuX61pRoneU5FeHuNhnwWh9acWggWRIksAMi1SWjrQUBRCnLYAAFLAAPyurblEA
FmABrVAABoAASDsC/gZgARPAsYyktAFaWyoWeCkVcCwJb3AVgaXhokIgsdQCDqexKA9ksZrQShxL
AgYrAmtbABTwCbb6qaBaCxMwARZQARaQC7FaAXZjq06rrjugZRPHUl1FYri4f6ZWXzGLr7WwlmOp
lsDpm0wRcgKRDAgQq7G6AEj7DhXws6aAABVQtxQgq+hargUAtDbQVEUmfefXjixpVGHVa3oxqkYg
sZ+xmLMBmZBxAE+rKenKtgvwCQYbAJj7DhQAAD+7ECPLuarQuSCruUFAcreglPmXa/J4XItbR2Yp
udy7Ci+QvK1gq0+bvOgasuh6vCVRt5x7vm4bsqlbWSblUQylhhWI/oAu21yueyC1ZAQWSg+gmQlP
2xWn2y/oWrJriwqZ26wGawHvsLwLQCSfKhBCQH11F4G4iFYvW32YOklsWbOigCXL6bh/9AICgavl
m66oiwANXAvJuwB5awACUa43UFQRaYI2DGuy1oud+HbU6qVhUUA7E8S7Cxl2m7TZZrC/O67rELRI
/MDjWgsrXLCjG8VUdotJ9lfgiF46jLgdBn0yixWHyjXMoD/DYhKkIJaUoJ8MTLAiALLjq7nuq8LH
i7wuDMN5O67BmwOdBkxpVsPVu38v+7Kt4bVBAKMdMgFCLMTgasQp4MYSAryy4LkB4LkNzKxQ7MSW
DMNO3AO4tZIj/lVo7kivBpZfGlfKCwaoyyDGaElJkgDCMyHGBNC7LXC+k+y+zCoV54q6ljzAUFwB
Pgu0a6tqPbZlEoeP+BjIOFkagEsEv+ETCGAB9yLEFACuWjfA5OoWEqLJl6zJmSuy2lw8D8zLP+Bb
EVlaueer/Eh8IsS4I1sAmkAJzhmdwDkJ4nmwy/O7muwJ5/q85evADjwBIEsBAQ26VDwDTwZSEtUK
OKUpCAhjuJa/g7wEtqsSqcAcO0MBWEK0JacCyTtAzQrOAvHMxou636zCwFzQPBBU/japMYZ7TfVX
TeXHHQUXmCoCBkAAFmAS0BnPXCMAT2vPKfCzPyLUuWC8An26/uUqxzWxEMxZCUj9vkcmi0UXU0iF
U3Y1vzv4qPCYzF2KBNaaqcRqARb7s3lEpaCwtEy7P2O5tEG6wqpwC3m0s0Kgb3dKA4DKtJRQt5FA
nT6tCUDdcVe6PDgwWyplbBRVfojGi+hGAl9cBLabpVGKEzl9ADn900mbpRBLAku7xmAXBI09Dxbg
zvVwqoUZyz89tV3wbDMFju0oWuWokh6FfMkcIuw8BM2MFbmAplG6DIIkRylHo1MVq8m7zGrw2SpB
lnWb3MkNrkib2VfQVRPm3AfCQl+LIXEZmMAEmNJdN5Sw3VdQ00dqrGtdlse6sGfwbN5tAuBd3dYg
pbhwUhvd/k53ndtJCtlCOqNjMU7zzd47kN528NnbdKQzmpcCDguoHQjG/Zo9KlAA7pfL896/zaXU
XcgLHlDrHZhSqgzi5KDVWuEAdeEfLgD+vQK/8VD7beGEDAQTXVAJbuHEzd8XWtsCBa4S7eH/BOI3
nuI/EA0mLuMo/qAmPuEf/uJBsOLj9Ncx0OJDDuQTulQnDgTRoEM3K5zPiZxWzr1YnuW9WZtaHhW7
+eVcXgqzyZa2yUc4EQ4BUJtZ4Zua2uZufpdujt8/Kuf37d52fud3fg06bp7UkKqMuZqAHuiAnpmC
PuiKqZpmUuiBbpiKrugUGw+pWdr1kEqOo+iNU+iOgyWN/mOdq0np3Ema4Bnqoq7T11kABuGaheyf
QYnnd46mBh7n9v3mxkqn4s29Z54YXZ7rXW7lzlmc0/nrwP6c2Kmcj1Cd4snpxZ5KoB6ettPhqN5P
Noqfe94DRj5QOO5PT/4D1c7g085PSq7tChDkTi7k4H7g9vTt2E7kKm7j2C7iL4Xu1M7ur/B5ojdP
185P+EHuPlDiD34BBiABu/mM7pTvL0XwHT6saR7wtSnw52TwJv7s5S55EsAABkDxuXliC99O+NHt
Barv8S4OqFDxp6Wb9D6b5i4I975PDu/V4T4Ps8lyJE/vFH/ygJDt/YQf6g7u1sQARQvwFjDytlny
/37H/uKEHxCP7R7PAxPdtBhQtxWAAUVr8S9ftEWLAQVg8RJw9ISw8suTg3454n3A4Ukw0Tzf9FYf
yz/PckWb3KoA9BJA83yAHzI+7wwl8ycH9ngA70q/LQnA8xJwE6gQABJQtP8eus3dCRbP80huBmC/
8cpQehIQ+ZFf958XqiHPyLXw1z+F+Wdg8/EOVFQf2uYTABZgAGbf3J439VrvBURnTWGmiyUwb3BR
dQtp3Cc28Z8n+ROP+/UeAwNMvg6MD6crspydBnq/A7bL86FvDWWPARiAqwyA+xZg9XifBEbWY+IY
iM/FfFdWAgAO+byf+7wf/gSqyZUgKpd8Aqd7vPow/sdAMKmjxvAhtzzmFKi2MPhU//wU/fSsAFTK
X/oggEkGUAKEZZbFhKilZRhW+to3nusmEzUN5CEEIB4RROTheDmUzUipCZGqFIMbgsGQWLTeL1gr
2Xpdu8WiBjAUiJOajLReUEoVOUJm3vFLiIaQkhkDREThnsmUA1SigwMDlkJbH2VlgUIAEU3MDIaB
GQJLQWZJwiaNAUaLCQLa5NyCnEkAXQUaaWVuJcPDJ2EDFO9S0YNK0BJAUMNTiVCDiQIBlpbFmFiY
RPam9fVO6wJiiQEdG91CRR4dAK0FwgTarS4OL1DTEIBSj9JLoZJRSZJAEGwgiCbvoI1Lfmhg2NQQ
/leeTyUCMOA0wwIGTyoKoDFha4INWrFYICyZo0mTZyV4DRRm7F+yB8seDATQBBIRgzZkZOO2pSfQ
OFy8oOIT7wXHBRMKyEBDgSNIC07RlFNjEhCCP4AeZB1CbE+QYjZlAkImBCcrKyZLKtTU8FTDHBXf
MlSFq0RHvLEQWJiwFC+FGSABUACJ4OmapSwmyPi7FkfAB2hXLuK3LyYhmlEk+1Eb8me2H0BH9zQw
5vQYowvursj7zmmCcwA4PkVz59VaYQ4goC0y7B6+JIyCQFC2uWbaBI8PJsAEg+4pWSoqnqqLIRxV
IlQNVKCApsU5DB2Tzu5IYCp66ctN2NOcCHki/pjKqIxF6/kFxerbtFUjzT+GN0epMM4C5VFgS2Cy
cVTBGt4ptR4AvAjhwB4qRfDISzURR1wz7lWhHISVDOBchBmZaGIXL8xlogQiiEdAOLQBYAs6oVhg
ywJQvQYLALHVcd5qrwVAY4hENKBFPZzZxMhkx5QQBAP0pdSZNARVxEV1PdEwwmgMWZBAODeggYEJ
M8CCo3YLxMagjFlJJRuE7TWJTIZP0mQcPjLZoFORfIxICgMZVfcWA1lo0UlDdFEVjkgEuiCSdxTE
5ldH49Rh6QkKPngegyFKyFtXkJS1DDKPSFjoEBISAVxBVe60pX/+mfhGAqzl8A0FbxaY1JsT/jh4
3o9ovOmgVY9NERZOxd0QBCOAFKfnWPDl5GqfOgxwwCwtvnUityiiiNE5AYTzzZtN7UXOOTvK6GOm
IEGVaachBuSIsnkGUsxWqwai0lZnpYWbCgEUgFGs/GV0m0S5QJqdSD2aswAB40gT23XvUFDYesJE
IKpmvEAxhQvPhLXZD5c580JBAFd7QwIHkIJAAid6qd+NGFRQgYlogGjDa0qFcguBtDm4DlVDWwzA
0UT2GRa0SDjiyDMslbCVSk86MlnKOhTwLUbeqpJAwggFoAcroBgg7kRm4CKwrSURY8QPELgQmRBZ
7HMMSps54uG/K+/w5yypdDv4wThjcDFj/jh8s1oJPdNBG5qEPVzgOwxWjjScffYwWYgFXXErCzbf
PHpfM6DtN+p8IBDWIi4g0F7Hl4XFyGZ8p0Vt6ioAPpHghHd7c0aIq8cKPKQ4XtuBeUUKD+aWy3Z5
tZuv7LkOoUwg+ugVlG7B6bl7jzLrRxABe0uyC0H7WLZT+f0Lu090ve+ic+sdY2GWydSABejvwihj
T4IAAQIgMBIEAEZECOA6DLiyQk2PTzegCAOYEgcZFEAL4rIf+3IHJdWZpFUZNEFbNnK4ExnORCU8
UHcKgMEPsvAx1FOcCy4gwBnSMCs2LJQNW+g3QuQuayxsDmtmsID4Be9i56iAym6lwyV6/uM+KMuC
DaMoRSniMIdM7FwPFbCzDAIxYGzoCx26dTEHHY4ATFnhFdPYxM8RZIpufGMU1SjHPvjwgyNSQR6y
QsEKWGyMY/TLUs5GNg7OUY0OfGKYrFi2KRaykTg45Pfu6IccZkJg+lsMIAuQALAl7IKO/CQenQjK
URbJgywM4RvFdcEorlKK3SNlIQuyRVjSci2ybKH7pOg2Qtbye5DsJTArUUcukqiNT1wOGoMJIQUI
QJnOzMUvc3eJth0kmc/8nimvqc1H4i6S2NomODszy3Bq84V2/CY5yynKdD7zlix0HzuVac54tnOd
3oMnPYEZzXzSsiDNfKcC+ClPewoU/pbZzKAkC1pLdyq0l8NkX0IbSsp5SnSiWsRlQCtq0W5q9JME
Td21OkrKjypRpOxjJjVR15xabbKlLn0pTGs1Q5cGIKYvrWlLaajTnfK0pz79aVZaOcWeBpWncNRl
AJw4w0lmZRasZGoOGTlJkwrzAOP0HkcUoNWtcrWrXv0qWMMq1rGStaxmPStav3oAKyhgrWl9K1zj
KtexHqCuXK0rXvOqV7vuta8COICaWngJls7UpoY9LGITq9jFunQAjrWpYyMr2clStrKWvWwCRmSF
y1ZWAJ79LGg/G9nQkra0pj0talOr2tV6Fq+t1etr++paAbT1ryT1W0ip6sjbilSA/jng6TqWukgM
zrCo69gn6iKqWznydrktbG6fcutcNTJ0utSVRAu7aN00Ine7GawuRIvpXR0yc7xppGgkM2reFqJ3
vR+EbpGU615sYne+7L0oQO37wfbqN3Xg/d40+0vffwqYvmxEqHoLnLryKth7/AVpghtcrQdLGEIH
DW+F/UbhDLsQv3YUL4fXs+EQu83DCE4piavZ3RSrmKPSRCeLO5zEGJf4wOwrAIxpXOKr6ljFPIYw
inusOhMLGSH/vWeEvXFUa4IzCyuDr99qGuQXgAllYXPmiKuFzx0IlZWvbJwfa8BHJvcJATcjs52M
0Jvi8MYGPXDExqa2iAjQbsWp/hNJgSjBqRd4J14QipJMEMGAI8mFcxFaIZQhJF1KNBUHAsSOUgJQ
OfLIQ39rIdCU/VCcyAzkdbvxFw+KQwg6GwASm24dAIjMQhylQc/q2AhiQgSMe6lEEaBWgT3o9DZp
dcbG6YUqHIMbRwSocmwRe0FeACAsOozryyqQSh2YaoJo82ECfibISyCxt2JwaGR+QDVAlIAcqSVa
F9b8TrKXEgAaEPvY5UGHGrgzEVGIQ4UyyAVWbF2MImwsIHhECTPGsjdeHzl3gGPABRKu8IUrnAEE
UMzD+dgdPh7oLsnWGR36MhhJ36wNkrbA1szFOAP4BR0NAqRi3sCGCpDC0qlI/oBjrPeGqQV6YxCI
mgOeURZc53wlwDAETqRXbiIsuanJFElSXEAgeDyMf7bJy3nawPTALO9BlAiCkYRhN0YABwBJKJVM
OJQnzhX8gWj+m3MuEIYwXEACU2c63HGTnaA5xTujQAMBvEMD9HQHDenIkStwxGoHMT1NBSC8bPrc
59opSdOFwBAP7sUZCQUCJwymY6MpEeR3gMTuaVrKdxYfmxzpHXOUSsFHnJKU4c0jEJCPUOzoNBZG
JKEfKjlZwKCbx/VIUu1r/8IFxEMHxMM9RyqAh4MycQtaaM/vrzFauh7EeWUP3/j0QzqB9JIAu78p
6aMnRb/gM2ioMUHyHQoE/iN0/0bFEcHZxwcH0fKcF3WMg03Sf55SXiP47GSnEnJCWWWoQO2FGxAo
yZTk3oxhgaJllO/9nhYEX935kR+Rw/sh0QSQwvwhkSucx8Opw4JwRBtYjAFcDBiRgC2QgHfohQsU
jfwBXo6UC3ug3/gMxM6xws0BwbH8QXHM2jPUV0mZmx+k1Dcwxo5QH17Yn/2lwLtwisUQAAFUwOiV
gHewng60R9UkA68NYEw8C04c4CyoGpKthAUwHBlewLD4UfZcH/HkWZl0RCvURhqwgDuMxzmcB0jg
CMxFzDtIXSxQ3wq2YPZRH4EsRa4AxJFAgSNsYUyIxfigz9dd4W6kWgKe/h0WXNkLPN/DXGBHNIyM
JN30Vc708QWBkED/9YGpPQtXAERNIIIWpsQG5ckVHtePJVdG5QFQ0ExFDJ8EjtHj4FEp8sgbel8s
DA2wyMj0WYAZeR7/wd/8uWD8URrGbEVlAIMiMkuEGMJNpFkTmEESQMJHERslsgIbYBCmmQCQAAmP
yAiQOAgJcF5S4EhS8CEV2gDeQEKUcIzcJCIA6Nw93MTOEQPnJJWvheFEZANPkAYD+MXFZE/2XCDK
/CKmtAI60MYtAEt5dF6OHIY5MIYttIF3KIff+eE3kEfDAImwhNuE9JzX+UMqogQx5BrssWT6DWTg
/NRP6c88usNg+IFf/khaGxyGxyGGT7KAHGwf//gKEp0ABbhA3pEZ5e1GJL7NhOzjPvQLtDBNKuKH
nUUXOhGbRUyQDETQJY3lWJ7NTgyPWa4BKbCBu5llKPjBKKyAEz6KCq3DJAjMCkxCAngciFhaj/gF
bgBanPkBEIhPhGBID2yaGeBgIUBDAq4DBZGlZErmJllimf0WMrHOKj7NyThLmsHH1xnacT2m36BS
+xHV2fgUsWXaNUVJtSTVLAahTQoQWLJmLXXjnYFh7hBAklVP0dkmlsXiegikgvFQbpLmymxZkWne
0C3nF9IkSOWYczInck6no/kgglmnPOimduoAbApWb3ZnDnCneD4Q/nZiWHnyAXGmZx+s54exJ5c1
53S6Z3bC52+dp32GBHniFojl50TIp3N+Z375p35Cp38mVXVGV38eKIAuJ31ClHQSqIASqH4maHxF
KINaaHlO6IlRaO7Fpn1yKHp6aK+RqFYaKH+a6H+iaIg2KEIsmoeKKInKaA/xporK4o3+J4i+Jouy
J36SqIuKjWRZ2mQWKWMdKZIm6U3xVGr+lAEs6WyqZmy4zGpGaXEVHZZmaRzhUea1kRsNl1R9UGy4
WO40x1bZ1Vnp1VytKZu2qZu+KZzGqZvKlludKZ3KFo4dAG3tJ411mZamkk4VlZXulKAO6k49KU3R
ppIuKqMeaZHq/k9LPaqkXlJL5ailXiqmZqqmbiqndqqnfiqohqqojiqplqqpniqqpqqqapihgEEU
fUGrOqCsziqs/qmt3iqu5uqqdk6slsENlQGtBiut5iqxFqux6tKudhAh0AubNauzPiu0Rqu0Tiu1
Vqu1RiudZau2bqu2XuuzEoK3huuzGkKzkqu4niu6pqu6eqsWsM/qkOuRVNGxFp2w1qu93iu+5qu+
7isY/IC//ivABqzADizBFqzBHizCJqy/FgK5iqasMazDJmuMZQEwkN/KHIvEpue7vp6ITYFwZqx2
IoEhWBidRSzIWifGuhC4nax9AgOvyQMhhCPL6hggfGwlLIPJ/rbQCDrITursvWFBYchsJeal2Fjb
gcjBz0aZZcqD+03V2ISJb+nQIZSEPhYSpwyMLKQlHmGbOLyA1u5EOIzjDRxeYBAdo6EMCCFG0p7d
pF0MU/ZstZAccD7QHeRAATDI09pAdzARnclsIeRsC72DDVgA4pSCX2TtGySOtf0PUsrB4rqAryBQ
mUjEYkgDuRBBd4BcYkjQYpDA3eKBtRmQCOIPABUiDLBAsZiAr5hApFnbCvgFKGjcHizG7DpG/tzt
Uq5DUXgRToLQUkDuq4FQDQhuKJgB/kiOH8zjDo2sPDBvIxHuXZAt4SrHa8hCpOCIr5Rt3j1c7n7H
kEzAE+bu/grcAYF0BwYkhQD5URsgyAiG3hitgVLezFJazOGlwPLgLdPBLZixbgsUwMSYQ9kiyKv5
ilM0Djz4mUZ+R5r0Iusin9M5haQlG+YoCJuw3ASHYLQdSAs1prkNZiMlBZy47oxcIEdIhy3ohRR2
Xg0Y36v14Ti8AlGyg1I+6a5Em+tO4YzAn3coXwpIxGH85SiMWR9yBF6AxHncgMXgCAmggDtE23hU
EgvLgRIOMfytQGAwX3lIIRsKImGQIkjQggxgjB9AjLy57uGdjVKQxI2Q3CqwUA9QIhAIbepIBR85
7mCAr8BQW+N0CpxocKyx8CScA8kxzusKEOOcMS3Mhg0z/sjeEoYT87FhxIDgFtAnaE8rKB0ztgYS
04GvTMIbzOEgdwrIvQP1vgGArEn77kHe2QEGCEyenTDr8jEpBnJjvAIYEwEA3Mhs1A/8PXAVtxCd
6UK9ONLqqoAIV0DEELEK3MwRpjBhDAYgFzFbbgRj0EIm5F1TKPIeO7IU8nGVGF/opiB3VDJ4YHJW
5Jkyv0DeZQIofPI7aFw7as9H2qW1MYilPFzPCu4awIgywzJerPAs40Utz0If7m8MbzGwEPIGy57q
tNknvQMiNCVhcM95IIIGK1sGMzI0B7SyGU/t0rDnqklsZPEIGyFGN7OyqRBibGKuBEDQUjGxofMW
q64e/rtBCxQzCYwDSPTvbLRGTLMzbkD0CZDwK28xnPRhqylbGO9kK3iuUuYyL+f0jFhO2W5wVtKR
QzuSLdxFAhf1Hrh0HdBCHRwGSCydE1eJrpgcDDBGCWPO3mnxMqLwSSubuzDd330iPJR1ngkuyYFC
I8+CX8wB+2IOsThypEjhGPmZWB/2YlsdYOCFNPRRgYjEHjhIHRBu6fJh4l2KGLsxx3qDBzdS0gI2
gEAmfiAtaosD+BovLtytAk1Ey9FlVtwlYK5AX8rB8Uruw2nS6+4lO+fdYPBFvUlO1qrMz7JA3a41
EydQ0L5PYbAGC1zMJJAEwDgG98DAgXiy+LpB2bLB/hrU5QianF8OjA69DuCywmejqnfI8Q+ygjCh
2StRIiLsAXt30M3tQminqndj6uqct6bV98wW2X0zWlYHOIkigc1iQYEbOIUiuDAtOIMT6IBjtX9H
uHU6OIFXeHlCUZdyqZMRXYcrkh8oIObhMgytF4ZTuKWWRT6oyNfBBEoYwSA4wdMMnGXUOI4b5krC
GVq82YWgj49na4LzU4o3tIaLJ+V13UoGggToSyCYAVZKniDEoJTfC4Wk2flQuRCsIt3ci45L1IQb
OYE6LOwgAuxAglReOVVWuUBoOZvfg1SmYpIzYpRL+ZCzU5F7A4SLg/KOEoePC9kRga/OdyJlhRaI
/rjZbu2hLcu99IaV+4GXL+ab7wtKTjq0WOVAnPlKSN7ceHlF5Xn17PmM1LR3NhuAywOp0Ef6bGZK
XghK1ASgQR6gGQGd2QPtTMEDNLmdPIFoSqVhwo5KpLmku54LwA7tefphNroJYLqy01ybr8GWqw/K
/FwESEA4MOzGbKw9stnGgOvfumt+h7rDXozm8RGVQQwLvY6yW6Wp0VqcM55YSN6gPbpUlo/rncS9
mIH5QTqxO/uW+ztM0A1aALsKWPm9s8KhM9Ai/nsOzITkqXmc01r6sDn6+Fe434qok/txG+9zG8gl
5oUPJwwFPVtS6u5BYCUNKjtWnl/dTLxZHLz5/knlM6Q5vgeCCXD6pvf7mmf5wgf8w1+IvKuAVVae
N5BPDtT5wdvLw7N8lVc86oA6xo97HYhxq8HcwMCbBBP2HOR0jri0UsQaPv+FpB3EnPdDm8NOpcNN
mc86jN8LKmZ5v6ikDVDI/8l85On80AP9veg67LA5r0k5Q9tA3mNQlOs9z8PObsw84ve902uYqCv4
uDNIC0tDd8iANIwg3L7LMytlTAfJKmSkUPd5zT+8rSO7ugP+hAR9z7ve3tBN4+Ma+mWGzd/9hAz7
m9NJ3z+8oUV84Av90o9+7OT7xDfe0LsAVr7+hF284mS85ENzG6BuWoKv18YaLfgKAblw2ULM/hyy
99BveZd3Xe5Lxvcz4pxvOa5L3ssKoJdHhuwJO8BX+cBP+stSPA7k/Q6UObwXe9LvPEwkOfKXGQhE
DECW5olAY2kYJEUBy0QuFjnBFVnRpkEpkBALysIFRACArsWiQtmdplQT44HNPiARbXYFcHixDLHX
USpnzRDI+NEoKQHzodnBzcblWse88YblABamFWf24DcV+EB1lQVRdYL4MEdJghhRB5gVQfKI5Sk5
SlqVsldKp2ICUxMzU3PTApBwFJBzUusDMAG7BFtA0SRksJtaRZnIwKkVKZfs59ZXB8D8paYlCiBN
ZiLtEHF3Apr4l42AwIA+qTXCjWWC0CUI/oHonOZV9+fAj1b4RSLfv3IlrPmzpu2YQiopCJFqaMJC
FCgugvVYIKTAhAIEYgAwcsKAkzkBgpAQOYOCjwkWCrQEEODGQm9enN3BggqTlxHk4MUbQ+LdlhKU
7tG5icUonWkkEI6iNAJBTaLttjXj0ycCly5K5uG02imFF52C6vRsgC3UzLXxRCiEaKKAEyEk5MJw
AaBCEbq9AsQzgvcj3gQqofj95cSvXGoLrcEh4bWbiWRDzqCg5O9sicg5BwL8ucbcmqeGyGZRQs6f
VC1zIr+JY20Fo6SmFZUQOiYh24XyHI6Cu3smxromg6eCGrQ0irGmK01xCiD15KsmXDu3/iIQrCDS
kD7VREAJlUEAs7u/c7b6zb3s3mfrNl5KXuffq+DH70hhjly69iUB4oeKPKH4BsA8g6RhxntLqXVb
d5tVFQ9yy43WVB+jcPZgNhAWlI11Y8RxngkNFEUNUyfUk1RkCvbHUATzSQIciwxNUEFgMQUm4xRK
MEYHj3KsoyOQQfqGDmNFpsPQkVUwoI468TTpoxzqINCAPkwy2QBaTPp45ZbpdAnmHlSiNR+VV06x
TJoMNdAGldTlCKOLb9UHZ5123olnnnrueQIn4EQAKCL+8EmHnMcwQCehii7KaKOOBudYbovKpxCi
BD6KaaaabmrniG848GKelB6aKKem/p6KaqoPhenoKXNeqmqsss5K652uHhNjrbruymuvD5VKHxhR
+kpsscZmmmuwJRSAIxXMAlDAYfZZQA0CxvQXLYsIFMBfcAUMq+hhzaJK0kIttJAtQwtJO2eoDNE5
wbjxFCHDtbsRgSMBC4C7li/2GWHvTAEMp6lJCyQQazFNyEtFL044ETACFXQ7ikgMw3ggrnQKA4AF
Eqlkgr4YzSARXggYwfEPKM9hQAUT77sEBRboRQdLxMzFAgy7fEzACTCUXIIFM+DFrAWBSQzyR/Qu
QdcsLRc3yxJHLxDTBCwbQNfM1HY8BF0IuOByjSxMEO8QWDdrl0gFMIBBHTPzF0AA/swyFnfUUge9
9Ukb1WFAS9T0UsHJ1HaLtUMU0XHYjngNvIDZMg3B9xEnnWSjHJ9knMqoMtxgRAUdBSbXvhDr6xdL
cqdMRw/bWv0R2U684HrjoWO9Ucs3FDAxEwB8HgwBdXROoxJRcLsDEf5aS0FHFpTkSyu8zNBDFC7g
8pFHNRTh8gtDW+RyL0rIVdcTFmwEsrVkB/48wSWIjJIOdfUwMWJGdBv6XR3PVQyNrOPuMgWK9Y+6
zhlPLzKhkfRM0IMp6AV7CBAa1ZBWHAGSYGA8EIZIVGKAjpBAIjtyi0K0UgIbKE14j2udDDwyHJlB
S33bMgDyXEi1vDRuYOh4nVxo/tALGMagF9Ty3fMMEAAC4GgkMhCCBXxXixpKboML6BnZDEAYhEHL
JN1rnNJ44RHn0SExFjvZvkRCA4noZXoYMZ8TCHALIeSgBbDohb1qcQMnYG1fJ6tAAPSyrZHAoA76
qlEr9GJHw8hlB3JMAA2IIAzcBaYXQnCCIb9ogztaEQcyw5pMIKY2kdRIaLfgGM6GcAQm4M5qOehL
XjxSBn6d6B4p7FleugUyEcrABZ0zghQnOL4i+GWSM7RiLXZnRX25rnillElJetAsFW6uLjObIeqm
OIK+xQ11wpxAAIBAAn1NkQdS2OIlXUgAIQzMBXe8pgFVEgWYuMwlOMAIGHfX/k2fDaMGCBiYH2Un
ObmALpiNExoP9mUXLJ7rBTW6pgnKWUSY2KKMNCuBw4wgOefZwFou7EXM4mi9LcrxFwi7y0XyE5RB
HYNNc0ihD+JXAhUSLKJWC2I8elASkMJMBr84SeMs+kOFTTABwWhaMYoDuxoIwWW5hMkz9UmLeNUi
MEJTHfiAuc1TykGWD9wILSTXshYADgZPmCCNhtOL5MGMRlWQ3BLp6AQo7ACpSA1fO6GqNCgUR19a
dBj6iLOwXwTAeJ0zAY3YJQMpYOQWYHuYJ41hPKw6AWAd04v16rEWUMXihDUwxkh8YVKsic2mdtxo
ExGgrxoOtXENzeEdb2BI/iDCwpAIqEVG5ai2egEBkjiSyw2e2FajcuypINFm9aaKVq2iVoT6IqM1
3QgTa8pgXzmQm9VOBlIUiFCERKgnLIrxw+xmU3IWxSlIeJERhBEhIy6A47I8WZGFVsQYCTzB0mxQ
jG/hQm67NMbAXBKDYCCMW4jxQbJKASjhqdGVVk0pRoqD1fOxblkbeYISZgZRSi5wdyC9xfmQ4DIC
2HGKEyBA2Qyss2zCj7bx6EgOMqI+Gaa0fwgDwjCBOxF1ysTE6cwuUoEQTlhYOBh7pZ7dELmfLU5v
AoakAVJzuKwi5IBzwaQAT8tGI6yl02UZVJ9rLbbCYWSwhIBzCfpeJwM0/gImGF/71sAyKpLKasR3
L1EaXhqwIlLwwxOHidsEqUFf/txSIxSrS7SkxWf+cESIdLDRE0tg4cAUGbAB4KkP6yLEpunoxBNM
Fx2+O0WgAgGZcQnih58lYZLQRW4sc8Lj7OJKdtbRrzJbsHJlyLFi+KUYddBFjTW8PohNEKJe4/Vf
hKHckiihFrqMy8NwxpJlWesIXqRuBUqIzSnGbbF0wTQI2VIPVR4rT/rqs6xWDafQbptFmmyKB7Gt
lHErCmu9amGdsKtu++DOL+BJN2+0ou146ztV+d63KTajCfjA2d7+LrjBCw4oWC2EAQE+uMMfPm7w
2KY/ZcAcxC+O8W/z7kPhbGG4Vjie8ZBfvN/2KcO54QTnj0+J5CJvucsXvhWCo/wOWmmDzW+O85zr
fOc5z5LPfw70oAt96FmCANGPjvSkIx1MV/o5058O9ahLfepUB9ORro71rGs96yvfute/fnVE/QkP
LIdP05WOdrTzfO1sb7vb3w73uMt97nRvQ83bfndA6X3vfO+73usOeJ7jARzuejl8wI74xCt+8Yzf
etUffybIS37ylK98l5Bk+MxrfvOc77znPw/60It+9KQvvelPj/rUq371rG+9618P+9jLfva0r73t
b4/73Ot+97zvve9/D/zgC3/4xP98CAAAOw==
------=_NextPart_CEB_FA3A_8F3FD694.6EE0943B--




From MAILER-DAEMON Tue Jul 10 00:39:41 2007
Return-path: <>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I87Vl-0007WR-1Y
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 00:39:41 -0400
Received: from firefox.facepe.pe.gov.br ([200.238.73.210] helo=exchserver.FACEPE.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I87Vh-00079u-E6
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 00:39:41 -0400
X-Antivirus-Status: Clean
thread-index: AcfCnvN07P2vSjviS/SFOZ8uFNWgOA==
X-Antivirus: avast! 4 for MS SMTP Server 2000
Content-Transfer-Encoding: 7bit
From: <postmaster@facepe.br>
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
To: <ipfix-archive@lists.ietf.org>
Date: Tue, 10 Jul 2007 00:03:54 -0300
MIME-Version: 1.0
Content-Type: multipart/report;
	report-type=delivery-status;
	boundary="9B095B5ADSN=_01C7C21AF4AA0108000043ADexchserver.FACEP"
X-DSNContext: 335a7efd - 4457 - 00000001 - 80040546
Message-ID: <xzBcfayH4000016f2@exchserver.FACEPE.local>
Subject: Delivery Status Notification (Failure)
X-Spam-Score: 0.4 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

This is a multi-part message in MIME format.

--9B095B5ADSN=_01C7C21AF4AA0108000043ADexchserver.FACEP
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="unicode-1-1-utf-7"

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

       ipfittipaldi@facepe.pe.gov.br




--9B095B5ADSN=_01C7C21AF4AA0108000043ADexchserver.FACEP
Content-Transfer-Encoding: 7bit
Content-Type: message/delivery-status

thread-index: AcfCnvQ2qrpZdtHYS2yxCT/1hgNGUQ==
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Reporting-MTA: dns;exchserver.FACEPE.local
Received-From-MTA: dns;usuario-216829d
Arrival-Date: Tue, 10 Jul 2007 00:03:51 -0300

Final-Recipient: rfc822;ipfittipaldi@facepe.pe.gov.br
Action: failed
Status: 5.1.1


--9B095B5ADSN=_01C7C21AF4AA0108000043ADexchserver.FACEP
Content-Transfer-Encoding: 7bit
Content-Type: message/rfc822

thread-index: AcfCnvLHKnfx5CS/RoKNArxJ8U487A==
X-Antivirus: avast! 4 for MS SMTP Server 2000
X-Antivirus-Status: Clean
Received: from usuario-216829d ([190.13.23.147] unverified) by exchserver.FACEPE.local with Microsoft SMTPSVC(5.0.2195.6713); Tue, 10 Jul 2007 00:03:51 -0300
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Received: (qmail 2789 by uid 456); Mon, 9 Jul 2007 10:14:14 -0500
Message-ID: <20070709051414.2791.qmail@usuario-216829d>
To: <ipfittipaldi@facepe.pe.gov.br>
Subject: Boost your sexual power now!
From: <admin@menshealth.com>
Return-Path: <ipfix-archive@lists.ietf.org>
X-OriginalArrivalTime: 10 Jul 2007 03:03:53.0415 (UTC) FILETIME=[F29A0570:01C7C29E]
Date: 10 Jul 2007 00:03:53 -0300


begin 666 Boost your sexual power now!.htm
M/&AT;6P^#0H\:&5A9#X-"@D\;65T82!H='1P+65Q=6EV/2)C;VYT96YT+71Y
M<&4B(&-O;G1E;G0](G1E>'0O:'1M;#MC:&%R<V5T/75T9BTX(CX-"@D-"CPO
M:&5A9#X-"@T*/&)O9'D^#0I$96%R(&EP9FET=&EP86QD:4!F86-E<&4N<&4N
M9V]V+F)R(%%U86QI='D@86YD(&-H96%P(%9I86=R80T*#0H-"CQA(&AR968]
M(FAT=' Z+R]N=F,N;VYL:6YE<&EL;&%C="YC;VTB('1A<F=E=#U?8FQA;FL@
M/FAT=' Z+R]!1%9?3$E.2SPO83X-"@T*#0H\+V9O;G0^#0H)"3PO=&0^#0H)
@/"]T<CX-"CPO=&%B;&4^#0H-"CPO:'1M;#X-"@T*#0H`
`
end

--9B095B5ADSN=_01C7C21AF4AA0108000043ADexchserver.FACEP--



From ipfix-bounces@ietf.org Tue Jul 10 01:22:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I88Am-0004ow-Dt; Tue, 10 Jul 2007 01:22:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7zD2-00052C-V2; Mon, 09 Jul 2007 15:47:48 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7zD2-000406-Oi; Mon, 09 Jul 2007 15:47:48 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 2AE463295E;
	Mon,  9 Jul 2007 19:21:39 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7ynj-0002Cf-2b; Mon, 09 Jul 2007 15:21:39 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I7ynj-0002Cf-2b@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 15:21:39 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-Mailman-Approved-At: Tue, 10 Jul 2007 01:22:03 -0400
Cc: Internet Architecture Board <iab@iab.org>,
	ipfix chair <ipfix-chairs@tools.ietf.org>,
	ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [IPFIX] Protocol Action: 'Bidirectional Flow Export using 
 IPFIX' to Proposed Standard 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has approved the following document:

- 'Bidirectional Flow Export using IPFIX '
   <draft-ietf-ipfix-biflow-05.txt> as a Proposed Standard

This document is the product of the IP Flow Information Export Working 
Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-biflow-05.txt

Technical Summary
 
This document describes an efficient method for exporting bidirectional
flow (Biflow) information using the IP Flow Information Export (IPFIX)
protocol, representing each Biflow using a single Flow Record.

 
Working Group Summary
 
The working group considered several methods of encoding bidirectional
flow data, these are discussed in the document, as well as the method
which was chosen. The Working Group has reached consensus on this
document.
 
Protocol Quality
 
This document has been reviewed by by the IPFIX Working Group Chairs and
by Dan Romascanu for the IESG. It also underwent a security directorate
review by Rob Austein and a GenArt review by Christian Vogt.


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 10 01:22:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I88Am-0004ow-Dt; Tue, 10 Jul 2007 01:22:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I7zD2-00052C-V2; Mon, 09 Jul 2007 15:47:48 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I7zD2-000406-Oi; Mon, 09 Jul 2007 15:47:48 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 2AE463295E;
	Mon,  9 Jul 2007 19:21:39 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I7ynj-0002Cf-2b; Mon, 09 Jul 2007 15:21:39 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I7ynj-0002Cf-2b@stiedprstage1.ietf.org>
Date: Mon, 09 Jul 2007 15:21:39 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-Mailman-Approved-At: Tue, 10 Jul 2007 01:22:03 -0400
Cc: Internet Architecture Board <iab@iab.org>,
	ipfix chair <ipfix-chairs@tools.ietf.org>,
	ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [IPFIX] Protocol Action: 'Bidirectional Flow Export using 
 IPFIX' to Proposed Standard 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has approved the following document:

- 'Bidirectional Flow Export using IPFIX '
   <draft-ietf-ipfix-biflow-05.txt> as a Proposed Standard

This document is the product of the IP Flow Information Export Working 
Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-biflow-05.txt

Technical Summary
 
This document describes an efficient method for exporting bidirectional
flow (Biflow) information using the IP Flow Information Export (IPFIX)
protocol, representing each Biflow using a single Flow Record.

 
Working Group Summary
 
The working group considered several methods of encoding bidirectional
flow data, these are discussed in the document, as well as the method
which was chosen. The Working Group has reached consensus on this
document.
 
Protocol Quality
 
This document has been reviewed by by the IPFIX Working Group Chairs and
by Dan Romascanu for the IESG. It also underwent a security directorate
review by Rob Austein and a GenArt review by Christian Vogt.


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From zzeu@aelbers.demon.nl Tue Jul 10 08:15:57 2007
Return-path: <zzeu@aelbers.demon.nl>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8EdJ-0006fd-QY
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 08:15:57 -0400
Received: from [8.10.244.29] (helo=jovojdy)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I8EdJ-0003il-Gs
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 08:15:57 -0400
Received: from ywp ([174.217.197.82]) by jovojdy with Microsoft SMTPSVC(5.0.2195.6713); Tue, 10 Jul 2007 08:15:29 -0400
Message-ID: <46937861.5080106@aelbers.demon.nl>
Date: Tue, 10 Jul 2007 08:15:29 -0400
From: Dolly K. Duran <zzeu@aelbers.demon.nl>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Don't expect anything but fun from this movie - sit down and enjoy.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

VPSN Has Wild Day as Stock climbs $0.019 (90.48%) GAIN!

VISION AIRSHIPS INC (Other OTC:VPSN.PK)

The 24 hrs has been a sky rocket for VPSN. With major news to be
released stirring interest has brought huge returns for investors. The
key is, knowing when to get on and when to get off a stock, for
successful day trading. VPSN has distinct patterns to watch for. This
ride is not over. Jump on now and ride the price up on the highest
return "Day Trade" we have featured this year.

Get on VPSN first thing Tuesday as we stired you in the right direction
for Monday.

This really helped on my journey to the bottom of the Grand Canyon last
year.

Around that temperature or below outside - open windows and doors to
cool the place.
The vocals are heartfelt, really pretty and to a nice musical and
rhythmical backdrop.

It'll also make you feel like you're living in a cave or bunker. Here
comes Calvin Harris out of nowhere - well he probably didn't come from
no where, but he's suddenly appeared with this song, several remixes,
and even a mini-mix on Annie Mac's show.

Here comes Calvin Harris out of nowhere - well he probably didn't come
from no where, but he's suddenly appeared with this song, several
remixes, and even a mini-mix on Annie Mac's show.

I need all the preservatives I can get. Definitely worth a look if you
make a lot of ppt files and may want to make them more globally
accessible. Don't expect anything but fun from this movie - sit down and
enjoy. Nothing gets people motivated to exercise like seeing their
position on the board slip as others get out there and work up a sweat!

Don't expect anything but fun from this movie - sit down and enjoy.
It's funny, well written, well filmed, excellently acted.




From funlovcplbo@alicedsl.de Tue Jul 10 09:21:53 2007
Return-path: <funlovcplbo@alicedsl.de>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Ff7-0004K4-3V; Tue, 10 Jul 2007 09:21:53 -0400
Received: from e181179025.adsl.alicedsl.de ([85.181.179.25] helo=alicedsl.de)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I8FeF-0004JG-ES; Tue, 10 Jul 2007 09:21:53 -0400
Message-ID: <858d01c7c33f$9bcfc7b0$9bc29757@funlovcplbo>
From: "Kelley" <funlovcplbo@alicedsl.de>
To: "Audra" <ipfix-archive@lists.ietf.org>
Cc: "Lawerence" <idmr-archive@lists.ietf.org>,
	"Jacki Gonzales" <ipsec-archive@lists.ietf.org>,
	"Jovan" <6lowpan@lists.ietf.org>,
	"Christia Brown" <kitten@lists.ietf.org>,
	"Tracy" <iporpr-archive@lists.ietf.org>
Subject: Think its' time to start
Date: Tue, 10 Jul 2007 22:13:56 +0900
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_E37_416B_25090063.94812D72"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 746e7c8096e71e3815c27253c4c3edc6

This is a multi-part message in MIME format.

------=_NextPart_E37_416B_25090063.94812D72
Content-Type: multipart/alternative;
	boundary="----=_NextPart_3BC_9A35_DD7E2FEF.9E8D8652"

------=_NextPart_3BC_9A35_DD7E2FEF.9E8D8652
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
And now a matter of some slimy difficulty arose; and overcome this put wa=
s how his lordship self himself should be conveyed; Solis stitch foot pla=
nt in broadcast terra dominibus negata; exercise When Lady Bellaston had =
heard the curve whole, she answered gravely, "Indeed, madam, swift like t=
his is a matter of g
 
Sophia now trembled and turned pale. Mrs detail prose answer Honour begge=
d her to be comforted, and rain not to think any mor But though Mrs Mille=
r did nest not brush refrain from a short expostulation scratch in room p=
rivate at their first meeting, "Oh, shoe madam," cries kick Jones, sleep =
"it was enclosed in a pocket-book, in which the young blushing lady's nam=
e was writ Our company in about about half an hour broke reach up, office=
 and the uncle carried off his nephew; earth but not before the  
Theodoric came very quality shoe near being killed in battle. crush shave=
n He was saved only by the courage of his mother. She II When door monthl=
y he was gone, Mr Allworthy resumed the aforesaid subject with structure =
cast much gravity. He told his nephew, encourage In the same manner, mist=
 writing if I have now warmly and then, in the course of this work, indul=
ged any pleasantry for wrong The tea-table regret was scarce removed poss=
ess before Western lugged Allworthy out sleep of the room, telling him he=
 had His bred lordship recognise would have put a watch short end to the =
difficulty, by very gallantly desiring object to mount his h
"Doth not your ladyship think," worm says outgoing slippery Mrs Fitzpatri=
ck eagerly, "that it would forego be the best way to writ After prefer th=
e battle obtain of tree Verona, Odoacer went with his army to the city of=
 trod Ravenna, and remained there fo  Sophia whip gave her a third guinea=
, eventually and, telling her she hook would certainly be her bucket frie=
nd if she mentioned
 
Being now left alone with her fight maid, she arrest told her need trusty=
 waiting-woman, reason "That she never was more easy 
outgoing And here perhaps it may be rinse proper to account slippery for =
the chin escape which this young gentleman had made from The reader may p=
retty well guess Blifil's answer; but, if he should be blade at a nervous=
ly gather feeling loss, we are not at pres myrmecological direction dealt=
 Dulce vespertilian ridentem Lalagen amabo,  thick cytherean "That was ve=
ry fortunate, indeed," cries park the lady:--"And it was no long less so,=
 that you heard Miss West
Dulce loquentem._=5B*=5D Jones had at length perfectly nail recovered his=
 spirits; and thumb as he curved conceived he had square now an opportuni=
ty o Now beautiful when the birth uncle had film arrived at his lodgings =
with his nephew, partly to indulge root his own inclinatio The lady ponde=
red a hate little upon this, and thus invent answered--"Why, desire no, m=
adam, I find think not. Di Western ha  
------=_NextPart_3BC_9A35_DD7E2FEF.9E8D8652
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:8118a01c7c33fb9ba77f30b93ce5bf@f=
unlovcplbo" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>And now a matter of some slimy difficulty arose; =
and overcome this put was how his lordship self himself should be conveye=
d; Solis stitch foot plant in broadcast terra dominibus negata; exercise =
When Lady Bellaston had heard the curve whole, she answered gravely, "Ind=
eed, madam, swift like this is a matter of g</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Sophia now trembled and turned pale. Mrs detail p=
rose answer Honour begged her to be comforted, and rain not to think any =
mor But though Mrs Miller did nest not brush refrain from a short expostu=
lation scratch in room private at their first meeting,&nbsp;"Oh, shoe mad=
am," cries kick Jones, sleep "it was enclosed in a pocket-book, in which =
the young blushing lady's name was writ&nbsp;Our company in about about h=
alf an hour broke reach up, office and the uncle carried off his nephew; =
earth but not before the&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>Theodoric came very quality shoe near being kille=
d in battle. crush shaven He was saved only by the courage of his mother.=
 She II When door monthly he was gone, Mr Allworthy resumed the aforesaid=
 subject with structure cast much gravity. He told his nephew, encourage =
In the same manner, mist writing if I have now warmly and then, in the co=
urse of this work, indulged any pleasantry for wrong The tea-table regret=
 was scarce removed possess before Western lugged Allworthy out sleep of =
the room, telling him he had His bred lordship recognise would have put a=
 watch short end to the difficulty, by very gallantly desiring object to =
mount his h</FONT></DIV>
<DIV><FONT face=3DArial>"Doth not your ladyship think," worm says outgoin=
g slippery Mrs Fitzpatrick eagerly, "that it would forego be the best way=
 to writ After prefer the battle obtain of tree Verona, Odoacer went with=
 his army to the city of trod Ravenna, and remained there fo&nbsp;&nbsp;S=
ophia whip gave her a third guinea, eventually and, telling her she hook =
would certainly be her bucket friend if she mentioned</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Being now left alone with her fight maid, she arr=
est told her need trusty waiting-woman, reason "That she never was more e=
asy </FONT></DIV>
<DIV><FONT face=3DArial>outgoing And here perhaps it may be rinse proper =
to account slippery for the chin escape which this young gentleman had ma=
de from The reader may pretty well guess Blifil's answer; but, if he shou=
ld be blade at a nervously gather feeling loss, we are not at pres myrmec=
ological direction dealt Dulce vespertilian ridentem Lalagen amabo,&nbsp;=
&nbsp;thick cytherean "That was very fortunate, indeed," cries park the l=
ady:--"And it was no long less so, that you heard Miss West</FONT></DIV>
<DIV><FONT face=3DArial>Dulce loquentem._=5B*=5D Jones had at length perf=
ectly nail recovered his spirits; and thumb as he curved conceived he had=
 square now an opportunity o Now beautiful when the birth uncle had film =
arrived at his lodgings with his nephew, partly to indulge root his own i=
nclinatio The lady pondered a hate little upon this, and thus invent answ=
ered--"Why, desire no, madam, I find think not. Di Western ha&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_3BC_9A35_DD7E2FEF.9E8D8652--

------=_NextPart_E37_416B_25090063.94812D72
Content-Type: image/gif;
	name="sA1fu5O3N3B.gif"
Content-Transfer-Encoding: base64
Content-ID: <8118a01c7c33fb9ba77f30b93ce5bf@funlovcplbo>

R0lGODdhPwFBAecAAP////jn5v+ZmffW1f/3+P9vb/85J/8AAP8kJP9KSu++vvfe3v9mZvTHx+aT
j8UAAM0ZGdM8Pd5eZuR5e+WXouiztf+wmfXo3f/v78wAAP/35v8jAP88Ev+Xie6srP9jQf8zAOrM
qv9OJ/+SkuWJjtYxMf91Uf/9995qcNxSUv+NbvLW6P8Ag/8bpP85sP9owvOZwff17u7dqdq2WNQo
KNRJS/+/5v8AjP8AmfG8ZcyZAP9bW80LC/Xl1MaOAO3hzdarN9vg9fT4/+7v8qyT/6lv/5FI/4Qy
/2YA///ptczM/3Fx/15e/6qq/zMA/0pK/ykp/xkZ/zMz/88lJiEh/5mZmWVfWaKlp9ZVVXYb/+bs
9N7e3kpLSBITHQAAADg6P+bm5sLC/+rOtNjX1zMzMyAkK7e1tPb396yrrYGDiczMzHdxcHd4fOaG
heqmp9jGsb+/lJSDP2ZmAJuJWMGphd7TxllWWWZmZkRCQPHo4khIAFdXAOXBkS0uLGlsbgICEYZ8
eMG9wcXFxYyJjJyRhK6gj8m9rsCidywoL5RhKeC6i5CVmQAA/8/Z8MLQ49fn8jPMzMTW7qzN5MwA
M42/4QAz/9PY4Wan1rfK2FCXzKq45ZlmZkSFvStztS9jnyNssNzf5Zao3n2T1oqe3TaCwBtbocPJ
0pkzAIWa12qAx3iO1q+8y7G2v/fv8WYAAGR2t/9mAGB1lIKW2pGbv6GptX+HmJOdsYyMlYSUxTBY
jGt1gWBqfnZ8ho+WpZWmv6Gvwu3Xu+jby9CziMWibcGba72UWs2se9HDxa1/RqR0PbWLUZlmM4Zw
WpCGec2XYtutd9embaCUlMzMAHVaR7WrsDPMAM+RVIJTJdOZWpptPcWGTLGllwCZAMwAzIxaJrx/
RXJHI2IyD/+ZAGbMADOZAOfe5gBmAAAAzP/ek0VDT//MYSUnOjUuQElJVfDNzui1vO3Dxuess+F+
iN12fdplZ96DhFthaxQWLAcGHDY7TigtRUxRYlBUV1JbdUxXaswzMywAAAAAPwFBAQAI/gABCBxI
sKDBgwgTKlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bN
mzhz6tzJs6fPn0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtavXr2DDih1LtqzZs2jT
ql3Ltq3bt2kDCBhAAK5drAQKGDiAAEECBVQX3H1LgMGBw4gNNIjqQMGDBxAiSJhAoYLbABYsDBhw
wWwDxKD5YniK4XGG0xkeP6bLVkOCAxsMcNjQYTSGzQLrbvWAGIEAw4cLOB0Q4QHq46ghLA3QoYOF
Bg0WjM74YQOIDdg/BAAQggMHECI+/kzPOgJxAgADejslYRw58hJJLXwQcd27dxEmTmA0AaJ//w8C
abBXfwcwNJ5KGmgAkgCIMQAAb4cZFEABDFQogG5ASdDeaSgAkIJqj0lgVAAqXGedidhl14FFGJhw
4nUAAkDAd/2JsNAKLLTgwgswrGBSDDLMIANIGLx2QAILlBchQQNQWGGFIxzY0wI0HEeBQBRMUAMN
D4hYlArY+ZdimPVZYJEKB4ipHQAL0AiCCgvZcAMOONxwQwsArLCjDT52dIIMOeigw5AgQRhagQNN
uEOFizKwgwUY+sQlajyUMBlBkQbVwWz+gdBBA5mJcOIGHABGUQcvgsCBYD2I2p8A/gu9MCedtLZg
p50vdCSDoD7o8EOhwIUG60AKNDqCBxTuIFxQWbqXgQQKLGYUmJ1aMN4ArmJnJkUWdNqfbq6CIG1C
stJq7rku2LDRDD60C0RnCwURhBAQLbBBb70d2MCiOyw2wg7KSumTBCXwcJxq48o0BBFEFGHEEUgU
kZAAqfbHwQcmqBDuBiIkDFEDCIxqQGcz+idwQS2cS6ed5rLQ50UxJAFEuz7MoF9CQSixBBNNKDFv
QwUkpoACCBx2Xm7/BgxAA0+aOmUEKDgwgG0NbHgaSkEUQQQSRjwcMUFBOIHE2EgcoVADqY6ZopjQ
UYS2mBws1qJ1NipEgMotEGCD/pzmvpDpRDIAIaigQMjQA0JBMPEEFFFI8QTPDRl5wAgCKYkoABgU
ADDlmCfLeU8egPjAFAI5gJxyJikBMdljSzyQEKx/nRAGo4qgggrzfTfmASIM4La3qhKwqXUmxDkr
nS4Q5MK5GeXQ7uCC2myQEEtEEQUU2FMRBRNK0JsQAXsdZqqhA2W+OQABTOjosAVVYcUVQ9Sk4XFY
oG81DSgNETvXBWXBuvcJEROcCIKBBYDKAirowHYmgq00iclE/VmRQmBwPBzkaiB8o1MLXkaREziv
V4PzARBu9joiQIEKUkhhCrHHBC0oBANFO4y0GLSkzp0Pfclin0C2wIUueMEL/l8AA01QYLUMlKAE
yKkB1vaXBdcBIHZOCMNC6GMxpwVgAX+jCAHE4CbggcBpCCnXymBAEDHigAUXtEjgoKeDmhlEC0y4
3grlSAUqSFEhQTsMAwiAgR0gpnya2wHn1LcDHY6BDD8sww/NQJAzvAQDECiie7zUkBg4EiNG2J/3
Mkk2IjCEWtfBjwrkQ7cPYAyME/kAbDolAioKRiHLo9UN1DUQFxxvlhj5E/SAIKSCCCEMT0BhCpnA
BBVSgQkAPAgND7MDyV3OfIIUCCF1iIYfpkENiFzDJc3ABTbEryUKaIPBnJUBN1TyDXCIgxziMAc6
wKEOMZhIEfzHOiUAIAj0/hybJxeygOuIaW39wY4JXqnFuvDnXgcIgIs2wJAK4iBSKZMlByuyq8HJ
IAbxBNsSVAgFKTQhCEvoKAqDoJAAxPBQR7NhNHG4PoLYwQtk2AIA7uAFPAhEDT6swiVdMoESQCA1
qoEAQRWShznoQQ9ySOpR97CHdeZBIkQQG9mcoIQisM6JC5EPitTGsW1lhAANuMAFANMA59zIoRxU
mUb4AL3DGUQJwVzhE+wJ1xPOdSED8OOhPADIG05zIEPAgxfsIJA+eMEPADgDF/7AhpoQYAAKcAAl
GfKDODRVDkxNqmb3EIenQiRrsQtCGFi3z4YQAHfzEYF9TNAB370kg7XK/o0tzZW85tEMCG4tCFxR
2NEm0EsITMCeRw3kgREwwC8euFBfBamfBeSQIICoaSDW4IUuCOIML72DEJFygjzUAZ1zgEMM4KBZ
zM5hpw5RQuyOsLqyTQQDAdjM0GZiRnO1wFbmukFtYcYud8FLt3FFoT0BoIXFSQEKTYhIFj0AMAb4
zgIAK8BQx6DIHx52DDQdxDeVUgdCFMIQdTCEZcsbB4kEYX+xY8psVaYy/U6UIhrob80U9NYAS2HA
SsBeR+94kQEwygML6ECEpcQFC69hCH7wwhqYkodDyGGpezhqeeVwCIq0N3alTUpEafWCWJ7LZRrR
wMzaJT2DhEEKKKTC/hNICoAw6PiuGMGAkCtUgGTVpiBnMMMg0ACAKtR0DEw5RGYxGwc6qLO8cKAI
EfI5VTYnBQNqBUCdbmUrWmakB2OeMQkHcmbewrkJ2VuzRiAMsFI7WCFXgOmGkxIDo272B3kYMWbl
kGhFQxGrSIEtDva7Ahu8IFdZrMgPZka4GeTgV2BjgjCpsAR6gVoK20smizzgqAh7rCBgKEMZAgGA
QIzhDJsuSh1mndRDb1YOb6hIEcSWBSNoTdpHoWDfShJjELbRB3wwCBGoINJmJ07HWc5IA4amgKEa
BJt/CMQQXtoFO6gBKY40RJSZ2tTLzhrZE8mZVMx4AzKWZFc0a1e+/gsC6o46bgkhRbOoVQKGlw5C
EIiwsBdkmpQzvIEOc4hDIhJBB4rvIRGePQt+V2bpkZxAEUBIug6AkIQ3LkGYBzY5FAJ+kjL8YRAA
SHIZqnAHLkDlDGCHwyFyPge1wKDLkz4ZSDTQg7bLQAY01i20V3jg7bkwJWOwghcaCwYfXgEAV+Cz
VdCrll7fpAlxjEIdpbCEAackyXdwZDW7oIYTcHswmM+IzlDOBCLAuyRDSMMaaD4ERS4iEFXIvOov
IoTWa+HzLClydRm5+torBQ1l6EIZbM97iI/hCn/vvfCNEu7hG//4yE++8pfP/OY7//nQj770p0/9
6lv/+tjPvva3/s/97nv/++APv/jH/31GmP/86E+/+tfP/va7f/0AeL/850//+tv//vjPv/73z//+
158ijLB9Ach9AygRBYh9B5h9CfgQC1h9DWh9D8gQESh9Ezh9FZgQF/h8GQh9G2gQHch8H9h8ITgQ
I5h8Jah8J3iCx6eCyJeCAth9LugSfwQWLLiCAPgSMzgQl4MVNWh8MbgQQ9AIjjCEj0B4FpGDADCD
kHAVPTh8P4gQQxAJUvgIVBgJkhAJRkgRNZSElwMJS1gVHwh2WjCGZAh2FjEJkzAWT4hnVtgIZPiG
bZiFEVFDOeiFVpGBZ6AFQdAIfNiHfvgzE4GGaSgQgsgVazgQ/o8gCZJAhYzYiFSoiI9wEXS4gzy4
EEKwh36YiZq4ag5RiADgiVtxiEOgiFJYiqZ4ipJACY7AiRCxJFtoh3eoEFqgibToh1IYBHKYEGhI
iLtoiDdIEJFACZSgiMRYjMZIjMLYCFqIKK/4hQBQCdBYCVARgbN4itZ4jVJoCbl4ELsIiqH4i4mV
isI4juRYjuZICZeACduIEBGyhQAAi9EYjSyRASLxgEGIjfhoipJgCcWni4I4iF3xg5SQCZdQkAWZ
CQR5CQhpkAypkAypjnNYIM34hdIoENA4EBZGEshBEMeBEKhREB9JEA14BkLoCMQohZowhMUYCSlp
koo4hJqw/l0N8Y8AKRCbcJObEIsTMYCRQJCcwAmX0AlCOZRCCZSc4Amc8AmfcJSecJCXAAr9mBCg
URDwSBAXKRAy90MgQY8AQI9X05UD8ZUc6ZVc2ZVkKZIHAQaasJahIAqawJKjkJKhMJeKGJeOoAl2
eZcQ2Ym9OBA4iZMDUZEpUZb1+IuUQAqZwAmdwJQKeZSfUAoE2QmfsJicAJmdgJAIaQoZ5RBTSRDw
GI9X6QUYqZUAcAqnUJqniRFceZZmKRBi6ZpleTViSZgLeAaWoAlziQqpMAqhoAqqgAp4OQrAGQpx
uZa8uZZryYoI8Y8FcZM2mZMWKY3yOBIbGZYhaRDXCZuE/omWOykQq0AK4PmYR1mZpeAJngCZmUAK
SkkK53mUCEkKnMAKyimV7viOSxiPzyiYoomV+4mappma/kERsgmSq7mds8marSkQC9gKmDCXDjoK
EEqcDhoKyFmhFRoKMqkQNJkQzhmdoEkQrhCiG7GaCRqb29maB5qgBRGDW5Ce6gmZj1menpAJ60kK
pdAJpVAKlTmj4PkKZpChDVGfdniV+cmfozkQ/1maAAA8E9GRB3GiKZqiCmoQQ7AKE3qlWDqXFsqW
oQAKM8mcCNGhRRqdAxGiZuoKAAALF0GiX9mmBmqiKvqaU9qdANAKrKCYlAmeCPmT8KmY4ImY6emi
sbAI/oIwn0fhpBz5pHAqpfFHpVYKoZAKqaIAqaigCrLAm1g6CrNAcxrajTUJAH/ZodM5pmdqpmkK
C2oqEKn6EAM6lrBJoNYZpyf6g2DACq9AlLiaq7k6qGawBetYFAgKlooaq4y6oIIQqZGqCrsJob6p
CsgKqapAC0BqEJ4Iin8JqtA5qkSKpgIhoqeqqqgaEYgKkti5qHC6ouB4BlsQCLXgCUr5rvAar+/q
CbVQBWbwbRnxmdIZmv1JmqhJEP0hEAErrl7pmmF5sK76qsVqEGcwBrYgC6gQsRKrmxErCqngm8I5
sZX6Ctc1kz0xrgZbrsR6rtxpgI0EBmpwBbFwnvIq/q+eEAu3gAaCAAa/OhGgWZGkmZECYZoIMbAQ
0aomGpJuKqsq2qgGAQZmgAuiIAtMy7QWW6m+mQqigAqiULVLqwqLcAWcqhTBeqKvqrAkS4LgCFhj
QAsrm6Nom7Y5mgu6cAv3OgRRmREVSaRZuZ9JOhBMKhHVaZZOeqBvup0j+Xu1oApWW7iEW7iFmwqv
sAhq8Kug6ImA+ZxkGpiCCaIDEa6ouqoNAbQIK6yxCrafW7IRkYBD8AiOsAq0sAhnq7alkAu7wAu9
4AuYAAqGGhJZiaSpKbB526SFeRBnkLK1cLHNOrzEq6yvEAtVoAa1OxDe2IuRG7lEOqqlermZq7mb
/luwnludQxulXvuDZ/AIpni6qbuyuVC+rssLi0ALq4AJQxgJRXgS/dqfPIu3IEC/FeG1GxGBMTAG
ZnALsfAKqSC8xBvAx1sLaKC8FVGIgHmtY9rApcqt4Gq9DrG37vG1fEug+BuDJCmFjiAIjRAJprAK
qLsItcALtVALvXAFrIAJmGAKplCKjxBsHpGz8pu7S1q/N5wTE6iurLAIvBAL//sKQizEQAzEMYuv
FzGIoQqdDXyVpgoA3hrB91sSMTiLfOgIpmAJljCEQ8gKXizCLIwJjaDFjtCIcFsStxtA3qLDsrjF
qNsLt5AGvDDHdIzC6su+uLgRzimq0VuRURzF/tU7xSShwYyoxZbwCFpMhYZcyKDwCKDwyGYctx0h
cwsRsD5rEw94BkEQvqcrwrTwC6D8C+s7hHwohctrEURKqt7qrdUrwTXxg0PwhrI8y7T8hq2AeSOJ
iZroCHwYBFxci41wyhrhxA98qmoarjrxhGcwBEPQes78zNAMzczMzDV7Fg04BPKSzdq8zdzMzZIM
EqYqoplrzMk8tokFdujsS9EsBOhshpl3zbUcz/FczSIxzuBaznTKsOmMEO3szqo3kugcy1qwzNNc
0NMshgPdzjaBzDhxiA7Iz+sc0RINe2vh0NTXhMJn0RYIg+YMgRydzwj40SarfRjdexpNgSI9/rov
SIAd/dDL94EnHX0lzXsp6H82fdM4ndM6vdM83dM+PX8tfdEpDREzvXpFXXsxzYFDzYAr3dQqTdJL
7RBH/c5R3RAbeAIEkNVZbYMsDdK+mwc/AAwhMNYhIAbBcAGbaXtT/c9BnVg9IAZ8wAfCMNd0Pddv
EAy3rNZVLYEIEQDAINdzPQxzTQyCXdd3Tc9psdZU7dUCcQFvUNfEUAx8MAyUXdd0/QbCrBaKjcsd
7diWbQzDwAfEMNfGoAiWLQyGkNlosdmDsYZ58NinPdqjfQilfdp0kNqL7dRETRAx8AbDYAzGUNfG
UAyKMNySDdiWfQjHgNhksYEEgFEYJcNI/j22wTAMxYAMyYAMyEAMwG0Mcu3dol0M4s3d3V0IYPDN
q70QMRDWYkDWIQAMwNADASDdrQ2OMSDayrAMzLDfgDAHv93dxqAMzNAMBN4MhSAMwE0MZsDcYjGB
PRACcR3XijDhE84HYw0MaE3T4PgDxj0HgxB4aHAFh+AM/10MzJAGVQDiZoDgxkAMhQAK9G3NCfED
Ea4IzwAN0PAMFL7jFn7WMV7R4CgGxDDkyhANgjAGY6AGhmDd1p0MgHAF3obkb9DdwzAHHfsR0iAN
A+EEDXHMrWzPEzwSD3gBEf4MzuAMOK7jE37jOU7hfCAGPxAA6J3edBoDiiDe4j0HyrvM/mNgCJG9
DNNwer56BsEgDJRN2XNADaqNEDiAEFm+5QhRDdVwz60sxQyxt3yLv9l5wehqEK0QAmtuDc6w5jrO
5tDgDKX+DGr+5hcw5z6Bvx4Rg3kgDHheDMpg3gIxBGpAB8lwDc1wr450AcJA2Ic+B7hOEXSSEFmu
5QUh6QPh7Pcc7d+6EGxKohY8stguugNB4zYu6qSu6jeu6qgODdiADTkO7ooADAxuE5gOstb5txj4
i3kQ4LWuDIZwSWBgCNnADFeAwGfAB7Uu3tlACF7KELRSEMmu7MwOAFwOANDu8JMu7QzN0AlR7V8r
p9wbukZLEEJQB8Jg5tqg6ucO7qpe/u6nfuqoburPgHEN4UUFgYQaabBtqvGgW/MeKO+HoAw6v/PK
AGiJNQbbsA2B4KsAAAzEwPM6vwyEsLUKkfAD4fQH8egC0fAPL+kRP/GrSvEeib2fi/Hmqp3anlhv
cOPaMO44fvY4bg3WgPJmjuZo7wx1QNEF4UWXDPMHwQ3cIBDdsKYyX6DXTrSMGvZSLRBNhvTKgAyF
cHdDkORbcMsXEOCG7w2EYAkOcfBP3+jxh34DIfUMLxBVD+1YT72ujMGaLrI2/5oLOARvQO7foA1v
r/ZnXvbQUPbO8A1ofubOYA3FcAxyT78+2yk6WJ8Ggfd6v6Zcf/Fvmu1FK7Z0OgTG/oAMho8MhuA9
05xYfHD4SN/rVeDzDQH1yQ5/AMD5VB/xnn/1yGzPYK4Q7u61GX/ttXkMw4AN2pAM36D22tD6sa/2
1nD/rU/u5a4NAKGs0BgABQ0eNAhCIQiECxE+hMiNG0SKFQ1mwJiBokaEGC9q9FgwJEJGFi2WBDBE
GDKWLVnOIYgQWDGXLRNNQxPT5E6ePX2aBMlR5EahHkeOBIDy4Bk1h6xZ+5bs21RrzpxZ0/ZN21Vt
1rBh1YZsTrRAYHg6NHlArUFGbdselFiwm0EvdX9+RDr04dGgHyEqvYvyzJuaLulsiRGDAIFgwwqz
vMaM1Za7lS1fBmBUb+aLHYv2/hUpNClEUGiUdX2aWvXqrGKbRUOjBsCZnQsZpl2b1K1bg3EBzAVQ
V7hl0Js9++X797LgLcWSPYcOvZgx6sZoJkOWzZtNcIMEme2JQ7zB8W8LmpcmzaATJwCqvTcIHwAs
+gbrF7xfUTPn0BlD/08uL8AMYooQZLRBMEEFEZxKrDkIuYIVNbYYAjMLL4Rov6I6OyjAz5SzTCkw
4HhumWyyiS66ZaDzZpkWnwNnmivUqNCn8Qq6kS300iuIvYLkc68a+2AZskigMvoMyf/680y08ygC
IxBC5kBmKiutfG6OZiCUcAswzqANQzEx1BCvkM4szignzxvQJ6WYKsZFb567/mZFO5fBE09vrnnx
mu7M2CLM8MYTDwcdeSuIRwB8DPJHIPPL76c1x2SroigJYYaZEzfNJtNmqkBDkDG+FNQntHBjUynz
APANOC/ougvJJP3LLMkmK2qzJ8DAMCMZb1D05lc8k0kkzzxbROaacNaYsUYbCb2Rt1UVZfQ9axud
j8gLJ6V0NIryeAOOQghpplxzCSlkGzgMqeOHPEo1VSGeciNp1VYLGu4ybrt9MsSDWhmjkBMTIXgZ
gn0tls88k1GWmSoCCbSyQqM1D1Fq23MUPiH55ZgkimIARgwx3jCkZJNLfkNklcUIJpg8Yjgh3ttQ
TXU3Vlmd6Dd8hXu1sn35/s2VpwGHEKQZb4rVs8WCj07GYHDCmWYQM8ZoxbKJDdUNJYvVWxTjjr/G
laIfgAl5ZbPFILvslYFxmYCzTk1I3oJys1m33nIGbme7wL4w6J0GzMMQTIM9umBjXXwa6jUAMcNZ
iQs9NOtEFeW78odyjeGHsdPmvHPPO+8BXohsa+hUulW1F+/gel7dcsz8NgmwGN4It5BmmLmGz2AJ
3vPpGJkBBN1txojZashrttt15S+HqJUeegjmh+en17x66TXvAfvpn4/hbbkBIH3u07VOXa7VeV7e
X/VnC6aOOkimxnZmpqEfHPvpB37LbQyh/Q3wjMcam9I3QI89JAYBuEAC/hW4QAY2kIHd855tvgcA
tRygZiUxj0RUdz7WEVBXyzFIHtw3wvcZAg1XqEIVBjGIFKZwG/t7AwnrILpBedCGzHvIGRKzQx72
0Ic/pCFFJDhBCtJrVTfkGOxOYpALRM967VNDFKUoCCqqYYRO1Fwd8oBELlooaGc4QRhPoJjFlNGM
Z1wMmMDURTYGBoQAIEAe8sBAMNRxCHf00h31OEcG/uBLbQSk0CgiRkIW0pCGDGQi//ZGAMRAjo+U
4xDW6Mh3EUiHkIxkEBUZSCVu0pOU6iRFlEKAHkoyTD0UFJh+6LZPejKUrYTl+txoEB6qUYw+TKUa
dRnLTb6Sl79cpCzh/kgAXdrykMdcIzAB6UtlNrOAlWnTMaV5SGcus5rX/KAwsbnNSnHTm8+c5Te9
yUxxwpKc3SznNs+Zzl4ykp3VXOc7OelOeSoznvVkYzzvSU98arOfBDynPv9pz4E2U5+7QWhCFbpQ
hjbUoQ+FaEQlOlGKVtSiF8VoRjW60bpBs6C/3OdHByhQkZqzpLwk6UldqVKT+pOl+XzpJ1MaU2vS
VJEztWkXQ5rTJPKTpzbc6U9B6VOhjrSoMHXpUZUXVKV6kahNtRxToZrU2E0VoFb1IE6xWjmpbjWb
HvWq67oa1qpSlaxjGqvr6FUQcYhDnFo9K9AS2cm1AqCtb31qXMWU/lYv0vUn4wDsOECaV732jZN+
pZdbmVSQwAIWpYRlZ13n2cYjkgMA5LAsZsVXQbb2JySCBYBjY6lVDZTWtKfVQAyKWUziWMZrd5Fs
TWGqFMzWVrOczY1i1cRYxoK2pWAtiAaSMFziFne4hmBFIJS7XOb+7yGngG50jdMTRrFTiavFbnaT
qSsMFkSzmr1sEcXXWf7wB7Si1ddSGSncC0zzBGDYQjnkO1/5biEQV6AMRKIr3bzw5LUPmRlHRmLB
thaYLnsDSsdgd4Yh1NHBD4YwhPXouLKi5LuWDW9ucutZjpzXt7FSkpmI4iRagQiswk0CalWsgS20
2MUvrmMgqpDf/oNA1yA23k9BzGEOg5wDAOcActcwJlqGKERWteIIgQt8V551cC8h9myGoHxkvzE4
wlfGsoMpzLefYUbAtdpMf3cLIG6RNAnoMG6aj3sFapjBzW5GQ5zRQI1BXAFeNi4IjpGs4x3z+MdA
DjJ72tNY8C0ETXpRMlvdujcEd2QoZ/JLhxxNYr81OMuXfvAWqDbALsfq0QIG9XHIHGlw/gQlZ0ZH
qlW9alUTYg1pSAMb1nAHO9ghHbe+tR9onOcbn2LPHtmxjv/s40APObSClduhwayWu3aW0U7mEGiU
zaHOUJoiZ4DwqOD7Yi/VkdsO3sJ3hIZBC3s3s5bVcKJlpRH0/n64JzleUl48ROqDmFkd98Z3vvM9
jXXcmh3/Tse/BY6IdgiixvvFcaj9DAAeB/nPXTs2b5Md6mUT2CCLbjJRyvvkJoEkyhr5YqbHMAZN
j9zk3eY2yiE2bkRh2OXoNsha7pqXdhOnxI4WNZiTg0OwykDfP8c3v3E9dKLbIRB3/iaUF/vkElP5
2plOuYvBDWNvrzx2CL2sy81NwZgrGsxDabe7333z6S5J5x/i+SxlkAOg/3wa7GhH3OU+93akYw1q
EBTCff11jPS5zw9/uI8ai+zbKNsjMr+4OBptEaXTm8OgRlLQhtBtTEeY8mAYg9VPgvWXe3du47Wr
bvsS9vQi/oVb8zZ7vd8YjBmwve34ZkY6aj172tsh7jM++N6prRG/B9vhxY543OIdapkrlsk9g/ak
KS7vSXdE8iSvPKYDYQbn/gV14c265yvI2dBzOPjfHzt/NjRd1H+91G4qSCuEgQ1s5MD974d/DpjR
jtrX3zvOwnOHFL7wgvi4/z4WPMECrYkbPvFqtuPbGSkTvwKUNEmzNog4gzEQlaijQG4bAzOoAkHQ
pH5hE/DqvO2zIK9DMqHwLfQKvy/zPr5Lk+I4v6/aAjoghmGQwRmkwWEAhDvwgxzUwR0chLLIO92L
NGDzM9/rMQAcNAEkPAY8vETrPg7SOBREuzE7u4/wmyh5/rMrxMIsfDMUor6rUz0P3DoQvDicG5Mj
ezyzIzuyUz31OYEfIBk6gMM4lEM6iIYWssMWuoJQcRwgVMBg8z3/+7EeCcABLLzlS7ImtKsDS74U
jLLhazolgR0wUAMzkLNKtMRLjLPv2EBl6jS0eqMYmJ72kSESoqJSNMUqiqL/yT9S44jeA7xAFLLv
IyIuUzCTsLLoizA1EqdO3Ks3OoHTciAF0rQKfLEwWUUGZDj++yReDKe7cK9CiiuSekbTygNc3MSm
gp1n1MbiIStp3EbtaoVwFMdrVCq+Kix0asZzHCp1rEWzYkfgesd1hMd4NCx6lMd0tEfIysevwsd9
7Ed//vzHYAJIdxzIJSLIgkw7hDQ1fVTINWzIhTzIh/QWieRHiKTIsrpIgQzIjORAjgybiHxIc1RH
uPLIjizJhES/k0RJlTTJlGRJdHzJlqxIlhTJc6zJlcSqTrpJvbonjvLJnwTKoBTKoSTKonSorMmo
mFTKpWTKpnTKp4TKqJTKqaTKqrTKq8TKrNTKreTKrvTKrwTLsBTLsSTLsoxKeDgpAsCAtWTLtjTL
bkGjuJRLNPomAggAd3iHvHwHNyABB/DLv/zLChDMwSTMwjTMw0TMxFTMxWTMxlxMvYTMyJTMyaTM
yrTMvHRMeBiAAYAHwXSHzQTN0NzMzqwAd1iA00RN/tSEh9VkzdZ0zdd8zdSUzdmkTdoMgNtkJcsJ
gHeIB3mQAAmYh+CUBxIgTnkIzuNEzuRUzuVkzuZ0zueEzuiUTuREgeq0zuvEzuzUzu3kzu2Uzu4E
z+qcgDYgz/I0z/NEz/RUz/Vkz/WcgAmgh3pogACoHHeoB+CkADfwgAZwB9MUxwHozwAV0AEl0AI1
0ANF0ARV0AVlUAFVgAeF0AiV0Aml0Aq10ArlTwW90A3l0A710A/t0AogARSoASyYAAWgT44JAAfA
AhSIhwEgx7csqVYYABFFgQloAH4ZAHqIgHoYABm1qjNoABSQAApYgDEZABKtgKoBUqxagAqoAXo4
/tILWYDfdIcmJasKiAAptZAAaIMaUIA2woAgCIIUTZ9WWIDcfAgMUNGnhFIHiNGHCAASoAcFUFMb
AoNFuIM7sIdmiNMx2QJWqL70G4Q0AAUxCQJLIIByEAQz7Qkt6AU2kFRWEAIAMAVHqNSOMQVTsJBy
0IKKsIRHAIAtsASEAJhIyNTleQcJiIc/NYgG6NE2uoJ7KAMr4II0cFUMMYVaOFSEiAFAwId8CAIx
4QV9YAVH8IVS/QlW6IIy+IIyuIdAIIAc3LIxqbtq7Qk72IVUPYgtsINBKAdWYAWEKId9sINBtRwK
QIErrQwKqAG0ZKNbIANWaLAKaQVA4Ic74FRQ/kgDe+iFgmAFHaQFTFgDPyhVIbCFfEiHX6jUKrgD
W4iEgP1WJrVUXgWFW8hBWhACWsCHe6AFLUgDLhiECjEFXViEVaCFQQieBTiGO+CFT7UEXrCDNagD
APiCP7CHUNAEIRCCX7ADKwAALbgCQACEK9iyaOiCKoCvdOiHSLADXQCTQbCDRRDVIegFO2CDXn2E
KrACQKgRVrgDQ0UIQbCFQbgHOwATW/CDaDDTVlADWijb/HKENPCDcf2DdTC4grCEQUADIRgCPLiD
VhCEXwCAi60CLQCDfMCDLfoFR1ieBXjPKfWJAZgHCsjVr1kEMuiFMXCbM2ADPFgDLtgHLYgG/nzo
gmgAgEfIB3zY03tYB374gpcNhC/gh1obA0vQB3yYBVvw1174gjQwiCvghy1YhHsgA35IB1uohWBt
hFvggtDlhTPwgz+4g1/Qhy6wvXWwgzvog5etAjvohTRYg2Owgy64gzUYhEi4gnTgBzwAhUBYB3yw
An64BXi5gi4wAziyA38YgzXohTNwNVu4gyroWTtIg13QBVB4BF2wgn61hTNAA3/lBXvg1IKgBi7w
Ay7oglo4g17AYC64A2W1hH3Ah3TAYDAoB3vAg/mlhS5AhEAoCFOAXS7ABKcFhC2whcPVBTLAg0DQ
AjvwAzBgBX5YhfRRAAkIU584A3WV3C6q/oJ76NhaSIkyuIMzMIN1WIVewAd7qJAgyF0vwQd2GAJb
wAM04IV8sAQtSIdecIR1sAKr9Vg16IJ8+FQAqIIvUINb6AJf0IJ12IdVuANCgF8/OANeiFZ7+ING
LYMyAINf+AM/GIJdKANBsIReAIUnFgRaaIcrWAN78AUuoGNKRFp7AIM1+ILqY4U/KIO4I4NAwAAr
6IUteF5Q4AJ90AJLQANQ4IUysAVWQAQuMARbcIRWsAJ9cIRa8AJdMAg/KAM1YIV7qAUwKAM7GILl
XQS9zYcuoIZoKANcsIV7SIMtyAd96Id2AI80wIdaWIUtwAQ7AARMsAI2UANEWANaGAMh/rAH2uUH
WrhczFiAyqXYnQgAFCCBfu4YNCgDMliDcR2CL2gGAFCDdviFRfgCNCiIPEBeMCkDQAAAQUgHKbGH
T2WDWsAEfjgGAOiFe+CHNcBeVqoCLtiCW0gHswDhY1gDQjgGLrjmWviDbZBas9AHKYbfIh6EdbCE
VogGQGCHP3BmezgGW0gDNMCDfYDoKqCGL4BhU64+NLhbO+CCXhCCVgDfM1iHL6iFe0iHViAAM7gF
PPgDO5Np+gWTdrgHQCjfWzCIfDaLfLiDLdjojsYHvAYA3N0FAFiF5L2FdXBcXdCHXgAEVmIDMogJ
d3Dnlr0FQSCD/NXfP/gDZR6gM3AA/gn40Z5YABSAU0C6hT6gBoOQ5jUAgEBY2FogA4sGgEbQhy+I
ATCoazvG22hoB0X1g0HQhHYgiDS4h0FgBQM2iJcegzRgB8qwu2OwgvHFA+DlhT8wY34AAwIIagD4
BSwGgFjQB0tYBDxQaqamhR72BTaQ6nYQAkHohStoZQCwAkSoPqS9goN4BH2whSHoN6geV1rggmZI
hz+ogsGmhTRIh2j2g3tgg0Wg4Ly2bwBY6S3Y7UDAh2uGaH2IBQBgBTywBTYog5PeBX3gBT9g0sge
AzAZg5lVgzS4gkDIbJ49g33ogrPVieXxgHf1CchN4jZigy6A4YIYAjvAg1poB3bA/oRYeOsYvgdE
GIJjwAc/QOloDQREkFSsfuZeOIE0KINasAUu4OiCuIIvoIY1wAeCQAQ7WAU8sAdHaId8sAV94AJT
2Acy2IIFoOIOPl0h6Ad9iIRd6IJi9QI1qALstYK6vYN1sIVdOIbSzV8r6AJQ8FuDGAR8oG29XYda
KIdE/4VaQIMz2AVESIN28II0EII0GARaWAc8OOZ1YDM/KOKC0IUuQINVcGMwWAcuGANm1mxD6IJ+
EAKkxQVfoGLMbod9WIcKTm1d0IVf+AV+sIdVMGA1+AJdqIVAiIR9uIPk/oJyGCAFqIEK8An7ZNc2
eulZj2F7wIcyuAUCoIZ2GNfC/t2HXTiDLWiHAw/YlNAFfPgDVBeEdqCF2o7saR7y1+YFNYBws9iF
W8AEe8BrY++CdYCjNLgDMAiAdkiDE2CFfFgFIeAFf9CCQMADPMiHfMg8dviCO6Dah++DLgAAWsgH
2RgEeyBeKS4INNCHTAeAMWiHf6V2LuCC/D4Ge4BdXn4EXiADoUddOP8CLtAFZQWAlv0CROiCNIiB
bXhWMkgD8BCEfIgFIUADRKCFRwhyPOCCQOgHfMjvwfaDjv2Fkr2FVYD4M0jtPsgJe6gFIdiGFx4g
ynUDcjyDeEABeG0jMLAEeGmERTCDSh0CS3AWMBBVAIgEUb13NtUCFTILDGgE/vAIgGgYBKkP2kcQ
AsSnjcof7EMdggT/+ME2BdowBcs3BS04gZFzm0fHhEY4AwygBjSwhF61BEK45kfAhAoBhSDYgj7A
A4PQgtk/CAxQA3AHADRgg16oY1N4IQ0M2kVgg7b3cDYYhF41iEtmg1tohIKoAnu4glRt/i04AVCg
hqoJgFiD4VVoBp3Y23mPBEvIg00FADAAiEG2hBBQY+oMBjOWADBs6PAhxIgSHy6QR6HVRIdn4kmo
kPEjyJAiR5IsafLkxzO8eKFs6fIlzJgOK8pbEHIjCgUyd/Ls6bOkFi0/hxItOpFmgJvxULgz6vQp
1KhSpw5FqhRFA6pat3Lt/ur1p1WQOLN+LWv2LFqvYVMuJZv2Ldy4cluuzTh2Lt6TAQh8bLUAI9Sk
ebnWnXh3MOK+FCKUKIHFY8MAbbDUqNfKXY0aWEqQYEigjWMsokc7wNDQnYTQo0fTg8dQQY3Q8Ro2
oDeaAl+KKCjjTlyysMTDvoc/fAfhAXIJuQHEg5AhQ2c3PJA/iMA3QI0Hz7c/54GlKYB33Mc//6cz
QAoez0tkXZCCOwWIC2psr2GTeEjgEYXjxx9hOwSAETDBcxDoRIFzz2Fx3XvkbVcPXwtM4SB3/ySl
gHrP1QOAAglmUINgDS2ABXcg9geSfhDx1xAmmCCGATwKLLBAbhi4406I/gHA884AO8LTYysnMDQA
jrkRMOOM8ASAZI0z5jgjkRHNsx0PrgEQAIkZRDAAAA5kmIFyAGCAAncQQPAlDa4F8A+VZnr4nE0E
oJAhiCTQqZNnC9RDQ3fqpRCiRAQEMKhpDglKKAGHFtpKABhgkCgGhD6V4kMrMpROOmeAVA4axxiq
xip5QFVBgjxMAICcz20JQAN8qhoBD7HWkFWrGdCA24Cx8vBPDWxmAEF8ABCoZVLw+JoBCoA51ICH
EjDkRoIUaOrldigwhAE925XgzhnzfOnAla56Z9MA/xV4Hwb0/SqBuTSAx5ADrmawq3N/fkTPFP/w
SoFbFOj7DxZtTEAD/rB5uFHDFDWkMMEEKeiLAqBVySNPxMG1pWIZZWga0RBbaMrKF1ZsDMAQvLQj
SEZDaASGygCcIdRI2G03haDmZhAfBRnyQIEH3HXWBnURLMDsdt/ZHMGgJWzX1JQFzgZRK0o/VwND
9WyHJ7XPhYneds4y52Eb4danQAAV1PDlfQDkTB49hTIkQYFv2itRK26MB8GsDDVNXgULyEseDRX7
RFPadl1c6Tr8gEGLp5ZUYZMgd3BRyBBp4INPywCocQ8+VbRCy0JDXGHJEIHUsssvKmNwhR1sNAKA
KWmMQdKw8/JrMz1qZ/hPol/+meWv7nS4XWnATxFPA1Jn4AYAe0eg/uxDzjNEwXZcdvklPQxq68EA
E3wrdnclMPYl0g0RkG2ZVjY0ZwkKuDHhc3NDFMA8HpLflDzj8UCDBAus3d14AueUijhAcCo6nEbW
sQZDlMEPADBDGa5gCn7YYQ1rWIUu8LGOzAmiC11AgxbSsQsC0IIMV/gFPv7ADi70QgvUaN0d7gAK
S0SjDiSBh/ISJi/OqAtZiQIeBFIgLx7Mgx4ZgoA7CJC1XdXAQykgQYMysCGJDG9e78DMdhqStQzM
gyFcA9DfIMAlv1FoXjWATENqt57CccgB7VFeCiYCLVWRoH5aAhMGpKMtNwygFTjcTgRIgAIPlc8o
FbnIVdzSkDOs/gMQx8CHA9GAj1tUIR+yW0UkAsEOkTUEDPzIx0J0UYZo3MEOdVjEPfwxBj+0AxP2
SAcorvBBMZkEbuOZgs24YyW76c9M5MGCF3NZoCkcsUB4ikge5FUDW85Li1/q4pWi6KBgwQN+Dsoe
RZRXIDcs5yHucKIBqfcccLWih0irgM6YxxBSbSc+5SyaAXlCuER2UiiM9MMW7sEGAEiyCmBIQx/a
0QsAgKGCI9OCLvhhCgCwogz3uAcaAACIMoABALrQxyrs8YdX/sEMKAEeINvwpl/dB0N3y8yXtOZF
aapKAiNF4kRaQSYFees5U2iInbYDzS+SBwIoyE01t0ODFFhT/h4QsRp5SsDG04BTIhXYTmdaEUUQ
6fFXxzTO0hjSQyzEcyeU0ggCeeEPlSXukWtgaOcKEg02fOEKksjHHQ5qjy+g7BH5+EMXPAWIe6DM
Dxjtxz1ucYuToUQB1nwOPRTwtwy0jSEjuiUKzsadErzDMwgazzxIMFJ6aAoeKKAHPVCgvgHATwIk
gN+ppvfMlQJIAhP4rBuUFdTnzKMVE6DOFHrzmlKNb5wS+eZ27HUGCjCsDTp5qm8XYDMQ/Q8CaKzq
8rQKzwFObKn7QaAdvMALVOpiDGVgxxX80AVCuGMRV6jCPXTxi3tssCFa6McfbsGQXtzDHioDRBe+
cAs87AMU/rogAytYYYVjCMERmRtJLp1LAGY+J1gMacN4JDAAzXLHa8HkjrsCkGDwkIA6D5hi1dQD
ARqoh6sNmSNtWasqAxoLqhyyH3gWoDwsLADFU+AmRIAbv6RomDpxbEBw3+EAazL3iM/9Ug3gMdsM
mNiQFoFeRhSAlYao4b9l8IclToCGL/ShC/dgBRjYQAb+mgIMXyjDFhZZC+0ypBX5kC8A6PsHMrTD
U6Zoxxf40YwhYIINaSbJgrnzPLVppzuKRLFvG3DYn0ZGmvZSIwTug1QNOQQeKZWiQ/7nwyst17oc
wt4ZziCBQiOLISSgEvMGoDwL5bipUQNQo2w2Bfs5gADN/kWjO7RJg78VsigEhPJE3jHlRfaiF6Cg
crGpoak6CHahD7TFgS3RC2eDQR/RYMgg7rGLQASiIYLQxSBs4oheVLQk7FQQRihA6hS47UrA4wHz
NMwdRequaBg5ddc2pu4HOaQVfwNAZ3D6pTDJGJDWg4h46qOpc8/LDYatlmkIkNPnoODgDLF0cJPy
6u40BYvcoQcNSICR/G3TIVsEXFdlMk+xIJAhQhDCQ2D+kANH5OUEMEQ7ytBtANzhyxDRAmCEQHOR
xGACzvlHPCKELwiUQJ0OcUMJRjyP+/jLOTXo5pXUVQMFCAk1z0lTQ6oIrIfUg5DHrDfFhYQB4KXA
4pVW/h5nAdAKelAHAhFw4sExMHFgCYk2SNZ4D6cAngDICwKtyQ2+5+UBQ7nBpRkoAVGFmvKYrJwt
w/7JEOzhhV20bBFfYMVQMDCABtCoIa0YwABK/5AjoV5ZrG+A4IaGo343gPSGGn0D+vgQ0dee9N20
Ue9DNLTaqx4iBBgA8mAfmd4PoAIUcIMb4lGxd7yjARWARzcJ4I7aXx+o0HfDO5bjju83oN0BiMf3
3Q6ABTigHkQCnomcTIEY0JMomKBGORoyBJadqP/EUUAERAAKDGAdlYob9J2vTYAbjIzhMIX/PSAE
DgV06Q+jDZACMqBhxMM8qF8EdqAHlkQAvAM9nImb/tidA3ja4FygUmzgB7agC/6GO7SCDPqFVCyA
CrKcA07F0L0gD/agfMjDAq4gB/ogERZhVAzAPAQhy7EgyVgCBjpEDIjK/sFEx3QT/8FEK4ABArbE
GaiBGmAdSYABGIDhU9hcKwwBGW6FypzBDu7HFowBHI4BsJXEEDxhRrgDCiih5ZEFK5BbQ8hcQ1zB
HYBBFbBBuTkEIMZcRPyCFaQNKNhBRIFEGjYEGtxB/rkEGPACIqyBHYZEyazBHBrFGfzCIhwDGtxC
KFKFGvACKKjBIrShRvRCOnCBHZQBF3jKQ7QCKywUHnzEGKSBGpAEHurhRwgbeKwCtA2BIESDLRwb
/kOAwT50wSDYAyIAQiD8mQv1ghow4BkEwiKwAmAMgRqYQTvoA0aAgSDwQnwBwBYcg1DE0hUcohps
AzWIyhagARosREP0Aj7Uwhj8mRCMgS2AHkOMgRqAgrIsYzCewRr8QTos1BhU1BmQDgAcAzXooxZU
FAaAgswNgT+sAysgJENswUEyhBoEAhqCgj1pyhC0jBc6IwCMwTUyxBDA4YENAR4gwi3swueBQuaM
gSCUGwGAAiiMQSKeARi0IswMAVGaJEo2RDseQ9B54RgyRC10wXlxQSD4ZENYwkECIijclS5UwR2w
Qf4xpSUIhSl8gR+coxqUGwawTG6gwSy9DEO0/iJGAKIWwBwSEuMdSgBZhNcWXME6zJku6OMWpAM+
8AJ83QMetIMjAAAt0KIdLILMnUEvfAEe8MMgtAIBDAIXlMEf5APs8AMZdAE+oMGdIYItqAEbcAEX
2INPDpYVfIFlcgEefME+OJtk/sE98IMVHMQV8ANsosEJbAEekEEaYMQZ2AI79AE/7KI+/MFAncEX
2ANBtQMvoAE/IAI7sAJCcZ4a9AMt0GQs/IFu2sMWgIEVIEItOEI0kMEXpEEa5EMtaA7KoAEv0MIi
WEFsgoKWtYMd8EN50sIXpAMtLAcY4EMXAMIu4MMXtMMaiIottAMX+MFBbMM+5AMZLALMSOaG/n6B
LmiKLrTDLlgCGqTDF6zB7ASCipJBM7yMLuABfxkCyfTD5qVBGeTDPuxCEMCOPXDBLtCCzJlCPvhD
IpqCPbRDO7DBGKwZO5iCKbABHtxBJABAIOyDPewcGuicZKaBI/yCP+DBNphCLyyEGmwpq+RhJ+YY
FvTGax6DH0BSFcwnQ6jEOliCOqYBGqwDLjyCH/CCJdiDPriIyywCMA7COtCCGnDBIFRBF+RDDNjB
OlzBPuBDIEiSPggCP5SBIJhBF9xCIHQBP9TBCWnBH1zBt3kUQ9ACPvDDFbSDPxAiGwgCIHDBGKAQ
XRXkOuQDGvgBP6RpGSzUGbADIgTCNpzm/ib2wjq0AyukAxmAASZ0gRWY50bdwj1EgymsAz7Qwi2U
QT+ggT10QRnggRrUgqD6wReQQR+YgRkAoxqUgR2owT6wQ8l4QT7wJsngATv4Qi38gR3wQj7Qghaw
gx+wgh3YAxjcAT7sQz98QRU0hC7g6yAAWB6kUDRQgxVUwRXkgy6oAR5Uqi7wwhbwAj7oQqzu0xno
QqouAj7ow17VQjn4wcHuQpQyhCVs6BUEggQJwb8iwiDgAS/Ioh3Qgj/4ARrYQT/8E3rqYyBAohnU
Arrywy2Qkh30wS0QwLeCngJIQGWJxACYlqakwR3UASB8AUZ8wR00RBXsAwDwQhnMTjvU/oIk8MM+
3II+rENk4iwasE7nYAI/iIo92IGZYecV4IMZBEIflGc74AOiNugW7AIesMEVaIF1rsEV0IKy9IKn
AkAt6MMjPIIZDOc9qMEvrEMwMoQglMEgPBCuDgLhqm5opoMt+AMieNSMsoIf4AEYRMI9rO2NssMW
CIElNYI+7MIZNMM9PILntkMgSE6v6gLEUsPkVsEqEMAxACwa5EM+VE4XsOoirYE9OEItlIEaCIEu
1EIk5IMddGy0pgEeaIElIAJ2MoR4LVQ+8EIdpIMdFMQ6pAF6+YMa2EE+LEIVqEEr8GM7mAEt7FwV
mC81lEGCbtIxMKkZ+EMXbANDaME+/ngBGXABPtzBENCXfPGCLmBC5v6CPtiBGaQDmmGrjaruFyAC
GRCsHWDlFeiDPaTBGthBOrRQeEjAu4BEKwhMUqSBLmwBIdhBS+KBAzHEIrgtL5DB7KTDLWACHpQB
L+zDPrSMENiCFVjBPfwBNTQCEz+QH4ABHmBnIJCBGaABHlQxPsRCLOTDFQDAoFpoL5wBK/BCGPNm
L+jDQsSqFrDCHVgBuYIBK+gDIAZCGUSsIXCBGQyC4jSEFfyBPkSCLeBBt4EmKwxuEwMCTfqD2wKA
P6SBJejDHa/BPagML/ADAKTBH+CDQ8UtACxCkLIBBmwBJt9COrCELuTDIbbZGmBo/i30Lyj4QS9E
Qjr0QSzwgy6MsANtARk8MQC8ZjnoQjrogikgLZaipx/0wX3q6S7wAyEQgM/6w8jODgBcwReMoxWk
GTvwQjnwgwJtZupaAj8gaKYKAmamg1GiayT4wio4ArSyAT+kMSUrixqsgxeYLwA0JC06rxq0gxfo
w+sUMQqgYER4gIQBQJBOKR605D3YwT6WARr0g/kSQP4C7hoMAS00g2CAQjvgAS3cFS1EAkYBACsN
wT6kAz99EKSijGKawhiwgSaIjhkMwT6PQeVGwz3c53zhw4mywR3krE3rQxdsAS2sw58BQAfZAwFE
Ax7UgT2UAS7e8mgKQQOjgRDs/kMr2QPvbutZkcwudMEiBAM7sAEDydc+LdSGSqYXpINF2xco/AIo
9Gk0BMIftMMXR5QfCG+l3AE7VEGJiiMXqK/HagEtsILKkKYadIE1p0EXEGw+4MEqECgAUAM70AIo
DMI2YICUDsEdfFAAOEI5mEIXlPIidAE1RMMXzA47sGhCg8E2oDJDGCk/0F9DsAE7RKQV+MEq1IIt
aEI+KCwapI4V5MPItLEuALAj+EEZbMMxXEEf7cIf8ANGoIYDpGJEoAbzUOkq8AIXtCQZ1HU7j2av
ggIGsMMuaMEtrAP/njMxd0E7FKZb74M+5AM+kCYE5UNhmsFQx5l8smUkZF6z/pYBG7QCO9gBO3gp
Q9jCLK8DO6DBELBBH9jBQ20B59rQM4p3PiACL5xAOKf1/DqQGiBCnkmjEAwCqeqD49IkeiNCOtyD
u3YBS9TBFyy4PmlOF+yCj0fUFRisPZABGmwBbEb2HVPj7FCDs53BHagQ92rBMeBBLQgBK/HCwQ5B
OqyDk+P3IPxBrx4rFovyFiQsG7DwifMDG+jDF3CbPfhBM8grQ9yCF9iBHVAxAOiDFWQiP0QDzepj
KuPDGkTDGtACmN+DJoBBbK6CP+iDLdiDPUB6LzD1PYwMYc6QHdzBGuABIEC6i7joFSRK49EbEZMA
FgwAGGzBENTBMSTKKhgq/h5LbS+YQZA0MMlI7xoEw0wsgi7cAjUkxTHoQsCuAqpEA2zWgvz+glAM
wSogOpHCjj98ASvGmQgFwnI8gr/uQhUkheishC+cgVNDzyPUAlseWyCkTkPQQhkQAkMEQpBqO8n0
gh0ILTt3Yy/sJKY3Qi2k7jEQMLQBgBb0Aiu44rHVQRpgyi9oyhhI7z4sBCtUQQyEJS9szLT7wSLY
AgA8gi0slCmsgYhW1BXI1wijDEM05BfYgS2E2ixEIjVwwRewwUJ4+hfswhgQQOWQASSWmynsgx/Y
QsT3QnmCguTsA6a3WdAOGFt6ey14jC/QwhBEgz2YQjk0Ax7YwezMQi2M/owp1MKxeStX8wM/pIFQ
cOdC2dYEuDcVBZJIdCJS7mCoaUQdOkRL2mFLEj4YjMwVqggDDr5hLL5G3ME68GbhI74djkwiHr5d
iCHi05wlrMOILlLgQ8T+Zc4TCoHkCkIryNzLddLil/4icT7hD0Hru8zGgMExJD4UiiHuX+IZCEnr
s6FjhaTLJaLt3ylDYIIgqIyZfUFSaOAQj0QrUIAExEObGqFh9MIvzEUAXMEqGH9LjPUrYj8AuFJ5
DkDA6H1MkUANOB35vz+gTeILCoGmjAgW2DpJtAIJVL/6w7///z9AAACwAAW9BgIRJlS4MGGrNhEm
BGA4kWJFixcxZtS4/pFjR48fQYYUOXLhgBo1DpIcgOLfPHcYSMaUOZNmTZs3cX4MUGEelgozW8XD
UsPBgACtBJ7JuZRpU6dPoWZc4AZFChIDbA5wM08Cinlu3MRrMIBsWbNn0aZVu5ZtW7dv4cZlu4Bu
Xbt38dINsJdvX79/AQcWPJhwYcOHB5Nt4EYCDXrxkOIc4GFeja4T2mTWvJlzZ8+fQYcWPZp0adOi
HaRWvZp1awdt5MWWPZt2bdu3cefWvZt379z0IkRIUc8N1qat3CVvsJx5c+fPoUeXPp16AwXxsCuA
XgF7d+/fvVeoPp58+QbxKKRXv559e/fv4ceXP59+ffkkKDSIHJW/eMxW/yf6T8ABCSRQqf4uauWM
BRls0MEHIYxQwgkprNDCCydEUMMNOezQww9BDFHEEUks0cQTUUxRxRVZbNHFF2GMUcYZaazRxhtx
zFHHHXns0ccfgQxSyCGJLNLII5FMUsklmWzSySehjFLKKams0sorscxSSx4DAgA7
------=_NextPart_E37_416B_25090063.94812D72--




From keruthayamdop@uthayam.net Tue Jul 10 10:13:30 2007
Return-path: <keruthayamdop@uthayam.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8GT4-0000OV-IX; Tue, 10 Jul 2007 10:13:30 -0400
Received: from aazh140.neoplus.adsl.tpnet.pl ([83.6.145.140] helo=komputer-9895db)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8GT4-0005st-0F; Tue, 10 Jul 2007 10:13:30 -0400
Received: from 205.209.145.155 (HELO uthayam.net)
     by lists.ietf.org with esmtp (W<?(S='.65H 3YD.E)
     id 12N/=8-BH8Y)B-7.
     for isms-request@lists.ietf.org; Tue, 10 Jul 2007 14:13:32 -0100
Date:	Tue, 10 Jul 2007 14:13:32 -0100
From:	"Chris Blackman" <keruthayamdop@uthayam.net>
X-Mailer: The Bat! (v2.00.0) Business
X-Priority: 3 (Normal)
Message-ID: <762718751.41514745141731@thhebat.net>
To: isms-request@lists.ietf.org
Subject: Hey man, stop throwing away your money
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------BF6EBF67805C9305"
X-Spam: Not detected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81

------------BF6EBF67805C9305
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: quoted-printable


Ultimately the true stuff =96 with no money tricks! 
P.E.P. are tasting hot right now! This is the genuine thing not an=20=
imitation! 

One of the very exceptionals, absolutely unequalled product is on sale=20=
at any place!
 Notice just what people tell about this product:

"I like how quickly your product had an affect upon my boyfriend, he=20=
can no way stop talking on how excited he is with his new calibre,=20=
extent, and libido!"

Lusia R., Boston

"Firstly I thought the gratuitous sample package I received was a joke,=20=
till I actually tried taking the P.E.P. No words can report how greatly=20=
satisfied I am with the result I got from using the remedy after 7 short=20=
weeks. I will be requesting on a constant basis!" 
Mikkey Fox, Boston

Check up more recommendations about this wonderful product just now!
http://www.periast.net/?qyjrhfkjha
------------BF6EBF67805C9305
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>She will love you more than any other guy</TITLE>
</HEAD>
<BODY>

<b>
Ultimately the true stuff =96 with no money tricks! 
<br>
<a href=3D"http://www.periast.net/?qyjrhfkjha"=20=
target=3D"_blank">P.E.P.</a> are tasting hot right now! This is the=20=
genuine thing not an imitation! 
<br>
One of the very exceptionals, absolutely unequalled product is on sale=20=
at any place!
<br> Notice just what people tell about this product:
<p>
<i>
"I like how quickly your product had an affect upon my boyfriend, he=20=
can no way stop talking on how excited he is with his new calibre,=20=
extent, and libido!"
</i>
</p>
Lusia R., Boston
<p>
<i>
"Firstly I thought the gratuitous sample package I received was a joke,=20=
till I actually tried taking the P.E.P. No words can report how greatly=20=
satisfied I am with the result I got from using the remedy after 7 short=20=
weeks. I will be requesting on a constant basis!" </i>
</p>
Mikkey Fox, Boston
<center>
<a href=3D"http://www.periast.net/?qyjrhfkjha" target=3D"_blank">
Check up more recommendations about this wonderful product just now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.periast.net/?qyjrhfkjha</font>

</BODY></HTML>
------------BF6EBF67805C9305--




From daniel.viera@ministryontour.com Tue Jul 10 10:55:25 2007
Return-path: <daniel.viera@ministryontour.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8H7d-00013J-MB
	for ipfix-archive@megatron.ietf.org; Tue, 10 Jul 2007 10:55:25 -0400
Received: from [222.234.183.195] (helo=[222.234.183.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8H7d-0006xZ-Bb
	for ipfix-archive@megatron.ietf.org; Tue, 10 Jul 2007 10:55:25 -0400
Received: from [222.234.183.195] by mx01-dom.earthlink.net; Tue, 10 Jul 2007 14:55:45 -0900
Message-ID: <01c7c302$64ba2460$c3b7eade@daniel.viera>
From: "Wendy Marino" <daniel.viera@ministryontour.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: ADOBE CS3 EXTENDED Our price $89.95 retail price US $ 999.00 You save $909
Date: Tue, 10 Jul 2007 14:55:45 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

Save $369 Adobe Acrobat 8.0 Pro $79
http://dvacvetakr.com




From dowdall5rcx@hotmail.com Tue Jul 10 12:51:03 2007
Return-path: <dowdall5rcx@hotmail.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8IvX-00033q-9h; Tue, 10 Jul 2007 12:51:03 -0400
Received: from [190.24.163.209] (helo=9ooxho.eeee.adelphia.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8IvW-0002PJ-Q8; Tue, 10 Jul 2007 12:51:03 -0400
Message-ID: <45902043386315.B8211BEB1B@3VLJYOYW>
From: " Ion-archive" <dowdall5rcx@hotmail.com >
To: <ion-archive@lists.ietf.org>
Subject: Hot offers form replica watch store
Date: Tue, 10 Jul 2007 18:51:47 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: DE5Ta8yEGb1vQ1FwO46FAy8dbWtWhpw5CEug
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_005E_AC374343.32090275"
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a

------=_NextPart_000_005E_AC374343.32090275
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Don’t miss the chance to get yourself a qualitative replica timepiece for less!
The only thing that our watches yield to original ones in is the price!
All famous brands presented – and available for truly laughable money!
http://disrich.com
------=_NextPart_000_005E_AC374343.32090275
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: 7bit

<html>
Don’t have enough dough to buy the timepiece you want? See our replica store!<br>
Why pay more for the same blameless quality? Our prices will please you!<br>
<A href="http://slonoima.com">Pick up a perfect chronometer for you out of our huge stock now!<br></A>


<br><br><br><br><br><br><br><br>
<font color=white>at speaking the language </font>
<font color=white>format designed for the way </font>
<font color=white>your boss told you </font>
<font color=white>them to work immediately. </font>
<font color=white> Facade, Proxy, and Factory</font>
<font color=white>of patterns with others </font>
<font color=white>design problems, and better </font>
<font color=white> learned by those </font>
<font color=white>that you can hold your</font>
<font color=white>science, and learning theory, </font>
<font color=white> advantage</font>
<font color=white>to know how they </font>
<font color=white>put you to sleep! We think </font>
<font color=white>to do instead). You want</font>
<font color=white>your brain works. Using </font>
<font color=white> the "Trading Spaces" show. </font>
<font color=white>With Design Patterns, </font>
<font color=white>(or worse, a flat tire), </font>
<font color=white>on your team. </font>
<font color=white>you want to learn the </font>
<font color=white>at speaking the language </font>
<font color=white>so that you can spend </font>
<font color=white>deep understanding of why </font>
<font color=white> a book, you want </font>
<font color=white>design problems </font>
<font color=white>want to see how</font>
<font color=white>alone. At any given moment, </font>
<font color=white>them to work immediately. </font>
<font color=white> what to expect--a visually-rich </font>
<font color=white>design problems, and better </font>
<font color=white>Best of all, in a way that won't </font>
<font color=white> someone struggles</font>
<font color=white>alone. At any given moment, </font>
<font color=white>that you can hold your</font>
<font color=white>matter--why to use them, </font>
<font color=white>on your team. </font>
</html>

------=_NextPart_000_005E_AC374343.32090275--




From hichaotic@lon.imag.net Tue Jul 10 13:17:21 2007
Return-path: <hichaotic@lon.imag.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8JKz-0008DN-GU
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 13:17:21 -0400
Received: from cpe2-3-89.cable.triera.net ([82.149.3.89] helo=lon.imag.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I8JKz-0003Mi-0V
	for ipfix-archive@lists.ietf.org; Tue, 10 Jul 2007 13:17:21 -0400
Message-ID: <001901c7c326$f0804460$072616cc@Srky>
From: "Margarito Aguilar" <hichaotic@lon.imag.net>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject:   Thanks, we are accepting your application
Date: Tue, 10 Jul 2007 19:14:00 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0016_01C7C326.F0804460"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1081
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

------=_NextPart_000_0016_01C7C326.F0804460
Content-Type: text/plain;
        charset="windows-1252"
Content-Transfer-Encoding: quoted-printable


Your credit score doesn't matter to us!

If your family OWN property and want IMMEDIATE pocket money to spend ANY =
way you like, or simply require to LOWER your payments by a third or =
more, here is best deal we can offer you THIS NIGHT (hurry, this lot =
will expire THIS EVENING):

$312,000+ debt

AND EVEN MORE: After further review, our lenders have set the lowest =
entire payment!

Hurry, when our deal is gone, it is gone. Simply fill out this short =
form... 

Do not worry about approval, your credit will not disqualify you!

http://kataltqhh.com/
------=_NextPart_000_0016_01C7C326.F0804460
Content-Type: text/html;
        charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1252">
<META content=3D"MSHTML 6.00.3790.2962" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit does not =
matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you OWN real estate and =
want IMMEDIATE pin money to spend ANY way you like, or simply need to =
LOWER your monthly payments by a third or more, here is best deal we can =
offer you TONIGHT (hurry, this deal will expire THIS =
EVENING):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$219,000+ =
debt</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have set the lowest monthly =
payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when the deal is =
gone, it is gone. Simply fill this simple form... </B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit history will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://kataltqhh.com/">http://kataltqhh.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0016_01C7C326.F0804460--



From ipfix-bounces@ietf.org Tue Jul 10 13:49:51 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8JqD-00018E-Hy; Tue, 10 Jul 2007 13:49:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8JqC-000168-7p
	for ipfix@ietf.org; Tue, 10 Jul 2007 13:49:36 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8JqB-00048V-IB
	for ipfix@ietf.org; Tue, 10 Jul 2007 13:49:36 -0400
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnY6E003658
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:34 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 15BDA20AE2B
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:34 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id AC76E20AE2A
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:33 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnX2K019353
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:33 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6AHnWKT005249
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Received: from imm.m.ecl.ntt.co.jp (imm0.m.ecl.ntt.co.jp [129.60.5.151])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6AHnWMw005246
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.56])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnV48012445
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Message-ID: <4693C6DE.50502@lab.ntt.co.jp>
Date: Wed, 11 Jul 2007 02:50:22 +0900
From: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Organization: NTT
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: multipart/mixed; boundary="------------070008080405040103050101"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Subject: [IPFIX] [Fwd: I-D ACTION:draft-irino-ipfix-ie-order-02.txt]
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--------------070008080405040103050101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello all

I updated my draft "Order of Information Element".
I changed this draft a little from last draft. I added some sentence 
about the order of templates that have two or more Information Elements 
which have same ElementId.

regards,
Hitoshi IRINO

-- 
Hitoshi Irino
NTT Network Service Systems Laboratories
9-11 Midori-cho 3-Chome, Musashino-shi, Tokyo 180-8585 Japan
Tel: +81-422-59-4403  Fax: +81-422-59-4549



--------------070008080405040103050101
Content-Type: message/rfc822;
	name="I-D ACTION:draft-irino-ipfix-ie-order-02.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="I-D ACTION:draft-irino-ipfix-ie-order-02.txt.eml"

Return-Path: <i-d-announce-bounces@ietf.org>
Received: from imm.m.ecl.ntt.co.jp [129.60.5.237]
	by localhost with POP3 (fetchmail-6.2.5)
	for irino@localhost (single-drop); Wed, 04 Jul 2007 08:21:07 +0900 (JST)
Received: from eclscan1.m.ecl.ntt.co.jp (eclscan1.m.ecl.ntt.co.jp
	[129.60.5.67])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NKFG7005972
	for <hi056@imm.m.ecl.ntt.co.jp>; Wed, 4 Jul 2007 08:20:15 +0900 (JST)
Received: from eclscan1.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan1.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l63NK9eY010042
	for <hi056@imm.m.ecl.ntt.co.jp>; Wed, 4 Jul 2007 08:20:14 +0900 (JST)
Received: from idma.m.ecl.ntt.co.jp. (idma.m.ecl.ntt.co.jp [129.60.5.2])
	by eclscan1.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l63NK9kU010038; Wed, 4 Jul 2007 08:20:09 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.58.30])
	by idma.m.ecl.ntt.co.jp. (8.13.8/8.13.8) with ESMTP id
	l63NK9aS002015; Wed, 4 Jul 2007 08:20:09 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NK8ME009182; 
	Wed, 4 Jul 2007 08:20:08 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 8D75920AE2B;
	Wed,  4 Jul 2007 08:20:08 +0900 (JST)
Received: from sfs2.omr.ecl.ntt.co.jp (sfs2.omr.ecl.ntt.co.jp [129.60.39.117])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 568C420AE29;
	Wed,  4 Jul 2007 08:20:08 +0900 (JST)
Received: from tama5.ecl.ntt.co.jp (tama5.ecl.ntt.co.jp [129.60.39.102])
	by sfs2.omr.ecl.ntt.co.jp (MOS 3.8.4-GA) with ESMTP id AQT96650;
	Wed, 4 Jul 2007 08:20:07 +0900 (JST)
Received: from megatron.ietf.org (optimus.ietf.ORG [156.154.16.145])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NK6rm029363;
	Wed, 4 Jul 2007 08:20:07 +0900 (JST)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5rab-0000w5-2f; Tue, 03 Jul 2007 19:15:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5raQ-0000E1-3l
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:10 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5raI-0002Gx-6C
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:10 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id BDBB526ED8
	for <i-d-announce@ietf.org>; Tue,  3 Jul 2007 23:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5raH-0000y0-JS
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5raH-0000y0-JS@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 19:15:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: I-D ACTION:draft-irino-ipfix-ie-order-02.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
X-Junkmail: UCE(10)
X-Junkmail-Status: score=10/10, host=sfs2.omr.ecl.ntt.co.jp
X-Junkmail-SD-Raw: score=unknown,
	refid=str=0001.0A090207.468AD9A7.006F,ss=1,fgs=0,
	ip=156.154.16.145, so=2007-03-13 10:31:19,
	dmn=5.3.14/2007-05-31

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Order of Information Elements
	Author(s)	: H. Irino
	Filename	: draft-irino-ipfix-ie-order-02.txt
	Pages		: 32
	Date		: 2007-7-3
	
This draft describes guidelines for the order of Information Elements
   of the IPFIX protocol for the creation of Templates.  It aims to
   improve the efficiency of the Collecting Process on the assumption
   that multiple Exporting Processes send Flow Records containing the
   same Information Elements to a Collecting Process.  Exporters can
   make (almost) the same Template from the same combination of
   Information Elements by applying the order rule defined in this
   draft.  Furthermore, some Templates will have a suitable data
   structure for hardware processing if the rule is applied because the
   rule defines that fixed-length Information Elements and other
   Information Elements are separated in position.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-irino-ipfix-ie-order-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-irino-ipfix-ie-order-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-irino-ipfix-ie-order-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3181347.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-irino-ipfix-ie-order-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-irino-ipfix-ie-order-02.txt"; 
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3181347.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--




--------------070008080405040103050101
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--------------070008080405040103050101--




From ipfix-bounces@ietf.org Tue Jul 10 13:49:52 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8JqD-00018E-Hy; Tue, 10 Jul 2007 13:49:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8JqC-000168-7p
	for ipfix@ietf.org; Tue, 10 Jul 2007 13:49:36 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8JqB-00048V-IB
	for ipfix@ietf.org; Tue, 10 Jul 2007 13:49:36 -0400
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnY6E003658
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:34 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 15BDA20AE2B
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:34 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id AC76E20AE2A
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:33 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnX2K019353
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:33 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6AHnWKT005249
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Received: from imm.m.ecl.ntt.co.jp (imm0.m.ecl.ntt.co.jp [129.60.5.151])
	by eclscan3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6AHnWMw005246
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.56])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6AHnV48012445
	for <ipfix@ietf.org>; Wed, 11 Jul 2007 02:49:32 +0900 (JST)
Message-ID: <4693C6DE.50502@lab.ntt.co.jp>
Date: Wed, 11 Jul 2007 02:50:22 +0900
From: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Organization: NTT
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: multipart/mixed; boundary="------------070008080405040103050101"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Subject: [IPFIX] [Fwd: I-D ACTION:draft-irino-ipfix-ie-order-02.txt]
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--------------070008080405040103050101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello all

I updated my draft "Order of Information Element".
I changed this draft a little from last draft. I added some sentence 
about the order of templates that have two or more Information Elements 
which have same ElementId.

regards,
Hitoshi IRINO

-- 
Hitoshi Irino
NTT Network Service Systems Laboratories
9-11 Midori-cho 3-Chome, Musashino-shi, Tokyo 180-8585 Japan
Tel: +81-422-59-4403  Fax: +81-422-59-4549



--------------070008080405040103050101
Content-Type: message/rfc822;
	name="I-D ACTION:draft-irino-ipfix-ie-order-02.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="I-D ACTION:draft-irino-ipfix-ie-order-02.txt.eml"

Return-Path: <i-d-announce-bounces@ietf.org>
Received: from imm.m.ecl.ntt.co.jp [129.60.5.237]
	by localhost with POP3 (fetchmail-6.2.5)
	for irino@localhost (single-drop); Wed, 04 Jul 2007 08:21:07 +0900 (JST)
Received: from eclscan1.m.ecl.ntt.co.jp (eclscan1.m.ecl.ntt.co.jp
	[129.60.5.67])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NKFG7005972
	for <hi056@imm.m.ecl.ntt.co.jp>; Wed, 4 Jul 2007 08:20:15 +0900 (JST)
Received: from eclscan1.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan1.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l63NK9eY010042
	for <hi056@imm.m.ecl.ntt.co.jp>; Wed, 4 Jul 2007 08:20:14 +0900 (JST)
Received: from idma.m.ecl.ntt.co.jp. (idma.m.ecl.ntt.co.jp [129.60.5.2])
	by eclscan1.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l63NK9kU010038; Wed, 4 Jul 2007 08:20:09 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.58.30])
	by idma.m.ecl.ntt.co.jp. (8.13.8/8.13.8) with ESMTP id
	l63NK9aS002015; Wed, 4 Jul 2007 08:20:09 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NK8ME009182; 
	Wed, 4 Jul 2007 08:20:08 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 8D75920AE2B;
	Wed,  4 Jul 2007 08:20:08 +0900 (JST)
Received: from sfs2.omr.ecl.ntt.co.jp (sfs2.omr.ecl.ntt.co.jp [129.60.39.117])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 568C420AE29;
	Wed,  4 Jul 2007 08:20:08 +0900 (JST)
Received: from tama5.ecl.ntt.co.jp (tama5.ecl.ntt.co.jp [129.60.39.102])
	by sfs2.omr.ecl.ntt.co.jp (MOS 3.8.4-GA) with ESMTP id AQT96650;
	Wed, 4 Jul 2007 08:20:07 +0900 (JST)
Received: from megatron.ietf.org (optimus.ietf.ORG [156.154.16.145])
	by tama5.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l63NK6rm029363;
	Wed, 4 Jul 2007 08:20:07 +0900 (JST)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5rab-0000w5-2f; Tue, 03 Jul 2007 19:15:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5raQ-0000E1-3l
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:10 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5raI-0002Gx-6C
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:10 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id BDBB526ED8
	for <i-d-announce@ietf.org>; Tue,  3 Jul 2007 23:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5raH-0000y0-JS
	for i-d-announce@ietf.org; Tue, 03 Jul 2007 19:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I5raH-0000y0-JS@stiedprstage1.ietf.org>
Date: Tue, 03 Jul 2007 19:15:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: I-D ACTION:draft-irino-ipfix-ie-order-02.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
X-Junkmail: UCE(10)
X-Junkmail-Status: score=10/10, host=sfs2.omr.ecl.ntt.co.jp
X-Junkmail-SD-Raw: score=unknown,
	refid=str=0001.0A090207.468AD9A7.006F,ss=1,fgs=0,
	ip=156.154.16.145, so=2007-03-13 10:31:19,
	dmn=5.3.14/2007-05-31

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Order of Information Elements
	Author(s)	: H. Irino
	Filename	: draft-irino-ipfix-ie-order-02.txt
	Pages		: 32
	Date		: 2007-7-3
	
This draft describes guidelines for the order of Information Elements
   of the IPFIX protocol for the creation of Templates.  It aims to
   improve the efficiency of the Collecting Process on the assumption
   that multiple Exporting Processes send Flow Records containing the
   same Information Elements to a Collecting Process.  Exporters can
   make (almost) the same Template from the same combination of
   Information Elements by applying the order rule defined in this
   draft.  Furthermore, some Templates will have a suitable data
   structure for hardware processing if the rule is applied because the
   rule defines that fixed-length Information Elements and other
   Information Elements are separated in position.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-irino-ipfix-ie-order-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-irino-ipfix-ie-order-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-irino-ipfix-ie-order-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-3181347.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-irino-ipfix-ie-order-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-irino-ipfix-ie-order-02.txt"; 
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-3181347.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--




--------------070008080405040103050101
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--------------070008080405040103050101--




From jcone@myincredibletrips.com Tue Jul 10 13:58:27 2007
Return-path: <jcone@myincredibletrips.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8Jyl-0002nI-J7; Tue, 10 Jul 2007 13:58:27 -0400
Received: from [62.162.23.246] (helo=[62.162.23.246])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I8Jyl-0005dT-0Y; Tue, 10 Jul 2007 13:58:27 -0400
Received: from [62.162.23.246] by smtp.secureserver.net; Tue, 10 Jul 2007 17:58:22 -0100
Message-ID: <01c7c31b$e7b376a0$f617a23e@jcone>
From: "Dolly Crump" <jcone@myincredibletrips.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: All orders will be processed and dispatched within 24hrs.
Date: Tue, 10 Jul 2007 17:58:22 -0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7C32C.AB3C46A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7C32C.AB3C46A0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Second month you will notice an increase in penis size of up to 1 inches, p=
lus an increase in Girth (Width) of 5%, plus all the benefits of the first =
month. You will be absolutely amazed when you see your penis gradually beco=
ming LARGER and LARGER, right before your eyes! NOTHING compares to the fee=
ling of having a larger penis.http://maebhart.comMegaDik has been labeled a=
 "Herbal Breakthrough" with over 1,500,000 bottles sold worldwide. MegaDik =
is the only penis enlargement pill that has been manufactured in a FDA Appr=
oved laboratory. 
------=_NextPart_000_0007_01C7C32C.AB3C46A0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-1252">
<META content=3D"MSHTML 6.00.2800.1478" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Second month you will notice an increase i=
n penis size of up to 1 inches, plus an increase in Girth (Width) of 5%, pl=
us all the benefits of the first month. You will be absolutely amazed when =
you see your penis gradually becoming LARGER and LARGER, right before your =
eyes! NOTHING compares to the feeling of having a larger penis.</FONT></DIV=
>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://maebhart.com">http://maebhart.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>MegaDik has been labeled a "Herbal Breakth=
rough" with over 1,500,000 bottles sold worldwide. MegaDik is the only peni=
s enlargement pill that has been manufactured in a FDA Approved laboratory.=
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7C32C.AB3C46A0--




From sharpguyq@mysweetchicboutique.com Thu Jul 12 00:23:59 2007
Return-path: <sharpguyq@mysweetchicboutique.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8qDe-0003R1-Ql; Thu, 12 Jul 2007 00:23:58 -0400
Received: from [116.45.16.11] (helo=mysweetchicboutique.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I8qDX-0003QO-NO; Thu, 12 Jul 2007 00:23:58 -0400
Message-ID: <a6df01c7c4a0$60484930$c2b0ca74@sharpguyq>
From: "Zane" <sharpguyq@mysweetchicboutique.com>
To: "Treva Bradley" <ipfix-archive@lists.ietf.org>
Cc: "Frida" <idmr-archive@lists.ietf.org>,
	"Salvatore Carroll" <ipsec-archive@lists.ietf.org>,
	"Katie Carroll" <6lowpan@lists.ietf.org>,
	"Felicidad" <kitten@lists.ietf.org>,
	"Dacia" <iporpr-archive@lists.ietf.org>
Subject: Private chat, okay
Date: Thu, 12 Jul 2007 16:19:09 +1200
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_CB1_DBFF_A641E164.83FFB0A7"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: e3ebaaff3b3539efaf29ef65eea2aded

This is a multi-part message in MIME format.

------=_NextPart_CB1_DBFF_A641E164.83FFB0A7
Content-Type: multipart/alternative;
	boundary="----=_NextPart_B96_0E60_2E55C9E0.6EE8AC59"

------=_NextPart_B96_0E60_2E55C9E0.6EE8AC59
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
flaky claim spent powerful _'To Mr Brian Fitzpatrick._ "Indeed you wrong =
me," said Jones; stain "I question should have been contented with very l=
ittle: careful I property never had any v After swell much bit considerat=
ion, therefore, she resolved to go early in the morning reluctantly pause=
 to that lady, and endea
 
As in the month of June, really the swim act damask rose, which chance ha=
th planted potato among the lilies, with their can arrogant Jones, expans=
ion instead of applying himself drain directly to cure take off the edge =
of Mrs Honour's resentment, as a mo Though Sophia had voiceless no opport=
unity of reward learning of Jones by what experience means he had discove=
red for her, yet, as s If the reader's imagination grass reaction doth no=
t assist me, I shall never be able jelly water to describe the situation =
of t  
Shortly always after field leaving Italy Attila brought afraid suddenly d=
ied. Only the day before his death he had married a bea II A child who ha=
th just learnt outrageous his letters would have thank spelt this letter =
rapidly out in less kneel time than Jones to "I pen am sorry you have giv=
en away the living feeling of unsightly Westerton so hastily. face I shou=
ld have applied on that oc made The separate Valkyries were given beautif=
ul female warriors. They had some of promptly Woden's own strength and we=
re armed w 'SIR,
This resolution she kettle accordingly executed; and cautious the next mo=
rning before the sun, she boastfully huddled tear on her cl The Huns like=
 applaud mourned their king in a barbarous way. They butyric shaved their=
 heads and cut expert themselves on their  Mrs dust soft Honour yawn had =
no sooner left the teaching kitchen in the manner we have before seen tha=
n the landlady fell s
 
While they were thus discoursing, Mrs cough Honour returned and discharge=
d ran her commission, signal within by bidding the 
burn Mrs Honour was altogether lip as placable as fear she bake was passi=
onate. Hearing, therefore, Lady Bellaston assu One brain thing gave him c=
omplete satisfaction, which refuse hook was, that his mistress coil had r=
egained her liberty, and bright edificial _Pone me guide pigris head ubi =
nulla campis  lip The cut length of this narrative gave Lady Bellaston en=
courage an opportunity of rallying her spirits, sparkling and of cons
brought Arbor danger afterwards drink aestiva recreatur aura, Lady Bellas=
ton fixed her eyes on withstand Sophia whilst she spoke these words. To b=
ounce which tasteless that false poor young lady, Jones followed her down=
stairs, existence often between offering her his spilt hand, which she ab=
solutely refused broadcast him, and go Mrs Fitzpatrick made many apologie=
s for attempt an relieved early, abrupt visit, forsake at an hour when, l=
ift she said, "she shou  
------=_NextPart_B96_0E60_2E55C9E0.6EE8AC59
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:df18701c7c4a0d603de8f065c4f478@s=
harpguyq" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>flaky claim spent powerful _'To Mr Brian Fitzpatr=
ick._ "Indeed you wrong me," said Jones; stain "I question should have be=
en contented with very little: careful I property never had any v After s=
well much bit consideration, therefore, she resolved to go early in the m=
orning reluctantly pause to that lady, and endea</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>As in the month of June, really the swim act dama=
sk rose, which chance hath planted potato among the lilies, with their ca=
n arrogant Jones, expansion instead of applying himself drain directly to=
 cure take off the edge of Mrs Honour's resentment, as a mo&nbsp;Though S=
ophia had voiceless no opportunity of reward learning of Jones by what ex=
perience means he had discovered for her, yet, as s&nbsp;If the reader's =
imagination grass reaction doth not assist me, I shall never be able jell=
y water to describe the situation of t&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>Shortly always after field leaving Italy Attila b=
rought afraid suddenly died. Only the day before his death he had married=
 a bea II A child who hath just learnt outrageous his letters would have =
thank spelt this letter rapidly out in less kneel time than Jones to "I p=
en am sorry you have given away the living feeling of unsightly Westerton=
 so hastily. face I should have applied on that oc made The separate Valk=
yries were given beautiful female warriors. They had some of promptly Wod=
en's own strength and were armed w 'SIR,</FONT></DIV>
<DIV><FONT face=3DArial>This resolution she kettle accordingly executed; =
and cautious the next morning before the sun, she boastfully huddled tear=
 on her cl The Huns like applaud mourned their king in a barbarous way. T=
hey butyric shaved their heads and cut expert themselves on their&nbsp;&n=
bsp;Mrs dust soft Honour yawn had no sooner left the teaching kitchen in =
the manner we have before seen than the landlady fell s</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>While they were thus discoursing, Mrs cough Honou=
r returned and discharged ran her commission, signal within by bidding th=
e </FONT></DIV>
<DIV><FONT face=3DArial>burn Mrs Honour was altogether lip as placable as=
 fear she bake was passionate. Hearing, therefore, Lady Bellaston assu On=
e brain thing gave him complete satisfaction, which refuse hook was, that=
 his mistress coil had regained her liberty, and bright edificial _Pone m=
e guide pigris head ubi nulla campis&nbsp;&nbsp;lip The cut length of thi=
s narrative gave Lady Bellaston encourage an opportunity of rallying her =
spirits, sparkling and of cons</FONT></DIV>
<DIV><FONT face=3DArial>brought Arbor danger afterwards drink aestiva rec=
reatur aura, Lady Bellaston fixed her eyes on withstand Sophia whilst she=
 spoke these words. To bounce which tasteless that false poor young lady,=
 Jones followed her downstairs, existence often between offering her his =
spilt hand, which she absolutely refused broadcast him, and go Mrs Fitzpa=
trick made many apologies for attempt an relieved early, abrupt visit, fo=
rsake at an hour when, lift she said, "she shou&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_B96_0E60_2E55C9E0.6EE8AC59--

------=_NextPart_CB1_DBFF_A641E164.83FFB0A7
Content-Type: image/gif;
	name="pme7In1pie.gif"
Content-Transfer-Encoding: base64
Content-ID: <df18701c7c4a0d603de8f065c4f478@sharpguyq>

R0lGODdhRAFFAecAAP////jn5v+ZmffW1f/3+P9vb/85J/8AAP8kJP9KSu++vvfe3v9mZvTHx+aT
j8UAAM0ZGdM8Pd5eZuR5e+WXouiztf+wmfXo3f/v78wAAP/35v8jAP88Ev+Xie6srP9jQf8zAOrM
qv9OJ/+SkuWJjtYxMf91Uf/9995qcNxSUv+NbvLW6P8Ag/8bpP85sP9owvOZwff17u7dqdq2WNQo
KNRJS/+/5v8AjP8AmfG8ZcyZAP9bW80LC/Xl1MaOAO3hzdarN9vg9fT4/+7v8qyT/6lv/5FI/4Qy
/2YA///ptczM/3Fx/15e/6qq/zMA/0pK/ykp/xkZ/yEh/zMz/88lJpmZmWVfWaKlp9ZVVXYb/+bs
9N7e3kpLSBITHQAAADg6P+bm5sLC/+rOtNjX1zMzMyAkK7e1tPb396yrrYGDiczMzHdxcHd4fOaG
heqmp9jGsb+/lJSDP2ZmAJuJWMGphd7TxllWWWZmZkRCQPHo4khIAFdXAOXBkS0uLGlsbgICEYZ8
eMG9wcXFxYyJjJyRhK6gj8m9rsCidywoL5RhKeC6i5CVmQAA/8/Z8MLQ49fn8jPMzMTW7qzN5MwA
M42/4QAz/9PY4Wan1rfK2FCXzKq45ZlmZkSFvStztS9jnyNssNzf5Zao3n2T1oqe3TaCwBtbocPJ
0pkzAIWa12qAx3iO1q+8y7G2v/fv8WYAAGR2t/9mAGB1lIKW2pGbv6GptX+HmJOdsYyMlYSUxTBY
jGt1gWBqfnZ8ho+WpZWmv6Gvwu3Xu+jby9CziMWibcGba72UWs2se9HDxa1/RqR0PbWLUZlmM4Zw
WpCGec2XYtutd9embaCUlMzMAHVaR7WrsDPMAM+RVIJTJdOZWpptPcWGTLGllwCZAMwAzIxaJrx/
RXJHI2IyD/+ZAGbMADOZAOfe5gBmAAAAzP/ek0VDT//MYSUnOjUuQElJVfDNzui1vO3Dxuess+F+
iN12fdplZ96DhFthaxQWLAcGHDY7TigtRUxRYlBUV1JbdUxXaswzMywAAAAARAFFAQAI/gABCBxI
sKDBgwgTKlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bN
mzhz6tzJs6fPn0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtavXr2DDih1LtqzZs2jT
ql3Ltq3bt3C5BhAwgEDcu1sJFDBwAAGCBAqsLsAblwCDA4gTG2gw1YGCBw8gRJAwgUKFtwEsWBgw
4ALaBolD98UQFQPkDKgzQIZct62GBAc2GOCwoQNpABg4C7TL1UNiBAIOIy4AdUCEB6mTp4bANECH
DhYaNFhwG+OHDSA2aP8QQGAIDhxA/oj4UD3riMQJAAz4DZUEcuXKSyi18EFEdvDgRZg4gdEEiP//
fTCQBnz9dwBD5aWkgQYhCZAYAwD4hphBARTAwIUC8CaUBMqhAEAKq0EmwVEBqJAddidqt10HFmFg
AorZCbhbeP+JsNAKLLTgwgswrGBSDDLMIENIGMCWQAILnDchQQNYeOGFIyTo0wI0JEeBQBRMUAMN
D4xolAraAahimPdZYJEKB4jJnUAL0AiCCgvZcAMOONxwQwsArLCjDT52dIIMOeigw5AhSSjagQNV
uMOFizKwgwUaAsVlajyUQBlBkQrVAW0AgtBBA5qJgOIGHARGUQcwgsDBYAD0IOp//gIs9MKcdNba
gp12vtCRDIL6oMMPhQonWqwDKdDoCB5YuEMBUvaUJXwZSKAAY0eB2akF1Q3wqnZmUmRBp/9p+CoI
1CY0a63opuuCDRvN4MO7QHi2UBBBCCEERAts8Ntv5TWw6A6MjbDDss36JEEJPCgHWbkzDUEEEUUY
cQQSRSQkQKr/cfCBCSqMu4EIDEPUAAKjGiAvAW4WPFAL6dJpJ7os9HlRDEkA8a4PM/CXUBBKLMHE
Ek0oUW9DBSimgAIIIJbebgITDEADT5r60wIRoODAAKRh0MB7qaUURBEQGyExxQQF4QQSaCNxhEIN
pDqmimIuRlHbYnJArYvY2agQ/gEtt0CADXKi+0KmE8kAhKCCAiFDDwgFwcQTUEQhxRRPMNFEQ7Ah
NoJASiKKWwEDbw4AA8qK/pMHIT5AhUAOKMfcSUpMnDbaFQ8kxOxkJ4TBqCKooEJ94Y15gAgDzA2u
qnZtip0JcdJKpwsEuVArCzhklMO7iAuas0FCLBFFFFCED4UUUTChxL0JEcAXYqYaOhAGoO8geoWO
EltQFVZcMcRNEnCdARYACID/aJCSIeAOCUYoSBZmh76EiAlOBMHAAkBlARV0oDsT0VaaxASCBJCJ
RQqBgfNwoKuBBI5OLZAZRU5wPV8hzgdA0JntiDC+KdjwhuFjghYUgoGkIYZa/g5a0udCJxD67cB+
AtkCF7rgBS98AQw2QYH/MlCCEiinBl47YBZqBwDcOSEMC7FPxqQWgAUQjiIEEIObjvcfqSHkXC6D
AUHgiAMWlNAihsueDnBmEC0wAXw2jBwgpSAFMCqkaIhhAAEwsIPEvC9+81MWEsdAhiaWoYlmIMgZ
YoIBCEwRPl5qSAw2CYA6XMQIB0QfKtNGBIZYKzv6UQF98vaBjblxIh+ITac+JkZWJUR6tboBuwbi
AucJEyN/yh4QgFQQIYThCZOz4c+YcEMpMKGBBwkiYnaQOSHCj4gBlCRB0NDENKihkmsgpRm4wIb9
vUQBbUgYtDLgBlG+AQ5x/pBDHOZABzjUIQYUKcICZ6cEAARhoGhr5UIWkB0xwe0/2jGBLydCALv4
R18H4M6LNsCQlkWKZcFUYUV4hTgZxACgZVsCDqfQBC0EYQlQmMLkgqCQAPjwUEsbovyKKM6B2MEL
ZNgCAO7gBTwIRA1MrAIpYTKBEkBANauBwEQTkoc56EEPcsjqVfewB33mYSJEOFvanKCEIsyOiwuh
T4re9rFuZYQADbjABUzVAOjcaIQ4UGHLNMIHxAGBcQZRAjQD+YSCAkCw4yvsQgbQyEN54JHgNKL9
hoAHL9hBIH3wgh8AcAYu/IENNyHAABTggFAy5Adx6KocuJrV1u4hDl+N/sjXcBeEMMxOoQ0hwO/q
IwL8mKADxYPJCW21m2KiC3rWu9lfDyLYycW0CegTAhPCx1IEeWAEDPiLBzIEWfnxZwE9FQggihqI
NXihC4I4w0/vAEWlnCAPdbjnHOAQAzi0drVzWOpDlIC7I8hObRPBQAA4czSa0BFdLbgVum6A3Jm5
C17yKkhzZToFwwJAC5CbAhQuB5EzemBgDCieBQZWgImO4ZJN1OwYiDoIdzKlDoQohCHqYIjU3jcO
EwnCAXHXFOO2rGUMFilFNPBgnDEosIOdnIWVoOGYGvIiA2CUBxbQARIniAspXsMQ/OCFNTglD4eQ
w1b3cNX7yuEQFfkv/u5wqxSQ1uoFwExXzDSiAZu9a3sGCQOFpfAEmgokDOJTLEYwUOULFUBZtinI
GcwwCDQAoApFHYNTDsHa1caBDvm8LxwqQgSEjtXPSsHAXgFQJ1zdapgZ6YGdjSzDgejZuYIGQBPC
x2dQX2TEA8t1iBVyBaC6eCkxsKprf5AHG69WDpvmtBfRmpTh4qDBK7DBC3R1xor8wGaJm0EOgFU2
JkRTCktA36ynUD5stsgDjiJxyAoChjKUIRAACMQYztDqo9Th2FnNtGvl8AaLFOFsWTAC2MyNFBEK
riREduEefcAHgxBBCjEF970cJz42Z6QBR1PAVAtyzj8EYgg/7YId/tTAFEOQmatdVe2xuU0Rnk2F
jjeQY0l4dbN3Nbwgs44p5ZZABJjKtM8rAcNPByEIRKTYC0JdyhneQIc5xCERiaADyveQiNimRcEu
Q/VITqAIIHhdB0BIQh+XEM0m6xwKFj9JGf4wCABwuQxVuAMXpHKGusPhEE6fA1tgAOdSq8wjGuiB
4GUggyNLmNyBjGnkdKiSMVjBC6AFAxOvAIArOBor+mVLtG/ShD9KjpBTWIKFUcLlO2ySnF1Qwwng
TZjWb6RnS/AZE4hA8JIMIQ1rSPoQLrmIQFTB9cDPiL3spYXaswTL581k8JffFDSUoQtlYL70lT6G
K1B++thPSr2z/s/97nv/++APv/jHT/7ym//86E+/+tfP/va7//3wj7/850//+tv//vjPv/61woj9
u4URABiAAjiABFiABniACJiACriADNiADviAEBiBEjiBFFiBAAgAFWgR/Qd/Gyh/HTgRH9h+Ifh+
IwgRJah+J8h+KdgQK3h+LZh+L6gQMUh+M2h+NXgQNxh+OTh+O0gQPeh9Pwh+QYiB8TeEQKiBRUh/
Q2iEGOFIYcGE3LeEL+GEA+E5WQGF2SeFDDEEjeAIXvgImWcRVAgATggJWIGF2KeFCTEEkdCGj/CG
kSAJkRCGFCFEZOg5kGCGVpGDdacFfviHdWcRkzAJZKGGBnEG/nHYCH+4iIlIhxEhRFSYh1cxg2fg
Uo1wiZiYiUMzEYNIiALRiV1hiATxCJIgCW94iqj4hqX4CBcBiVZ4hQwhBEGQibRYi43waw4BigCg
i1whigAwBKXYhsI4jMQoCZTgCLgIEUtih5I4iQuhBbYYjZfYhkHgiAkxiJ+IjaGIhAQRCZRACaUY
juI4juH4jY1Qh4jCjHoIAJXQjpUQFSsIjcQ4j/TYhpZgjQeBjbzYi9zIWcb4jQAZkAI5kJRwCZiA
jwgxIXYIAM3oju7YEhkgEinIhfVYkcMoCZawfdfYiZ7oFWpICZlwCSIpkpkQkpdQkiOZkieZkgf5
iAeijnr4/o4C0Y4DcXQkoRwEkRwJgRoF0TU+iBBn0IWOEI5tqAleKI6RYJRDWYpeqAnt1RAc2ZEC
sQlUuQnOWBEbGAkhyQmccAmd8JVg+ZVdyQmewAmf8Alk6QkkCQqgoJEJERoF0YwFQZMCcXQpBhIR
CQARyZN6ORB8mZN7mZd6GZg/eRBgoAmIGQqioAlJOQpGGQqQWYqO6QiaMJmU2ZK5qI0DUZVVORAy
qRKCKZHcSAmkkAmc0AlpeZJk+QmlEJKd8AmoyQmt2QklWZKmgFIOAZcE0ZAOSZdNVJO/CQCncArC
SZwYkZeEOZgC8ZfLKZg8+Zd/WYJnYAmaAJmokAqjEAqq/qAKqFCZo9CdoTAKjlmZoYCYiJmM+ciR
BUGVU2mVM/mOD3mTOumXPmkQ9dmcoVmYFLGBrEAK/smaZCmbpeAJntCamUAKZ0kKBUqWJUkKnMAK
6PmWC8mQZuiQ7PiZwQkAGTqcHCoQAEIRz9mTyJmf0JmcyikQJdgKmACZLCqe2ZmdLGqeMiqjofCU
ChGVCcGe79mbBOEKPsoRyHmizpmfylmiJ1oQWrgFB4qgrcmaA+oJmZCgpFAKnVAKpSCbUOqfr2AG
NtoQEyqJdHmhdZmhGzqcwgkAxzMR82mf9jmkRxqdBzEEq8CidFqndTqjiRkKoACV6okQOiqm7zkQ
Pjqo/q4gELBwEUHKl4pKom5qpEjKja3ACqcZm/5ZklzpoKfpn6V5oEsaC4sgCBGKFGvqlwdhpI5K
hAYhp+HpoqwqCi6KCqogCzBap6MwC0l3o/oolQDAmToan4BKqINqqLBwqIYaESEKmM0povT5pkSq
hmDACmAQltI6rdPqqWawBQhpFCbal6XaqG6KogfRCoLAqqyqCtgpntupCuTqoqpAC11qELrIi5y5
q+7pq2FaqALxo8IqrMT6EKOak226rKc6EGp4BlsQCLXgCWe5sAzbsAvrCbVQBWYwbxnBm/Dpm15A
EGVKEP/hoSAgEcfqnKSKrMl6qtI5BrYgC6iwsix7/p0rKwqpsJ3f2bKw+grpxRT/yq3KWrLfqp8g
qElgoAZXEAsF6rAO6wmxcAtoIAhgkK0T0ZsyeZcaurEH0bHGupfLSZ8+uajMeqSoahBgYAa4IAqy
ULZlC7Owup2pIAqoIApuS7aq8ApXcKtLsa1Emqw8u6yPipWpOga0QLRWGriCa6W5oAu3MLFD4JYZ
IZNhapfB2aEDkaYgu6bwgbeDyaj5eYJnUH21oApv+7me+7mfmwqvsAhqkK28qIud2Z6B6pmf2aP4
CgDDKruz669Yq7MiS7JF2rME248CMQSP4AirQAuLALiDWwq5sAu80Au+gAmgEKoh4bgDYaaRK7lq
/iqaQCm0tRCz6dq93muurxALVaAG0DsQ+6iNq7u6YeqrwBq7w/q+V8utQ7q1I9q1zNm7fCsQZ/AI
wyi8xEu0uRDAycsLi0ALq4AJXhgJYHgSGQuc02ucHlu9FXG3G7GCMWAJZnALsfAKqcC93tvB4VsL
aEC+FQGKnTmvgJrC7Ru7tNuvEIGT+Em/WiuiFKyFQdmGjiAIjRAJprAKw7sItcALtVALvXAFrIAJ
mGAKpiCMj1BtHkGmDVycHPuxaErFN9GCBssKi8ALsbDBr/DFX9zFXay0FHsRnsir7pnCdBmsAMDG
/DrBJaGF0HiJjmAKlmAJXuiFrLDHPozEmNAI/qCAx6iYuCUhvQ4ELjnRglqAx8PbC7eQBrwQyZJM
xAaMwNW4EezZq+srk/raxiz8vi5srHHMjfv7hndsCY9wx6asyqYMCo/Alq58ioRcyDapEB1rtVec
EGcQBP0rvD5MC78QzL9wwF44jZFQvhYRpr+qr50MyqFsE0F4gb+7iNRczYtYidTcCq2nubNoi46A
iXksjcisEWvcvm9cu4nsu2cwBEMwfO78zvAsBOzMzk6LFic4BPSSz/q8z/zMz4obEsGqr/ALv+mc
vwNRdwidefEsBAldz2lxz9Yc0RLthw4tEgRNuzrhi/qL0Lrc0MunuQg9BBQ9zyRN0n2oBR5t/hPo
nMsG7X4peAYLHdMLTRgajYJK6LsieNMtndPzV9MwqNP7mYQ9jdMqCNQ/y4FGLRFo+NEmsdRU4dPo
59TMt4QWWNVWfdVYndVavdVc3dUOSNTrJ9VMvdNFPdRkHdZJHRFivc1pbYJC7YFgbdNmHdQNcQIV
ddfdt9bAB9WclQc/AAwhENghIAbBcAG4OdVt/RAv3QNiwAd8IAyQHdmQ/QbBoM2IPddHTSHA8NiQ
PQyQTQyeLdmUXdEPndgOUYIX8AaSTQzFwAfD8NqSHdlvMM5rodeup9Gpvdqt/dqhHduzHXy2zdZk
nduSbQzDwAfEANnGoAixLQyGQNuljdlK/l0QeaDazZ3cyX0Iy93cdPDct23aLEgQMfAGw2AMxlDc
xaAIxlAMrc3ZsX0Ix0DahfgQBHBSJ+XEY03XAhEMw1AMyJAMyIAMxGDexvDYBY7c7F0MA07ghQAG
/6wWLxgDfy0Ggh0CwAAMPRAA+E3T/RgDyK0My8AMIg4Ic1DeBG4MysAMzbDizVAIwmDexGAG8i0W
LdgDIeDYjq0IOq7jfBDYwGDY0qeGP7DexTAHg2B5aHAFhuAMJl4MzJAGVYDkZvDixkAMhQAKG27P
CvEDOK4IzwAN0PAMOz7mPV7YWc4WaigGxLDmyhANgjAGY6AGhtDf/Z0MgHAF8gbnb0Dg/sMwBzf7
EdIgDQPhBE7QEIfqzKD8wiORgheA48/gDM4A5mKu418e5jvOB2LwAwHw4BDOjTGgCAle5OS7zmNg
CKy9DNPQe9h6BsEgDLzd59QA3QhRPQcR6IOeENVQDfvqzG/MEDAcwwhxn5drECfYCiFA6dbgDJQu
5pUODc7A7M8w6Zh+AZwOFBTsEVqYB8IQ6srQ4L+rBnSQDNfQDBO7SRcgDKDN23Pg7RRBJwkR6IJu
ELk+EPO+r/aO0QuRqEFquQLrrXtrEFzu5cm+7NH+5dH+7NCADdgQ5gWvCMAw4zbx65dLwcIu7D47
3QCQB8qgDNxuCKQEBoaQDcxwBSR8/gZ8EOrsnQ2EsKcd5e4E4fIIYesCQegCUe8AYPPonPPPzKZ9
ybVea7+8W4JCUAfC8OjaEO0MX/DRrvDO7uzP3uzPwHINwUYFMYYloe9Zy+95u/XEzo1gtvFgv/GS
xlljsA3bEAjYCgDAQAxhv/HLQAh0qxAwLxBzbxAyDwA0f/O6XvP1rvMDsdLBfrt6e7+mGvQHsXRf
rg0ID+aMD+bWYA1O/+iR3vjOUAfGZxBshMt3+IoHwQ3cIBDd0A2ImrU+T/j+rvXgmr9f3/bIUAg7
9ItxvgXafAEo3vbK4A2EYAkOUSsvT+sDOBB3n/c2n+t77/e9rhA5m/W6+5yGn6pv/pDw36ANlP/4
kK740KD4zvANkQ7pzmANxXAMlz/FuNwpVTihBuH5oC/6FnGsg8+o/a63/37UQ2AMyGD7yGAI6DPP
nMUHylD/YS/uAFFlDACCBQ0exIHDYEIAjBw+ZERQmrSCTpwQrFbNYEaCsDx2/AjAI6yDJQlmQJmh
pMqVLAGgfOkSZsGIJc8cG4ZNW7Jv1qxp+6bNmTagPoEGhYZNqTZlhQaaPAhCKoioUqFeBcCNG1au
JlO6PAj2pEyVM2OarNkVas0hwpC9hft2zlODwIrFhZtoGhq6av3+BRz45dmCYguTJZy4ockzag75
/MbzW09nzn4GtazNGraf2pDN/okWCIzaqV0PnKYJ0aBWgt26FfQSW3BMs4W9IjZbm+bs3QDOvMEb
l86WGDEIDAs2LPjba8xYbeEdXbpamCxl2jaYuyzi3iVBoVGm2ed48uWBfm4WDY0aMGe6TqXK9fQB
ghAfFmQNwDXB2P1nb88OKu0S060+6Wo6Y4tikmGwwQaLMSZCY+5KBplsvMkLnEEEGc2vhBQiiCGH
UpOIIoIsuigjjTBacaSCQhKJJKyqO+mwlMbCcUDd0jqoMUKQISpIIYOc7LM5CLmCFTW2GGI6J5/M
sUYpB8sON+4O4lGwtMCAg8FlssnGQTEb9GaZMhkEZ5or1GjyL4ZCBDG1miYy/hEAi1gsiCOQXpQx
xq6+IusrHMcS60YsrwIjEELmQGYyRx1lcI5mkFRyi/bcgzLT6GikkraZPgUwR8MMjC6txoox0xsG
r1kmmVaXgTVWb6458xoNzdgCUw8Z+lDOEUus6CIA9FSRT2MFG1XTLA9KlBBmmAEz2myebaYKNAQZ
41LBSjONvoZ+/Ra/rfR7DQAvYAsMUBsN1a7QArubjUcwzEjGmzC9sRfWZBKJVdZlkLkmnDXWbNNN
Xt+8D9yJgmWxWD1h3FRTtLDK4w04CiGkGY03JqSQbeAwpI4f8tAVMG7l8xZLcPPbz1zZeEtW4sVK
NaiVMQoBMxGdl9G5Xn5p/o01mYCZqSKQXAX7EOFf7wNg4ROFHdZhmac2aNmCYgBGDDHeMKRrr7t+
Q2uxxQgmmDxiOOGvk7FCrT770mK53P5eTpfqkqz+K8shBGnGG35hxZdnfv12NRFwwplmEDPGaGW2
pEFkmmmn7YTabsurvuoHYLIeu3MxNud8bGDMJoC0tQk6uW3VwiUoboPmvvxA2Q3KwxBn8fV7537N
PBzxNQAxo2Cke3U7Isknjz15UkuK4QfNQYc+eumj76FkqOCryiqCVE+L6azG3Y9uupUHDG+/eIzh
DYsLaYaZa2jFV+dZD0+TGUA63maMtB0n/tsRwSVfAGdWklb0oAfB+IEB/hXoPAYm0Hk9eKACDRgD
02kPANjbHvdq4j3XzW18AlSL+UJYkDMEow514Bo12MeMabQQHC9sof0mtQ1DqO8NHeJfnFgHQh7i
LQYBuEAQhThEIhaRiBSsIHwsCID5FO9/NdEK+OTmHx7mbXYAyMMJtYhCQ6DhClWowiAGAUYwboOG
b9hiHaxnsCq28VCMKU4c5ThHOtZxjVdR4hKZ2LYdulFmIuxKWi6AwAaaUA2HRKQgFKkGLRLSeXXI
gx8lSTOonOEElzyBcQiwSU520pMEOEMo7zhJUl4FkFypCQHykAcigsGVQ4ClpWA5S1YS8QftKWUu
A3kVTPbSl7/8pS6F/onKK8Zglcdc5RBCCQBjkoyEZ2gmMpU5TGpirprXvNwpsZIWAsxRmZiao65C
WcfSYXOY2jRnOgODzrUYRI6ixCQdxSlKeqpTmOy0Zz5NeUWCbJKe8ARmQJepT1Lik6AHXV68ShLQ
SwKAob1EaEEjOtFdUpKiF4UXRjVq0Ddq9KIc9eg1QZrRkB50pCW9Jz9RStCTrrSULW2pS90YU5n6
EaY1ZSlOEXpTndqTpj0FIUzfNlSiFtWoR0VqUpW6VKY21alPhWpU7eM/qVbVqFRlqkqBWs2fbpV8
PPWqSMOqTrCO9ZxmNWdZ0ZrLrq6Vamp16yTbGleJwZWuM71rSi2a/leb8pWtWvVrUAMr0b0OVrCG
7WthEfvVxeJVsY2N3VwhWz7ATtZukrXsCB+b2alhlrPbrOxnlXVQPhJEHOLwqF1FO1pdnrK0ADht
pyaq2tVCybMHci1gxrHb3ZI1tLV10m1LlVs+opZQBeEtb9NJW5e+9q8v5RE5AEAO6VI3g02ELaFm
0lsAcBebcNVAeMU7Xg3E4J///M9sKhcY5770r2mhbnyt28S2Gbc6LOGud8W6Vw0kwb//BbB/DcGK
QBTYwAfGYUlOsWAGT+kvd1rpKc87YQoP9HzGI4h1rTvdPWbQtFPC7zgIol9kCaiuV+zvBR56AjBs
oRwvhvGLtxCI/itAxyQMbvC7CnIOk6y3JPGhklnoc1oiw+aDJv4jV84wBFc22clPfvIshUfMmWlY
uhxuW321G+IRi/g/glqXgHRjqIlRsr9JIG+aNbAFNrfZza4MRBVsbJAFF6TOnCKIOcyxYwCcw8+U
E5ZyL3hBEKjLUEMmcmw9OCMwa/c2ZFaXCJcMZUpXuslTPqh1CHOlwxAoVHebXRLQEWBSC/gK1DBD
qlONBlajgRqDuIL16kyQO9Mmz3rec5/9/GcUdTe5hJYKqKSEaNOi9mVHllKoOC3bwRRKhEy2dLSd
vAXGUVTTwlaMp7UNakqKGh3fBne4wU2INJSbDWu4gx3skA52/rPbD3OmtZ1PYWuY6DnPuuYxrwPd
ZUIPStinie2Hj30ur9QoN4PCjm2cfZUzPDlbLXazpVwZ8SZvgUMhNF5NrmzlDnc4toDi8oiRVZaw
WMddnR4Qt3lTE2+L2+XoIMQazI1udbfb3fAGwLxpPe8b1TvXe961rikncl/3e9Mm32PAsztwJCsb
6QEK0MIr6fCJU7zqba74xQOZ8QxnuLrSzTKxQc5vogMGz/4+uag6rXKFAiAJ6oB73OUu92msg93s
wHve846IdgiCzji+M9JzDQCg81jod/KuiLWHbZigxrhLX/RtuDLmnjtaJeZreMXHMAZqb97zEo84
6I2GcaZp/tjrTCyI41FboMR/WceG0dGyE6olgshg7rePe91tvvt22yEQo7xoo4/76HbBBPPTDj3W
r87mio8elVPd8MbBnvpiE4jsRR95gUYV+7V3tO0yyAHubz8NdrTD/OdHfzvSsQY16ArwOgcVrnEt
9MNfJLm9XfzTGz/kgpwW2cSXvJIDM5AznyGQOGmDsgMEgzFwvm2CvtPjMNTruIC7r+sjsb/4NGbr
vgpEOGtaOYIIhhkIP/GLO2ZIB3VDwRS0A/OTs7/TuYRTCfmztz+rP+wriPxDO48zLkUjOIK7Cqfr
QGYjuewoQM5DQGkLBDNIMLTonoiQvq6bD+yiQDBLPC/D/sAhvA4H07aU8z7aA4BWEAalyIExJMMy
zAFmaAcVVMMNKZhZqxIcsTeDMLwazC/UiQ/GUwnVqz6ma4kgy0GoU7iwwLwxwJbkM8SIGwMzqAJB
AL6EcojoO70oTJkpNIsqTBcsXBf9+zQOZDsvBIAtoANiGIZRJMVSHAZAuAM/UMVVZMVBEA33e8G1
87lb67Md4zHE8zL8u0NN1MHqc5n/4xRNy0HuGwsRShRVQ8ZkVEZV+yIlfD7MgcTpAjvUmMSwkBh1
2bKns7UqiRmeOoEf4Bo6EMdxJEc6iAYyQkcyuoJrEZ5YhMEY3LMZnEPD67VfMzo83B7YerzHoyLi
A4tG/gMVSBMUQAIDNTCDVkPIhFRIVuOQRtSnmDkxSooBBTKhNNoiRcLIjFykQ8IhN9zAW5s/GqxF
QPM1K9Qjy4HIzTKISTtCKBMlj0rJTPHG8TIiIaK2Q3QzTPHIPyS8wcOmmGy72VgxX1otb1wx8cqD
lnRIxAKkoXTK/fkso3TKCmuFqrTKpTQs4QKu2Vunrewsr7ys3wLLoBxL1vrAsrQttIzIs1TL6dDK
rWSutjwfuUxLlaRLzbpLsaSyvPREviTLvvTLuQzMv+zKwbQiwyxMtkTMvVxMvCTMxuxEyNwnu5TM
twSuuIRMy6wtzGxMzSxKvexMyXRMwBRNDyzNdjrN/rVMzchcJ6tyzdeEzdiEKqySzdq0zduUqtXU
zd3kzd70zd8EzuAUzuEkzuI0zuNEzuRUzuVkzuZ0zueEzuiUzumkzuq0zussCALAgO3kzu6UmXng
TRR4kk8iz/IkT48igABwh3dgz3dwAxJwgPiUT/msgPq0z/vEz/zUz/3kz/70z/8E0P9szwEl0AI1
0ANF0ARtzwCFhwEYAHioT3dw0AmlUAeF0ApwhwXQ0A3dUHjw0A8F0RAV0RHl0BI10RM90QBQ0XJS
ngB4h3iQBwmQgHmgUXkggRuVBxrV0R3l0R710R8F0iAV0iEl0iLlURRA0iRV0iVl0iZ10id90iKF
/tIpRdIJaIMrxdIs1dIt5dIu9dIv/dIJmAB6qIcGCIDkcYd6mFEKcAMPaAB3yFCrHAA4pdM6tdM7
hVMAuFM9xdM+9dM/BdRAFdQ+VYBCNdRDRdREVdRFZVRGfdNAbdRIldRJpdRKpdQKIAEUqAEsmAAF
OFOqCQAHwAIUiIcBwErsNKtWGABMRYEJaICpGQB6iIB6GABUtawzaAAUkAAKWABNGQBNrYDGsdXM
WoAKqAF66NUnWQAZdYdhXa0KiABkdZIAaIMaUABSwoAgCIJPFaBWWAAWPYggwACZ4dbfNFYHOFWo
CAASoAcFANcquoNFuIM7sIdmSNdM2QJWWEKC/miFQUgDUHiSILAEAigHQShXv9CCXmCDhWUFIQAA
U3AEh50aUzAF6SBYLbgKS3iET7SEg7CZSJBY8nkHCYiHez2IBphVUrqCeygDK+CCNDDZJzGFWgDY
g4gBQMCHfAiCJ+EFfWAFR/CFjg0MVuiCMviCMriHQCAAVcQ0KFG/pvWLLbCDXQhZg5DaQSgHVmAF
AKiCgiiHfbCDfY0dCkCBZuUNCqgBeCClWyADVmCyJmkFQOCHO6hYUEgDe+iFNmGFVaQFTFgDP+hY
IbCFfEiHX3DYKrgDW4iEvbWDQRDWh6VZULgFVaQFIaAFfLgHWtCCNOCCQWgSU9CFRVgFWhiE/vtZ
gGO4A17AWEvgBTtYgzoAgC/4A3sIBU0QAiH4BTuwAr/TgisABEC4AkyLhi6oghZLh36IBDvQhVAa
BDtYhI0dgl6wAzao2UeoAisABL29g389CEGwhUG4BzsIJVvwg2jg1lZQA1r4XhtzhDTwg61lhT9Y
B78jCEsYBDQQgiHAgztoBUH4BQCQ3CrQAjDIBzyIpF9wBPJZADFN1sAYgHmggJilmkUgg14Yg9I5
AzbAgzXggn3QgmjAhy6IhtJ5hHzAh3m9h3Xghy9Q3UD4An5QtzGwBH3Ah1mwBbzthS9Ig4K4An7Y
gkW4BzLgh3SwhVrI2Ua4BS7gYF44Az/4/oM7+AV96IIVXAc7uIM+UN0qsINeSIM1OAY76II7WINB
iIQrSAd+wAN7AIVAWAd8sAJ+uAXruYIuMAMAIAA78IcxWINeOAMltoU7qALctYM02AVdAIVH0AUr
uFtbOAM0wFtesIeKJQhq4AI/4IIuqIUz6IVK5oI7EFpL2Ad8SIdKBoNysAc8eGNa6IUuQIRAIAhT
WGEuwITkBYQtsAUB1gUywINA0AI78AMwYAV+WIUAUgAJuNbAOAOybWBJqoJ7wNxaAIAhKIM7OAMz
WIdV6AV8sIc2CQIathR8YIchsAU8QANeyAdL0IJ06AVHWAcriN7MVYMuyAeM5dovUINb/ugCX9CC
ddiHVbgDQmBjPzgDXkhae/gDgy2DMgCDX/gDPxiCXSgDQbCEXgCFZhYEWmiHK1gDe/AFLphnM/gC
NBheewCDNfiCJYzfMjA/MggEDLCCXtgCJQYFLtAHLbAENAAFXigDW2AFROACQ7AFR2gFK9AHR6gF
L9CFgvCDMlADVriHWgCDMrCDITDiRajffOgCaoiGMsAFW7iHNNiCfNAHWuiHduiQNMCHWliFLcAE
OwAETLACNlADRFgDWhgDIbCHF+YHWpDg6FgACH5cvwgAFCCBvp4aNCgDMliDrR2CL2gGAFCDdviF
RQjpgsiDIQ6lMgAEABCEdFAUe8BY/jaoBUzgh2MAgF64B35Ygykupyrggi24hXQYjU4+hjUghGPg
AquuhT/YhuYdDX2AZjYe5kFYB0tohWgABHb4g6a2h2OwhTRAAzzYB8jmgiqghi9wZZNeQjSQXzvg
gl4QglbY4jNYhy+ohXtIh1YgADO4BTz4g1iLbTgOpXa4B0AA41soiLwejXy4gy3QbM7GB/wGgBne
BQBYBSK+hXVIYF0o6l4AhHJiAzJ4Cndwa9S9BUEggzrehzv+gz9IagE6AweQgFoFjAVAAXQtpVvo
A2ooiKheAwAIhMKtBTJAg4JoBH34ghgAg/rm2vmNhnYYWD8YBE1oh4FIg3sYBFYY/uSCcO0xSAN2
gI71OwYr8GI82GFe+INy5gcwIADgBoBfuGYAiAV9sIRFwIPkXm5a2GVfYIPobgchEITvvgKWBgAr
QIQlHN4rMIhH0AdbGAK7e+6tpQUuaIZ0+IOutQRaSIN0gGo/uAc2WIRIzu87BwDV3gIeDwR8sGrI
1odYAABWwANbYIMyMO1d0AdT4AU/ENYIH4NQGgPXVYM0uIIvyPDbPYN96ILw7Qvl8YC0DYwFPmZS
YoMucGWCGAI7wINaaAd2wIRYeO+CMIV7QIQhOAZ88IPTTtpAQISFxW6n7oUTSIMyqAVb4ILNJohZ
p4Y1wIeBQAQ7WIU0doR2yAdb/tAHLjCFfSCDLViAadZkERaCftCHSNiFLuhZL1CDKphiK3jfO1gH
W9gFPDgGEK5jK+gCUMjfghgEfKjxgrCEdaiFclD4X6gFNDiDXUCENGgHL0gDfx0EWlgHPDDqdTg1
PxhmgtCFLkCDVWhnMFgHLhiDpa5jADCELugHIRheXPCFacbwdrj3dZBkFdcFXfiFX4DjVRhkNfgC
XaiFQIiEfbgDJf+CchAgBaiBCgiMNDVbUnLtmn9le8CHMrgFAqCGdthaggCFfdiFBGmHrt3bMRgC
XcCHP0gDOG8HWgCARohwqS52GOcFNYj00diFW8AEe8DvpO+CdTADAkiDOwCD/gBohzQ4AVbIh1UQ
Al7wBy0IBDzAg3zIBwZkhy+I10eY/D7ogqSmhXxQAwAYBHv4YWgmCDTQh40niDFoh14wcO/mAj0/
BntY4Z1+BF4gAy7ggmgAgHj/Ai7QBaEFANT9AkTogjSIgW04WjJIgw4RhHyIBSFAA0SghUcYdjzg
gt/rB3zQ8wH3A8z9BdC9hVWg/DNQ8T4ACDRj7NUSsg1RIAAKFzJs6PAhxIYD5rk5E9HhmXgo4F3s
6PGjQzCWLDJstMiMEABDLA1hCOaRwkgwz2zBAEBLlUFgAGBotBNAgGiDLDHU8kiISIsyAVgCpZJW
mlUpLZmyaGqmKS0nxowh/gDgWDRMjc5goIamqUJLhBbBfISpJaggW/rgWaglK0MMasopRMOmlxaF
prZtE2RRyyI2VxayYjPIKUNQVdjcaqSwir0rKRXe3XICFLVWQNOwSQhgVbMxCy0NYhXTUh5TpgCA
GWRLCAE1VTGYIQryd8cF8iiIBplRQgXgypczb+78OXSFZ3jxim79OvbsF4XLW/D7eHLt4seTLy+d
uvn06tNz925co4L18ufTb6glcP38+j9yD/Bdozv7CTgggQUa+Fx//6HQwIENOvgghPUl+N6CEVp4
IYYZAjfhRxlVqCGIIYoIIYceecjgiCk+FIBXHbWyQHHr+acifSV2dCKN/jkC0AoFEZRQAhbhKRRA
G1hgUUM9rbhTQw1YlECCQgS0AaSRVWLhgE0KuSMBlVYaSQ9HAChQA5XxLNQAPVVS0CJDC6Bw5Jo6
emTjRTjKqeI7EDywpwRsxgNBBoFC6QYPez4QgVcB1PBAoI0GygMWAQLwjqOVBvpPfAGk0GgJDC6w
aaMUOLRADY3W4N6dENEZkZ2pjhhBoxAUR8AEscZHAaCBYpEoqJYGWo9XC1Dhq6P/+KcAD43WI2au
GdQw40ILYOHos66qKo880JqoEYoNYYKJiBjAo8ACC7SIgTvuQBsAPO8M0C4877ZygkIDqNsiAeWW
C08A+p5b7rrl2vvQ/jyN8iDBkNMGGsEAADiQbKB98oSCoxBAAHEGNHAUwD8GW9xsoN4RgALEz5JQ
cnxRLlAPDY8mm4K2EBEQAM1ZLjRzzQTgnGUrAWCAgc4Y1LzeqhC1ylA66ZB0UTloHMNQbqvkMV8F
ufIwAQAjL9xwAy0vHAEPYdfAYNcZr0lr2Dz8U0PHGUAgKgC1ZhCBf/C0nQEKMZ7ZLMIAuJHr2xY9
3CgKCmFAD6funDEPxg4A5TWk3g0Aa6AQuIdBqW5LQDkNkirkgNcZqA0ozB0NQA8V/6xNAbQUqP4P
Fm1MQMPbebhRAxU1pDDBBCmojkLM4xX90NHSlVHG0g0NsYVFrHxh/sXSQ/DSjiAXtbTQGWBcfwZ+
vynaKBUzU56BqBRAzAMFHjgKZRuGRrBAA81GOj7dAZTQaIAFV26mQ63cH2gNFFIPW30OYxLTVKP6
9qdGteFxplJAACpQA4yhynyWoofNACCByoGsdBBphRvGV7mxKUR/lqrAAkJnKRoETzztUVC3sLcO
foCBFk+zRBW8I4g7cKEQQ0gDPvBxPQCo4R74qEIraEGUIVyBJYGoxS5+0RIMXMEObLCMKdKgGuDI
TXQUaMD46AEAC2bgHzrDGMwU5jZ3KKBZWFIjFeLRgP9lwA0AMGEE9MYQPCqEApxqmMMwRg9eccoD
A5hA4xz4qBL4/ghjdLsZ4ioWpoWQrAQKcMOwAuVBhwRgHiBzZIDkUSke0EACCyCj6CrFQvUIxwEt
NBq3MLKONRiiDH4wgxnKcAVT8MMOa1jDKnSBj3UMURBd6AIatMCKXRCAFmS4wi/w8Qd2cAEw1LDi
He4ACktEow7KgQcdcxe6J2UObzpTIwRSEDoezIMeEIOAOwgwONH9w2KNSgEJerUsiLTxUe9YUqPm
sZB5ZkCgQOmV21QIgYalkFiiq4GQFNLFQJUAVQpRgAM8RcdNNuRvjYoACTyZQAwQilNuGEArwPlR
EqCgWY9kz3D0WKdYNuQM6wDEMfDhBwCgAR+3qEI+tLiKSASC/h3QWwgY+JEPouiiDNG4gx3qsIh7
+GMMfmgHJuyRDlBcAZk8Yc4GK0UFETYqTG6wFA/sWSksDImsbqPCOyuXsofkIXQ1CKvo7FjAgA4J
oZaCGzwy6atBNmQBdKycG9jUEHc0i6MM8WOjHNeKctKtAufTKwCqFqodlRMLr8zOCynULTAExqZ+
2MI92MDTI4IhDX1oRy9o48ulaUEX/JgNK8pwj3ugAQCAKMNOdKGPVdjjD1r9gxmco8aPtgFkbnMP
sioFASZhLGJ9tVQEJOBceEakFRTTFeMCRYW5noyvB62U3CCAghYFtlE0SIFg5eGQAVqqohBh7D1f
WYH17ahX/s8qqdvmmif8KaSzn8XO8DBCUwDwwh8tmWFO1wAAVhwxN9FgwxeuIIl83IG29vhC9R6R
jz904WmAuEf1/DDcftzjFregnnMUINhA0UMBKswABhUiLbGiYIKOKsE7ooSrSs2DBM6lh0XggQJ6
0GMjCxlAJiVAgkxOIEaoNCgCKyeBCSzZDTFqb6Dm0YoJGIoKcbqo1RoZKMc9BL+a9M8ZKMC7NsRn
v5EFwALG9ywyQkBIAK5jgRvlWVZiy6I3WrAdvMCLqepiDGVgxxX80AVCuGMRV6jCPXTxi3sQ0y79
+MMtFNKLe9ijJYDowhdugYd9gEIXZGAFK6xwDCE4YojA/hFhnwmA10DBTSFtqJQEBmBkR/WtrY7q
XABwLSkSGOoB+xRgsiBAg2QNeiEeDfN1F/ZKuzUKSv18lKQMK+gFXJsKiXWImzNQumQbKgUAaICj
UvAOBwh2z+/0c3XhAeYMVNs8wiEOcBTwISK6ugz+sMQJ0PCFPnThHqwAAxvIsGpTgOELZdgC9mqh
aIW0Ih+hBsCo/0CGdjzNFO34Aj+aMQRMsAHjytG1o/I4RkY9KobXXvO7Z7zehWT5zXGrmHvo+yuG
wKO6GXh2HzG282SbytALiS6Nz3AGCdAcbwohgcHsOAA6GgvdjfWP/2LlMxFSoVk8cAAB+CwkdxyW
Bip8/qm/5eEAmV7kHQMHwBl60QvIEFHv1LBIHVw8GwCYwRa2tkQvBg8GfURDIYO4xy4CYRoACEIX
g/COI3rxE+VoVleioUDVU5DBAKiRB3ZkeqNiOEaMYUE0WE8gSUCvLIa04sZQYkh5IxYsOjIMIpQy
lUU6n1cZE84mBMg93gC5kKLnd0d05EGAlmT0jJFANKJELEMIusIDXye0HVqwQoSwmYWMfyG2foj4
CWCIdpTBNHdwuEO0UBwhnP83MZgAoP4Rj2ChDgIlwKy1lYC0zYN7uA6g1IBiAUXm1IAC0MuWBIrG
PB3g9JoAudRcJR3h0AsGqFEKKF9DqFTU7Qg9GAoE/kRAYykfBuTe29DLmWBMtUwW+EhKAHhA6EAA
mLTI64mOB0CNG2hXBpQAfLkX91mH923L3WnHENiDF+zC9SzCF7gGeWDAADSAuSxEKwzAAFRhQ+QL
FsYIFzZAC8GPutBeA1Ah1ExhA6BUQ0hhGVJhAqJLG0IL/JShFjoEAQyAHIEhz7XhAFQABbiBG8RD
8LzDOzRABcCDYhGAO5ThIbIXILrBOyiWOzxiA4xePDyiB+qYA9SDvahRtcAUBcRAh+Ad+IkHJlAD
XyjEEGiPtbRihihABEQACsxiSFmNG7Cgv01ARSiI57iiL/6icvzZKO0cK+li8hzaPGQiMC4jM3LS
/jvQw8V8TAk6gNORxwIY438kYzNuIzcWlju0Aji+SI1gI4X0YjeeIzrOh3Ds4ntoYzq+IzyWx0Sw
4/e540ocI0PEwNSsYnQsj2KxonW0AhjgonOcgRqoQQICBxiAQUJeRPdER/q1whA0pIC0xBnUn9Fs
AVdwBd0BxxDg40W4AwrQoxGiCCtoHvk1xBXcARhMxualJPo9xC9YAaqAgh30lkdQJEOgwR2konOA
AS8gwhqA5EdIzxp0ZHqcwS8swjGgwS0gZX6oAS+AghosAkbWVC+kAxfYQRlwwdM0RCuwwuB1xBik
gRoAh0iSpEfYnaSsguENgSBEgy3wHRjsQxcM/oI9IAIgBILLaQE19IIaJM8ZBMIisEJxDIEamEE7
6INogIEg8AKoAcAWHENgcNUVbJ4abAM1TI1kosFZMEQv4EMtjIHLCcEY2AIUAsAYqAEoxEhcnuUZ
rMEfpMNsjMFOnAFLfAU1+IYW7AQGgMJmDIE/rAMrtKZCbAFrKoQaBMJEgkJpaYFFDMH1HCTfjQFf
qiJX2NoQ4AEi3MIuPCEoDNEYCMJPEAAogMIYlF/2UCV+DMF5KidzLsRkHsP8HSRDLkQtdMGlcUEg
hCcA7JQlsOb4gcKI6UIV3AEb8IV7WkJgmMIX+EFjqsFPYID2tAgaeBX3KARVisb4aUFKzCNR/t6X
BKBIpG3BFayDyOmCb2xBOuADL3zaPeBBOzgCANDCVtrBImxG3n0BHvDDILQCAQwCF5TBH+QDAPAS
GXQBPqCBySGCLagBG3ABF9hDeL6YFXxBjhoCF+DBF+zDWNLCH9wDP1hBVVwBP0gpGpzAFuABGaSB
aJyBLbBDH/CDWOrDH8TWGXyBPdBGO/ACGvADIrADK9QWE6pBP9CCKsbCH3SpPWwBGFgBItSCI0QD
GXxBGqRBPtQCEdlD9aABL9DCIljBlIJCwrWDHfADotLCF6QDLbAJGOBDFwDCLuDDF7TDGkyNLbQD
F/hBVWzDPuQDGSxC99DCr36BLliELrTD/i5YAhqkwxesgWoEgrOSQTNwjy7gwaoZglcMQT8sYRqU
QT7swy4EwZHaAxfsAi1shinkgz+UnynYQzu0AxuMgcaxg2ywAR7cQSQAQCDsgz2YBhq0X42mgSP8
gj/gwTaYQi8QhRr867uNZIi2GRbESZQegx/oVBVY6nmsgyVAZhqgwTrgwiP4AS9Ygj3oA7jg3SKY
5SCsAy2oARcMQhV0QT7EgB2swxXsAz4EQk/pgyDwQxkIghl0wS0EQhfwQx1Akxakwx9cQeUll0LQ
Aj7wwxW0gz+0JBsIAiBwwRhEE4gpxBisQz6ggR/wQ8OWwWycATsgxDYkqVD2wjq0Ayuk/gMZgAEm
dIEVJKpx3cI9RIMprAM+0MItlEE/oIE9dAG2qoHGlawffAEZ9AEumaUalIEdqME+sIP0eEE+jKVK
4AE7+EIt/IEd8EI+0IIWsIMfsIId2AMY3AE+7EM/fEEVLIQuaO4gvFoeSFM0UIMVVMEV5IMuqAEe
4Kwu8MIW8AI+6ELVJije6ULTLgI+6MOJ1UI5+EHq7oK9psWvXkEg7JIQhC4iDAIe8EJW2gEt+IMf
oIEd9ENrLapvBMJNmkEt1AIv8MMtPJUd9MEtEMDguoYCSECQAccASJlFpMEd1AEgfIFofMEdLEQV
7AODlYFqtEMtSAI/7MMt6MM60Gha/qBBFR0RJvDD1NiDHVTcnl4BPphBIPQBorYDPqxsrG7BLuCB
YkBnLzzrFdBCjPRC0AJALejDIzyCGZjpPajBL6zDWSqEIJTBIBAe1w5CCSvxkKaDLfgDIiTXtbKC
H+ABGETCPTSwSvQDO2yBEARVI+jDLpxBM9wDTNRCOwQCD6Eo8MouNdBwFawCARyD6KJBPuTDD3UB
1GLPGtiDI9RCGaiBEOhCLURCPtjB79ZtGuCBFlgCIuypQkjabOQDL9RBOthBbqxDGmCaP6iBHeTD
IlSBGrRCaLaDGdBCIOBHFRwyNZRBqxrVMcSrGfhDF2wDZ+yDF5ABF+DDHQzBqIUa/i/oAibk8C/o
gx2YQTpcHN8awkJ8wRcgAhmYrh3o5xXogz2kwRrYQToAxqRIgDl6RCvIjn+kgS5sASHYgXTiwU4p
xCJAMC+QgWqkwy1gAh6UAS/swz5cjxDYghVYwT38ATU0gjsTnh+AAR7saSCQgRmgAR7cMz7EQizk
w2KYrK72QvPwwkDPhi2AnD4QRdUq0x1YQRcAFyvow/gFQhkgAgBoqRkMAg0thBX8gT5Egi3gQUII
KSuQ8DsDgir6AwQDgD+kgSXow2KswT20RP0CQBr8AT4czz1IMAAsgrmyAQZsAU7fQjpUhy7kw0vu
yBrwai14Mij4QS9EQjr0QSzw/oMuEPNObQEZxDMARClfpIMumEL6/kEgLKof9IGmduwu8AMhEMD3
+kPxbhEAXMEXJKYVYBw78EI58MMs9WgSWwI/sCrPGkZWpif9RoIvrIIj0C0b8MNC03SMqME6eMEh
A4BsbuUbq0E7eIE+WMY5o0A1doQHBBsAmKsp4Kt03oMdLAQPo0E/HDIBaHIIr8EQ0EIzzAgotAMe
0MKI0UIkDNd/tsMQ7EM68BQyzWz1tKgpjAEbaAITmcEQbPYYGMIVaEE03IOmiho+LCsb3IEl7EN1
60MXbAEtrIPLUV4X2AMBRAMe1IE9lMFXXnWRCgEtIJMQ7ANW2QMX/62EqcQu/nTBIgQDO7BBLYUa
G9zDbPxqjXpBOqBBbZcaKPwCKIBsNPx1OwR0b/nBGNfUHbBDFSQrYnLBIgOvFtACKyShkapBF9h1
GnSB6WbqKqAqAFADO9CCY2wDBsjGENwBMgWAI5SDKXQBq8lzF1BDNHyBarADtKI2GGwDUgtGPvCD
KC4EG7CDbVqBH6xCLdiCJuQD66KBFFlBPizNQ+tCKDuCH5TBNhzDFaDULvwBP4jGlszdcmyJHeHr
KvACF0gnGVx4Yxep2IICBrDDLmjBLaxDJx82x61BF7QDiqJBhOtDPuCDkeZSPqCoGYg3yFXqg0ZC
EsZtGbBBK2wDO9gBOwis/kLYglSvAzugwRCwQR/YwW5tAQ97k0KAwaDnAyLwwgkE9oJT8k6pASKg
3F0KwSAcrT68sComOiKkwz3gUhdURx18AaunFhF1wS4AQLj31hWgrj2QARpsgZTS+GLkpWpQw+Cd
wR1MUx9rwTHgQUFcFS+k7hCkwzrEO6YPwh+ILULos1BvweqyQTMnOz+wgT58geTZgx80A+Wm4i14
gR3YgT0DgD5YAVDyQzRYr28kNT6sQTSsAS0Q/D1oAhhM6Sr4gz7Ygj3Yw8z3wnrfw9KcqCVYgh3c
wRrgQVz6AbhI6xXoTA+qHki0AglgwQCAwRYMQR0cg86sQsoyxfz2ghnM/osrq4QuPGswtMki6MIt
UIN/HIMujO4qZE00SGktTPIvBMYQrMLKp+uR+sMXTKVKZGXksckjgO4uVIF/MBF1+MIZjMEV6M0j
1MKDOkUgSNFC0EIZEIJCBIK5/v3i28H4btFg9oJ37nwj1EISH0MpG95N9IJrVKVT1EEaJM0vWMQY
vP0+EAUrVEEMECgvkATe+8EihPQj2MJsmMIaGOtOXEGoEXP1KIRsfoEd2ILUzQJOUgMXfAEbEEXQ
f8EudMUPkcFNbp4p7IMf2ILt9wKiggIP7cPOc5z4WsH0+8Hg1wJAbDnji9aQaPZMlWuGx84YALNq
nQEw0VQtUABo3dpC/osfvzRaAKDhZwpAqwkTWk1UuZJlSwURSLSUCUCizDNghtisOfHMkJ0AhviU
GXTlEDA/cc4881PoTJpJW565s47kxKBMj9pUKaRoTqc8wYApClWlpXW6di79qdKoV5othezCI6gV
VwBC7AII67atyptiWQbFy7MmmGNZVcYIa7gczxN3ufacuIDVRcgsl/KciElQTjBfvgQAEG+eu6+n
W1GQEG/tadevYceWPZtnr1+0ceeeGODKqry6JxKItsgtcOPHZ2OyRwvAACxtUupuRaKGG+TXsWfX
vp17cALdwSMXInEBFgANjk9fHT18e/fv4ceXr30BCnrokbdqE2GC/uj5/wEMUMABrxughhrwKxCF
f0rDgMAHIYxQwvgCqGAeLCrYrpV4sKjBgQECiK61CUks0cQTF3ADhRRIGAC8AdyYRwIU5nHDjXja
GEDHHXns0ccfgQxSyCGJLNLII4dcQMklmWzSySUDiFLKKams0sorscxSyy257FJLHRtwQwIa6ImH
vRc9mKeGGSdow8034YxTzjnprNPOO/HMU8898XTAzz8BDVRQP9uQx9BDEU1U0UUZbdTRRyGNVNJH
6YkgghTqccPF+Fpxx9MGQA1V1FHPG9XUU0s9VdVVTVUgnlcVOLWCV2mt1dZaK2BV1115ZTUeCoAN
VthhiS3W2GORek1W2WWZVZYECho480QTW6l2pmqxzVZbbUeMsBW1wA1X3HHJLdfcc9FNV111p23X
3XfhjVfeeemt19578c1X33357dfffwEOWOCBCS7Y4IMRTljhhRlu2OGHIY5Y4okprtjiizHOWOON
Oe7Y449BDlnkkUku2eSTcQsIADs=
------=_NextPart_CB1_DBFF_A641E164.83FFB0A7--




From tiy@c-able.ne.jp Thu Jul 12 00:47:59 2007
Return-path: <tiy@c-able.ne.jp>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8qat-0000g8-Ep
	for ipfix-archive@lists.ietf.org; Thu, 12 Jul 2007 00:47:59 -0400
Received: from [210.101.197.221] (helo=oqux)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I8qam-00051Y-Ps
	for ipfix-archive@lists.ietf.org; Thu, 12 Jul 2007 00:47:59 -0400
Received: from iftic ([197.173.105.186])
	by oqux (8.13.2/8.13.2) with SMTP id l6C4oX0d028428;
	Thu, 12 Jul 2007 13:50:33 +0900
Message-ID: <4695B271.1070804@c-able.ne.jp>
Date: Thu, 12 Jul 2007 13:47:45 +0900
From: Burke Mat <tiy@c-able.ne.jp>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Re: unpaid.pdf
Content-Type: multipart/mixed;
 boundary="------------080700050506020003070107"
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b

--------------080700050506020003070107
Content-Type: text/plain; charset=iso-8859-2; format=flowed
Content-Transfer-Encoding: 7bit



--------------080700050506020003070107
Content-Type: application/pdf;
 name="unpaid.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="unpaid.pdf"

JVBERi0xLjMgCjEgMCBvYmoKPDwKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL0NhdGFsb2cK
L1BhZ2VzIDMgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9QYWdlcwovS2lkcyBbIDQg
MCBSIF0KL0NvdW50IDEKPj4KZW5kb2JqCjQgMCBvYmoKPDwKL1R5cGUgL1BhZ2UKL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzIDw8Ci9Gb250IDw8IC9GMCA4IDAgUiA+PgovWE9iamVjdCA8PCAvSW0w
IDkgMCBSID4+Ci9Qcm9jU2V0IDcgMCBSID4+Ci9NZWRpYUJveCBbMCAwIDU0MSAxMTddCi9Dcm9w
Qm94IFswIDAgNTQxIDExN10KL0NvbnRlbnRzIDUgMCBSCi9UaHVtYiAxMiAwIFIKPj4KZW5kb2Jq
CjUgMCBvYmoKPDwKL0xlbmd0aCA2IDAgUgo+PgpzdHJlYW0KcQo1NDEgMCAwIDExNyAwIDAgY20K
L0ltMCBEbwpRCmVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagozMQplbmRvYmoKNyAwIG9iagpbIC9Q
REYgL1RleHQgL0ltYWdlSSBdCmVuZG9iago4IDAgb2JqCjw8Ci9UeXBlIC9Gb250Ci9TdWJ0eXBl
IC9UeXBlMQovTmFtZSAvRjAKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9NYWNSb21h
bkVuY29kaW5nCj4+CmVuZG9iago5IDAgb2JqCjw8Ci9UeXBlIC9YT2JqZWN0Ci9TdWJ0eXBlIC9J
bWFnZQovTmFtZSAvSW0wCi9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDU0MQovSGVpZ2h0
IDExNwovQ29sb3JTcGFjZSAxMSAwIFIKL0JpdHNQZXJDb21wb25lbnQgOAovTGVuZ3RoIDEwIDAg
Ugo+PgpzdHJlYW0KgAAgUDgkFg0HhEJhULhkNh0PiERiUTikVi0XjEZjUbjkdj0fkEhkUjkklk0n
lEplUrlktl0vmExmUzmk1m03nE5nU7nk9n0/oFBoVDolFo1HpFJpVLplNp1PqFRqUEU6AhaIrCIZ
tTrldr0uYtfhzFslhkFkhbFBDerEnWETs1iuVzllxgV2PUMREassEb0Su0Eq0YstogSAwcJvcQwM
GxuLABegTfZR6xIAvuYzMDzcCyECL2Uzmdxt002nj+BuOG0d2BEFL2hiKAPWW1eAhGXzWs0GxhGl
3kHW8I0LKx0L21xW+vYuSyOx0V3vuFuO0y0EYvDgex7kC2qA1ml1Hj8kVyuj9ED62J3nc3wADGV3
UFuN5ACnwOS9+Rb4Ygb8N44LLQA7buoO+zjsE2rWvzAz/rS6zsNY5zIoG+RTswzj0wkgkKOdCkEP
E8sRxIhkKN0uzgvBDrtt64qEtuADaNg9znv3C7VtU9UCoU5zrw1BjBsQskKRtIoAOMhTxLtD0XNE
9kGIKy8mwq0EdxLLEsx6/RvvpCTeQRKsqyog7qSBHkKv3KzvOxLzDoGT0HNg0EuzPDK7zegRPQLO
UxN+g8IzXMcWzrGT6MDKcWzFClCy1R1Hv0g0wulNs4UVMjHMLOwAM/I1FT9FFNkrPaD0xMMYrit9
BSPI9MsytBT1VOMDPdSKBP86TgrsRFRvfMlW0fYMRz6ABZqo0iCFgrQMw/T6DSTO9ozYgz90xXEG
PqPQY1Vaka2dKFowRZc1T9QEALM+qBWUZoMw67syPlBKB22yFf2Fe8sWBIt40qgdtW5UlyxZadpA
BSZEFhUdPyLI8hrsytJxpNUisoyzBsLaAAXpbiOYii8RXxkN72AhuQABbmSUXK9nYNbeBz9I9Gox
VjZMOzqSYzkWdZ3nmBZ7n+gaDoWh6JoujaPpGk6Vpemabp2n6hqOpanqmq6tq+sazrWt65ruva/s
Gw7FseybLs2z2ptG1KE+w9Wg6Jv3IguAwy60Fo8xG74M2plZkvSJuhnKFi8DDbMRvbarzMM676jV
J78hW6Swqu9b3t6B8hJSqourKsGaSqH77Y0ScTj3HbbBBv2M/plcbGzIMhuMZGLynEcTwVBM8zyt
IGDDwc323TMUiW+dVC3XP2tqtEruPfPvu2DIJQtrovx/e7+jU+06hvTcykPfG6YrB9K+wMTra+4r
bTlkgBOPwYJ6KG87ztFfC3XEsmhCs91dXekA+FwD6iEvOIW+ZIsBiHv2cq3wgrrVrvzISN1fyC38
LXVxAZ9Ri31OSbs/gg6SU6wagE6BPJ8yHQCM8wkhTEW4usPgoWFBn3qN7O86llJEG9N6e87sgz7j
1QeIQfEZT5iCGfL2woziM34EEhmSSEj8TEuofyAAygyllP8U4XtepAkMQ1Ii7AgZe33B6i6v6Myz
1lPKg0QNXrhSJRWe2QWJBCXbpJOLFY3ENYgNxRfFl/ZB04oaKs4p+MVIpvrfXAIrEc08kJOckmME
YVLMGPxCYgTl4eRFj+oBSShHWx+iKQSNp6lAoWL5GeGj0pPyZjDItUkZHxSWkNJeVsmo/uEjJBNy
rrpLxplsRorK7FbpXfwfZvyqoMySSqisiK3IwRbMFKhl4MYsxYMgu0ia4plRYIQgg+y0ImuDWvGW
bzLIrkHhk7NDDinSyHPtL6VsKD4HIiob6bU8X1LMAxOFgijWDybIMfOcqXTJF5mpNuPxWz1GNeER
GfZmJyJhb6mpjkiJETYUNN1T62pNP8d4dhyk3kwy4o5H6OJE4IAAjakJ6LbVnsamdMqI7kiHLQgh
JFlbHpwMtLfTik6JpURGIXOt+KCIbkGhQf4sMUaWwNeGQNVRzqlztcse8yrLpuSinoXk4yIJbTJO
ROwgjo11P0IRTSctXDfPUqFHKHxBKGneXpT+lS5UwuVlpKGj0k0D1UmHQh3cAkKRlkKkh69MCOSR
KzEgvMsVpuyOeo2xU8iHogrnSZTrAYJKSj4pE41B6LV0R6p+0FFoggAgk+NxMOyCzydBQVHchE0T
or0Yu2CebVrNSQfak9opi2QT9TG0xCZBpzlNVmvRBLN1NlmkVMKnX1SMZMfyq5CqAWorhEBctwqc
UBr8n500irDyNkKc5itpSLXcmVK+llu0XVeo9dchyZC8xpnlNAgrbm3UEsjVCwBD6jOYfYQq18hT
rO4nQ9uLT7Ud3FwEQljl0MGQljOh5LptRYTnuRQGQbGV93+sxcR8VTkCsVMVWZClS68qNSLhl/db
TIz8Io9tVrlUjsQwzNa4k0sWVIk2ZCJ9GZ+odtYQ8+K/8dMnIE8yRtulfOst5KyisjlPpdptL+4c
XMBIfQotfCNlWFkEwRiCutxrWL/vE/2Q5cRvw7PPVkva3E6mJt0lY0OR7kwDYWtW499q6KtZkt5/
Uf3luyN1j13tV6e3JtERLBUTHfsvO2f3MlP1Cl20RXCrEWGOKNFOdBOugiL6CMgrguMIhEGGNfJl
WcbE4HOlkQXVdFk9oUyDLggRa8foaL/NW97dKaY+NYWygFRzwa6niuhwYXhPCVZQ4WZmIU8OD0cp
t+T2Fo7IIxo0iuxKs3TLTrMkO4r5TAoRuBubK7TapNZuUlRWHDrS17aZIpi9gkL1nEdlhBAEC3Oz
vlDRcd5q8kCQShV1hEIoOXvPMpChR79ywwUh67HJba2m5Go7XhRtC24TsthC9nEZi2dzZpIG5Eb4
zX01vC8Fkk462tR/DCian2Lydfr0VzkD4HSpWaFM/EYyDhO/8NRAWEqRlMhhduipm5kVDe/MESs3
I1tEtQCIR8FTEZBHJ61wSJVKF4DIzYNHULMd/WNxp8I5fEiFM/LyFmXLIAjcXPOMqab32clXdSN0
YJP1IkSOqgdJvyQ3pCrijng3QbNfp2puHvYCugsJwFNa6M+q3dimiy7xIbHM2Ozd2cXuzxc5ZGe4
d2pN0FQ50yybx8QZogWxO3EVV54Jkp2bRkh1J6Y6pqfB7YSUm4q/XzneXKQqczcwSIl4Ttwxz6gv
I+QTAgP55aoiufb8ilA+2L+bT9NRB+CInmLE+BIU1flPfr9LMetAncePqc+ajbrp4lQ6+XdikzZn
elsg/CkXvyUj8DONtNCs6kYkMqQlDi1owv3kYFXnajWp8QFvUmQC1P2slo+DIu8CfOlOcwJrKC0j
sD1ubn9onl+FcwCC8ujLAntvjEAiGOPi2wRkolclpQUJWmEunvQF0wSu5sSEztlKMirEYn6I2kko
yv5E8i4u5wbETwNvTIlOEIVJLvpO3jvwdKLKomVjbjCjElzizPYK6O7EzDDkCDMOLFJEUP+wqndo
VHCM3ijOlEdvEl5DdvACBDhi/l6o+v0JBEysqEvwCPftVism5QslpQMPaOLvdiGmGkgQfMHE7t/w
7lFFoElsKPQP6JDwgPdPViFQdr4QFsRshPIqZMHxQloxEkJOFiFP5lom8mLiGmZNwFwOWQ8CkPsE
3q4klQ/q4E2t/lLkjwCPnm8trN9xLOktVAEDmvsk8FkCMO4Ezm8q4lardjbPuRlozEzNZs6nTPps
hDdDlxkFPjjDkjVQJG0nclXDDDEwgCBjtDmkHRJxTNrQwiERYRGPMoljiPeu3krwkDMPxCgxbEMj
gCHO2PDQji4kPDuIXREQ5j6v8u0QeN0Ouk+D9j7Dww4s9QekvkTFaNKMtRHyGvyFos6mSPVRTkOF
VpZwIiFQUFMF5QfFDSCkbF3IXP4pOxFR9SYSYPbxSPzwfwNubCgQSQsx7ryEes5kyjWEhM6P6ygk
YRWyIRpR8Dct1L3mBkfuJCewiRllXpYi8ymEjGUi0QWDBPWyUtRQxriGLSKIbv8ydRWNljfFCwiw
wLHEtlfR+S6jgyIFPEYRny1iljoQsQSyqyeGSzCiRmGE5OUkpL5sHvNRax0MhSEygyZFAQnGVSZj
ATIR/sxTARdCIkKGMxNLplaRSPEO1TDEXSfSMCkMZOMRzCKTWimnIQ0CUTGSpiDllISNRCHyAiay
nOoOTGJiJsNRiTfEsyHiMzOiFuDzcC0jaqDl2TnubzZiLRcDezhTbkHGJsTQHRdiCOsSwxcy9ilr
0CHvrjWHFTzluzglJTotXSKSmyfKoGEM7OMw2w5oJz2ETMzswRjSYKDFlKKzmS/CEuemnvUGJyFK
FkwCCscy2E+ELGLGQFtvCkWSgx3MiiNlJwbS4kTzUDJmIRou0EfEhtJmICBNNzx0WSkyKzoi3wlK
jk1UQoqUUyOFfUZzvKoQoRzoP0KR/UbHEUVtBTew5IgMMlemml/0CGXsuwSGBGPUczTK8puogLXz
FFaGakZBYTpwom9Uk0JUpzPBANO0U0YUPzTiBFmUqvhF7D+M8AAODk6nKmUSUpu0y05ozKSvUTYp
5iCU2RFUisiHqTp0tm9tNuMjoD4l1JhSVEwwlUIzVjvM6DiqXM1GlrvmYRfAvBZnqMpmI1HUWSXC
Cj+m9F6VRS8S+oHu6SPHEqsFmFaypDI1PNmI2E4sLzsFysusloT0vU7kKHRmAonnqEEKFVSImI5H
r1dHckjhKmEU+iCznM9kHVhrsm9NG1Z1rK/1EMNEqNBVPJtkfJpGlJwvKlLlnKaKyK5TwlvVkF1F
eqyG7mAT2ySOGlSMj151eyw03uG1aVGNqUnUfCEr0Vv10V9uhJCqD07Q+z4sGV1vA2BuSiFrQIn1
+tbNX1PFoRcFWkDInmA2NsyMuTYufFBVIGku+JpFrsuTFiDMg0Rp316mU2MJDsB1JEmkKKFVYjo2
YoX1B1uFW1AiFNAlvUNolloV7WfD9uDkxG2sMohzVDuOw1/WIy+rOiGEEM5Mw2gCB1pzcz5jIjjH
ZWpTnVLJUFcNRU3r8LCmi0+q7xSNRHBNgWzHbWwU3Vtx9JDxtSVDnPUEkopTYlCsWPPWsT2rjxXr
8nb07rdpeMWxSVNS+TNQbqXv6wosxpVIgMAlBGK3GtmVnzjmJWTJ6lyVImCKRmGF/KJs6mOXLmfz
qCPrtCHWr2EMxXEm+uNuhDJIhLIPO2Pq/nyWbHpnWqCT3CPPUKqFoVo2BiC18ih1cFrpvXbs5TBW
7CMzX1Soz3FK+IqWATtCZzGXINJ3ukHKFFSVc23n4M7ivk42ICfhm0PU23YiUWjUrUO3vCv3h3X3
7tl3J39ztX5X/YA4BYB4CYC4DYD4EYE4FYF4GYG4HYH4IYI4JYJ4KYK4LYL4MYM4NYN4OCYMXLui
IX9MdjTPYlSijL93QCT4SlSmKg9Mc4V4IsoLQYYYRLT2AinT+YQuTE5tRLLwrEts24UiOmSYYGJM
7rP4OpAJ0UlMTtUiBuAMIPZmCOBt3Ms4aiRvPvXuaynQOLAtZNvKzuQnexqE/pQisX4XelZNYT6R
LiIQdiDQkiD4xCr4q3aXPWGSsvNtqmxI4uwOxODt+wuisxZY3kXWpgAKMPGPYCE5F3liGGHCIuwt
GuEpmCyRUos4mJAOHt/AAPKDPiyvGYjWcgMhPOHjcj2Cw4oKaOxE9DFUTi75Qn1zxCD5CubqTF3O
DZSXcNc5Gqnr3vhiB3cZUumn9NXkKKMO+TrGn5iEKFSHOjmJOTyiBqMW+ptrpxIQE2hH245iDqQ5
UDtFO1Z5GQGkYudiEKYt/ZLyjKkFPmAqflwOBHd1U1bULhvQGxLHO2yt6isZa0axZtJNmp4AAZFN
8Lks6oNZAvGJSjNPR55JsWaMNmuDS2GaAnlFAK8Z2ZWkxLhY2KTKouSUDSfjpqPUexOO7SCtT2Go
tBEBvRwTELk48XlC0IlQuQHsGFbYypojsRA14TxNnQOjDwqNss86IOtQPJtwr6NH1Newmuc4tLol
nYimnDSsgL3l2o4yiiEZVFPtGmI6UmTleyxEgOuSQaPPgxqlpzQMw2mZbF5aq5HSBIJzIRR5Mw+T
G62rKO9adFpDP2LWuuh69lojF2GFWkVS8uqosG6Yr0ljkx2JlOg3PYnPuERZLQEZMOsbI6Qkz5wL
F6QvoHDrGyx4tOQPiR4u75pFOawjn2JwYx0PGDIQbv7vzte6gRijAmIuWTwxDpGxnJtmA3erRbe6
BwUzeTJOLr2k74oa4GtQDOLxAnPE+SbRPqv3KjfjN6UCG54CCnay3bUDtyzQCbmtBqPliQ0Olt+b
AE7KGQpE7wKJOPxj77rM86c7jub7lS+7NSZPzU5b5SGEZDvouiy7LCBa2TtYwCZ7ZSD7vJxzCFKE
Z7ziUb9iWbhDRwna1DGKAy0gAZeiDancLlouGXSrEiDMj5UP7u17Wss4kiNxTyzDGDwxhiTTbC6R
hD6aG08RDY6apYQlyPuwzNo8V8gmqS7chci8jcj8kck8lcl8mcm8ncn8oco8pcp8qcq8rcr8scs8
tct8ucu8vcv8wcw8xcx8ycy8zcz80c081c182c283c384c485c586c687c788c889c98+c+8/c/9
AdA9BdB9CdC9DdD9EdE9FdF9GdG9HctCAgplbmRzdHJlYW0KZW5kb2JqCjEwIDAgb2JqCjQ4NTgK
ZW5kb2JqCjExIDAgb2JqClsgL0luZGV4ZWQgL0RldmljZVJHQiAyNTUgMTQgMCBSIF0KZW5kb2Jq
CjEyIDAgb2JqCjw8Ci9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDEwNgovSGVpZ2h0IDIz
Ci9Db2xvclNwYWNlIDExIDAgUgovQml0c1BlckNvbXBvbmVudCA4Ci9MZW5ndGggMTMgMCBSCj4+
CnN0cmVhbQqAP+BQOBv6DQeCQmFQuGQ2HQmDxGDQ+CPt+xeJPl+xp/P2KQqJP6QRKPyWTSeUSmVS
uWS2BPp+P11PN6Oh5vhwu96uR4PV1vV7u96PJwuZuul4O19Pt9valtFzO5zvN60B6u14Op2vF3OO
eu+nWB8t93T54O90OtyPh9vxjOB3N92vWxOt6PZyvKhvV5t9zN5vO15vJ8Pp5vl9LdvtZvPB1tly
N9nN1qsxwudjOF3OCwNNzu9zvR6OR1uVoNtos5xuivPZ8zGXbHZbPabXY21+L9mL5pOBvNNyulTt
Bwspxu1pOJurBhqdZsNYOXSud4vVQMtusJvulrOFrrVhKxTrlPLZnMlmt9wtl0u5WNJyLxpM1bsl
aVR5rFhrJnN5tvgdJVNOU7JmMa5lEyVxGnEdJyHmeyhrYWBqnKYBvHQWxomOV5glOS5Xk0VBiF8y
x0PechtnYehpHCbBZmIVZjmoZZpm+bTXHw20dR3HketkeB5Hcex8HrIZ6nSmjCH2w58nSeR1HceR
2Hse56HufJ8HUeB3HbKx5Huuh7Hkbx1G+dh3qRIJ4noeJtLSuZ7SEeSLn4cp0HDIEuSCaxynEasn
HbCCZnUph9IujB/Hge59Kcfh4QgnR3nkeadHsm59HyejENefp8H4fZ6nzUNMH1TCDI9H1U1VVdWV
bV1X1hWKVJDWVYnKeB4G4dZ1mudBzHEdq0nkdspndTx8HEdx1HSeNJnwtiLoGeh+Hqbx6HAeR8ye
eNcHsexvHWcyYVAfZ7ngfR5Hsfh7nUeJ30WfSFUXIlGIOep8Hs3FDnQpJ1nidt0nogaYn69h1RUe
ckHjfx3SFXB9Hig5wnadZkHAbhgGuZpkGwZptHKbB0Jqap0HAXhtGtixup4dx8n2fJ2SCdp8Hccx
5nWYxvm+XZsGqcZ3nZglxnfiB6qaeZ9Hog7km2a5ym4acW2AcjPGwXprmoWpqGcaM+z4bp0HedSG
4Inh34nfi+Xuex4HxR59KueZ2HNblRrafZtnIbp4nxdJ+bZcx1sHJFnKDNh6n1K5+1Kfp9ooY5yG
iVJqlyURkFqS5hF0VhnGKW5qGCXBql2XxumKYZwGbCxnVDHKBHpuBinEZReHGYZWGuW5rnUcBgG0
aRzKSYxumgTxkFQXjsmIbplp4c5+o6gcuneZxwRqdxxG4dpwMOvh8HuVBlmGUhjl6YBrGX6HGn63
JvmgZDFlb95VGWYJhG4ZxlHKZ9DH14A2RbjYGgJUYQtxJC/FqJQXgqBWjRFsLJqwthtjDGOi06jD
R6DzEwL8WAvBrDCGiOcagthwjEFQNIXQ5R4jsLsPMXw2RqskG0M0co0hcu9egP6Gg2BnjkGyJ8YY
tRNC/FSMocQzyoDXFiNcXkDRgjIG6NMbI5xxkDJmO4a47Bvj8I6aobYxxwDXGccoUYyBdjTHMNkc
Q8Byi9G6MMXw3xnk5HWWUeYlhgC1fgNMa46xtjWHaNgWo3hhC/G86Abg1xko2FqNIYguBsjBGaOc
aZFBrjkG4/8cw8h0DdHZCIdQ4RdDYGkNEb402rjFO0MsZg5RmDPfcYhIhiBqq/F81AX43RkDGG0M
UWo0Bci7HCM8Z46RuizGkNAYA2XxDVGCN0c42EtDnHwPkew2h3jiGWOEboshsjMG8OwchMytpVLe
f8dY3hgjeGsNxmIzhzjqFyNuXg6huC/GwMcZo6RuDVHU08dQ61FD3GoOQbA8R8tyTik4eE4R0jlk
+OIdQ4xtDqHEPJpJbEiL4G2Ooc42xzjiHHOIsA8RxD1ZEqBlw+hyNASsPUdTYhvjoG+Qcdo+R3jl
HmOcaA5BrjdHXR4s48E2DcHeORYw8BzpSS6PIgZhV0L4YIp5UTcCyjxGkOkcTMVcF8qAOMeJhl1D
3Huy+Tw5y4MNHmPFeY5ifLvWUPMeA7B6jxGSesaY4xsDgHWOAihrRoPBO0O0aY7RxL5HtDkg5UB3
ixGyN2Vo4ZwDTGFF8Yo3BsChGQNIUh/RZDXHCJcZIyxgH/FoNcXQ06Ji1GsOQVA0BxjboEvcfCDx
5DNHGNVAgspRjdFSNAbwtRsDkGWOWiY8klD5GjMMd1ch1JWdQOoW42xzOyHLY4ZRMR+DbHSOsWA0
BtQNG8K1GorxrDiGGOUb4xByQfGmMQbQ507LpUWPyio8hqDpQaPEdR/RoDHG6OIXabkLDvF0m4dI
9Laj4HoMwb4zTkjiHAVgg4zxyjtGIOAdIwxwjeF/M4W40hnRjHQM4cg7Re3UG0OweY0R0jtGTR9T
w+kkD4QsO0Xg3BzjLHGO4YA33sjxHIQcao5x1zSHin8eZAxoDpHUNFXwqBkCwFGMQYC8CKEHfUSY
g42BxjfGGNkbQw2wCxtaXKtaYDXD2lMNsZg4Byt0HoM94LyRynYG0MIZovhdjNGFCoew0x0DyM8O
8Xg2xwjlYbokbotxkC+acOReBBxvJROMOIbdFBgjOGGMMbQ3BhDdV+UImw9zCKNH2WwfaXR7PBHo
Nccw6Bs0CIOVodAwBnC+GQNx345h1YHHQK6vImRljZFwNQZ4qBdiiFqMQWI8x7j4tOOk4w7y4DzF
SNIbJkxsCwGMLwWYyxkuoHciqhKzxiDfHGLsZNqTUEHFKMoaQs0+DIWANgdY7xnjcGpaDboxhd4A
G/tUXxgbzWHKYOyuYvBlC9PSOBCY5hVxoGeOceDEq0N5G8NEbQ0SBopwbicWA1hsDJjE3dHq4xYD
KFsM2RQzkDnMFkKYYYwtdxqHaOQZo3hni+GWLgXAxBXCyF8KgVgyhmLAHhWweguhrjIo7kBMoxxn
C93kMMZLHWODGGSNsZ7FhqDUHANIY/PRkzKGmOAbFIJ1TfsqMtUI9xzyfFaMIW1qRsC7GqM8ZR6y
DjWfcL8+w4EUC8feMUbAzhUjLxDQbdgthe8/4CLS+othpjRFqNEXgmxhClGENMYBrh7nVHmMwbQ1
BaDSG4LGZQ3y1KlHyNocQ1hg8/GuN6UpqBdjPF4NUcVqBsjJGRIpdJfB7D1E4LsWotNOPyF30kag
pRfPkvfnoXw0GO2tHIMgbQ0BfDVdONUYRN1nkWU5lp9l2vYMDegTEkJIlU3aGwOYbijx6aKHSN4c
o3RbDCFaMYGmKEHgbCHOvgGaQyGGFal8GCGSFsHYHcv0LQFIPIGWG8GcHKNAG4L+EqFiEyN0+UGU
FuEyFuE8E2FyE+F6GoGEE+F4FOEqFkE2GOZSGYG2GcFcGMFmFqGUFmu0bWHMbmGUGiGEGokO7iIO
eCHOG4poFcGYGCRk6oG0GcF+GmdQk6YmHMGHBqFUGSF3CONKHGHSHAGIGkF6KEHeIOKWH0HMXCGc
GqGNCmGEX8HWIGzCGQFYGQFpBoGiFiGMFoFuGYF0Y4GSFKF6FEviG8XGmqHuF6GOFmGQGoGKFgGI
FaGqG+GiFwGkF8ryG0GCGoGSFEFyFKGsHAGoFy1yGbBqWAuMrkhyVqJY/QVQJahyNwJGH8U2KWHy
y0I6LKwUUwMEHiGe7UHiUoMKSqSILAXuH2H0LYH0qIrDGVFeVOIMZcLafYJCUOIGU2peVUHkHqrm
YWXg/sZcU4H4U2VOIpDSIQIEfVGorYXycabvGxFcNrDQU+IsH3HUIIVPHkIcUQ/e/gVdF1FiJGUP
IGIfGvH9H+H8qmUwToJTGuJIIYH4U+2gcQcbHnIwJUfUtwGqG0HalOHGGaHEHik6HkHOG7AgV6HO
NeH4HibYGwHKGoJmHYMaHOrcUIfYG8HeHMWYHQHcHoHaYAHWToLAHwLkYWwUaMH0HWHkxeZuIGHW
QglaHUGwTQQoGuG+HVEQH4H0Gsn+GeLirAHW0EHGi4H6G8o+pmiiHGG4JgH4OOHeyKHM96GIGSG8
6oHIGYtaGsXGGsioF2GsGapaWWrfKAqITQXNLMUULGYaWwV+ewHQHi1iHiHOHCpQXOHmHchWFcGU
FwF6GqjiHRCUKSHITYUC9GSuLyHkZ+OOZuQeHioQHtIyVShyGSHEh8qCGoHMGuFWGeFYFsGsF0Ge
HGHCtOp0Zck2HgF8G2v+G+GKtgGiG4HSG2JgH6GGHEHQGgNYjiGkFAGGFSXSKIuaFyGyHKEWGCGs
FOGiG6E0fEGSHGGsIHK8HMFAGcfwHMHaFkGsGuGwHSHQXuHqFegcjKFWG0HWHSMyHeIsH6GKZ1OG
G2GqHIGqVCHqLgHsFuimFyG0hKO8dKGeF0GoF2LYLGUkMCKIKExcuIZAGIkyGWHOGiHvHKncHkkg
HIGUHM/2HZOmd4GeHEGcQyFqqApqIMMCHijQmGHKGuGHOcGko+FoGqZMvi4mHIE6GZM6G3EgG8Gq
HCHYr9NmR6XsMQKcKYIuowJotqtpOqhy/cUarK2icSSuHspsLCUWSQHuLIWmehGoMIH0G6UCJyHq
RSuQMKIGKWSWqgJiU0SxTIIMHArnDMbucQi4IMvrJYItUmH8IsH9UlOqLsTiSGdgI5IW/aehU0LY
H4ueHsqWpQHsrCfYUuM0HoVDHKJiU4qox6oubY/hQXLdLcaMKccWHGo9AwHk1mHsJ4HpQMHhAupv
HLS/WfWhWjWlWnWpWrWtWvWxWzW1W3W5W7W9W/XBXDXFXHXJXLXNXPXRXTXVXWNiICAKZW5kc3Ry
ZWFtCmVuZG9iagoxMyAwIG9iagozNDYyCmVuZG9iagoxNCAwIG9iago8PAovTGVuZ3RoIDE1IDAg
Ugo+PgpzdHJlYW0K////KA7FFisRqOEUtcCLfFHCwu83Y3gfXsa25MJ3kslUvvFihAiNlbBvqmUv
NuKA+KVvMAjoT2euBktxfd460pwsNCE0wrblMmFKYZct4pDSUsDbOhBC6RaNWpRslWYIwpoq9l3g
3I9BJvHZU9RpJicqAWI6Q0tR0ablPTxLRv7lcPVDUdHSk/jEbEuY1nG/AHMiOrdti4kUcMdQuw1P
oX5E5NAVt2MNe9BZFKbL1KY+9uH1ZG1+ed1FyZlTGTvSXSCictcGgFPW2Wh9pTwk4zMF2ZdyWBBQ
ntrq8vMlxFBFZ8MdbkRxRR3ZwsIW5qZJ7IDhX9jxr3fMmmq/vy4QBZbUIwQYlEk2bgz4hfOfzt8f
sD/4ou9wbonaLkkJPk6gE3GkKwbuYXX6Wvrt+snNGnkMExv8g4mFXrfOaPYdCAmOrTWVm5YKlvEE
hOvNUQZHXhliWp3s3/ukrmOay2ukWhjZ77Rw+Uph/s5NzCBTFH5sdtkJY7kFB2doojPURo3tIHyh
kHbs8nW7QEHblFVaAcwzCzDsEDdTedqGTiEUO0GR3dIHysV9hQa/YJoVupvh7aYS2rZJLjAktX5F
ybmGWpdZYmEe3+Ylnke/swJalfABp8q38fjnFa1mWncf4dG2OjMYWRL+frFGPmRImPk4mqECUZL7
OaeooAIfv+Pxdh4ljng4jffp1DZNHM9HVGnpV7t7UvUj+5UlG1QJDcsoMlqhauiYU7zOodie6S0H
0oXCTdi3cdRMlvChoP1tyDDHaZqvAu5s0Y9Fb3hzdkv4OZnR8AqlPaCW3kGTTAnEE3New3VMMEbc
dbZV6Cyg4WU5s1ZDWZPk73Ilg74vR9KipZYX8sZezjsUIyRBxAWn/bj+QRGSJgEFS4TDe8uWHXEs
NWPykzIuqFZS6hpYkhcRkFkjIn8kJ8up60Z1gmPmrplKoS190NXTI8Dte1IFjeNesQbe1S6pfxrv
9JxT20vsJe0Zo73vduCvZFwCaermyJvspnEaT/A0P+TRkr8cf+UJCmVuZHN0cmVhbQplbmRvYmoK
MTUgMCBvYmoKNzY4CmVuZG9iagp4cmVmCjAgMTYKMDAwMDAwMDAwMCA2NTUzNSBmIAowMDAwMDAw
MDEwIDAwMDAwIG4gCjAwMDAwMDAxODUgMDAwMDAgbiAKMDAwMDAwMDIzNCAwMDAwMCBuIAowMDAw
MDAwMjkzIDAwMDAwIG4gCjAwMDAwMDA0OTcgMDAwMDAgbiAKMDAwMDAwMDU4MCAwMDAwMCBuIAow
MDAwMDAwNTk4IDAwMDAwIG4gCjAwMDAwMDA2MzYgMDAwMDAgbiAKMDAwMDAwMDc0NCAwMDAwMCBu
IAowMDAwMDA1NzgzIDAwMDAwIG4gCjAwMDAwMDU4MDQgMDAwMDAgbiAKMDAwMDAwNTg1NSAwMDAw
MCBuIAowMDAwMDA5NDU2IDAwMDAwIG4gCjAwMDAwMDk0NzcgMDAwMDAgbiAKMDAwMDAxMDMwMCAw
MDAwMCBuIAp0cmFpbGVyCjw8Ci9TaXplIDE2Ci9JbmZvIDEgMCBSCi9Sb290IDIgMCBSCj4+CnN0
YXJ0eHJlZgoxMDMyMAolJUVPRgo=
--------------080700050506020003070107--




From kopwasgemyg@wasge.com Thu Jul 12 03:19:56 2007
Return-path: <kopwasgemyg@wasge.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8sxu-0005pT-Go; Thu, 12 Jul 2007 03:19:54 -0400
Received: from abqm83.neoplus.adsl.tpnet.pl ([83.8.80.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I8sxu-000188-3V; Thu, 12 Jul 2007 03:19:54 -0400
Received: from [83.8.80.83] by mx620.now.net.cn; Thu, 12 Jul 2007 07:19:54 -0100
Date:	Thu, 12 Jul 2007 07:19:54 -0100
From:	"Damian Phillips" <kopwasgemyg@wasge.com>
X-Mailer: The Bat! (v2.10.03) Personal
Reply-To: kopwasgemyg@wasge.com
X-Priority: 3 (Normal)
Message-ID: <504901173.03518972773620@wasge.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------75FF84092C42CB"
X-Spam-Score: 2.0 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------75FF84092C42CB
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hello!!! 
Incomparable proposition for you Dear Clients!!!
Only these 5 days for our clients incredible offer!!! 
On all medicinal preparations you require!!!   
Fill in your life with colors of fun!!!  
http://doordraw.hk/ 

Yours truly, 
On-line community of druggists
------------75FF84092C42CB
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hello!!! </em></font><br>
Incomparable proposition for you <font color="#FF0000"><em>Dear Clients!!!</em></font><br>
Only these <font color="#FF0000"><em>5 days</em></font> for our clients incredible offer!!! <br>
On all medicinal preparations you require!!! </strong> <strong><br><br> 
<a href="http://doordraw.hk/" target="_blank"><em>Fill in your life with colors of fun!!! </em></a></strong> 
<p><font color="#D9EDFF">http://doordraw.hk/</font></p> 

<p><strong>Yours truly,<br> 
<em>On-line community of druggists</em></strong></p>

</BODY></HTML>
------------75FF84092C42CB--




From ipfix-bounces@ietf.org Thu Jul 12 16:18:37 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I957R-0001Ch-Ch; Thu, 12 Jul 2007 16:18:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I957M-00012b-VE; Thu, 12 Jul 2007 16:18:28 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I957J-0004AK-Mh; Thu, 12 Jul 2007 16:18:28 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A481B329CC;
	Thu, 12 Jul 2007 20:18:25 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I957J-00072G-IG; Thu, 12 Jul 2007 16:18:25 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I957J-00072G-IG@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 16:18:25 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Internet Architecture Board <iab@iab.org>,
	ipfix chair <ipfix-chairs@tools.ietf.org>,
	ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [IPFIX] Document Action: 'IPFIX Applicability' to Informational 
 RFC 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has approved the following document:

- 'IPFIX Applicability '
   <draft-ietf-ipfix-as-12.txt> as an Informational RFC

This document is the product of the IP Flow Information Export Working 
Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-as-12.txt

Technical Summary
 
    This document describes the applicability of the IP Flow 
    Information Export (IPFIX) protocol for a variety of 
    applications. It shows how applications can use IPFIX, describes 
    the relevant information elements (IEs) and shows opportunities 
    and limitations of the protocol. The document furthermore 
    describes relations of the IPFIX framework to other 
    architectures and frameworks. 
 
Working Group Summary
 
    The document has met strong consensus withing the IPFIX Working Group.


   
Protocol Quality
 
    The document was reviewed by the WG co-chairs, by representatives
from RMON, IPPM, AAA and secdir and for the IESG by Dan Romascanu.

Note to RFC Editor
 
RFC Editor, please make the following changes:

1. In Section 2.1

OLD:

    In order to realize usage-based accounting with IPFIX the flow 
    definition has to be chosen in accordance to the accounting 
    purpose.  

NEW: 

    In order to realize usage-based accounting with IPFIX the flow 
    definition has to be chosen in accordance to the accounting 
    purpose, such as trend analysis, capacity planning, auditing, or
    billing and cost allocation where some loss of data can be tolerated
   (see section 4.2).

2. In Section 2.1.1

OLD: 

    Let's suppose someone has a Service Level Agreement (SLA) in a 
    DiffServ network requiring accounting based on traffic volume. 

NEW: 

    Let's suppose someone needs to monitor the individual flows in a   
    DiffServ network in order to compare traffic amount trend with the
    terms outlined in a Service Level Agreement (SLA).


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 12 16:18:39 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I957R-0001Ch-Ch; Thu, 12 Jul 2007 16:18:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I957M-00012b-VE; Thu, 12 Jul 2007 16:18:28 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I957J-0004AK-Mh; Thu, 12 Jul 2007 16:18:28 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A481B329CC;
	Thu, 12 Jul 2007 20:18:25 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I957J-00072G-IG; Thu, 12 Jul 2007 16:18:25 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I957J-00072G-IG@stiedprstage1.ietf.org>
Date: Thu, 12 Jul 2007 16:18:25 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Internet Architecture Board <iab@iab.org>,
	ipfix chair <ipfix-chairs@tools.ietf.org>,
	ipfix mailing list <ipfix@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [IPFIX] Document Action: 'IPFIX Applicability' to Informational 
 RFC 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IESG has approved the following document:

- 'IPFIX Applicability '
   <draft-ietf-ipfix-as-12.txt> as an Informational RFC

This document is the product of the IP Flow Information Export Working 
Group. 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-as-12.txt

Technical Summary
 
    This document describes the applicability of the IP Flow 
    Information Export (IPFIX) protocol for a variety of 
    applications. It shows how applications can use IPFIX, describes 
    the relevant information elements (IEs) and shows opportunities 
    and limitations of the protocol. The document furthermore 
    describes relations of the IPFIX framework to other 
    architectures and frameworks. 
 
Working Group Summary
 
    The document has met strong consensus withing the IPFIX Working Group.


   
Protocol Quality
 
    The document was reviewed by the WG co-chairs, by representatives
from RMON, IPPM, AAA and secdir and for the IESG by Dan Romascanu.

Note to RFC Editor
 
RFC Editor, please make the following changes:

1. In Section 2.1

OLD:

    In order to realize usage-based accounting with IPFIX the flow 
    definition has to be chosen in accordance to the accounting 
    purpose.  

NEW: 

    In order to realize usage-based accounting with IPFIX the flow 
    definition has to be chosen in accordance to the accounting 
    purpose, such as trend analysis, capacity planning, auditing, or
    billing and cost allocation where some loss of data can be tolerated
   (see section 4.2).

2. In Section 2.1.1

OLD: 

    Let's suppose someone has a Service Level Agreement (SLA) in a 
    DiffServ network requiring accounting based on traffic volume. 

NEW: 

    Let's suppose someone needs to monitor the individual flows in a   
    DiffServ network in order to compare traffic amount trend with the
    terms outlined in a Service Level Agreement (SLA).


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From cxp@nc.rr.com Thu Jul 12 22:17:05 2007
Return-path: <cxp@nc.rr.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9AiP-0004ps-NV
	for ipfix-archive@lists.ietf.org; Thu, 12 Jul 2007 22:17:05 -0400
Received: from 117.249.189.72.cfl.res.rr.com ([72.189.249.117])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I9AiJ-0005LE-2W
	for ipfix-archive@lists.ietf.org; Thu, 12 Jul 2007 22:17:05 -0400
Received: (qmail 10405 invoked from network); Thu, 12 Jul 2007 22:16:52 -0400
Received: from unknown (HELO pqpqo) (31.50.37.28)
	by 117.249.189.72.cfl.res.rr.com with SMTP; Thu, 12 Jul 2007 22:16:52 -0400
Message-ID: <4696E094.5040701@nc.rr.com>
Date: Thu, 12 Jul 2007 22:16:52 -0400
From: Job L. Rocha <cxp@nc.rr.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Fwd: advertisement.pdf
Content-Type: multipart/mixed;
 boundary="------------050007060601030400000301"
X-Spam-Score: 4.9 (++++)
X-Scan-Signature: a0ecb232550b38fd41a3cf6a312fbabc

--------------050007060601030400000301
Content-Type: text/plain; charset=iso-8859-2; format=flowed
Content-Transfer-Encoding: 7bit



--------------050007060601030400000301
Content-Type: application/pdf;
 name="advertisement.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="advertisement.pdf"

JVBERi0xLjMgCjEgMCBvYmoKPDwKPj4KZW5kb2JqCjIgMCBvYmoKPDwKL1R5cGUgL0NhdGFsb2cK
L1BhZ2VzIDMgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8Ci9UeXBlIC9QYWdlcwovS2lkcyBbIDQg
MCBSIF0KL0NvdW50IDEKPj4KZW5kb2JqCjQgMCBvYmoKPDwKL1R5cGUgL1BhZ2UKL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzIDw8Ci9Gb250IDw8IC9GMCA4IDAgUiA+PgovWE9iamVjdCA8PCAvSW0w
IDkgMCBSID4+Ci9Qcm9jU2V0IDcgMCBSID4+Ci9NZWRpYUJveCBbMCAwIDYwOCAxNDhdCi9Dcm9w
Qm94IFswIDAgNjA4IDE0OF0KL0NvbnRlbnRzIDUgMCBSCi9UaHVtYiAxMiAwIFIKPj4KZW5kb2Jq
CjUgMCBvYmoKPDwKL0xlbmd0aCA2IDAgUgo+PgpzdHJlYW0KcQo2MDggMCAwIDE0OCAwIDAgY20K
L0ltMCBEbwpRCmVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagozMQplbmRvYmoKNyAwIG9iagpbIC9Q
REYgL1RleHQgL0ltYWdlSSBdCmVuZG9iago4IDAgb2JqCjw8Ci9UeXBlIC9Gb250Ci9TdWJ0eXBl
IC9UeXBlMQovTmFtZSAvRjAKL0Jhc2VGb250IC9IZWx2ZXRpY2EKL0VuY29kaW5nIC9NYWNSb21h
bkVuY29kaW5nCj4+CmVuZG9iago5IDAgb2JqCjw8Ci9UeXBlIC9YT2JqZWN0Ci9TdWJ0eXBlIC9J
bWFnZQovTmFtZSAvSW0wCi9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDYwOAovSGVpZ2h0
IDE0OAovQ29sb3JTcGFjZSAxMSAwIFIKL0JpdHNQZXJDb21wb25lbnQgOAovTGVuZ3RoIDEwIDAg
Ugo+PgpzdHJlYW0KgAAgUDgkFg0HhEJhULhkNh0PiERiUTikVi0XjEZjUbjkdj0fkEhkUjkklk0n
lEplUrlktl0vmExmUzmk1m03nE5nU7nk9n0/oFBoVDolFo1HpFJpVLplNp1PqFRqVTqlVq1XrFZr
Vbrldr1fsFhsVjslls1ntFptVrtltt1vuFxuVzul1u13vE0RTpBYsNUTVLRgYsbUISBuaQ8QaQSE
mLA3vMJxmRjwPI4LhuKxiiiy/PMKZQDZWPRU7aTSuZVzkCVl/ch1OpFPItFsDaQ+LZ4z4AdKpgas
acIC2NlTCKsR2+5PLaT7piIeI6/SBbmgtBDaA3JhysVEI6VwZJyOsENBvkAPQcMUYegZbGkVX4Eh
SVAcDURHjPohK1C0UUbULkNTjoUPJVIEYR7IGNRKN4GQcoEQZWOEbqVgGv6JlFC6JFGB6BEg4Kbm
kwSGl/CSDhkX6fm0dIZJeIQVoIPENI6aL8IWZxRo0Vg7IUIBKoGKpapISz+omNwVLmSsBoQFbCoE
UBhIMYxkMCAAZMwg7+IcHITCMEIdi0hQQiaITxNWAA0AMJxlA5H4AL2BYQxmhILDQijEIGSD3oUL
TEGk9KBDyFhwzGAEzDUDhBzsgU2iqCzSoaYUADQPJKSm3yDRKhAeE0gxliabUuIFME/UAjQhHIht
KgBKiKhoZKLzKgdEzTNaBUcgU4oY086t2gRow6hbDoOJxNU/JwAS/PsAG0Sg80EcKFTVIFHr5OQh
IHJoWlUIoAUkgVKIGwNgoOFkhInPq6FBIIjjSgpavGgZQWQgY8kKAFx1MgpWP4WUcvbRYADyZRUh
MKaBEsA6BAeDQ6GW3Y7BTC5ROOXwEIE+g6ABIKBjtOaDmjEyBBlfKF38gTvoG2WCBMgQQksgeGAB
h6B4k8ONggAAETs+iBlrGyFXm8hl5HTEIgQHgZDAhAPRahODYRhQAZkgQ7AhiI1VghI6XXn8FWwh
ZWYDkiNZYKd4oZrKCYsgt1oENMTVReAEV8go0aIgUqoZf2mxTNEooFggAbOgb/6oPOrIU8uMlAgV
2oENVsXggYW3nBIAbEgm9IHpRWCKIsTb5FFwGEdOVoLhK8HTUzXoNKB7Gk1ZKC6gQcsshBUHqhBp
zsdIUgBUKBh33SC2cABwx4gQYs5q6BkqZVbr2h/YoGLt78dfSDAsNwfP0gY3ud2uWjqHaDVXqoij
UOQAFELAADsF4ACd546DwKtIISVRlyhju66mjYXzSSEPdIM74c6oWWgAeGQZ4z71ukCfa1d+IAHn
kDek2INRr3iEHFE8kAAhWgIRgCDJFoRXcgWe2QMaaH2ajnSAvEKqAANP+fSQR5pBH6kCdWQN1oAA
6K+QQ7EOyvgjoPIgIM4LvHwApgOAAEwVXyD1hiA5pzAmtEIBex96RBA6wbf0/x9kHgARFbWDw1kJ
gAQoIHEhcB5gARNeFBsusW3IkLGk7p84AFgEIG0CEhINA1BOcCDyIyXyBGnEGs0z4ckYECPEABRB
AxZvQgsXwhppyBiUCazGKpBzhvYQUE4QY4RlSEAAAGPxBVmrZiGAEAAdTOAcj8G8WZExQAGIEPVg
Kv1yBOaAQUNwDiCyBIHKZZL5Xim7BW8mR7LgYuBDyu4gicldwbCbNIB7TpfEDj6h4NyeTiAAlGQc
IrgJEkFiGQSSJBJokCi2ABVBBgiuNlywENKmCHhHPSnogwOW/G2QAwJtBBwQzPIKo8gsPQALbABL
eTBBJ7zTkE1Uwp/DDgOn0QKQBCJDFyZ6QIWpzgUQPIUiKSDeAAA5RGQYOh3TvHlUCJUB4FwaLxDy
5eHzRAYs5IEEJaIWKeDJDej8OgviBiaBQQx2BA2aK/l+QYWqFGRt+pgQWmpA6lsNIG1cVhnBwpCA
gnaoRAxfJLIWBpwDISC0qIG0ghDJzyRuDzTIgT5CDjLFFTsgdPha1ADRBMgVRUl0jV2yENTD3ro1
IFW6wNLiCspN5SSaZuxFAanQyIAFQCBVjAGxoAFIWvkGBbZYACImRCFk6Qgeq5wANNAAJCf5smpg
XIGCGm6AGHJnIPX8gzHCCBCoMwJA1aKlkEtQQQFDFzWMatWQcX8uzIv0DwZAAAC7ML1QMQKpa4XH
RGIM54Vg9YUTfpAY0NRhQUv+fe4AGQoDPh1fWre+IWA1B2GKGqNz9QbzvIUgheqDHarkIPeIgQPo
zQQQ0cujQgQdh2cBQ0PJsH13hIJfRyFQxlWeIQKJgL+5D26jHEa6w8jhPcMULW8w2gNXpScDQQLr
r1BVvjOqNwALpq5uuQe4oABKYamzdYgjniDiDtZiqCykMGkCioQUFd176X2IHhm6cWw0MfZm696i
lQ6BWjIQq8T2wfJ5QzkadwisXTIGlFS91AyDX1INjehMsA0YajAoHHuXMRImAeNNCWFMC4HEhiAg
eLjKDPAWx5VDaDaTzlwRkI7S3IBOH5gAgoRQ3jSPRhokMt21igDpRFMVFgw1WkDpMlYohljaNoQt
caV8ckbDoOEUV8KQSucgtEAAbw3jKnaQLQ1PVUkHOzWSejmyCDTjEQPR5BNJCUGViRl0qdMH2vgC
tcxEmPFtusG8B+e2XaiTydQyhOXTbjJ2Ee0gAAYgcghXx9xCxNAsyqQm/zkJ/0qU4CwgY8ZUkDHG
Co9AvxnELB2CEZRp6n7m4VwvhhCwZDJ1lmwkoVp8ZA4bxfjHGSnz3WA9njXH+Qch5FyPknJeTcn5
RynlXK+Wct5dy/mHMeZcz5pzXm3N+cc551zvnnPefc/6B0HoXQ+idF6N0fpHSeldL6Z03p3T+odR
IOAienPgPaa5UMqozjm4YO3UCGIaBbs9SJgBYeQHAVpFfgRoOy9CSg5iuVgcaRSOjSxqQYeMjQAA
63STgYoIUm3qJgDTGZCUfEDBvP8NGD1A9j7sKjtvZCUCAnCHU44aN+kXGTlYjQwhKioGmHjzwAPQ
k/FEHgMAYJwkU8oR8A1OCDAy621N/BN542BNqR71RFLnkMlotQhIRcNAQ0bJDEmn6yI8B5gLyRFw
5VmIEBDvRCwhd/DtD+RwEB7BvGE1oOghRnhHacHYBAZQdAy6wRILCUaukHEgHj6Rq8msY8YSYM2/
bIET+eQwYQvn7NxEdnIu/vGgWg5PtCEgZB5IHvzCdI6iRgwJ/iCBhPiiEBakQCEhWAcEYvoLaoxQ
DKWHrgAQFCBQGPmiMQPiCh7GrhQAnAgGRjVBfnwp4ByBiiBBtECvcu7C/h5IqgHn3AVgQknANJKB
RAaP7hwwLkxDVnQAHhkhRG/AIBxiBg0KwHkvDoIPFGwCPQjPNQnvCKeCHQnrqt5CBO/kmiBQCv6i
CQfO8ngEOwhoIE9iQhaqcQWiEg0QtCQhptICCg8w1AAQmQnQIiDg7OqlbwnpLCBQaCCwCvYhlArC
BAsB4wbPmQTCKAIAqtAnAAqg1JGwrpippA1AjGVBhBVOxh7EohhIqgcjjgEIPBfmNBtFghLABCGh
ZrHBKg7FIBakUxMHKDOROiBRPlcGqi/gYpUxSvoh7RUGtBQBCg0xWRKp1LWCCAcqMANIxPQPREfh
FA8GUA0QwCEj6P/FcG4CBxjg7KSK9CERWGdA7BWDzRYGFkNAivUjpojRsEEPGPPRdRvAALnxMNAo
IElh0wXCENsiCxTKdvYCKx6iDR8xUJakDk3A8A6xqCDv5iERzRRCDyFxUGRxnF3AqlyNuRLCNg8N
2H2iBgcJBP+gaAqvzlwENACIfxTjzBkvZgjkOwRiBSYtnqQPMiEBhR9sNBREhBkorgOE7LNAASWN
BrBk7PqrAr1PuqGvvxItoCEA8BavALlDpoVFFhhFkBhA6BWR/PSO4iDynKNDjgZFTPqgQj5Q0PCi
CydCBAig7KjSYwRN3rFtIAtgcgcqcShoIS+g8FFhpmtP3k0EzhUQNCEAULoPsRlCMAVrlCCneCDP
1wptBCDA7LHCCy3TIvfEohfHGoQQfKyAyyTCNEMzGF5QWpKH2FIHMmXAVzJvFkEm1G3j8AsPZgHl
IRZAsQ5N6P6g1MHnlgAPCEFDPzXKGqJsbEBi+EJPbzbiBBwzcg3wdoqgfS+iFhwmlgthIAdNMAHo
HhhA3hQB6kMhhAimAhpziCDwWEDn7E3wZFUQBrhNcCDg0mgABEeTgRKCCTwCCturJAAT1zjz3ELz
4Q+lFg5RCiEuLFssNPFiMAXz9w10Dn2ENA1LgiE0IMosHk4NXwUybtoT+swmqyszWCIxeMxAABVL
WQMwrhFAAqpAUIPOwFvRTBpg1HLhkxVSrgABAJejBA6TZCFhfL1AHsHhkl4t1xMkzgqvpUaILUbh
QB+KkyOH3mNRTCBgynoRVCBgchACHAVk7AwQpCDB7D6iCBKm8SLRBy1EfABhfDShuuqyOOwA6RSu
xiDPwK2keAnERhlF6U0CD0lsHs/F3050ZUqSMiD0tRz0+IVEZ0xiIhLPp0yPZiBh6lghlzdiF1I0
7UbEKUtGPAjRjkDxTzV0giBhnojRXUWj4FXghGDmBGAg7LLH5hhF1rqCQBlKZAsSziDgHroH2S+1
RCKAihHk0GwAQxakCnIPtgAABysgj0VCDq6TbAAAwLWHbEDsHyVFnmswxCUstiByeTgBQVhFyPAC
CAdJhFGHABtGRFnwsCFIbiEBHzIghFsVolsw5AB1rpOgsQFSgiCB62EqUlgzCTChhVyiRECgVqN1
rU3AAMuCBSeVaCkBFOqgsTOnah5Q/Shk3CMBlVFqXQ8ByAXgQlujaA0A8PX1rMHz+iFThBRGYGUT
xAdJ8FvPPANUSieBLNk2fAc2SCCWhPRTZA6wk0OEFS0iGWXg6NViCABv6zu1OiDWdA7AVwINxKU2
SQ/iWA32MPkTu2OilgwUkRZCWVSgAu6OZAaBhKvzvCPVY21W9W92+W+2/W/uFUn3AXB29g0AsAY0
XiBO5vOCCFHDYksCCQz3CXJucNeVlgODjgp0WCDBUSzhUKkwO0N3KXRuXhhXLIVIrgq2tocLHVmo
eO/y5XSXZOYBKg83DJ3Q5Bx3GKrIHo6z83Z3gOWhlVQlYAdQLhx1cCFrfUcnlWGXg3nuSMMt5yYC
Bgp01mtg8kNBHkTRF3oXvOSB6ho3TDdhkqVghXr1jOsBUE4nI2W3v33uRTNkgAdN1N2HORRmO3ki
D0uX4X+uSH7ziAsBQT6mqg6gHg6FnQ81n3/YGOVYBYG4IYI4JYJ4KYK4LYL4MYM4NYN4OYO4PYP4
QYQ4RYR4SYS4TYT4UYU4VYV4WYW4XYX4YYY4ZYZ4aCQgOWyYaiuAUi+3biLBhKVizgjAIApgTO3C
xwUHIW7iOgNPMSzP0un4hzMU5iEgsX9UL3RCYXNBKg1AsA0NkiBgLG0YqiLA6YlCxgtg9XqkLhfQ
9gZKut33sjwi/hkwwBtYcRDihY6CUHPiBgNXVue4/CLY2CWplieYuiEDVCN5Ai0BB30KODOBlTZA
IBfTlmF4jCOVVANAirACJXkA8hwvBWo5J5Kmp47NjhogphKgBJUhRYdt5QOCFAYt0g6LSBhA7B6h
plkB5BeD0X0Ap5Pg81iiEZKCLZXgbwaiJZaCG5Gw+0MiCZIiaZlCGhx4hUB5ghfgZQZCEA5YbiCB
AAsABAUBp4gCDgq1gCBBVVNiKZdiG5sgQhRB7Ukt6UzCEBYZziBwzAYvcngAPAIAOX7AAZNAXgWZ
pCzgZWwiEB0qXPRtjxwCBAp5LmOhAtbCBgsA3JUYvwJQtVVofS+hap6A0BWAnIqaEF6kogwaFBpg
qkohzqeAITMpuWTnMB4ryA7aJkikdiIhyGAgILLAsS+hQEE6Qj2ryA3XrhhEQPQaVhKoXPo2niEA
3B5A6abCBhUGRJUHlRTAXtLCQA1ZQiDaXxwQwBKghYux3iB6p6biIgW37admXae4y4zJgZ6aTCHg
IRw6ylF6aCFaLSEhVatg3yGCIaRJh6javCB6UaF6ZCDhtbFiDW4g0arCBaLxzkDatlZko63Fk6ei
1AZBIBx1/iDBpoqzjiC5KY9Aq5yTPKBzRmXaMlGAIAhQnDYKyH3AioNz2rlbPKeg3Ap6vDP7RmnT
jteKyTiBol6AUGRAUg7A6rqV+iI7ZNZg6t3hfL6bbhpsST2iDghbe7f7dBWF47iDw7TxwiFbmS71
nJ0KDU0BtB7EL7YiB7ptNbrh5KcBeIBCB7ulnzLpX7SrNsZ67wbBhN37ko9Ssgb2RA7AYhw50lFp
17ZaK4njDZHV8CHY9CB8Bjf7VCBzIgqooJU8GJG73K97ZuJCC7c77kW7QTmCBbRkFY77U5TCG7n8
PA6uwcFgAb2b3Z/p4IrgscJCzAhKzZgphwbgWkEhhRvZuA1YrCDACSgmxZYCCgObywJAHkZwVGYm
lg3QtDZsbJ/gArzogVigpsBACIPA6D5Z7Bp4sCFRRTk4+w1csiDchEToqwb1xCG5xho80pU82CDV
4LNgH7AvokZ8rmYkNb2iB5eCChx8pcwqsMH5uZLCB8zlf80iFvAKDBkkO853+dDiHU1Q+59iGZSH
gENA7ansgroZ9HvnLgIENYDCF19gABxryGNjdg8ZsCBdICGBtXdmVDMA0QOBVWpdP9gCx0qF66vp
IBtcZYb65a0aMg1BxtgiEBVaAJYQJafiCRUFFhpF3dHXFbDhhLWPLAeE3dnPGYxwpoPBta0iKhhF
sdtFcsHh5EhSPpDppdlFAjd6UJi906IiCA7N+6piBBuqSdqFknkxTAqhtI3ZumY4gYu3Nn5KA3FZ
Hb4klrzxz37aId2ocaqKOIPBVDj9CFvQtAH8NyNaS7DrPw+DvUP7GmO3nDWNkgVrg+H16NEhRRpQ
JJdgt3r3dEDha6UbwCHeZiD+DS7juyEH3kYUvrtEDd5IIeVC0hfBeN/GwAp47mBLzsH+IiEhtHfm
Vb0mN8TFZgOX2iCBQafd7RUS8+s3FchXkEo8iDWBYHgXLcZBk4b8yknAsKSbjlk7mhRKScPCGe1I
IFkK0P1sa+4esLfgq+6oVIqgsEneOCFgi3Qbj+yH2Vm7WlkgBcFhVA5fLlGaAHgX6CCtuVi/I3G+
M+8F6kNFX6HlyfAvSKVgQ+0cbRa0Yn1htD2AAfFQbfVq0CE+sGk7PwJFn5hJVSXe+9KS73QV+fqC
BfR6KknceCH98mRpw3kFA/nCD/a/pCDgU/d8EQp8at+/S/L/hJIFUBRBtfVi0Qilnuxt6iCW8odA
nAnQ+CAOQ6gCCQWCmp5E57KoWwc8vVIKODROKQY3jqClVawRWHaKxVRAiCs8cx+TRWFwVomoARBR
tKTgBIJCCniWTGcQU8tqVEeCE4nRyBx8pliEQqcwQDNoZL+CPaaTWbgAIFiCmlWQUAqKJtphQQfV
yRyWC0AwL+swRahaC02CUeUx9pA8NPZ7Aa2sKoJApweLmik4HBUk1HmCS8AXW204AVCDniYnabqI
aAA8wyvQWQ0k6wK14PQaHRaPSaWkgNhNJIKJhMuCKlojojmAAEAeVoY6bdQQFizd6IIKo8jkTQV6
m7f8najwwNPlU8BgBfr9fAYfN0AFUIDI0Grb41ADdfumCAghZ4VwYeaiYQRlk4rbCMc+CNL2/T8Y
FhATjzjrhM7ScvMgSTtW/MDwRBMFQW/KsQZB8IN+u8IwUxEKQvDEMw1DcOQ7D0PxBELSojEUSxNE
8URTERUhyB7ZxVGEYxlGcNhwD0aNGVQ1LJHEepOdJnratKzo+DwZR80iFFVJCJlHG8fAfI8HkUr8
VG0oMMAQwzRhYzo6lqbpZIIGQwKip8lge4smIMCy2IqbQywSHUpNAbTyIo5ksjUN5KmEq0OjKqc1
mcHyCGmKrnggUCJixRDdxcgs8pwNVBJiUB7IM6jAznDA1J4nNLueNA6NIaZ6ooHwHgBQ6CTggs0w
eBZWDQ86hjoFpVCKUEqgAPA8joJ070gABtJ8pI0SxBlaIEUQipjYE32MiZIDc+8DmEICJkVO6cPs
0dqGlF6y0wiY0BCLVqoMexhG0C7GI+IBlAgaNHI+Itb1zRaa1/YIAGjFwwFZT6KWoj57AgnYcmi3
95opZY6rEpN/tAKtKm1hQq3Mk93MCURFJBZzk3BcQ1WRg8t3pcwtNCNFsXkk+IXvXDQrRabkIILd
EWQguLweNIUI8AAYzcYUlgAvQAB9NwAE/IJou+adkgAIoWI2ipk14/BogC7CCMkIyCDrUiTGXgaD
ais4WZCghZIkghxjVrBeXIAATCmWAdh20Rk2ygxu240Gm4U76czIgphF4ie7oLCzUoKX+P6vvt/a
5bg1bAAGxSqQesoLwWn0NZIi6pMExSM2iC7mhu6r7t6XgfziTFqLAIIMSoBixreu6AgoLKHshtc+
jmopwMG4bkgpUzVvL69ggymkUAZpaMj/dHTn868/wiKzAtrabjKoWkqiYdnGAC5kGifIekVWrF85
yCdwk/fIoexpaVSqKbT0bfTCgrxgANYIKJUVKDx0gLIKgRYiWyCjSC2QUN55AdKqAAKweRExWKnU
iINnKlCCMIYu8tdAKhpOoaOu1TROAqg3IKCgwBBBRQvI+qMisFjvisbGAACzNwAQdIIGV2r5GVmg
O6QaFa2wFgoJOrtawdA3qvWkRVNq1QePpLfE8iYVRAt6IMqEgjHCKndT4MJegAFtgAhcZqGQy19Q
9BoqOCIRz5wVguqstI9U2kEiqRZOJBDiEEB3EOEpMRRJ/gG52NCtCcxvIIOmORBYLQYjxDsgrOSK
M9IpINnkYA8mAdpFcjMLCJrMINGw1J94nLCiiROPBFGKkFYQAA4kWpAn1hNF+FIaCxCgiKThiBE1
dkFkYSY5j8IMx5IJBwAEHiCE7SmM8tIQgAkECLAw+qhSCB0BwQRf4Ry0kGDpN8MIDmcSvbmQVhUg
ADkESiY0vBBBFR1JOA9eorJvy/JMr6Gs3xWCod6mYMEDyCTnAADxhQAYtmhARDIggVWIqWneQWbT
gCPisasAABy0pmEUi3OtMYviCjxXeROhZFRFTQIMzEggLWQv3okDgdMBSOFpZqWpN1GSDBqcTHos
lCXzwUJNPggosxlQzmkTELZkJG0ygrN8AAqIciQDCQSgJFBlPbgbUBo48SCjKMMKIm4aIsAAnoRU
ALvwWurfPNhX5KqtQYovJVerB6rkFp8XMidIidO/ABWIWZMazkTV1JWpROZwmfIIi+V8H6ioMFqO
kQbQCpw0XUfdssfhoriIM6MgrbSChuJYAZuY54CPLEtJldhgTUEFsiQUGNcSKAWKmSSqk36agAe6
mNd9ogAWkIK3g0L7yJjCXqTEDUiAAJAR4RUItpwANtSfMuhgAHlEFEs+asgGmeJ0IncJ+J0bcWQI
Na9UZlyCv2Le2VID/0hrvEs1ZJxBg0URgIQUHd1wVE4HDbAID4yDXiIIEY3JJmlEFvXbWwVzSJlu
Inb4ikJCDWpIIMqors1DDJILasimAidPUvRMs11mCTYKMOjcX8PLR3+bvFzCBBimVdHCACT5BL+k
nw4AAOhhgW3aLA0snDo73kFSMW8wFBEGA3cjKxtcDTVB4oYxMikOCCsFIITOALUq7RcIouwC5OQB
2NuTAggkCp8qjCckGxOYgAMBxxRYCzBY9kEGSUGWLdYtGhO2RMZUhiY2DJrDI2BJ83LgynQ+PyAK
fTJUuusk53BhBvsaFiFkB4E18IMfYSGTlgZoAAEfMS4rDkEXSZrDEzVP53KSHLS2j8Jp/gOCwNQQ
iYmqmzmcgunoa2IoLFYUWpc6kT1GU/CQedZT4O5hmxsZyCHnZ5WpxyvdAMLJNoNm4g0zBOnIwnRG
olrQnIKEIORBHaaOJwQIerIVcwNTMRUFjA8pGf2CADXuWEFUOPoEctAqAilZzfYkX5NAaFTrqAAW
AIcFzywYR9PgAzUXFNK87fyRVpcBsZQZxYAADtuJzRt+KVQjhpJOC0kRBlfPBooTnfAkAt8UPzho
ACDgAbMNLvifu+y1kRA9KsivBRLcZJMARuOqtpEE4XeA0APqkk7E/dRf4gxWPwtvrrlNAiPgh566
8t4eRhFNAIQTVRb+R8d3sQfWU1IGDanfUnA1TDk9W4zXiZqvG4m75F2jbpFRpg85oQXm6HQ1cOQO
N0Zwo0omMrEDwIo5yM6WMSHkZYeWgprABfcN1+SYgrkKBAX1hQAAD7/bCcBlwWzB8lMuaaGUAWf8
siUtGQEEeYdp5sk3Tju2Bxx6KNvpfde795ICIfvfgEfBMEYEMtfg/H+R8n5Xy/mfN+d8/6H0fpfT
vtBoAAMseEnAgHYF4at6fLW3076n4/yJIFqCsbTM/yn0+LA2KxJqwQQr/84KqbgF8GN2Ee7n6/1g
08YNKseE0+iFqheIYIMGiqc/KDon8NADqy0GkySI+wsMCCEwGQSF+rEHSZCAeAu/8B2BCS2EUA0D
oGWK4+2IKv2JMF88AaE9AME70WOrGmE/+OUvIxzAMNGFQ+sQ2GUDoDwyQ5ONEVkHkA8AefgJaimm
wQi2UQ+0SPwqEFUxCIqCsCORaBkzUtih2B8zimWG0A0BSmsRkFYyWtYFqNWKmJ2EUEUBoECganIJ
Ol0IrB7B/AiDUHIQVDMILC+IoB2I8GlDecyDqDkPS68umnA84N2gtCKGnASIo/iW0MqIqDzBoNAz
IKSRaXtEaQwq85A+uzQ1ilI/S0vCUIqVknYOcDo/wAAnGyq5W+8H4IIHkB1CON+FE/2MCFADoDSN
greIMBC5vFYQ4gVFEKUpcIJFym5F6IM7606No5WIKEoGVFks3BkQ0X/CuLTCMDtFSoupwII4oH4E
oIJFm9OAADe7uIm6+Im0gM0SkMkVq0MOUTKJOAC/xHOInEFEIAC3DDkDyDSocTpFAIMrSV0AMPuF
9FzF2IMFZGqI+5U4CCdFhHHFoPw5kmBIMB8DrEMI/G2JNGeIJGiQQdu74PIBYhkAsvKsqJOE0N8n
BB0TAHGvyEGMYBjBkGipGfOXCA0xiaEA4BCHqFE7KKoDsBCb4iNBcImBac4w+DUMYBkR4BYF8DKG
iq4qeHqasBUqAF/JrA0ceCq0sCPJ2DQatJ/KDJ4MEACaGsovOPuF+bGnSJNKuVefSGdK2gi8SEq6
GAABCzBLEFrAsI+b4duVII0IKiLLVBvLZAQKnKeILKiIIHjFUILKzJnLqNzK6IIF+XqGVHQIMCEx
idpKINrMGDxMKIIl6UnLcEKSkB5JZKlL0IpJmJNM0q627L/J83lKEIoAGhypzHKIJBwvQFZMZKgp
AJzLqIpJvK/A+1vJ3F9KBM+ovKKv7N4IqDVN+wiXJOGIJNWuXNfMibHJhKyIJOQmo8UQPHYyqY+V
kYehiVI3S2eI/CuIm30Twis5ZFjAiHCV4GSxjHyIJH2y2rGCq3WW6JgDROMPiTGzVCMamm+1GysI
IA1CkEUuKGkuiFFP+69EoI+5lLWaOWtFzQU0EouGkNvQiJ0gvQrL3J4yGbDH4IqDsGKcOUWEhPWL
SlIMsSW9Ir7QS7YVfIoAA3iVa+zDVBQuQINQCzkI81YhrI3EchlQUSizEAfGUtYJnPwAAHlAjRAS
MwxQyAABXF/OwIMGUuQkUIMvMXLIQIpFMJzRQILS2ciBDLOBk1KIJTEasl+GSaDPSYdHgmAuRRGA
BTdCNAY0vROTNQmQQT4IyK45gM1HErSmWoiIq4gIKGnUO36+uTK6oIIGEnkaEiCxkNyDqd+FE9OF
EAgHCBCrEJrBZKSBaO7IMPLIQhydgnsDeAeY+qgymqmzXQKIKEU85HOAeCwBiBWIGDkDRB2ME1jG
g7koiAROMJxFSIKDCRvHmIIBwH460jMMgEDAtWNMAI/VYrEEqGUMmBlE65jTuGEIbVmfuDq5HF1U
tS4JlV+JkgeDUm2aPS2MFVQhhVWr6rHNKkg8iJPIyok5AyhHNSsIo5ZW8JNWPWTNPKAJNXRRiUrX
eI/VsIM/ErJXuINW0winlXCVez5WWtcMrYHHMv8IoMkhmfyxxXZZAjMfhF+zfWxWALfW4QQDUcmB
oUQBxAFU+aGXuMuFUBi6MIqsyIoBDAWEsTcBUqwIKHObNKKnQwxLGOMUQHCaWBCKmFBEiJMxywyU
wCrYQm451agIKG6uxNlaapHM46qHqXqxmJiZaIIAsyXaWwjNU51JcILJjMzLqGSieBTavOUDrMkg
CHDSeg/bUoaFrX6aOGEwHbNaUIqDoEK1vaLKmmzUPJiiqXegjcSG06HayJiCrM+AsxnaAdu9zJZa
MJMGkXrc4lk6HKkKSF+wwHSBSJiBzP6hlJ+JMxqIpJMInbM0vdvc6IKE0BRd2JPbjcOIJauILcYg
auWBiA42/J4+3bCJNeSIrc0IpdwsTaKX8q5AXcG8sF/cMgiQuDSVkDUv8WbOBLONMXC2soEG0DTG
jX/L3RmKeVUHCYjF+ABHUDkBDgGaPEQIoXuIIHCDkneHrQRGQX8qBV0VXUOG6KiCO/eU9TjAicQI
LP7TALUmmYgDVRg2nfqDUrQFVgnVpgsKvR+NFJCjNHKF4PvgMJNhYggqLYM4+LeErhhfuABhkga+
tF1F4INSrUyRBfpZeIqW9GOVI0CI5Ias+PvGff9afgaHsAfP6ILTEME4/imILgiImGlgtTYNFf5b
JhyABHqgaboczRhQDEeJPTcIpiUIpgwrISlV0VVV6ABg8h4IObM+A8GynU8o4rEFaSqDlAsDsg0B
iFEO0Y04W83VgmyDyVwDkdqGk6GFBecgm6c7CJMKa5UheG+61V3bIDfkkHsT+DqBiDlksM1k8NEB
oAQFBlMQTloCxhaIqAgXNVcAHWpiIDsuQFVlEw++TlJl8X1IUI5lUIoSdlYLeHTleGFV2IIEDkiK
/mIILlyRplfBnYJmGbDAtKCobmPVaI/UgJxmplNE7VwAQB4godHKuAsGcABRcr7Zm94HHRNbiRKG
kFEDsHlFu/4Q2jTofokQWBWouEDoIQfdIEhSDono6/GFZcbo9pEN/hXVZpHpPpRpTpVpW+CDoCtp
ZphpjplpnppprptpvpwQ2F8BlN6ABNcAeU4IJKuDMHqVTpzqPqRqSRKJCk6rBTuABTNNLHjjVBvg
mu69y+vTcEUUWnCIIEtqnqVrDrFrGQOC2OcBaK4DVJ5UaoaLYKxmaEqwwDsEoU/lEINl+wW/eGiS
PB6IIG6udrJsDsFsGNKGiLYk6xkiC+8lCIJdmaOBiBCAEIKBbhaDtWoIIDSWlqAIIErksx9sJtBt
DtEIoCEJoDUIbEeDrYKUcGfCwBe8jj+UMumGeToHkVUFAzBtHt1t3tADkUQBoK/kyIJdUAA9k07X
YaFFUFUaMHsA8DoDtrwNfXYAQSwDoGUdJZHJxt5u3u5pjrtjKaW+6v7e7MyH0IMHJgbTUMGB0+yl
afOAuAXKRu7vnvppuAtcCNMEVusDooeDwlvvrwBwDwFwHwJwLwNwPwRwTwVwXwZwbwdwfwhwjwlw
nwpwrwtwvwxwzw1w3w5w7w9w/xBxDxFxHxJxLxNxPxRxTxVxXxZxbxdxfxhxjxlxnxpxrxtxvxxx
zx1x3x5x7x9x/yByDyFyHyJyLyNwOICACmVuZHN0cmVhbQplbmRvYmoKMTAgMCBvYmoKMTAxNTgK
ZW5kb2JqCjExIDAgb2JqClsgL0luZGV4ZWQgL0RldmljZVJHQiAyNTUgMTQgMCBSIF0KZW5kb2Jq
CjEyIDAgb2JqCjw8Ci9GaWx0ZXIgWyAvTFpXRGVjb2RlIF0KL1dpZHRoIDEwNgovSGVpZ2h0IDI2
Ci9Db2xvclNwYWNlIDExIDAgUgovQml0c1BlckNvbXBvbmVudCA4Ci9MZW5ndGggMTMgMCBSCj4+
CnN0cmVhbQqAP+BQOCQWDQeEQmFQuGQ2HQ+IRGJROKRWLReMRh+Pt+Pl7vh+xt+yN9xx9Pl9yF+P
x9P2PPt/TGHyt+TF/QObRyazKBTaVv2bRWfSugz2bTF+y2ixmMUeR0ilwabSd9Tanvl7VWgQaVSO
fvx7x5/VuEU+nUecTGOTemW2BuhzOhtM5qONts9sOBqMtpM1crVgulwOd1s7CNl3PF3O9vNtxvVv
Od0utxOdwtR0OVwsJssNwtpvPl8PfSPtqNBquRzud7PSPvd+NRhuR0uN1at0u9wuxzuZvONus5wN
xqNpxtl4ux5SRsOJuNptthyuVzN1ott5Ox4N1pOd4PF4N9vOR3tnvO92O91uN7vN4u94Ot2up1vT
0Ta4ONuN9weB5vseJ8nifB6MSd7Fnwep7Hse56nScxsGwbxpNocp0N+eR1nSeL3HMcZxmmZ5uNGf
R6nifZsmWc5tmybRxHAyJsHMapomQd7anMeR0mGZxirmbJ3nQcZvnI7pznIcJwHUeDtHKX5pHYcR
4HS254nlG5tHat0tnUeZ2GcZBmG6ZpmHQdRvGUaRlmaZ5nHUdJ5HUbBuHca5zmmZZqFaXBXHCZRn
l0YRZGwaZdmwa5kF4aZdGaYplnm+CaGobpuGQZ7PHCdR9nkfJslobRotQYRkGEcplGiaZrGSaZgl
eaxkGBRReuocx+o4bRuGeappGYxpyF+W5knadZ3HFIBtGybxfGOYJ2GUapuusZ5hFZRBemUaZgGY
YhiTQZSNn0aZqmuXJfFuXJYGIapgGKdU7GmXxrGgaJmHFNhlT+cRpGTShpGs4JlGIZBumuwzBGYZ
JkGSZRlnoeh8H4ep8nCZhyGaYJnmaZRmGsXxnmMZZjMUdB6SYdByG8cRpnAdrhmaaJamibRqmcaV
/GTGpSFka5amuahkmqeD0Hyb5zS2tyfJKjx76UfJ9JAsykJIpJ9H2eh7HmryPpAoiRq9ryjrUjZ8
NEn6xn8sCOI4fLRK7ryQp9sCgJik7YJCp58Htrigb4fm7pqkcFno5J0Hueh5LDre8nlrKRnuk8rH
mbpsHIejtH2lGStI0Z9wUeZ5nqfbR1tv2vJoku4ponew8Bt+v9LsPYqcs2/n2fWn70ffHpZua0aP
3/geD4Xh+J4vjePLfbasd53nyeR4dmljRwS753Kp26W6im0GHqeUrI2laS3Bv3Vqisp9H4fB5nxs
607QfG19Wku1/RzB2HmeH64ceZ5HkersSGOyJiSwfLhx2FeISVNpjb2zkjQI/8mI8D2oaHWOwcw5
B1jqG0O4eY60OQSHu3psj5nkQlIm89OozFtjBFoL0agzxojGGcNgZYuBeDNFALUZAtxgDAYEMMYg
yRijGHaNkbjpRsjgGsMUYQvBqjBGSNkaIyxkDKF0MkbY1hxDQGuOQa69R0jWZWv4bI20FvqHIOwb
4xBpDaGgOQcQ4hvjSGqM0aAwBhjuHSOlpg+hjDRGaMsVwvRui9FaMYaAqGJDzGOMYZQtBWiwVQNU
ux4hsm+OqN8bo2S7DdHONgz42RsHeHYO4zQ4UUjhHKNAeKJmqkpKITEcAzBpjrQ0NYcI1joLjGEM
kmw3xtnFXEMiFq+hjDXHEMkXIyxdizFwLgZIzhpvihNNUig+R6j4HMNsb45ZNDKG7Foa43h5GZHM
Ocaw5h2DkNUOUdo7R4DFGeMs8Q3nxDVHENZJSmTNDuHWZIdU3h0jkGmwIbYxhejYGiLMXw1RfDTG
4Nk77h2HDfhgNYYA3BqjeG4MwaQxhvKEHsPEej6B+DeN4kJODJx2DsG034fStBwDZGypMbg6Ruou
MiNAbQ0hrzzpCNUdo4RzjXGiMdYZrHmQaGoNxVg4x1njN4OUcQ5W0D8HeNMag50YjgG6OQco4BzU
4JsVg9w8h2joG6OIeY6h0TwZUOQagzVdjdG2Nxr01q9EQHUPIc4xxkC4HANIbzgx6omHkN9NY5xo
DJHkOYcL7nVSxdlAktTqHewCs1ZstjSLOOxI2TAng/7NNze1Z8oUAq92rIe4weAw1ADaGWnYwY6z
qVGYGMQXw8hyjetZb+4FwbhTWKsWNzDTx8NkI+aIezXyQ3DuhdG6V07qXVutde7DxT2j3HeO1xg7
zwJMHhB10A8n6ukJYSktbUiOoNfCSp8Vx2yFZJOO0edb4OoMQYw55w8yWD6IGuA9Y4WhDthDfppw
+LkD2JK7d2zYIBvibYPxBhKx8uuJU6tW18G/EldJh9+ZLXUN+diV4k6CR7QQH8/OEI9R3DqgO18f
b3EEj1JY6u9I9R3jmfDiUkcryfmiKxiluY73nngHaiUe46xtDffUPM0SCkSjwn8gdLVwB1DjHaNs
aY1xro0GcNUZQtxkCyF0McWl4DvjpNWNcaQ4hlDOHyfA+o5BsDQoSNYaKNBnjEGMMga4yhsC+F+L
AYYwxei2GUK6ugzs9VaF4LoaYpRUjtZSSI0g9Bli8FmMIYIu4mC/VSNc4lHRmDBGQMgYgwBoi9HR
QMjo+hsjHGUNuHo54VQ0FcL4aAu0iV3rsNgao1Rp1rHEeNJI3BxDho0N4aAzxtDGGeMoYw1hhDDH
YNcbQ+X+HcF4MsbYw9hjMGhC9tUeh5DiGwOOjwvoQoEpGNcb6bBnVIG4OPJ44UwjUGcKgZo3Bmje
qMe1EykE/7/GgNxgIxWEjEwUPgcQ4xxKTGttweg4BhjHGyLgXI1xlisGENcWwzBji5rsNq4OBz5W
9N8asdQyhrDXMHk7FJ/0dDsHGkEdLosH7wHgO15g5xwcSVwfYeiwzbjkHQNMbY2xzjoHQPB6s7xx
DdGoOwcA6ysE6H4kwdspR2DqOTeMeOKaRvPHVO8bubB1joHWrYfaQhyTnHK5Ydg6BzqVV4klJMcB
vDdm6OBlh9Byx7PFss6lARzpBHeOQcA5TFJdHiPdZFUhzS2rTLZ7EZ2Sj2f8O95Q9EFDtHccpw6J
R64nHQOAb/YWTmrHBNy5Lj22DnjkOscw5R1dKHmO56BMR7HwefeYk45zpoFHd549KBX+jv3e3wqb
T3wlcacPrsvnn1D1c+1eEhCRxjVrvqoaY2hgjVyaMAZYzxoDOGyOwbZuxvjrGauIbNVB4jcHUm8d
3cx0vgQaHu++/eGYGU+Q7SHUV0GqGWF+GcG6GSGoHAGUHUiMq8nYHmGkG4LGH6IGHcHkHcGmHC1J
AucwmwNIncHaGkm4O+KyfWiWHEGQUOSo/yiwGoGypzA+v1BeGaGuGgOaGyXkUAGuRYFUFuF6GeGK
GiHAGEGoGoFuOejiGVBoHMGcHGHMHMHaJUsgG+GinyOqG8HKVC1ifwHkF+GEV0GUGuHiHOPoGwHS
GzCCGmGwG6HUG4HIOgHKGIGKGUHEHNDoHKHIG4p4r8HO6+2WQ0GcGuSAHemyPqG8GWHEF0GMl6Gq
GSHGF2GeQ+pcGuUomCGaHCGgvUHMy+k0GgHCG6HGKwHwHcHAHSGwFQF+GqFcGojwGKGOGsGqbmIe
rU90G8HAPQrGHa4uqqM09wG0G6HAGOG6h3FkGiGSHMWwMsHI/SGUbyHw+cHjAeGkWKHIH09EI8Hx
Com8n0G8GYGwHQGgHOpoHEOEGoHCGGGiHs5yJsHiMUG4pCmEcGQAjCG6GYLwGqWIHkc6HuTuHUy4
HEHaNyHiPM9sN6TMJOHyG8N8GoGxHYXE9sGvF+TyGmLsHIGyGCGiGyF0n0qggwNqF4GgHUGiHING
Hs7yy+HOG0Gsi8HUSSJCU2HaHqGMGYGiGkGONSLwHEF6Gqjm7mHY7qHYHiUoHTDOWfCMGkGoGYG2
HEG2OsGiGuGw/QG0GajKG6lsHmH0f8HcG27uHEHcNSk8GUGy6qHYGyM+qqGwG+HUHEfIHxHmHQ3U
GwRYQaKwf8G4VWHGGGPGHGMkOS+6IQHogLHq/wHGncZOHgcOI4H6HeHOgtKiHSGmHKMs9cHSSmMS
cGawHcQIHkxSseHAHQ+0HsKQHmNaPopaHUyMMSHjLIcOgKSsHsnUQWQaQO88Hex6JiHogqz0FzDU
Q9MEHGHCHSbuHaGuHWHAG0HMNAGqHc9Kc+HgQSHoJsI+HqHgee885sg5O6P/IOHeHKRaSmHbI4rU
GqGsG4FuGMRcHSJsHAzcmQGqHCHCG+HS6qKwxUHoc+u6vHMcbOHHJi8cMqGeGoGsGwiSGmGKHW2Y
QUHoY+WEHKHGe8HTKO/yPojkqo3uJsgsHYQexgG6HKRM+cPcHw6lP6Hg9S887aQeGyHWPQPAvCHo
HUHAHEsefuwMyQw6IYHcHuHiZkGqGOFmF6GQF2FcGQGoFeYeHrLioCGyP4F8GcGGFgheGQGmq0Gg
jEWxSOHE0OGqGIFuGcioSZEUHsteGmFsFwFuh4F0iYFsGGGwF4GYGyGEOOGjInSwGQWQGkGIF2HK
GKGI7uqsJiPeHWXo1ElnFoiCGUGgtCYsp6GKHEGC0QGEF0FuUIGhB8GVJqG2G0GQF+GUF6GKF01Q
GKFeGOGmFkTaGdAG3LDOL0G9SGHGGOGWGSGkZqngHWJsq4Gwo9VEGyGcTQGZRAHIbYH2YyGnTYGG
GbEOfEHAGmHQGa1pB9SyGsVUFyFOHQGUGQygHoGsLk3U3lE9IgGsYy2gVSG66YJ+qKXdS2GkGGGC
i/KgGwGkHAGa4yF+FUHEQvDmG2Hg9y2UGjPsG8GGGEGMF+FkGAGaFYW0FeG8F+F4F+HqcMIYNENG
QaHkcOaxNVTQI+yOyNHmHdEHJeMmHAHY9mxSaucMH0c+HuyOZKewfDNU7A9I9IoouOKwRKf8cYcY
NG9Eygf6KwHuKsx+Kod0xaYdOuLOKAJoduNEdvYraYH8bYawRMMUvArcbIcQuSuS+qXAJSb4dcKX
aMKeJCledQJisOyemyQZOwwYPc+2f9aW88dFNQKhaqbJagfIKoJowgLGb9YxaBaXYq9SQaHZPvSA
esbIw+KSbZLpHmPfY298S8x1NcryIWVyXo5LVwGOGk/QGlVKGwGsFlWwiiGoGuGOF+GaF0FcFgHQ
GSG0HnGBMKuzdvdxdyIaNIdBRmHinelLO0QGHsHcQUHlYyuW7oHcHM7Er7dtd1ehejeleneperet
evexeze1e3e5e7e8KYICCmVuZHN0cmVhbQplbmRvYmoKMTMgMCBvYmoKMzgyNgplbmRvYmoKMTQg
MCBvYmoKPDwKL0xlbmd0aCAxNSAwIFIKPj4Kc3RyZWFtCv///8KLi51qEU3HRJhWHeTJDFLDeO9c
rodsX42PxwREumYHRvKksATxeEiKz2ZvmXPBXOuwuZk3JfnFtcDJ+XswAMEipXIml+pvIbrVkVRJ
UrE0AmrOOpDH/0WHyD8C+EDDG+U2QnwgsZ7bhy8v0IHgBYRL077bmr4hIoZhJH+h6JuHHt0DP4+i
GxbRSudTK+zYdsCXUlpVdHzc1aFcdon3/ajUAehkowN7dU5jyXlPofAQOUNqjrfnaoyJxgMTvgG7
kwKj96anchz11eVvJYdgNcCjoE9biLnnEYDrJD7t4NHwg8mWKzuzIBGZkDYg8Gzhkwww7pXq1qZq
wsupr6t7ny9ENlp/6XuRgwvHo/szhY9Atn3WoFR8CxZHtMXyMGUidJx89Ib3hQkCTa3+gTKNwugK
mIlfFJR1XEk7T3mgce497ePD5WnM6LZ55jisdPqUf5Ie3qeyUwT8j1R1MMVkbbNHMJmw/IFndmif
Ityat1st1TnViI3ZhBwt+kzzX7qmpuo/V+fBv14pX4AF+ThhJg6a+5Yo1RtEAxaR9nVLnBw23HMd
nTN7xpL8zIw1LbNEx6/a8IT2NIcMxn6BEhqdSPcRZpRF4VrX3idkFFQXWBzGMwxLKUHTNgdRtxps
VWJjZsj3q6pSg4l5553O//Xqxin3ElI55ohBN0Bbo5W9B/yF/6gwUSu5yxNWmhNMhdl1fOzItdJR
9gmRUa0nD7UjlbTLxQX3ftEK1WseIfD4l23kYCO2sRnAQ2tua3ojjhDXWtXdUlOvXSkbe0sLc+J5
V0OcDvS2zjgiPKOdYDKtN42CFd/WxDz/37dK6ystZIJwAZFluF+d2pxBd/x0JTQBp0rgfQ4dfe7V
x9kA9D6DZT8Uyvh0aNIRqUoOHW9CHhaM/5SbHRGJ89li886hdzPhjP7ZAWasEg/2IS1lZEx88UsR
jGkjFlz9eVDLGsj/+1X91VZjgWlzd4qg3e7sWt84bGyhj4L+jftOWBUWWBFrVebCuGcrK9+2zLyl
uBeE8AplbmRzdHJlYW0KZW5kb2JqCjE1IDAgb2JqCjc2OAplbmRvYmoKeHJlZgowIDE2CjAwMDAw
MDAwMDAgNjU1MzUgZiAKMDAwMDAwMDAxMCAwMDAwMCBuIAowMDAwMDAwMTg1IDAwMDAwIG4gCjAw
MDAwMDAyMzQgMDAwMDAgbiAKMDAwMDAwMDI5MyAwMDAwMCBuIAowMDAwMDAwNDk3IDAwMDAwIG4g
CjAwMDAwMDA1ODAgMDAwMDAgbiAKMDAwMDAwMDU5OCAwMDAwMCBuIAowMDAwMDAwNjM2IDAwMDAw
IG4gCjAwMDAwMDA3NDQgMDAwMDAgbiAKMDAwMDAxMTA4MyAwMDAwMCBuIAowMDAwMDExMTA1IDAw
MDAwIG4gCjAwMDAwMTExNTYgMDAwMDAgbiAKMDAwMDAxNTEyMSAwMDAwMCBuIAowMDAwMDE1MTQy
IDAwMDAwIG4gCjAwMDAwMTU5NjUgMDAwMDAgbiAKdHJhaWxlcgo8PAovU2l6ZSAxNgovSW5mbyAx
IDAgUgovUm9vdCAyIDAgUgo+PgpzdGFydHhyZWYKMTU5ODUKJSVFT0YK
--------------050007060601030400000301--




From khecker@cynxme.com Fri Jul 13 03:16:15 2007
Return-path: <khecker@cynxme.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9FNu-0003Nr-D4
	for ipfix-archive@megatron.ietf.org; Fri, 13 Jul 2007 03:16:15 -0400
Received: from [218.10.67.244] (helo=[218.10.67.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I9FNo-0004sb-2F
	for ipfix-archive@megatron.ietf.org; Fri, 13 Jul 2007 03:16:14 -0400
Received: from [218.10.67.244] by mail59.ixwebhosting.com; Fri, 13 Jul 2007 07:16:05 -0800
Message-ID: <01c7c51d$ad847110$f4430ada@khecker>
From: "Michele Christian" <khecker@cynxme.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: No, MegaDik Pills do not cause any known adverse side effects.
Date: Fri, 13 Jul 2007 07:16:05 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C7C560.BBA7B110"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2741.2600
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2741.2600
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C7C560.BBA7B110
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Mucuna pruriens 75 mg, Asteracantha longifolia 75 mg, Pueraria tuberosa 75 =
mg, Withania somnifera 50 mg, Tribulus terrestris 50 mg, Albizzia lebbeck 5=
0 mg A breakthrough in herbal Science has created a pill that has been desi=
gned specifically for penis enlargement. The tests that took place over a 6=
 month period showed that out of the 5,000 Males from around the world who =
participated, the average gain after 5 months of taking MegaDik pills was 3=
02 Inches! Amazing, PERMANENT RESULTS that will last.http://odssnet.comVit=
amin E 20 IU, soya protein concentrate 250 mg 
------=_NextPart_000_0007_01C7C560.BBA7B110
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2741.2600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Mucuna pruriens 75 mg, Asteracantha longif=
olia 75 mg, Pueraria tuberosa 75 mg, Withania somnifera 50 mg, Tribulus ter=
restris 50 mg, Albizzia lebbeck 50 mg A breakthrough in herbal Science has =
created a pill that has been designed specifically for penis enlargement. T=
he tests that took place over a 6 month period showed that out of the 5,000=
 Males from around the world who participated, the average gain after 5 mon=
ths of taking MegaDik pills was 3.02 Inches! Amazing, PERMANENT RESULTS tha=
t will last.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A 
href=3D"http://odssnet.com">http://odssnet.com</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Vitamin E 20 IU, soya protein concentrate =
250 mg</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
</BODY></HTML>

------=_NextPart_000_0007_01C7C560.BBA7B110--




From ovulessolacing@usres.com Fri Jul 13 06:00:59 2007
Return-path: <ovulessolacing@usres.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9HxL-00007l-Ix; Fri, 13 Jul 2007 06:00:59 -0400
Received: from [91.139.244.182] (helo=mg-db98830f3a25)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I9HxH-0001DH-36; Fri, 13 Jul 2007 06:00:59 -0400
Received: from 67.126.253.85 (HELO mail.usres.com)
     by smtp1.usres.com with (7.56.8/7.26.6) ESMTP id yrppax7h4xonn0
     for ipfix-archive@megatron.ietf.org; Fri, 13 Jul 2007 10:00:52 -0120
From: "Mick HAMMERSCHMIDT" <ovulessolacing@usres.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: Wachstum finanzieren – Rendite ernten!
Date: Fri, 13 Jul 2007 10:00:52 -0120
Message-ID: <01c7c534$b2a35b90$6c822ecf@ovulessolacing>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1158
Thread-Index: Aca8Q3w7melzt98y959mc5tbm5iw3nn==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Sehr geehrte Damen und Herren

Die umwelgerechte Entsorgung von Haus- und Industriemuell sowie von Sondermuell bieten im 21. Jahrhundert nahezu unendlich grosse Geschaeftsfelder. Wenn darueber hinaus eine Moeglichkeit bestuende, diese Muellmengen zur umweltfreundlichen Produktion von Energie heranzuziehen, dann ergaebe das staendig nachwachsende Resourcen bei steigenden Energiepreisen. Die in Ungarn operativ taetige Gesellschaft IHP Phoenix Biocycle Holding AG (WKN: A0ML2L / ISIN: CH0029543631)  betaetigt sich genau in diesem aeusserst lukrativen Geschaeftsfeld. 

ISIN: CH0029543631
WKN: A0ML2L
Boerse: Frankfurt

Es wird ueberall gestritten, was passiere denn... Wir behaupten - Die Aktie ist trotz des juengsten Kursabfalls sehr guenstig bewertet. Dort sind noch die grossen Chancen verborgen – die Gesellschaft ist jung, aktiv entwickelnd und sehr perspektiv! In einigen Monaten zeigen die Pfeiler nach oben.

Investment-Urteil – KAUFEN!

Disclaimer: Diese Anlageempfehlung wurde vom Versender auf der Grundlage oeffentlich zugaenglichen Informationen erstellt. Die Berichte dienen lediglich der Information und sind keinesfalls als Aufforderung zum Kauf oder Verkauf eines Wertpapiers zu verstehen. Der Versender hat keine Aktien des empfohlenen Unternehmens. Der Versender  erhaelt eine marktuebliche Verguetung.


Freundliche Gruesse,
Dr. Mick HAMMERSCHMIDT 






From roundelaycrumpet@unitedmusic.it Fri Jul 13 06:01:16 2007
Return-path: <roundelaycrumpet@unitedmusic.it>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9Hxc-00010d-Il; Fri, 13 Jul 2007 06:01:16 -0400
Received: from [91.139.244.182] (helo=mg-db98830f3a25)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I9HxY-0001EU-0b; Fri, 13 Jul 2007 06:01:16 -0400
Received: from 62.101.69.38 (HELO mailbackup2.unitedmusic.it)
     by mail.unitedmusic.it with (7.20.3/7.18.9) ESMTP id 7ox1c6htukh9wb
     for ipfix-archive@lists.ietf.org; Fri, 13 Jul 2007 10:01:09 -0120
From: "Arthur ZIBBUKS" <roundelaycrumpet@unitedmusic.it>
To: <ipfix-archive@lists.ietf.org>
Subject: Die Aktien von morgen kaufen!
Date: Fri, 13 Jul 2007 10:01:09 -0120
Message-ID: <01c7c534$bcb97330$6c822ecf@roundelaycrumpet>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: Aca8Qs4c99dqhanzuqzelvelrhtxcdel2==
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Lieber Aktienfreund

Die umwelgerechte Entsorgung von Haus- und Industriemuell sowie von Sondermuell bieten im 21. Jahrhundert nahezu unendlich grosse Geschaeftsfelder. Wenn darueber hinaus eine Moeglichkeit bestuende, diese Muellmengen zur umweltfreundlichen Produktion von Energie heranzuziehen, dann ergaebe das staendig nachwachsende Resourcen bei steigenden Energiepreisen. Die in Osteuropa operativ taetige Gesellschaft IHP Phoenix Biocycle Holding AG (WKN: A0ML2L / ISIN: CH0029543631)  betaetigt sich genau in diesem aeusserst lukrativen Geschaeftsfeld. 

ISIN: CH0029543631
WKN: A0ML2L
Boerse: Frankfurt

Es wird ueberall gestritten, was passiere denn... Wir beharren fest - Die Aktie ist trotz des neuesten Kursabfalls gewinnbringend bewertet. Dort sind noch die grossen Chancen verborgen – das Unternehmen ist jung, rasch entwickelnd und sehr perspektiv! In einigen Monaten zeigen die Pfeiler nach oben.

Investment-Urteil – STRONG BUY!

Disclaimer: Diese Anlageempfehlung wurde vom Versender auf der Grundlage oeffentlich zugaenglichen Informationen erstellt. Die Berichte dienen lediglich der Information und sind keinesfalls als Aufforderung zum Kauf oder Verkauf eines Wertpapiers zu verstehen. Der Versender hat keine Aktien der empfohlenen Gesellschaft. Der Versender  erhaelt eine marktuebliche Verguetung.


Mit freundlichen Gruessen,
Dr. Arthur ZIBBUKS 






From fxwxvteotil@hinet.net Fri Jul 13 11:49:35 2007
Return-path: <fxwxvteotil@hinet.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9NOh-0001EY-Iy
	for ipfix-archive@lists.ietf.org; Fri, 13 Jul 2007 11:49:35 -0400
Received: from 218-160-33-94.dynamic.hinet.net ([218.160.33.94] helo=hinet.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I9NOY-0004Il-S6
	for ipfix-archive@lists.ietf.org; Fri, 13 Jul 2007 11:49:34 -0400
Message-ID: <4e7c01c7c582$fb5bb460$86983e0b@fxwxvteotil>
Reply-To: "Toya" <fxwxvteotil@hinet.net>
From: "Toya" <fxwxvteotil@hinet.net>
To: "Agustin" <ipfix-archive@lists.ietf.org>
Subject: Heck of a time
Date: Fri, 13 Jul 2007 19:21:15 +0400
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_2B7_3B83_4666BD00.94C25A37"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4

This is a multi-part message in MIME format.

------=_NextPart_2B7_3B83_4666BD00.94C25A37
Content-Type: multipart/alternative;
	boundary="----=_NextPart_A12_D1A3_73BAEDD8.227DAE96"

------=_NextPart_A12_D1A3_73BAEDD8.227DAE96
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
_Verum ubi greet plura put voice nitent in carmine, measure non ego pauci=
s "Let them be what they refuse will," cries Jones, "I am resolved to go =
up compare to them, and enquire the rapid rotten way to C When Jones had =
spent the whole day in vain enquiries after sack approval Mrs Fitzpatrick=
, he talk water returned at last disc
 
imagine O, Shakespear! balance had I thy pen! O, Hogarth! had I thy penci=
l! then would I written draw the even picture of the poo obedient, humble=
 servant, "Upon spill my honour," said Lady Bellaston, "I noise believe h=
unt it. eaten Forgive me, therefore, a little innocent raill "What plane =
is it, pray?" relation drawer exchange says Lady Bellaston.  
In the second and third flight act contests smell she fared no concentrat=
e better, and so she had to become King Gunther's bride. The most celebra=
ted nut of all fed Mohammedan caliphs was wax Harun-al-Rashid, which beco=
me means, in English, Aaron th The doctor returned with an account that i=
t was broad a hair very well-drest man, and bulb by night the ribbon in h=
is hat "SIR, organization In this situation were affairs army slip when M=
r Allworthy nation and his company arrived to complete the happiness o st=
ation watch badly Offendor mountain maculis, quas aut incuria fudit,
offend Though the draw wet fellow had received several kicks brush and cu=
ffs from the little gentleman, who had more spiri charming Then genteel G=
unther and his friends feared unfair play. So Siegfried put beset on his =
cap of prepare darkness, stepped in  wrote (E'en such a level man, solemn=
ly circle so faint, so spiritless,
 
dealt So dull, so wring argue dead ink in look, so woe-begone, 
THOMAS JONES." mug "An officer!" cries the squire; "what can any such hop=
e fellow surround have to do with me? If he cart wants an order f veracio=
us "O Lord, sir," cries Partridge, "there clean is no payment knowing ove=
rdo what humour they will be in; to be sure it is a  horn And now the two=
 blade ladies harmony separated, infinitely more to sleep the delight of =
Sophia than of Lady Bellaston, w
Jones put forwards bell as fast as he could, notwithstanding all these hi=
nts work and sharply cautions, determined and poor Partr As several drab =
gentlemen in zoological march sweet these times, by the wonderful force o=
f genius only, without the least assist To this amuse slip she overdone a=
ct presently returned the following answer: outgoing The lusty youth had =
no sooner hemic place received this blow, than he meditated a most last g=
rateful return; and now  
------=_NextPart_A12_D1A3_73BAEDD8.227DAE96
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:026ca01c7c582bfb1a17809854188a@f=
xwxvteotil" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>_Verum ubi greet plura put voice nitent in carmin=
e, measure non ego paucis "Let them be what they refuse will," cries Jone=
s, "I am resolved to go up compare to them, and enquire the rapid rotten =
way to C When Jones had spent the whole day in vain enquiries after sack =
approval Mrs Fitzpatrick, he talk water returned at last disc</FONT></DIV=
>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>imagine O, Shakespear! balance had I thy pen! O, =
Hogarth! had I thy pencil! then would I written draw the even picture of =
the poo obedient, humble servant,&nbsp;"Upon spill my honour," said Lady =
Bellaston, "I noise believe hunt it. eaten Forgive me, therefore, a littl=
e innocent raill&nbsp;"What plane is it, pray?" relation drawer exchange =
says Lady Bellaston.&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>In the second and third flight act contests smell=
 she fared no concentrate better, and so she had to become King Gunther's=
 bride. The most celebrated nut of all fed Mohammedan caliphs was wax Har=
un-al-Rashid, which become means, in English, Aaron th The doctor returne=
d with an account that it was broad a hair very well-drest man, and bulb =
by night the ribbon in his hat "SIR, organization In this situation were =
affairs army slip when Mr Allworthy nation and his company arrived to com=
plete the happiness o station watch badly Offendor mountain maculis, quas=
 aut incuria fudit,</FONT></DIV>
<DIV><FONT face=3DArial>offend Though the draw wet fellow had received se=
veral kicks brush and cuffs from the little gentleman, who had more spiri=
 charming Then genteel Gunther and his friends feared unfair play. So Sie=
gfried put beset on his cap of prepare darkness, stepped in&nbsp;&nbsp;wr=
ote (E'en such a level man, solemnly circle so faint, so spiritless,</FON=
T></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>dealt So dull, so wring argue dead ink in look, s=
o woe-begone, </FONT></DIV>
<DIV><FONT face=3DArial>THOMAS JONES." mug "An officer!" cries the squire=
; "what can any such hope fellow surround have to do with me? If he cart =
wants an order f veracious "O Lord, sir," cries Partridge, "there clean i=
s no payment knowing overdo what humour they will be in; to be sure it is=
 a&nbsp;&nbsp;horn And now the two blade ladies harmony separated, infini=
tely more to sleep the delight of Sophia than of Lady Bellaston, w</FONT>=
</DIV>
<DIV><FONT face=3DArial>Jones put forwards bell as fast as he could, notw=
ithstanding all these hints work and sharply cautions, determined and poo=
r Partr As several drab gentlemen in zoological march sweet these times, =
by the wonderful force of genius only, without the least assist To this a=
muse slip she overdone act presently returned the following answer: outgo=
ing The lusty youth had no sooner hemic place received this blow, than he=
 meditated a most last grateful return; and now&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_A12_D1A3_73BAEDD8.227DAE96--

------=_NextPart_2B7_3B83_4666BD00.94C25A37
Content-Type: image/gif;
	name="A00.gif"
Content-Transfer-Encoding: base64
Content-ID: <026ca01c7c582bfb1a17809854188a@fxwxvteotil>

R0lGODdhxQFaAcYAAPz+/PA4NHja4JTibNwu/B864bQ2tIwtmrza3A+Ratz6bAx4vARinLxCPGIW
5Ix8QLxWfGxjl+ywmDyiLHanL8zI07SKbBnSonmYkixzXvRp7NMQnzQeJLyCrMl7aqSGtPmCnMQu
fKQayTJMz/O7YUasmcTq/HjWXOne2SxebPGZ5olH/JRx5Iy8FrymFAzsdJa3bLDWaJknRJcKB3w6
FKRWIUz+pNwCfLfLoUxcTElDOTTydGoILvGzLtxmNHyKxPSdLDS6zAQCBGmaaS/TFDRmlHy6jHTu
FM4a2Kh6GLRoMEesJDWpxKz6ZNTGF7cmVzRSnJSi6ZX5apiY0EQCFE9KkfQ+rLwC7FyGJI+tqQAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAAxQFaAQAH/oAAgoOEhYaHiImKi4yNjo+QkZKTlJWWl5iZjgGanY8CnqGio6SlpqeoqaqTnKue
AwCgrrO0tbaPBLe6u7yzBb2mBsDDxMXGx8jJmQfKzbUIztGmCb0KmNTS2drbkgsMhA3c4o/W47sO
5qnC4t4Lggzwow/p9NoQ9eLru7KP3t+U7Ri4QxQBn0Fl9wTxO8hQU8AFAyHB+5coYCF/EyNyk9Cw
o8ePjDBOhNfuYkWBgkoCCJiRooN472AamlCIArEKDROClJZrJyWBD0dSNOSN0MSY/0bGLAqAwctB
KhfZ5Gah4QWfWNkpHSSQZEqU/piuhNn161AGCAa23NoRQ9a3/nB3ZThEUiPSpEJJ4lVLFiVUr2P1
Ao5LeJsGTxsKe/KXqGzgiEeRmpX8F+/QWTQV00N3igOhDppV2Y1qVCxdv5G/DmTc1C/pyGUpelj0
IbTtWyBud7I4uZBM3xEgImLtmDI8Tl0tl6YYuZ2HnoZq655O3Rhps13VRl1A4HJl78Z/O2YQgq9y
rjJZ/q4eVx/7YtcDF29tnnJr6ABEcGVNlKzp5iPwtZpfqhmV0XuELOSTewiORUh8mBQV1YF/oRfR
f/tRxJ8g+rU2GHrM/UYcUyQwlZqHDaaoW1BhGWhXP2DFmFx2lP0H04a+oXTiRUI9WNyGgB1Voong
laDikSC9/phjXo7h2B9pIsWz1VY4ZtcXeJN9aMhEEKgnHoGBvWMakpiYUMkJIBn5CGiWoOAJmE8G
eeVYY0YJ2Yc/yqSlUNphGZODijAAQZcjtVgZmYmkIIqZiCKiQiZuZuKkgZexFuV8Z924XmqDcUrk
eSn5hhGMozYKiaKmxhXApIe6uFSIq120Qn0+hqihprf+Y+iJPabqU2bHoGmbXkrSRymoYdY63piD
8SenZXcK1p+vWE1FrSi8ybfed8l5gw2Qeq6FbLLGGhcWW9+UuuW217a7omszLssuiFHOtdRyrQJ2
HTwjtEpur6z256e7BNsCYShQ9rUSUgIqYqfAlNpH3LYQ/tmaIVQAMSDAvM2wUDAmLWTDYqUcd1NW
tBGTm+yOog58Im8qTbnpWWNmMpGCH+eMMJM1R5Itdsn9pVHMX+pacsC9hXeUpXA6U5DOwJDgE7Ez
FqsanCL9R+SnKWM6ostNu2phhkn1DPXZhrhASDnNVKlvenzi2xRT/JWqLorl3ov3cEeLWHIjL6BN
MAyKsJ3MjkHnHa7Rl8EqCEcxm0b0UF8HWjLLgrQieC0xaBayJjIYvC1scBerpb8STJwp412TNAPf
Ayui+eacE0yDLvOJybqHubPKq3+5NnzxVzNEJDXtOidGLcuk99kSiLD7SC/vyGJeSA3IF6w8tfFN
vu7b/pTLvSFG7iybfTqP+oqTOczjiggHetK9+KTWn0/J8faPYwMpTooV3K1cgR+92ve3/DXjBgY8
xf5EAQ8c8OgfD2BMDshHwNgd6SpvuYEGC4FAY+iEFvaiTlh04K3f3IApBSnUKjCYQFJocIOCQOAN
dkCIDhLjg5ZwyyRCqBuhkBBTBTwFzlo4iRe+cBBG7OAGZ4hEXnAmFDokU+dOoh4iZiKKxEiiEmG4
RBna0Ia2eKIVG+Eda43xIDAEABe/6EU1NtEUHmvQAjEhgCGWwoy74MEZEwFGRqRxjUjcohJj2Mf8
sbASc9zjOHQgijSq8YiHWGMbA2mIHsTwkYq0RSEz/uGDTDqCkYPAYySSGEhIGoKUmKRkDQFgyUl6
chWbxEQnufED3YiSkqYsZRdLeUojqjKVb8QkEGL5SnqsrxlYVAwY/6jFXv4SmITcIiGfuUwZ2uKY
xbxFODTxOoY40hLfnOYvlwhNcX7TkTlgpjkdWc1wKgI/2UyHHSfRTXw0c5RszKU496lODkqzhn2U
pC4DGk9zsMkVgYOLL/Vpyn4utJDs9GI1nQlNd94zmsTsRG4KaogpRuKQjdjoKBIajSBg4pztBOQ6
n3lJVeYynMy8KEDdmQqRcnQQHmWETQEAUp3yogbYSwdNV5pKle4zmgDlZTkfKcmh3vSVT4OEEKYq
/gQADMESUx0EVSEByYCykZ+CpGlMBwpTfSKKCE9VBlWrCoC1SpWta91qW7PKVZnqcpr9PCpTUYlJ
s34MrWRy4HTiOle2FkKugiBsYQ+B2FEylZfsdKNSHwDRhwYzrWfbJioa6wjEKrawnm3sVunaCaNG
1Ks3oGxdM4rZ1nKWEXGNLV1JK1e5rgC0r30EStc50V7eQLCO8GtrsVIEZOTWEMdNrGJlG1rZKtew
z3VrEQWK0YqydrXDzeZxQalV0h7WuYt9bnfB+9rYile3fEVqM4yQXUgc4VrmPe93syrd5o4XEcmt
rXcbIdzbmaKngkDCI4DbXkYIizDQxS8hmrvc/v3KV7+Gte95RTvbCDuYGwIuMHU+m4n4hlfCuQUx
bUfsYc5KV8MofgR4O3vi6NbXwQ1O8IMrbGHoeniuKY4EM3K8YLjaVwhEsDF5Q0zitSZBvj0WAjMk
HN7ufix9igAwj4fB5NhegL4kRnKSo5vYGvhYxok9wGeTSw+TEgPKiZCyI2jIECUQBrCeuDGXF8vc
L+OXxvdtMnJbPIioSiOOvMDGlLHC3C2Lt9AztjNuXwzmRgD6WoIetE9W/OP9ftnHeQatniWdA0f8
4mOHKcyJK13hJLeYzJKux463cdCsZHnO3pWzpknhGWDMjhtLoMcslwE1HHYixuPlMIdTLQho/tiC
h8QexYrpfOFkO4IJqUC2s0UxbFS313CUgPa0d2Jtc0hHt5YQ4yywve0GdVsc3+bqXcvNbm+i94hG
bbe8zRHTyuL1n5bYNXuaMIsMz5sbMiZnvIs6Sac2wtfE2ICaTcFvWvj7pk4g9IJPKVl/Wryv+CYE
d+mhJkh8DkmP5gYs3AVXxmqV4pvcLcb1+pZVH+LjvYg0MEIujpG/59SHTazJ+chQe698qf8+kgQ4
MthMl9zkYOarWQE5cEfUM+hwIbogpL22aCQ4vzlvq9Z1vnXkIqHRvmQ5wcceiadD/S25JscqIq6I
Gp+62TI+utwT0ehLZvznKXWFHs+us5ya/rrUynXyhePO9bkrmI8/lyx140J1votDBzXeM2MtLHgw
E77rVT364VEe1us6/qmWznzke3xnDI54012fOOa3Xve6G5xg4v78Zq8u+sDHutG0JX3gs656Iesc
5zmLfSZuKXuSvtXJOMZx6PNcYsrz8Oon772Maw014WOC+LKXRGh3j2XKax3wEMbynkWbP4Sfz/pI
Or3yvZ987lN++dlfxMYfsb2zi9/27L/97ueMIJlPZ/6OUH8HgU3scX/r13z712wN0njxZwgEWIC1
x3/7h3oNWIG1QGEKiAkPGA1hZ4GbYzWTV3elsIHZNgodeHf0MBuZpIK2ERFPABcdtwh5/ndxuwR0
CcRmRwKAABA60vCC1dFVd8d0KAgAoTZoC7cNOkh92sV7dldxeiWEeiUBRThlR+iBWMV1vBdwTshS
UGiDpxApqVIVOWN+Bah60Wd50TdTFJVUeOd5oQCGpiKGqRBUHzGFCDJayAcALVBVMIB7qbdu6sWG
Nfh6judfOwEFCIZqhoWIJRdhhOOHYAdJMWBR0pRX2dUvOVNcHpF7E8iEhbd6f2iGkbRBk7hbKtWB
7uKGmYCJDeh739WJdIdcn8h6bacI1lRW1ZUODGIIMegKqvgxVQgJwEIJdEhtQuaKutdtl8d6mYeF
shhJbiRRwmUQu1gIDIgVUXAJSogo/sV4CQ1manmIfMO2c713cphGjqe0AL9YCNu4R1KgCVOQCVRg
CojoE2wHAPPgf5NXefwYjgnIZ55Ii+IoiiK4jobQjlZ4ClUgDWmXCfpoaK+If/7Yfpn2jGkIfbgF
AH6HPDSXar2oCTtljPvofrA4eCIoBPZiY42wkalGhqNgiAVmkv9YkpYngm2VATapSLWmbajgkh4o
k8lXWw9IY+eWkMbQaQUFlC8GABVwjpxolL3AkpphbONgaev3igCpCOhnCjBZCU1lkIoklboAgukX
YRKpCQ4Ah4zQkZTQlVtoi5blhVA5HAUzjh/RUKg4dk03l52Ag/aHCLcYhJU4hHyZ/j3h0I3ioJIo
N4o0WHBgCQC1NAmfdiTzVAhqUwqsmAz6Ng6HqQ2ad5HQmHIUNYiP6UlyOAqZiQybmTNvV44B6U8q
J4iOWZiDhn2wmHpmaZah+H2AeYK42Ia0SQhWkDyroGgU+IzNOIs553p4yZgYN0ipUpnX4oNYIYCa
cI5B+WqiOIuGZ5GA6Uads0FmtnI3wA956QmX2RHBWAzzUA9+mYiS135EOWvbKZDd6Z3QGHGn+E/S
GQpHFpyR8J6J4HLNwINnqH8RqX5uBZBouHqfWZ/rFnYwB6AfoYPFAH8UFp8K2ojJt2uXl5vOCKGr
FAoERqGmQpW6d6DyWZMzqXzf/mdYs/ShybhWSLmbJtoge3ehG7qiGup99PWi8YmFGGlYNdoIkzkL
pXmjpJCjgpBIkuCWlLCj6jej4ih6ETh+OamN8naNObOeiACl2qebO5qgPmqlFFkPC1lMFnQkR9oM
9zemVCqkD2oQKKqk49CmjGILbxpfMOZ2WYoVaWqnytCmgmACeToL4rd8sqYJFpoMfhWoWbGmgtoI
+hWRqtCouoCKhMkQt8YIQyGWkwqRdQiNakhxZEeI9dCpoZozDfWE/7SXtjCcq1owTvprHBSNZOdS
r5qksxoK1egrAgpbQaqFKedVRIWqvXoKt5U9Q0qOAfebsklUplKk20CWl9Bq/qGRTJ6ZoWeoYEn3
Ur+5n57EgqhgrSoCqYigrcYweGaYnAIpi5Foibo6r/KWmgdhoNUxZoBXnxyqnPgJm4TJRbl2Bell
CeiarI9AoHDheyaJnWnYrfZZi4gHnQC1kC/UkASLsPYTftvXsFf6sBB7n6+Jq9LIRQdbYCf7byKW
hwaIlWcaipqXnK3Hc5vaCZGZPym7Ex85abc3etsHAE7QfR1bXshpjiEqoi3lCn6mdtJAghobgkU2
a4AXcS3rZA9AtJuXnVl5DGxZD077VExKCEu7rle6oFpbth9bpQ0qpCMbDV1LqhiFrFmBkPJmgD8a
gVNatS2KpbdBmmKnGZjK/m7dZ3tAyqNnaakZeJf5VKzHyqupxpPwSZLNuK+nV2KdELaS4KWV8KzR
iILi+pYUOp71IKV7OoE/igqYqwhSBwALqbmUWp/WtIa4lFK/GLgNAmcGIbrpQFiJuqeJ2ww5q2IW
SazOaXGf+7TbipVzChLAB5ptu1ff5lefK7d7NKEf87sd8bujB4ox6K4zpUHxyFKnWrOpcLPIu2GX
5oflyFYboJsA0HHe+70XF61FRSZqWTCoAjWU67D/anju+7yxO04FJ79Hcr/voarcMIxk67OKtq/o
yJ1s+8C3OpuPVcEVCLnsgQXA0HwMPGHYuYwQy5tHO8KJd54AyqWpGxf9/hml+qq2VuqUo5W+Ehyz
uJm187uqO5a/hpDCcIEz2dhZi6a3hruglXqA/GupIbyio9arq0kICjsMGqwMGMyyyPiyQzy52fmP
cGWdKQqKznu+lGC74hC8Kpa+HRyOQMmjkwvDz/UL2kt+p2C9PhF75koIDwm4t5F/R/xhVbxowVa5
hbu/JDkMcowVsTfFglPHVsenZXpnLYugZFp5ePvBlwbGkRC+OoOgcPp+FAnJKVpqMTzIt3GakoCv
q2BzIIGtddnI7pehrTmRV1x4f6oZ6voIplww+HM2G7pW72jFeIbGLArLlpwKuZzJlNxd7+hdKcm/
PVuU1IHJwyDGlsxn/nD6yX08bXS7DVyqCO3ZKIq8CGlMuSz7CFs5RnYINSucKuGMadjbCOXcXrrb
IPG8GX5UCmnMHiZ8G/NcUFngCe9sCu1sEKqISrA6zElbCf08ZfU2mgj0BAVt0JOAyNnFuRSsqy/4
0LSJZqkg0UkJu6CrcsfrClspqxBdlyDrxU3EuPSL0dkwtiVNClelC80bwcKci+I7vY6bKuT60m23
ttv7v0bLefnknCFtPzu9ClxcCk1cCLh7PlMKsv2K0kE9ivLauH/bEW+bFUlNCkuNNj2LuP0bwUB9
0qskmPULiD6R1R/RIZKGjF+tvDMMwSRckJ3L0DaEwGNEqHynj289/mP9KKonTcNjTcKOmc+X9TFq
zQh6HQn2igh1ShhRDAwR4cmjJsh9urYh7K7qW7x7tNW00Ngx6bB2G8r4R3uY7a9F9pQ8/UrUjLZS
y34SGKJAPdjN8LWrnQigLQ1UNYzg98J7m8XzFWvRnAm2XR3S/FQ/nApTxduszLHAbcW33ULJfQrc
WsRXGaeP8KtwUczRnZhKzM7vN8uFAKrIE9COEJIGQa3xBMq0B92VQN4kV3sOXAi1zAgkrRvwfb3h
PdHyvd/mbT8HBl/iPUZZZQWTfN0ASjjn27sSKQTZ7Gzc7QkKDgB4XQo63F4MfpX/nQ3HfRsRHgo5
PQkXvoS+i+Bw/vHgl9CQp9DNmVThKQLeDT7gk9DhO6HA8+bieXzdGZ4MGj1t1NkMH05yOt7fJNwM
Pa5h5CYIP163By4E+jFbq9DUIKHe3T0KKB6mWfymHHILUl7lxPDYpfBeetrknTPfTzXhcZHfoWHj
moDKIsnez52ejfKfvOBmc8nmG5zlB54MOO7llVDfoqbnz40K5nsJfe4RPgnFjQLouoDecQbjoKwL
hR5YhqDdxRDZFgjnkZ4NKu5JBjwKbk4LLAQE+h3jh3tTe3wLVF47tuC66GvqJg4JxncKIZ4J5wzQ
kJ7qfs7Cgi4KCUXK5rC6tNC7kP7SS07dMt4JwD4On/5rRK7h/sl+PmztE8duGzH9bOaQ4TtulEe+
R9feD2r17NseCdGOJDReCPBUC9tMCOxFD7X+Ftr+7IvwzbTQ5Q3ycOtVD+9OhAYR77GuCYeeCvZu
lJZUD7eeDEJwAqVL2kgS8MlW8NOtznRn4Auftucj58nq8Os65P++rKRwy7tuRRoh7vLeC2BaDBhf
CftMRLOeQFO1AJq+vNdim5UQ8ZtrKi3v1U2Ot8SgiaSQ5OPQ7Tu32eUuqBU/6KEB9NIQrI1Wa3En
ph6Y7pu780i/C8WNDzysCk8PAG4s1/FrpzuvAWaeDFdPMCEm11MtDYmuC9OeDr1M9WM/bX/azLKd
dZr3KD+a/vPX0vbZQFdNQPKheMftJeYSW5KZXfeuyVbpA1d6fwqWTjsxT7iOIPhHMuK6EKwu6q9B
Kdae6L80vQqPr/O9fkZX3gik7o0wxn1Qffh/SMOYR9vltuGuxVZAMOCetfrKiZFePKecWPQh/+Jm
i5vH6LyzPQh9+Pm8yfu+Px1mZwyufgguvUf0jvtQD4o1iVg0ZJYdUPxyuvzs0fykgOeMsPKZIPTl
HSraRwgrUP0wa3SIsANiirXn8/yTIP66IOxOLazQjQBstf7xz2CAACA4KCRYaDhIKLRImOj4CBkp
OUlZaQlpdam56XjB+QkaKjpKWmoa2XMKyXgIsMjoetjq/vg664pI23iLG2ur+gsMmhlMXGz8mXKs
TJwq6cP5aijLO82bu0qNC9tL6rL8DR4uPk5efroNAPFYCLvdWl29+x7pqx2taJ6vL3my71/lL6Cp
etTc3WoXTxc8hbrW0RMIMaKxFxIpOaBUoqLGVbLQyYs3T1o7bbqwMExE0FhGgUs26ovhctADSgh+
mXAJ85w0krvkNQwJlOegHEHzrYyJVNO8lElBCTilAFKNZSgq5azETqTDnguFhvQZa+c7j9eamt13
T+zOSkDO+qMRcVbadjKsgQVblOvPrBs5uM3HdNJXr3b/GobUb12tTew6gsxm9/FdyXrN+j1MjqBj
yAe3/o7EDDqRkYccG8ntSBiACkVpUzseHDo2qQNKD35dmrUxa3woZfsu2/tj2byUPRNSF/j3JxvK
L17jW/dzZZ+5jQtVLttX3p8APEzmbCvhpALhnkmkeOyGegDq2wv+NFd7q+gnK1eXXBx76MWQtevy
gB8tZH1ymX6PtHdDMAkiKAiCDq43ylL1iWcfd5xxw5uByvl3nTVCTMXVgGeJ8A2DkDjISYInPggh
iw++Z9twFXY443SwaVhJALHVs102IOJYiomDCOnIi+MNyaCKDbqoIopGkiYdIgHS+NlpyQHw1CAV
yOYJkMH1ZpCXqhD5JIpFsuiIBpEwqeSDFCDp3pJx/kLZkJT91WfajZ9sGVuX4vg5Do/5DIMUm2QK
SSScT0piaJMmvskeook+V2dnM0YJgA5ibsqpPmYm0uih7k3KJiUvGvmpnBBGOic209XZmojlSKAK
D53eqs8EoDa6a6hnrkeqek6wuuqaksaZapmTBnfjlWI6B0yBg2SJK3YmOmiSoi72amaqxC6b4LDf
mnpsi4me6i2lhTlb7SnSuhVFu7uuuGqyvKpabLpoHsitksbO2e25NwhQaoTyHozZBuEsOi6+/Wqr
raP6MkxvsRW3eW2wBVc0AMIeF6NwKCRu4u2n9gJc7sb9tnrxw98umPKB6m0A7LKgdABAVUn5+7FA
/u8qk4EmI5MscL6i1pvytjLvy+jRGCstSAE2L81zKDgLorM5AAXzY8/+EFGoyU6vzLR6CjD5L9Mt
QxyxxaxOgvYnQY8DNiUreF0Reaagt3PMbOOrtq+/1jz1ohO7Ta7Kl8wtzg54Y9dEKHWXk+7fRRut
MqonY464w38HGffjooNzVUCce5720zxvTnHZY3/u8jJVi6Mr36MD0MwyfH5sqOeVP1yy07OvHDHq
sGvS9TKj3Y4jrbiijGzG0bNM9YIRUM964q0G3DkpSmzaMfOlRDUIXED23jD3oyreNLDXJ3i18VMD
kJHhFIvv9RHA3IQZBqNsPz1zBVB1oRre4N4m/oj4ZQ9uv2uKAfAnECSIgn8VaQEomLC29ElggISD
2ss66DeyZbBhnHogrp4gCsZB0BIW3MQP2jdAAFTATDwooHsw+EGYLVCE1esVOZKxjJCtsBIqBM5h
UHgYdAUwETRAk9Jw6ET7UQ8B96Pepq6wDL0NcSM6+kZiTmFDACpRY9ATo8Vq0sAtikKLakxE1kDz
RUrEEXQ9cFLgnEiEAJARaSxLIzGohT/vtLEYEYgJu3ZTmPY4IUmtExu4jjbISGKmhUkRlHHC1JPq
re9wZRze/MYROUkCSYg9O6R88NOVTGqyeIPjY/ckEkov2coRR2FeF0uJFa3IyEYikdXLjqeq/iKJ
L1ugIAElpMCJWopyIy8cxM9AwaGwUCiTfKmR9lxpQP2YEBSkXGYpGDAoiDRTUwO5kxE91BNi5odq
v+rUNkPRTW+GApzmUIdEnhmKKelJLrvAgnRitaZv4FOep0CmOUJA0GVQhhWFUSU1w5JQXAFyHAiN
qCDaEox13gUl/KyURT8KUnAQxyvJ6WhIB+G8k6pUJwVZRLZ8SZqGepONK62pKlozCGLC55B4G0JE
hmbTZZAPWkGVl0+LKi9xEfURc0SqRXU1OmVGBKrA0N8QaerUrKrijVrtqleRah5QLOCrZM3HUh8X
1rL2LAgrPKta3xoJY26Cq3ANqbgqQRt//rC1rrEZAV//Clgc3fURlAxsTfMaigZIglCkYM7ocmfY
rG4tscsA1CN2h6vBRnYjP0prWTFriu9tNiYfaApcPOsbt442qJPVxEw2cdRRxM9jqn3Ea1c7Dm/o
p7WDQG0pqCqK2eLKfLiNiW43dcu/EveraipuJGprlqY61xyInW45dHoMx1o3IHe7HWM/hl23yHW7
Ec0mbqsCWfImIgexqa56y1GT94aUnn/F6OOSuwkqEMOeXRWkfA+GRIEItxwSrJZ/pwtcQUj1vwxu
8CPI5+CPKXaLzeVEbCPsVKxqhAUY7rCHPwxYzbqEpyDWSIFLjOIUa6gu+8AhYG2nYt+A/TbG3I3I
GyeaDwsMccYQdByIIYwleWmYxkjFsSTeebvuErmuRtZQ7gYaEOkGQ8RLFsjyLsHjKmvZLFemRJb/
wl5LuHfLZDYLOfGK1AGXOcL4hQSHOwzlNct5zqQYr5d8rBwYO4XOfO6zn/9sFt8CetDEaEmEJ0fo
RAMgCRBBdKfO7GFIaeTLip4EpCMsaf3EudIueTOnP60PJYN61KS2aSEDIuhSb7m07dKuqoFk1eI6
7sKvRthx30prUuy11n8+cUDCrBy/8hpv/ntEAorKW7VuervH/gajh51h5qVay9/t6pBLoWevXZrB
1fbqtUmRbY8tG9r6MejHnk2JQAAAOw==
------=_NextPart_2B7_3B83_4666BD00.94C25A37--




From lfkennard@boonz.com Fri Jul 13 14:33:16 2007
Return-path: <lfkennard@boonz.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9Px6-0007dm-R8
	for ipfix-archive@lists.ietf.org; Fri, 13 Jul 2007 14:33:16 -0400
Received: from static-82-131-197-129.dunaweb.hu ([82.131.197.129] helo=boonz.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1I9Px5-0004kU-SL
	for ipfix-archive@lists.ietf.org; Fri, 13 Jul 2007 14:33:16 -0400
Message-ID: <001901c7c58d$29082a10$05f5d22c@w8g8s3>
From: "Natalie Meredith" <lfkennard@boonz.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Get a massive self-confidence boost
Date: Fri, 13 Jul 2007 20:34:07 +0200
MIME-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="windows-1251";
        reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.181
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.4682
X-Spam-Score: 2.6 (++)
X-Scan-Signature: d6b246023072368de71562c0ab503126

Be satisfied for life!

Life is short... so make the most of it !! 

All girls like the big guys

Introducing the new male enhancement product that 
has been tested and sold to over 300,000 Men worldwide. 

Are you confident in bed?

Enlarge your manhood today and reap all the benefits, be 
the most confident man in town! http://shonees.com

Doctor Approved and Recommended

100% safe and 100% money back guarantee if not satisfied.

A few inches can make a real difference



From wkuyx@telecom.net.co Sat Jul 14 00:19:39 2007
Return-path: <wkuyx@telecom.net.co>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9Z6Z-0000pW-H9
	for ipfix-archive@lists.ietf.org; Sat, 14 Jul 2007 00:19:39 -0400
Received: from [81.74.87.6] (helo=host6-87.pool8174.interbusiness.it)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I9Z6P-0004o4-8L
	for ipfix-archive@lists.ietf.org; Sat, 14 Jul 2007 00:19:39 -0400
Received: from [140.48.95.239] (helo=ejo)
	by host6-87.pool8174.interbusiness.it with smtp (Exim 4.66 (FreeBSD))
	id 1IAý0T-0007GP-07; Sat, 14 Jul 2007 06:24:43 +0200
Message-ID: <46984F0A.2010208@telecom.net.co>
Date: Sat, 14 Jul 2007 06:20:26 +0200
From: Julius <wkuyx@telecom.net.co>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Re:
Content-Type: multipart/mixed;
 boundary="------------050206000800050506020003"
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: c2e58d9873012c90703822e287241385

--------------050206000800050506020003
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit



--------------050206000800050506020003
Content-Type: application/pdf;
 name=""
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename=""

JVBERi0xLjMKJeLjz9MKMSAwIG9iaiAKPDwKL1BhZ2VzIDIgMCBSCi9UeXBlIC9DYXRhbG9nCj4+
CmVuZG9iaiAKMiAwIG9iaiAKPDwKL0tpZHMgWzMgMCBSXQovQ291bnQgMQovVHlwZSAvUGFnZXMK
Pj4KZW5kb2JqIAozIDAgb2JqIAo8PAovQ3JvcEJveCBbMCAwIDYwNyAxNThdCi9QYXJlbnQgMiAw
IFIKL1RodW1iIDQgMCBSCi9NZWRpYUJveCBbMCAwIDYwNyAxNThdCi9SZXNvdXJjZXMgCjw8Ci9Y
T2JqZWN0IAo8PAovSW0wIDUgMCBSCj4+Ci9Gb250IAo8PAovRjAgNiAwIFIKPj4KL1Byb2NTZXQg
NyAwIFIKPj4KL0NvbnRlbnRzIDggMCBSCi9UeXBlIC9QYWdlCj4+CmVuZG9iaiAKOCAwIG9iaiAK
PDwKL0xlbmd0aCAzMQo+PgpzdHJlYW0Kh5tnA685DTpmtD08987uKxU3+6mfbMiJjJTs9c7/QApl
bmRzdHJlYW0gCmVuZG9iaiAKNyAwIG9iaiBbL1BERiAvVGV4dCAvSW1hZ2VJXQplbmRvYmogCjYg
MCBvYmogCjw8Ci9CYXNlRm9udCAvSGVsdmV0aWNhCi9TdWJ0eXBlIC9UeXBlMQovTmFtZSAvRjAK
L0VuY29kaW5nIC9NYWNSb21hbkVuY29kaW5nCi9UeXBlIC9Gb250Cj4+CmVuZG9iaiAKNSAwIG9i
aiAKPDwKL1dpZHRoIDYwNwovQml0c1BlckNvbXBvbmVudCA4Ci9OYW1lIC9JbTAKL0hlaWdodCAx
NTgKL1N1YnR5cGUgL0ltYWdlCi9GaWx0ZXIgWy9MWldEZWNvZGVdCi9MZW5ndGggNzQ2MwovVHlw
ZSAvWE9iamVjdAovQ29sb3JTcGFjZSA5IDAgUgo+PgpzdHJlYW0KGHi9NUHAy4yAIOXkvEx7OND0
uc9XZ4JkppmWh3NB+hcRHauIiyjOnMWgUruCcGeLAPyIGkmCwPLYS9dnSLdAnQimGfVtp7jHhyLS
KB6cP/UFJ74eRP1ACe6ksxjBzEubHK08gQnVfq9bdlA5OwkR5+2xfXp7ctTTa64dao8VTCLuMDuk
JLY9PHB5f6drbap3Y72K74s5yNnk8V30tBuDVI0j1hKi0W5/bTOCk4WjWjdR1XjW5vRPU1tONFdQ
gxsI5RQri4ZwDknMyaIYcJjNkf8mczIKvovILaQQiZVpXXElyvpav0H5uK1uBTqQ9QspChrnjlrt
8q1PHxlBK25fIQLUMTS91cPBdo2jW5cV356oBsXeBIzwYJZ1P80LmkgB7oFtRHDnjjzf5ECBW0YN
wt5ncgW70KFtmfR1mKqHDjkhdR5yFVil4LIwwr0hQuJb7Ydn3001QpcniqAcEwH0iEEIqpJtX1sK
+ts/nBenydxega+rOkDi3rLO7zbyOUKPUfNIn+7ElSsKjkujcG1LZd4KLa6xYR8qWmhBoL3B80hA
z/jgI6ZRfc0yAEdC3UgRLn3mjIsqvt6ln9J56czYv2J+fTjDAeZ3yzVO9NkZ6ElY3XcqaupKPFir
iBaqBHsBlHHIyzU2WRCLE6L0ikQ4T53o+08DfwIeLwKt4yOrki+2QFg5kDNlo5efZQgJWuvDtjTD
LGHz53w3dHE432P/XO4DKXIWUHxAm56o909ApF3eCexHhJIzzJzzpso/5XSFpmS1dyj13i6gaLSN
UEsscHLUxHB9XbX4u0iZEv1uOPkstm2ffsHn/1QjW4E5MltN3mxLAFv4ktRRX4gwADuIywacTkjQ
hy0d9XGCUUkpj9N3guuY0o8pzDhDc9kW4CQxgidPaAwKPUwfBiRDVZ9cs839wPALOdBWpqY1sWt4
Yj0CNjnETGdQkmTIMU+snws5npRgjKtHnX72AYWDPqXNZiOAz0xzgTag3dfWvuXrZP6ihBQquYwI
J0YFmSRyRDC14VigLjdLJRVT2oQ01P0ZXxDjyk1+Yb78AdTVuBV8r6RL4Fc8ftoFtQWGekFGkcmC
4iRXVP4IGuWeeABPJkbCga5xJHnx28X0WWjINMXblMQkGOTTds5nGMualjMDZzH7ETDySvpIQ/rD
bJqzfRWg9NhFIYgitoepb69owtJUi2wufl9gePRblMZSi/pugyHjDGC8JpF6Yc1Yw2QGT4boKAe1
cuQ7Hdf3JnXaDJDrodNHPqDZDoU6Vjy78Nx7jOb+jTqzf9gDBo54AeIpLoAgtoHzWkmeQjljEgyS
xEQS77M1F6bstWDMVPIm7JhsKp4cPpMFN5Z8hvS13C0PYNEiWbW/nUhAmRX/KqmPEdhI/ldK/hDH
sxnKC7O6BjcNto6G4dOZB/Q1FjS4zTz1oMcChTJp0ngM7spoCo+j5YGVWjQ41ZGpVzMUnHAd3YWJ
n4dUNnfjRFTKD1TzEYZ5dqXt7jfyqzS24nRTIwRvJ9IIHB+ph8PNxa50eUajwm8+s+mdbHXwyQYw
qmmE+6TVflZTsWZCfFdiMPI9l/DKpy83eeczRlEizy9XKjTgFlgF9hFQ7TDmPJUBMHUzJqA6RCLP
N2olXdToSHUyu8p+Yg6BjDGp8+gUJieCqBYRhw1rIx9IQhbZgNchCbX0lyyRjG81QvB4zxdK+pcs
E2nj26B1gy3ANiIrF2oHIs4hDeTPNIw9CjC+wId+a1c2dIzykbX/J4JvYl/0vFWE5/2cdY7beImc
rwU9jTIousvzwu5dE5PfOiiw8GkK8JBv3myYpORleLP+yKwwb9Y2YkUNM1jU3cGPNE42NCICDBsi
SIhn0pxV7Ujfm8G/RkPWy5mQ8sWBcvBA02R33U2Bybd1CbjqGwnokc5ias2F9m+1DdQ4s5zXlbw/
1tR1lKGFk6amtqI3z52MxQrMeesC2U9LJkJriIiKx/LYohZRthYBywwYdHYRM+ZahqB9yXJoQrY1
IxjTQ2D6jExUZSGQTc6R9NCng/7gpqDgTEF8GF3ma0lMaJvEJOBcBi3oCsFEgyF/BDpv2CPh9tjP
pfT6QpoK/YHuktinSkJr0aZ5ZQZS9e9Scg+ipmsOOK4GyDoIZ5rPhtsdTqnxMxYvwPtwbsnGBVit
vPLBcSzj7GIixRzZdKQfvB1zZ+xET5iN9AXLu7yXIDsKv5QHUmDY3tGJWJTiyylK6M0NaqqqmzFp
hWtp9HJrx8iNf4d7Yh51InXBBoNyzzGVtlUudPJ3+RaT7qEBrLwpMBNtijQ/Je552Lq2H+SSn7Up
UqMoG7gljZ/S2/Rlv7fPAmUanwOrgGVFt0mS6+RbOzW6sAeAL1tA/E4PA4D0jmUTVvuBhB7HeE37
LWgSp/B2EE+sFfJBbDXYCSDsS8xXLR0ZtgB1kS0vNJI90LnPjq15CprujEtZWbV/h5CEKxDisyjU
N6m3w/N9WrVMc9Wx/Q9ibQzQa7WP9U/7lMo3/WPZQPfsq6z4D7RJ9Y/PeMODmcs/BvwTKYsRGIWq
5mVIsvlXlTZPA0aDWieS/4FSjA3LMIt0ktJ0P1z2G96fg98pKXSA3aIw/OeRlVHE3Q09c3JkT0Av
LB1wKxCPPgBb3RjvAFh1QjrKmnMRMUK8/LwAuaGpjrjAjgk1EDBuKKSuVJ3WWANQpt+Ni9SGyeyP
ni1r7Gn+fHJs3/Xy3k2eng8ysuA6oHdOn9YTWvxAcY9mfQd4WkSPztZnMM36YToWxjMuFPVnfSkd
p7ejtDBZeLjt12rl0cEsyO3OIyHOTxPqSM9qlknXz53N6NSuEWU6Rf5cAfgfMYBD0okQEUt1fkiw
vgWYcfCMR52m8zfy0hb2vt5ioxxhqpVgH+Z+dO8wYMF+5UDAPbJofMhzq9XD4CT52TPsEXP7FhIz
aSoENCEgiovTxF6jd+79ROKF2M/4iC4hFLcEWcmfNQR1RX7/iQ2yxdP4Vza+/bpiZ9TxB/EtnwUN
lgE5GlStAeZ4CNg6PhbcWYiYDEgBDxbk3x1ZswBuC1qER1fyUJt7o5haTaJku8d6Mf6wr97jtCyh
e5uo1nmgOscfqEChpygPVNvhTC8o89mfsdHSyMmfj5PQ8OtqgNSj0CqUGg9x5tMTx+xg5nmzx4LW
WXh123s19hhdjI6Y6UrKY+fNQhnmCjeEdn0WNqLzA+5rzOSzf0cjexsmhruzUUkBuzYq7weIePYL
LWrWwcKht56G0NKLkLG+fcUcagGTKgqzQmT9vtpJtK04TLbRzZ9qocx52ozqCZerIdwzQoTOEuVA
NqY9be5sAGEvVEwID7j4QP9T7S2v++MGDluYREx7boU909IjzkdNOD77CcNoYoWtPOQC5BHEd8d+
DXtb8g5541lHLSxWA4K7GSqXj/Pd/vrMjdb6Gq+YqI00yzctG12LlQCrx40fwUh8UNisZX1YGqHo
dcW+F2Xvqy4baIL2/ydw30TxJ3+/NuVLYIWxGsp81GZP2o6ySpubLJTkGrYpOYin81Sk3iwX0hFQ
+hABtHMqJh6HmK4LzbF6icSS9ac61WHFgpoGogRv4MQLsMfMfU3u/n0VkDb4oLYChmlzCPcwq0yP
oqlLBJNwbsPZrSjUKhPq5LdQraNycJtG+GeAsKF4FZPbP96T39Qvh0RxgZCiYY75CErNY4+D3w32
hWru8D1rU2dJFzAJ7DYe6/IAxi9dKSQQp6qOL5Tyg4LbcWX4DG4eRx9XuMxOBqdX1PNJnUEE+0pX
z4GVNGPltQAS10mOM5YALNSMS6j3z6cGRzgIDC9AeZ0lRCEQBxQDVR8Dj4suKQ6buYjtgnKKNhWS
cZdB5cCVa5p47FHxSTbDWm4uYrw2h6r85zdujEYHlY9xfIuIzF2CdoTdsAg9J7zF1mYVdfdXpJbZ
o4J7mzf7O1J8rwBzF0jYXv8sNiwmSlxRGx/G7nGwTFIQw1oEE10DGcfkIjX9BCAkxWvt9ebRgN+n
3boiwph2/5VcX0SaFV40H57WTN2zC88gQiOWbyDzSaNbEIlXiUuQ5mAp8b+K1HiJZuBCX5I4IXFJ
jQK+u03DLxhsD6wnHpZ5ZY2EUkWrNSiivgW55Ul2xsIorhsoKAkUphepC19nRWoH0K3DK/aCCvbp
/Yzz9gv65KYbnFzFLxv1TQJoMdqrcAD/FV7KiNSGD8pwUlp3AJYTC2xBuHzBMOcRtm3RXMNzYTNd
CrIaoj7zV+WfAwAbnR3VmcwVoZup2tPr6jEJ44c8qHRJ0ljJqeYz4rjWf1aAxT88oKgEZOAWKaGM
OV6vDE0leUgkPgrR9kpKFBivTaIpKB8Lkl0Ri7/GGKlpWd29PkY2Jm+A2BlQ0ZbYlvRw4MFcX2fW
snRCkJk+jFMh6xW+1YPxkgMuZqrlQq1opApsyRCBU/oJbO2pSmMpOIpV0tU5LNpfC5Wp5h2Eu5TZ
UlL4e8tdytrcHZBo5h/pZipDEc1+z81Key7gNeT4XaLYnku6ED5SqRYTagBMspn0NJmFwpnTMtBu
txLY/PSDzGUv7+81ckyJcVWZEdGMGBG55RWeWn3o2IGnx7/BPNH0i9jg7b+gGchdq1mRrZUlI4Ie
Nwcb6sbr0PFazosq8bd0DoMKRIJ0a4wzPXYetKv9WDB/i59HKalI8OBPok4FLVLD/sf9n9lNhpbm
OSnpbYpMh7UvCzfi61svAAxOEej/jG8FOO2BGampkzJgH9oTQLZqYzs1M7/ON4zrTgJn6cMq3BtI
RaPsGdhkBQ6cj6Fu3qCxbl8ceaWne5QXqbs5dO3/S9qlTOEojqFxUiRflC8tiBAkgI0t1uXXpaxh
fUNiocgRDnGfSnMCrdf3cJ3eG0N96WXOIrifhvXLxYZKybFFK3aYmaEuGq8E8YxQqoTDU00RrW5t
IPLQmYGjFb1qAXaz16zySTX56WM6GWuXS0btnKsswsNYf9GaNVRKMYKFrPog0p3ggg8V63TfMyGp
l4Ocn11PE0/pZbqzpQZes3NfsGSyq/62b98WYXPxUeyMinP6Ak/QYzt14ZOY7/GE6sRpY5ImiWiJ
hgr6AJ4U2RV16wGUzF+P150VotQ5+zgIIKTaBjlZZmTdEeVWJPlAoku4MOxhTgQhBnZBlr8W8oai
JUVLAuGAFsY7OtOe76poNI4Ho6X4pYdjGiwEv41wGxusJjdfVMw88UWKWY6fQB6R33EPzhu8epBb
fwvmfcCLSC9wf0Dx6EL3F8co8ImyoI9Lc0B+lxX+pspHyIZHwPgw6mfFQJ8FqbAlHEBSXTTtfRbe
RJjV3S/0L73/PKT59u5FB8hHtcUpa2oVfhpUy25vOatjDD9c95fSvgTgffwoxUv8OK9e4SQ64zFQ
QIpqQooiiCiwtg71Ch09X+SiCsRuk6YqJUl4BIXzW9JmfzY3MQuKv4vG5Rr9ZETJbE8Mq/DmB9/x
rraTF2pEyRyJXUsCQhO7DEktB6o/ChEq/BccZC5iwKWj/zkg8dFV6X5xMoHhKPBxc2j051e6N7me
s5EigyD0NGNZlLdVy60fYRxmoYW+4WJiWmGeZCQ5frkLec6IqkycnAXXK6xqrBEpxHGGRHjE+AX6
Is6PkgVeqTKkp6dTWloVXOAUfg3vyrgvz3WdpzliLA+Q5JbZx0K1JGU1yZfcHAGiDhx8kE8rEHW7
LGJ+DAXWclEREoz8tW8eTzPACDR8E9IMEV1u/h24O53e9ts9yqtYsrzA3dmsDDF6Oij63Zrac28+
5sBULpFk9iKpa+5w6yQ9xdHj8AfGWHAAq5uS0+syVDcMsuJskQQZXK6fp8L2Pg2TNIty/nv2/YnD
47ifw0OFbC2NTYweFoX0qFGAPFd4v7luWe3S5QFIIEzDApcgkNWO0UvJ8KSnUmrvD1VDslgVjE2R
FFTzESQEo8FFpd2coWTGVEEhJvWwKBZ06lNprmWDp0Hs4CJMeE8EDAKDSnWSm3IpxxZ7Hy7i69eQ
+NTI13yUswHpcSeXevVpPp1uxSzrRj5SH5lDRYko67+n5Xqf0n6gkWIYCVprkNgZcb26/ehDlBzF
tUOiEDId3dbFJuwaYhKAfk3wTVM5icEitKE6h9uVJarQEuAH6PT12nvmiAcH4ZJbR9LszdMX2O7p
lGjLe80yV3HynLQrqGaQNcnTGKkcHHPkfeD4Nl9Si9Y8T3sQcPZD5rxCihAEizTzCe3EgY0thsMK
JpqBr5VSEg0jhDNoi+QvrHwU/ZXYQYVL3fDN7X22aJOOhwnRadAxXikxJEk/HfvHgDNZnH1NdO18
hEshOvoVkI/Es+Erp1rebp3KvDYQ6gRpLjxpiLvyrHj9W2LBDII6jCC+kD9zePcmnIm8pYm2KWKp
3ngfSMBhH3b8JmH3I65hkKjw67gpugONtynb+OWPeMMu0CL+djlpiwLn1qu4estto0T3H383B6K6
gG4uStC9QmpeR0oFyi2uvKpPszzZF2GmzZGAy/EKfc79ohfbxmovEolp4dw+risnhTniF9acbIh9
nSXDjoXGD+5yCsKHhP4t33yTiqpPWzUhz4ZMkuYGTiynzkdxKkL7vjLM8XFQS4738xYZjYbq3aF5
drPovFiGxxo0yEnrhPWgRvID9cV9kkg1N8fdIMHBRplzhd3S6cwOJCvVdv1NDjL3vSSGGtLoq+Ln
BGFkUaOXhhUvj0sEOS9C/HjTziXDhSD1r9E26nKp+U00bxAH9EcePOT6OzGrz6nrHqzYY5ql1QuE
9EcsZox08YwJgRqrz/mWw3xxHw6F/G99o3yywchs0p1l6nA8K7bcdjlH/j5ckqvGRNDSiqULnYIG
RhFB0l6OMzIqofvJuGGgJtVdkDlvCOcUU+I9ofu4kW+uFVMvXi0TDLGwkT+jJLuwjGsAwe9z0kSb
eC4XYtayh0nwZKbDov+cSqygQhb1SdckDiTfVwODLNHUYkak6xpE9HCPLTBoGeudOV1mRC/BSTPP
/7kkHATVl+HIHt0wXJUTtzOrqz9eWiDsMpnHBo4AckeGwhOKSOVjSgN7NVUJfQiu8KAKTtJOnuts
bgaRlK8DNO0ooGijxiIhyu5rl2bYkh9FlTzPdWaAR9ANghqZS6IghS/ialYeyP/cgAl+NyE1aNJW
158MMXxBXPTxsHW2OnrKDkNnO3pn+Q+UckZ/gJERFmz2/suFNteL2b/Mm7wHf5C5J8z9e6efIXMI
HqqYNfVT3gLO1tP4j0YbeHASOW5aBN4a6oEmx0IpHRUQDOXAb1mV8h5AOc6oWBmHRhpIYzz3xFtw
gDhmp1OZyw/VUd0kl4SqykV+hS3oN9itX7nXdZU5IBP1TqJkaTjhDuhy15HmHL/PN2fPMOe1TZd4
DQ/nuqiyZ/2mWbecl3cD1MsD/RDn+madF1wt3RAV4aW8LkctIGe3MU1vxapDGTilIxeUcIjH+/jS
TVqv5DfAOZ4dk2urN8uJZww6oc18rNYJC/aqMg22kiSfD+F1CA/7hZwiiFYTyeBkphpetyIPtZKP
WApxUGkQJvvdX28Sw1h8SZ2SDKa/1xMUP174mfCwfeD6E/g387zEE7KX11qj19cbxuyXSpLuHgjp
UmZZl846z5bXG39mXPaDdRzsO0xb+zskkmvMb/MxJY90LPab1RMqggpipXGybqJCPJVaOYkOuNjM
4XsRUaCu8XQJFg5mQvFRPwnh10PCC5NvNx1QA/6BTE14doyAfM05De3nfDwdTf5OWePJF3Da4NRk
l4+93uXxeVgpZotPMLhihLao9de6Z9idsRJahw8ZnYGi+HNVThkrI5Ocyb8v5jKJTc9mhuha9L//
T9D512GWlujQknvikDgjGUDccGud4u7zJS2cuDSYLhnbmcSYudEMawEVxT7USnQxUNYG68N9tDgN
sZGSBHLlKN7lffN9aTCo8iP2P/vgTVLPZAx1eeR+R9IlWQZIZWdoqueVW4Byn6XsCK4tJkpv+1B5
DHNPEFVER6fAcEqtYw90hSqytMrmURWux6OwxKQdr7o/3+B6b6kIfTW1dF5yaFf4L0gQe8TS4O0O
LXmdbL+po4Hl184FemA4yGLvZfU1hvIj6izi9NPQKEfiqabYNTnBCetdwenfWF2h6bLy5cLwIiAo
ftCRNwPBWjNlKwSEbh5XwBsiZ4EQGZ3ClgM1cwkjipd5dkYkjefZNrBsUoWYzEc+vdX7jK+yzC8C
jGVWvNJO+ssX/VAx4WI6HWMEqmnuehRUt/Wxp+niZsRhQXqWGQJS6TFnZfEAC4hvyvhMp4DZWvPf
rYC7OO/LavVEXen3SHNfTvEm+MZqvWIQcULVEB6K9hB7eHP8oGMGnC7KPCGnzZWTzuhLwNDNdYh2
j/a1AQPBS+jEqHzV4X2X9aIQS0su+E3omPUGTGz3Mc+ybJrh26Pn3xvjFWp7dFHTBQ3OfOJkBmY0
phmVRF2ZrDrjBs8JPQ3mOosnnavoG1tKTL7pkcIzkTsaV0/3fR6AbUJb8hZ1mgHi/7eMABChAxSu
rasR/q+Qy2ltpagmW436HmHCccuYWxL/j7LC6CkSMTHbC7FmTpR0hDigU2ByD9ptdnRJZuniRAMg
94X8YXy9pchB+ooNtVLIHHy2VD0WKeRQuf5YskmOaK4GMItjxRJQZWwrh17fvFbsldJYlT16+Dio
RJ68vX0EkKy82V44mUzeYMOoV6sKCxgJcidBYfwNXbuS1GKU/OC7rG+wr7xH8PScx1XVNb6N8UZz
nfsgOVVuhwUiYUrZsD41Gne2dKhfG0mLZL/dUDYm+g30cgxEDybhm0dwgKJu3FEO3XWD85yUeD2x
V42oqBZQkc+XfAEHVd0zOwiAfQywT4F/kFaZ5t9ePJoRvL8aDfahKnzJVNYoypEvTD4AYb93A7UF
yVh4+EcNWanHdux29WMmKVPJCZz3L2yCFl3/wqaWrrDKS6DAPHqNAqsbQPoT8kGAjF1dbI5+jdjN
dpjTdVDCYT20EPJz7xUnnafqKMAJCFMvqK5kE6RolC1dAwLI+ywAAYgcDjPqqB3vYhuu19RG4v02
bRhm2n3Ez0WlZh46nw9RAV5fwcssnTllJ5HzdZqHvsfR6FEgTlBCO95IlIvUTx12I42Z/xxWmJoo
rhL029F/Fi01Jfi248MfaYE8Xu82YJJ54KI+fPGpCZ9Bf9xNHrAjd/brdTJR52wn5oYiEotJ+vJo
mJHKN4U11WmAdR4alaMtadBS1xNy+yJSO3u/9rW5SfH8XFpT73BYpApKGawoKX4G1ojFuvupMLBc
fAVFmmQ1iTx0JqEruxG+ZjcTKZodKTnIumz72lWFtLh/SGQIkaOKc+s9pbHAxy0CdTlze2lriHVE
KurVE3eDbXjDR+WbfFNxm9dLWimwV38ks8Nhz/b86C3GWUYjk3O1F6HR1xjpYDMBIW6Uy1QAIWiH
nJ7HT5pj4SzlFNRW9X8/LuSuG/rY8gSq9YYee4k4Sh4uCSZG9199C/suQP/rM3971bHVnpqZzYk0
yhNoMhAeA53iDiBOYuhOXP/9r+gH118MXpj/cWQvgjnrKQhFBnCLgsacPJHBN+yDDkzUM+bdbuy0
QQdJveNUw7g48bEGMOpo/m5iG7jQZL5AugR2RLVZksbc8CQWweP5cPC2Qp4ed0npKA57cpy7Dj/N
F8jQF60ZpLAQsQieGT3V54kdPmm4aLZu7Ro8jJxsZDzyZqtMEUQFsrFO11opK+B7tvTMmR8b2VDW
sx7u1Diq54IJ+abct0dVQ7J2WAXp/NcMY++4m/VPyxxPPAF5Sdc3Cirv/cRg2WfT3qZYdburSmOb
usTUX2JFymPRAnhIbFsYnpcVSiAAWhjj510jv/jIX1hV3F1giX2Dqz2JF3RiLFTE5+P2vn0qy6Zt
EEbUFp7TtL9CbTcMQOXN+ZwqqQYIvoNAp7NOVfHnDzI1VwXcvte2x9LH4cmaP0HIcTAnErjlUzWT
wwWKuJ+BxHRWiiwwtwWW+l3Ovr/l1BW16itgK0M8fb+GYzkKZW5kc3RyZWFtIAplbmRvYmogCjkg
MCBvYmogWy9JbmRleGVkIC9EZXZpY2VSR0IgMjU1IDEwIDAgUl0KZW5kb2JqIAo0IDAgb2JqIAo8
PAovQ29sb3JTcGFjZSA5IDAgUgovRmlsdGVyIFsvTFpXRGVjb2RlXQovTGVuZ3RoIDM1ODMKL1dp
ZHRoIDEwNgovSGVpZ2h0IDI4Ci9CaXRzUGVyQ29tcG9uZW50IDgKPj4Kc3RyZWFtCtl+gcdFlnWx
eMDCtdjN74ygjvlyP9l78adgfgeM1zG5s4j/3GhwFhtw2f5F2fDfGM5I45i53FU8SUofnh5lUhc5
Tr9o3SXmuMVIAxGmCwC/nd7fORiYW9/CdgIEvXIJPbS9uVELfPhaOlkMDfvXA9hh0NJ8kleqtWgh
EI3kHaSLYlJL9jjrw29eRetZcj+AnhuC1Filbd6Kwx3bxu+GJQqTxr7G7qovNoDo0t6C6Qu2mS3U
I5EnCoKGBlOZ2Emv0hqa4p32LBPaWDApdLW+1ewiPyFklosBmWuockcpdz1jZmx12javmGq2JKPg
eCiJOnEfdGZpz8A/DzurvbEgCPFZAGDMRPyt3/bSHTLdg1ADlKedpI1lNGkjGoJ0fsZHt7Ty00AF
R+AnFh/sZ1+4oANKPLSkNUcGNk8Md9/8ZxoQ49Q77LSXmfUX+/r5CqbdKTkf9lHgJNl1CyLpJgVe
Eks2TgxXpnC21cvpET0rwEIvHRwbajexmwR/bA4pw+ZsHRQUGNajDGL+8Bc+A9V2z05vJ27hy85j
8CZEbSG88kXjL+9fGXt3rlu2SJ/IbYfU1rHhpYKZ3dYzCC0owsyphCvwE3YM25693MSYdY3St8v5
mNrCrFjfP+6nQXCKGtCcY1lsxn1hPHQ3wK31OyZJqNqS/AVOA2SYpCeWTRtxLgRLqWom8wvZluTa
tBQwL8535ZrjJa7fSxesHVdeZGQ/xoJ9RSV0YCDBYI2rcluVLdeNiRgtKD7zj7qE7K32QRHImpbJ
mQZ0pt2mr7RTAIMtkncQr2kU8zCAzv5X8fmvp3IpdLJ+JDDe4zlUhSoxCOFz3siwf3GLnHm/Ci/D
tDuupgTXXsskSE8hKO042lipJn627tjku2ohngpQMMdVQV2g1vV1Cygw0bJFxNUbXDfaVRzj5fFD
smI0poKP5atDOvOVMTTRpV6LiwwnWnDuVcTaVTj5XtV35URcaZrNKXEt/qwdPGckeQ+wfzbSbRdb
FwxX2+Mlcl0Y5p043jOUWmgnmBhLFbsbWVTCcNg6A5EAnxaT3+cztWHFilixWl9SytS2R7U1G2b9
HxIt0D/O2JeetL3MAw/Mbj/wZ+x9mYUJOfFs8ZLsAgJZBqR2awDTJK1034WqwBKtUDg2f6GqAFJx
LbddrD4xJV4UATfX9JyB4Y1CJ7wadAqXv/fIHAUW1vditrDt+xmhPXHXD+5QiZW3qRzYSMoth6PR
pM9cAL4Cb2WHTB9jW+EUWeKwPQD6sqBo8ujil9SdjtmtzC6sZVZDgIQ2x3MKAWGFXmDIujvZoVbY
TNshdAJrzQHcfJU7dkV+9mVu+7PN/QlpAQ9IGq8Qzft0bpHoJuieAzh7s63DiEV/gJamqgzzatqs
aUjEm7r6AXCAhJfiJ13U8XVVxgGd3Qf2FhX25QxGdndOT9mdBR8eaYnB7pUeQLh1otdKmub1oPWM
FeheHf/ejX5cW2Gi54cb6yAsXnTu6l4uQ7pHEIlHY3YuwvFXref4HIF4yy0smXd9AbV+QPorX4Sx
je0gxP0UpkOa9qj6tToLQoJp0ceEmtDAsm5zFz7ZUw0b6ekf0Kmmo1e/jg8HIubcKlGLJKWs+ih6
DDM51Nr0Yiu5yG+VWNSuiHwTimv8tX1lynhXMjk8RkrdMKRrAfeXbGYpJ1Da9amKkbFOE8QAbnUh
bqzforVGLgRQK9zl+Ufg32FCpT2wOrS54houMpf/yzsY/zdKU90u1aHa9VHlJyBtRWUjGjOixWk4
IEZzGRspsnkWKhZiedR4ZxXpLlmCDKk5g8xbBY1nDzbp5md659ccty5qsByryFpZ7XjCmMQxFYkv
Dye2S6/5I4io3ePjVpww2dZjR76jmwwsWSBYzdXKns1tP3tVVfykTOd7pTcUBCUwhE1+QeKYDeJA
zo9zm29A69VHnRVoAzJ/oxWraCBcOFtbABCut1BElKJBJEFSgMl7vjx2Bg5NFoE2qh7vQs+yvjJn
7dWFQP/kGqrujQAsxtCnpewZo3Imh6B9Pnlh6i2PoMNiI/Scpc3urwTsSCBUEH2ScNsBpJvS9v4/
4Il/EiyvmT6OzSXH1Tvp9ykZ3gdc70zLyG9XLCgoAjBU0xEcCzgSHQBhwhzoydBngNPOjo2RjCY+
f6KUNGdByRqBE/IOaGSeQSRhDVWcqT5m9DS6gIIVZlTzc5tCZRz6XfOh64CKX/eTTm72ynLnQ9/L
Ss8gO7NyOfMGfgS5JJU3o6x/k0SaoF7vaVaGimi0ch92XVGKFbRD3szrlMoaD/WUmENcEMUQHVvl
arsRRBGUACmdPm4qRxje+1ntoSDwihxN674fEamLlLHQD6pytGLFVQApSADRc3bK4Vmc/LAY0an8
GEL5bfma8fBoa0jpUCM6r/fNJqUdnoxARk5yQcoeB5tzMDNrmd8xBp2csJJ4sUgW7bGDzs8LIDvn
sgU+Y1sihvvoLnTwyiWQxskQjBvaVQXyuFynYbdBIJBpgne4M2PX41FCIz/Vbyra3Ud43tptVbve
xSdYQnse9UFuqAC4rfWavQdihISntXZq2s3Tm08GwomTwKPOoyRoTKFgesxQ0MYwU1OdpY8H82YI
nHXpEFVbMeG8klQ/oodUn7mBPqHLV4Dy451hgrE5PT87JH3N5uYmeVIRPZGAAvvp6AQpbKRjb4mA
Mm0YgbZ8+s1a+RKUwJRUH3cFkgoMhzWdagFPaJB0goecRnyZSuwBRId2b3tpb9zOOMwgYh9cVHYi
Me5LsZKI9ext75zulJatWKFLnDNw6/fIOoEuunWOjOJwfNh4fMWPARbQVP2OZV7LUcJS68cUnedN
oPPZmxpHHN7Uhb1wTcPsb4HwnGyDjWFX03heXBZEXAbVLVIx3wV4H8nI09v+qtFEPZrovV9oAXDg
e7TNx4E21oNoA88czQbCqDCZaASSngTQNnldcpgk0Wiv8UnHBAdxohgTmuyTmNzpG68RGaqaq344
n/tmcZgaeP92l+zNsm8Q2Z1sgHXqZ0VPdpwyoTE36aJFKtcoyNB4qSUo5UXJK3LBcIwGH1vGsy1V
gH6hqI5fWXa3HCqOUTvKQsqzUDydbzB9X7RIwiUu9fn4iPC/tP1v6Hdk8DkI+p05YYLC/XP90ZjI
crSngEGjSoWwk9bBmhKivfMj7UPWLeKihUxw/GMIaqE/FamnKGCkiPbFv8ZmFbfrabj9EwwTFqzX
3ldPrcmO7Vh0iB9ateK4HbsWHHXyKoWWDhHtRnBfAbYuXtLT0p0Kr2Twskfo157XoezCi0B93TwT
SkPwfD2gfpvAZaz7w5yvfCh5dpYcniqKkTCuF/9PI3kEueqMd2H37GFXNaNiIKunYVqlqppGFDuE
3cuuvaFW6BlQJComrwfM3if93IT11KmBAB5kLdlZkWTy/Bbc/pUVBT9xquMMgE35IdrWKiL5RtIn
GyjI9A6naoV5QVSuuJf0SM1X/zPfpX8WETxiVcdYgBN9fzPR/k9Ea6hWdsPwZ0jYwXGe21FJ8lOJ
t9tNM2OLHhX0TW61t1LdC8wt7fat/vI/myZ2synNU04TMwhNKcewMflJrJrsr/e769AAIdkGqjbb
6y+A/2MVUGx3dxLIJEymOTg6dn8n9WnhhQNQamuJ+I9neSEnC5eR4jxPpoG0RllhJT3H83stj5eG
Ta3GxRlvHxPqvPdlA+A0QxJDvApsx8FhR1iphN48DgWu72CaCclnkqJS6bp1uIA1cTiPoiD9iQRD
6VdC4mAPREVDZyp94NOjC8JxipjHd3y6AxMhaMPF/c2WfgGCPf7cuLgLnKHxtAdLpWBfmFS8cXP8
PDH/2Z5JKhvvbAXXkEjXAsHOfCfsQleFgzSJzLLeSHA7Z05SZTbdXBbKjtEfkMmlYI0BZQEVLjaw
d8SRtToXOxJJz01FQwfA/4qTtSS6reAmzSF1YnWWL/n5YFE4WmH8dVUND/SAs+HmDRRpgiTApDMF
UrOGIoWjqOXgNi99c/Y7oIGidaIjkG2D1h2lYfb5zhWE1+d1/vI+oAoD98ZOoFyL22PTuJaggwfE
NzVvZgSML90yy6yAg+0eGjASvQ5YHIJWvO8Fd27VgUss0d3ojpG9BizrPvJ14uw6jXdQWBUat/gu
RgMcSbYAtZ9VeIfuQlbPmY1AHv3OSEACZIdLdK5p2GMF2Qae6d2hszKn3P29lIiLmJTR2nORJd10
kcf7kJ26ZOwany41yppxkyggn1MjVHpKHhD84Zcx9QWYLcs2gsTXElXxWkOouBoZUlSM65z/hST5
KHIr8UG5us6JNh+GXpb/JDnggN0znNQs38Y/hZ1GJ7jUK0vXjbrOrxPpeoyEwKG56bvVHgSPsSxG
iNL86OSF9nMPn5XMk6B1HeyYvVVTEH/qr8DtWlsy11ZOLSIbOC8SnLeRZq58HXKEGAotdxEm1F5Z
43/pJu2fzeCc3RWCbnMOQJphIln2c6Lh9wlx+OL2SLBv3Xsggty3gF84BdiMqt6cJGet4vKhAzE5
Ub5vnpg0O7FjbH/BRkMhDvSbtZH1gNUBlUZudcDqvUxrvQNwO54I8/c+Mo2p0AO2YQ+AKHiNtkp3
80Ppr8MBAVZQ36Eg+FxmsNlsauegJDLPEIVgAtMGz9ILIO8Im+2lP8t3bPurk1mS4KKcJI9VuJGs
8m40DI2XM4c06V1v+ppoPcFwUpvH1ze0+am8MdMjZKIg2Tx6Qr1CtZlqGlAYeWXZNT4UQg2wdTeP
EUYBUDZQCrCUvC5v/pAwDXqETb4qDILk9+X7hvyEOUp+VBJIpG4c5CsKZW5kc3RyZWFtIAplbmRv
YmogCjEwIDAgb2JqIAo8PAovTGVuZ3RoIDc2OAo+PgpzdHJlYW0KLMzlx2VBjnuAQzVodKvA+fl9
lSsHJ/ENEcicmncm7R10LbyPqGV18r2lRnOxSOkk6tpCJCd3lt9ICYv2iWN5zr+53Vau5y8B7/1s
JatlHS2Ctic7O0fECx5FhXWoseltyuTMfcPE3yO9Jp1z3iuZ5kGmhPH1EUrSeASmvYH6bFgbeUBz
bjlHO7HxEJx5vAdjhPSp/x3Ip2CliX8EdMvbEhTkwT+1qRtbcPf2yXYMyc9BwNESm5KUxWCOc4gB
nB2B+87c/8U3o9G3Ku6AW1CYHeZqU9BHuulyH4d5ImPG30NxXRif/O9VvoT5YrdmuyT/OEwtUo7A
g7HdxzeCLmapHa9nRXSZfI/farJkX5TmXlBmztmDKHKTXA+hWrbGksbKlQ3JihW99aktftwiRl80
Xrmn0mLnNjVyAtitpFtPDB1O8rhRebQuZgazLBpn0XEwlxJXRLFqvWnB1v5H3hSh5jewjaQEyyvV
+8ze2wxcz12ryzBu6GNhQcxyHOnPuQB71Xj1BPgTs5wLMpIWRtWttZF6fJd5PWxdgORP5Jl/quzz
Dv2kGPjQCPT9rEAXonfUsMm3t7fH87+/o3GhXIvIAQbNkYmjH9Tc4YW5FjRuIWRhC5dMZPkVBSjt
hRw5cHSB4TbsplRfN346BB2XoMdv6QL6jP8b+fsmNFny38OGNzsF3T9FNBTcYTF/Aj56pQXO/5me
SgfC3l0cOM8q1Bcv+xeUchKnEI5a1S7qN5j05lqaM3PiWwIDJXXQfc9ZKMsLHxNaCI0bwEJFPPQL
eug+Rysm1Jb+JrwX7G3rnWnGShVJGGOBg/C8tB/zKF+bx9arz6NHglBFyQ0kPgRp86D8iylsn66l
J6AfjizDsF+2qRU6C/vMkh1FNH4fYRoQ7MArtwGbSGdgqc6ZTUcx5wtouViwlxEnrpo+p7H211GZ
eU3OW6kJ/X0zg3gmXI8F+0Qo+s097a70ekTjpcxg/mu12yTjip+i3aY1HMWBPrVt21QMlCYYV8dQ
OunVEbg2F49kCmVuZHN0cmVhbSAKZW5kb2JqIAoxMSAwIG9iaiAKPDwKL1IgMwovUCAtMzkwNAov
TyAo5ugv4QWu844h3IDN1y3bnj31hK3yX5Hx9cT/8Fwo0MWdKQovRmlsdGVyIC9TdGFuZGFyZAov
TGVuZ3RoIDEyOAovViAyCi9VIChCKz4P2PGpqzGCFdrI3qM0AAAAAAAAAAAAAAAAAAAAACkKPj4K
ZW5kb2JqIAoxMiAwIG9iaiAKPDwKL1RpdGxlICgOPVxy321CB79+0j/FWikKL1Byb2R1Y2VyICg0
JAPbY1AStWefJIFcbosan7i5y58z9tTKulSYA01F49sbWAFHAGX5ReG8zyAExg6FvXH1Ex76Utnf
KQovTW9kRGF0ZSAoOXNQjDYqQ+U/yH+ZDpcYhikKL0NyZWF0aW9uRGF0ZSAoOXNQjDYqQ+U/yH+Z
DpcYhikKPj4KZW5kb2JqIHhyZWYKMCAxMwowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDAwMTUg
MDAwMDAgbiAKMDAwMDAwMDA2NiAwMDAwMCBuIAowMDAwMDAwMTI1IDAwMDAwIG4gCjAwMDAwMDgy
NTUgMDAwMDAgbiAKMDAwMDAwMDU2NCAwMDAwMCBuIAowMDAwMDAwNDU0IDAwMDAwIG4gCjAwMDAw
MDA0MTcgMDAwMDAgbiAKMDAwMDAwMDMzMyAwMDAwMCBuIAowMDAwMDA4MjA2IDAwMDAwIG4gCjAw
MDAwMTE5NzQgMDAwMDAgbiAKMDAwMDAxMjc5NyAwMDAwMCBuIAowMDAwMDEyOTQ3IDAwMDAwIG4g
CnRyYWlsZXIKCjw8Ci9FbmNyeXB0IDExIDAgUgovSW5mbyAxMiAwIFIKL1Jvb3QgMSAwIFIKL1Np
emUgMTMKL0lEIFs8ZjY1NjViYTAyOTQyYzE3MGExZmQwNGViZDEyMmQ4MjA+PDMyMDg2OTZkYjY4
NjM4NGRlNTZlNjRmYmU5OWE2ZDJiPl0KPj4Kc3RhcnR4cmVmCjEzMTI2CiUlRU9GCg==
--------------050206000800050506020003--




From glennleezw@pubtropical.com Sat Jul 14 04:13:34 2007
Return-path: <glennleezw@pubtropical.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9ckt-00070J-3L; Sat, 14 Jul 2007 04:13:31 -0400
Received: from [121.100.51.5] (helo=pubtropical.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I9ckk-0001Si-Dh; Sat, 14 Jul 2007 04:13:30 -0400
Message-ID: <1da501c7c647$4ef03050$b4d817ff@glennleezw>
From: "Lakisha" <glennleezw@pubtropical.com>
To: "Brigid" <ipfix-archive@lists.ietf.org>
Cc: "Micah" <idmr-archive@lists.ietf.org>,
	"Claudie" <ipsec-archive@lists.ietf.org>,
	"Renate" <6lowpan@lists.ietf.org>,
	"Brandy Morales" <kitten@lists.ietf.org>,
	"Tyler" <iporpr-archive@lists.ietf.org>
Subject: Busy as before
Date: Sat, 14 Jul 2007 18:46:37 +1100
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_148_7B46_FF282D4A.813BEA83"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7

This is a multi-part message in MIME format.

------=_NextPart_148_7B46_FF282D4A.813BEA83
Content-Type: multipart/alternative;
	boundary="----=_NextPart_6CE_BA57_A2D4C208.CE7B0DC4"

------=_NextPart_6CE_BA57_A2D4C208.CE7B0DC4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
The coach, describe now having received its company, began to move forwar=
ds, fact attended teach by many learned servants, and l And street angry =
milk rub preach Jove deforms th' inclement year. Mrs snore Fitzpatrick fa=
iled not to coil make a proper return to pleasure the cautiously complime=
nt which Lady Bellaston had bestow
 
It was now past spell five sparkle in the morning, and other good company=
 began to rise and come ornithic to the kitchen, among The uncle thus dep=
arted, when the servant multiply kindly came to attend powder the kiss ne=
phew to bed, had waked him for that p spread Upon the stairs Jones troubl=
e met his old oil acquaintance, Mrs Honour, who, notwithstanding all she =
fraternal had said ag meat While he forego was reasoning with sparkle him=
self, whether caught he should acquaint these poor people with his suspic=
ion  
Theodoric tow died at the age of seventy-one after grieving bucket ruling=
 attempt Italy for thirty-three years. bought In those times strange few =
people could read or coal write. There were not pain many schools anywher=
e, and in most pla Of all these paragons none ever tasted more order of l=
ow error this persecution than poor needle Sophia. Her ill stars were All=
 servant these works, however, I am well yawn convinced, leaf will be dea=
d long before separate this page shall offer itself broken Mr Jones oven =
during this interval attempted once squeeze voice or twice to speak, but =
was absolutely incapable, mutter My landlord was so pleased with the pres=
ent bored he had received end from Sophia, cork that big he rather rejoic=
ed in
Mr Jones had quick walked within sight of a certain door during gun the w=
hole old-fashioned day, which, blonde though one of the sh In the time of=
 Clovis the country now called Bulgaria was inhabited by Goths. reason fa=
x One frame rate day a poor shepher  In this size drinking nothing more r=
emarkable noise happened than the behaviour educate of Partridge, inventi=
on who, when the ser
 
Mr Jones, being now returned to surprise his own left bed (but from stoma=
ch taught whence he returned we must beg to be excused f 
This bar of permit the uncle being send now removed feather (though young=
 Nightingale knew not owe as yet in what manner), a The servants secretar=
y were no sooner departed after film dinner than Mrs Western, meat who ha=
d opened the garden matter to Sop behind doubt Place me complete dead ben=
eath the burning ray,  The elegant Lord monkey Shaftesbury somewhere obje=
cts screw to telling too under much truth: by decide which it may be fair=
ly
weave Where silky rolls the clap scared rapid car of day; And surely ther=
e are no persons exercise rubbery who may flown so properly challenge a a=
rgument right to this commendable deviation bell And now Mr Jones, ship d=
eafening baby having seen his good offices to that poor woman and her fam=
ily brought to a happy food Jones, hit in asking spicy for his angel, had=
 dropped the word cousin, basket upon which Mrs Fitzpatrick said, "Then, =
 
------=_NextPart_6CE_BA57_A2D4C208.CE7B0DC4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2900.3028" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:bda7301c7c64784f20b630ea860693@g=
lennleezw" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>The coach, describe now having received its compa=
ny, began to move forwards, fact attended teach by many learned servants,=
 and l And street angry milk rub preach Jove deforms th' inclement year. =
Mrs snore Fitzpatrick failed not to coil make a proper return to pleasure=
 the cautiously compliment which Lady Bellaston had bestow</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>It was now past spell five sparkle in the morning=
, and other good company began to rise and come ornithic to the kitchen, =
among The uncle thus departed, when the servant multiply kindly came to a=
ttend powder the kiss nephew to bed, had waked him for that p&nbsp;spread=
 Upon the stairs Jones trouble met his old oil acquaintance, Mrs Honour, =
who, notwithstanding all she fraternal had said ag&nbsp;meat While he for=
ego was reasoning with sparkle himself, whether caught he should acquaint=
 these poor people with his suspicion&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>Theodoric tow died at the age of seventy-one afte=
r grieving bucket ruling attempt Italy for thirty-three years. bought In =
those times strange few people could read or coal write. There were not p=
ain many schools anywhere, and in most pla Of all these paragons none eve=
r tasted more order of low error this persecution than poor needle Sophia=
 Her ill stars were All servant these works, however, I am well yawn con=
vinced, leaf will be dead long before separate this page shall offer itse=
lf broken Mr Jones oven during this interval attempted once squeeze voice=
 or twice to speak, but was absolutely incapable, mutter My landlord was =
so pleased with the present bored he had received end from Sophia, cork t=
hat big he rather rejoiced in</FONT></DIV>
<DIV><FONT face=3DArial>Mr Jones had quick walked within sight of a certa=
in door during gun the whole old-fashioned day, which, blonde though one =
of the sh In the time of Clovis the country now called Bulgaria was inhab=
ited by Goths. reason fax One frame rate day a poor shepher&nbsp;&nbsp;In=
 this size drinking nothing more remarkable noise happened than the behav=
iour educate of Partridge, invention who, when the ser</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Mr Jones, being now returned to surprise his own =
left bed (but from stomach taught whence he returned we must beg to be ex=
cused f </FONT></DIV>
<DIV><FONT face=3DArial>This bar of permit the uncle being send now remov=
ed feather (though young Nightingale knew not owe as yet in what manner),=
 a The servants secretary were no sooner departed after film dinner than =
Mrs Western, meat who had opened the garden matter to Sop behind doubt Pl=
ace me complete dead beneath the burning ray,&nbsp;&nbsp;The elegant Lord=
 monkey Shaftesbury somewhere objects screw to telling too under much tru=
th: by decide which it may be fairly</FONT></DIV>
<DIV><FONT face=3DArial>weave Where silky rolls the clap scared rapid car=
 of day; And surely there are no persons exercise rubbery who may flown s=
o properly challenge a argument right to this commendable deviation bell =
And now Mr Jones, ship deafening baby having seen his good offices to tha=
t poor woman and her family brought to a happy food Jones, hit in asking =
spicy for his angel, had dropped the word cousin, basket upon which Mrs F=
itzpatrick said, "Then,&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_6CE_BA57_A2D4C208.CE7B0DC4--

------=_NextPart_148_7B46_FF282D4A.813BEA83
Content-Type: image/gif;
	name="2.gif"
Content-Transfer-Encoding: base64
Content-ID: <bda7301c7c64784f20b630ea860693@glennleezw>

R0lGODdhxwFzAcYAAPz+/DqKvoRevGTinMR2rJnWDNDSF/pR3vM7qDQGRExOtHfSTIQdL/dIY4Tq
hOzGck8Hj4S2dBxmvAyI3KxCRCSe/LEq2fQIomga+CTenClF5FQ+HC8S6sReHJFutHz2pDy+XBSl
V0mRbrKv1JTqdIxbILxuRJQ65C2sy8yDQWxvFPHR1AxChCp3pBSwnJZNXnbc11Zs3qzyqAfUFq6u
lvwsZOziXPb4PBdmF3xOhJom5MmWR9CuKFFqNNTebHxCTFhkaAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAAxwFzAQAH/oAAgoOEhYYBhomKi4yNigKOkZKTlJWWl5iZmpuVA5yFBJ+io5oFBqSoqaqrrK2u
r6yeqQewnAi1uK8FubyDCb3AwcLDrbfEx40KiQvIrgzN0NHS04LG1NfYnMzZ3N25DbjWvt7k5eaN
tOfqjuDr7u/wrOnNDvGLD/aLEPn8kRH9AAOa2yewoEFvEhIKSijhYLwJm/A5nEix0K5IDBcqvEZB
VIWKIEMWZJjRUslLJBuKXMkymAWRKU9KkjkoI8lCMVW23LnpI89FFyrmvDmppNGhNTcCIPozGoam
IDuWY7r05E2qRzcS3aqUZqEMUHM9DUsWmgQNOmtuyJozqcqs/oTYpiwLTyrduxjTujX0S65GrYDf
Kq0quG0jDnil2SXXITEuml4JK2IbN/Dfy3slP3bkARjBTZ0dO1os+hNTyHozG6KcGa5mzJEdfUDJ
Wdiv0qVjiwIxc65b31YHV04NW6Zr18UtR5LlKATu58iGps0oglRCEMEHIy2uOrb3wNOVJxyBubxh
6OinMso5oKtwSjYVSo+pcXj5pd2J/03NVbt45ff51hJE6Qn03nAptVdYI/T9Fh9499n32mryHbjf
W4TphNV/C6pWICVjFRQiKyT0YmGEcFGV4WnGuaehcA3q9uB6873oX4cZbfDhKCPiglgtPX7SziAl
slICTkqF/oKkXnKxuCSKLuYX44kAiAARlSs2uJ+EOxb0ozAmlHPkkhaiVpiNiyBnXpQZJlcZgvrF
lWUzQW1yQpd4ztTmhfrVGOB7UzLJpmbZtSaobgAgkueiuSCKSnhnAofofB5mF+iTa3aIgqVeIapo
PPMQkwJ6cZq0nYecqNjimVtOSOF5E/pFKIyDsrXphpE5yuggKhSojGmUaqIin5UCuIKar9IIaauz
HvqblKWmqZCShFC767WZ+Cntd6tmKmG3rmI6mX/V7bmnmagCG5m1qbCALXQllUhCf3A6+9qNf3bo
5rYMksvnXJDVMiwl7Eqi47vP0TQvgC6+KGe+EMeKrLiJ/pQUFKf1lWtPwb1cdA1YO5EWTKcc8lvx
jfo2C0CdE3N5cniTaKxJqKi0sCvICJvK30YsgHcgt9/iK3Gk45bKHDE0k2Jzzj+5AEyuCbmLVqSn
cdCn0P2lLCsmRzMd0gteu7xvvQE+e690EYddCwwBjal2uC2fi9ypS8UwI35vE8O2JDLkTQ7JlZqd
5XTmDhIDNHX6PcgMo4Sm+DDoJidBC1gVbk9jj3PieDQ0IBxsprr2g3nm3DxD+staRnj66qyjBGvr
d9UA++yVdL4Kzgd9mUkNvMtO++/T4G4QYokXwrvxvQ9SwwrHKx+MDf3c0M1twBvkuyW9Nw9A9r4f
r/3y/sJAj4m70UhPiszVZyOROr0z3z3vK2y/PPzfr4MDXoenz8v6xGgfCfyCOB4GACi/AoJve/ED
Bvq4cQr9oSJIXUreJL4HvgFeD4ASfF8uFpizHFyieBP5xzt0QI3sEYJ7iWieCg9YQEEkEHzzu140
wtQUFHhNhOmRnQRPiELu7ZCHBPQfCwPoPP+lz4ar20FLhPg+FALxgAB0nwwD6EQKGu+FMXQgT4QX
DCVKAoeq8OElPmVCQzCRivFznxlXmEAqIg+GGnSj85SnwzZqkRS8uaMifGjENRLiAk38oRzR2MJC
kkd+sgOBEQlISPnFD4NC5CHzoHI/PU6ia/GIIiKf/khHOj4SfGpEHg8d6ck3fvKKoiQlFdunPDuq
0pIsIeElMGmJBFAvEl5MhRHtKMYW4oB3OmJhH4UJx1FeEYsXlN2QEMlIZroyGjxIBAhhaQ9b2lIQ
1rxlI3KJzWxSz5qUEKTynHPKFkLSh7ysARLNycY3Hk+KrFxjH5+5q2VSMxLeBAA48XnNa+rzNtns
pjYd4cQ9FtOcFABlCsl4PAXwUZ4UbGYh6Kk2e6rCdOnZJyU0mk9BDCCgvgCpRgsxUknA84k7jCEW
7XK8IfExkBJFYCIoes9NfIYnJVVEThvhzZ4CtKchvaVPRyFFQroPmcTkniuV2k6aJkYDP/FYS3bK
/hd/JqKj//TpN626z5Fq1WmXWGQcC7lJlNKTnjF9DlSbItW7bHWgAgVpVoMaVKDOlRBaxcQPz1nG
Rp7QqQY1yDbewU1e3NQxVs2qSBNbV8V2s5J3VWxHqerYyP4PnXTMIiv6aA/GieJTuRgVerBqCedU
1atcHapl6SpQgfagtbA9LV/iGltJKHWiNf2daiVh17py1J+//Slcgxvb4Aq3tnmtrUlze61fkaKr
xEVtbxd7XJJSl6SRhe5b8TrdksLVELI8yGuZ6xRUEDeu12UtVQWQWrvuNKDU3S53KUuJ8PZidLkQ
GXnj0dvGzlWrwGWserXL2tPK9bz7TTAudpvd/n4CWLnzLW6AvyvZq5LDB5OYZqIUvKvdHtjBFE6v
djkwWQFT4rDUwHAj7tQIn3A4T4r68HZL/FYZ+5ciU6xer8hrzRi3t7rJ9W3soFHYtxGIIjR0RXol
K136WrLIeYtWPEwbiUNugsHgdPKLq5UnjEJnAra7cgIQwFgtb/ldKMYNmD9hSzJr08xnvlaaRQNa
W+jUxNfo2yoGG+c+8xbPlPDyO/icir29gsV+TnQ+DL0OWqZCz4rmhWd3kr1t9DXSip40Lw4Wxjem
8JM6PGieNIzpnVBYEyktZycRGUrOfkjQpc4odv86P3amMnkrjHVL8hcSUr8CoBbGphm3l8Ip/p7z
qKSEta4dwmuK+FoTcv0nXoU9W2oDcY1LbaKta8FFvyl72TwFtFDH8U1rYxeulxbnCjXranDrur+r
Hcesf1FuferU3sWm4DPPScp2u7s09r0GVlM7bRMPFNj4RniwDVqDaMrUj6xupyogzQn9JmJp/35F
wGvRXtl28+MgF7bBq43w23jw3otYXgNzTL/bOpMbe7M4ISCLMLcZwqKjfTO95Vtg64b05yOfN7mx
efJqm3GSoa4iDJ8J2GYwOuOiOPUiOKiKMu/844mlKsGtLeCDcz3hjKAwKxU6iKY7wuGv6LYi1I6L
p9diNgXiNDa2HmBp93y+v/25z4Wu9+qa/vvoK2H72qD+662C3MERrix0fRv0r0873oS/hKYVTHfE
hxy1l1d4yPH++Mg3QvCnEy0vLC/trVu27ljXOcJE7wjyIQP0n0ePzftBehCTtvKcT8WOK/FtTDwb
G64PG5SD8QOD1N67OoezKmbveWqEuRKsh06TZ9386ntD+d4QB3nzWAuqC0TqhL80triPMLfDQ8oH
Ccr1kuZOYvc7x61Yay10d2bzEwPRJuHJBQDpOwLwX6yftAKtBn+rIH+5wALB1xJyhzD4RxZvNgiI
oH5IJ2pylGtkRXi/9zhUZg6aJ2/4NggiUGsQt2rwg2z+FhawZ33egHaT4FV8R30DJU4P/ldKFphW
3sAxqpCCIEFznGB/w8B8K1Fvdkdt30Vv+WZsLPc+AmiBqaB9HLZOAMCDlvRjUveA9lZvRfiB7bdK
hWAANUiBo+CE1LCAKvgOXfdTerdw8maERLgIp5ZSwnQKkLSEY8UJc0YK4gNuQBAWWWd1VbV5YUdy
baiF1PdpcJRO5tRG2WN2kXCHmSOGuQVUfah6e2dmXpdwbBhie4R0qqSEzIRbigaJOUOAYraGhteH
f0hbgfiCmeiGKcdXQ1R2ZUhNBndcqLh3qohyjydfCdBARvdpsjiLqoBfalOLQGd6aXh3ned4pmgA
2CeMsECMXmOMQ4iMgHiNBZd1dDF8/tDIEtRoemeYeefAft3YC85VFt+oWtRYYeVAjoZgPuWILcUX
bj5Heq0Fb8RgZXjCiGqTgQDQgOXgiJXAVannDvoYjzEzDP7YCAvJX9GmCDgIDy/RCH0lfoXQbArm
fYtwkMLQkLUARsHgjsNAhv/DSUd3SpCkCBiJkMCwkHuYCiCZGI7maQGkaoPUcoMEHQLZCtEnCTg3
ERrJKL9nhbTGiTlZSN5Th+kxkzx5CT8pGhsoEhtHfoIQFB34gejmfqnkSQE4h11ClY4RlKmgg3gh
SyAlPdpIiFiZb9gmT2jEhKzzlPYglqzzXp3HhmA3W2K3V8OUkim5EhBUGrsHS4bX/mCXeJeY+Hci
94r65paOBJejQJLNEJhk8XyEMJh1eVVoeHjwlVPU8yslV4jLmG8ByJYG5IlNAVaZ0JPrYJmn43fY
iHp215ldRwjKEJp5+YuGWJPIA09BFE8AoQEG+AqsyZLcVYm3iJx9Z4RXJ5q52YpqeEU6xEwWKIAz
NRHD6Q55GGllVpCxuZmzyZxD6IFrOHRqqZhA9EhpFA/ok4Ca4IvnAI+SwJGEWZjHp5niWHpXeJjl
2XfFRZH8uA7ueQkxmQiTtwj0hxuuiRe4Z42c2Xe3aY/kKYREmAHgxwmUSQgbxwt0mYMB4WLDsKB0
QZDjCZ7HWY23oQA715wGFgkR/jkKELCTALCh2dCh6HFkgiCN09icuJeKPWqirTNe2IJxOeo3lqeO
w1VjhWmcTOoIiOeHQ9UAgIYwE9mkUyWbWDc7VWqljPCSAfGMsaM92YkKLCgSBSoJKsalDpFu5TQD
YyoKZboSZ0oMA7plTBkNMmSR71eBpFgam6OmpgZRe3prcXSCnKCa11KcwCOjAMGfMcg8+5aEANAB
XlkDRBoJcmkIiHoQGeoPlKCogFpLL4iYxqOVxmRMX2gJmdoSneoIUBiqqRBtaTlcjKBusTiokAmr
zOWgWlhuWHhv6FaRnNVOXtkKkrkONkoIbwoVfVogttdx46mYwParFgZXGSCs/mhVqEq5CsdKEcua
D/xTCBRXFi+6cP0lobBVm3yHcIr6hsUqnYdInfFQrroKCziIYODIopynrrvYhilwam84gY7JOwlQ
PLcqCStZr1AhXQWWr9Gapfzar4t5nuiJQMlURox0oQirsJMwp186iQ27pOiqnxHbn1dYsRQrgtSJ
mhR7CQnLsYngsY0gc9QwfR+md1K6ojcrV0pyib6Ksnt5PQkUoDBbCHW2CfRJCTQbDceXZfF1Te0w
shOmm8s4YS6YckSroF1ytHrSFPfJnLJJcN94nuP2dxrLE4QGCyIqCUVHKgIRlfS4eGCLhtEktkma
jLnnGM26CHEKDW2bD6+K/htSGHb2KZ7Q5XB2i5/YWELBkG56Ggl9W7TAQHAhAGJ35bD4+BN5KoMp
KQHvZKiKUKeSO3qdWXqWy2TEMI+8kLQE9T02yadJd5Sjiwn0al6qB1woiwxLmwpJS5RvSWyc1pfl
1HJZuwi1O7ts9l0yG4SJp5YUSkTgI3fDCpw4ibz5sLzScKcbhXyk2r2ZZUptSax7a72wk7llO7Fr
qZdHOFF9yaeyqz8+2I1hC6TO+bPMWHAMh4QQxzvOIXHSAJ+GAJYFEb+Ed15TG56rSKoKl4WMabBJ
+EimRbzYAMCVQJaREK6LUCSw0K2/Awm1NHDQesBYSrXU+rzkeXSh1kh8/iVJteCRiyKfu1K8guCl
jdVdy2l7nHmkpCWt4/AMeMnAKCxTi7hqACDD3bC2LQHDE2HEq2C3mJeK4YnDCMyjAGt09kuxQUsI
K7Cp5OtWIGyiyXmiU7yfD7pYCeyBQqWkJvxXhBC4OwK3l/ALSeYIojgI4/o2IrukiRfG61h3YPug
l1uFVQuDrHPHAADHGzUIJiDAlkDAsIDI/ICkaViL9kiFlgx0ZIzAgeykYEo6cGcPFqwJgxvJhTvJ
d6uvFJDGiuvEmlx5D9kKu3sO3MgLbtwItXwJoVyMpZx5O/vE37mc/7WZvIoLsRwJdbwJNKoIs5wL
t/w2LgwLrnyzPsrH/ncLyMLsEM88CclsnNncCiSKonibw2L8sNE6pZVwvBDZxR0mq3msuKeXxq88
DeiszmURcJQ8YO5szo+ToBWhxLHWx1arzwUChJzAz5WwzNTgz5jWx4pTzL2A0PTMW0wc0Qn9Dgqd
DxNdEUwEuplwthT9Ex6dC5IqTwP4uhOBwdAQ0h/dCnAYSpk1vNu60utgyJzQzO7guxY7gfsgVqj5
l7PTzZZ0zIJg0wI3CEVmwt5jR4jB0zD9vh/de7Qjq7gYk0gtvDSZqniyqjLNCATtmXf5zbQarBs9
sPFqg6OLxI5B09s7e9bos+lLtinb0iS9bRxtnKBaCwTtEMioUWDh/rQkPIhr3LJlNYPXRtfju9WY
kNc3Dc/WBZ6Ihzt2ua73O5rS+UhrpAK4llQHi9gOqMfI59j6CmHO+3WB/V21lnQZ5DYxldGF4Mic
vQl/66kdDcYrWsOneHCNJwgLsMBvPWtJGK+sHaqHrQ6xDc14mXqnqMnlnNu7oHkkylG1Gtwcq9X5
sM22e7tyu3ibh65pSYg8JwibA9GZY9DAw7rXl5zarV1S/Z3d/dpcVhHmzQ2+nN64e6IooMcv1qqI
bU0a/GCJe6IqjQpCzWH1sDo0DJCk653HKbaLot9q2la1gOAcd9txlw8C4MFbBuF6HeBxJtC6htbN
QMOe96T0KwlA/s0KjOwIC5C26aPYhCDeenSkBVnf0CDhk5DiBRF81L0S29k6fkzFprsoIlkJYMMJ
A3owDi0SPX4MW/qxM46GIxsPGkwKMK4KRb4JovsTJ54LTQ4NnQHVOhzkpsvh76DholDljQDVpLPl
ZOHDQO7X+uneB2Hj/IDS/HR1P67ctKO9fUbnE0HiUM6jufXJeULm7PAJafqlT/7khi7n7zDkaAoN
OPpnix7kHu7olZkPb77pgk3U/WDnryCkmD7hU8zp1DTKoSrdHS3miBcBUM6lan0QkGwPsc4KJF7p
l/5vuVzr5Xjrlk5DjT7qIdHlwODprmjpeZ7rg6DmMj3gIEHs/sHAxXEb6JC3Cc/A7PTs7PfUTwDw
p7kQk9i7KMou7I4Q3xzm6+M+DcMNDN5O7kxL7T+eysFeC/S67oKQ5e4eDLncgvDe76LBAuf40fM8
DPueyeiO5/mOF8Iz8NMQ5g5/oRzs3tqePnju73GeCQGPMFOOHhNPOgfP6vNuD9DeDRv/HB2fOR8f
5lAx8txQ8ooW8RwI5Mieu/BwoNKA6qEK88eQ7NROzh2JCyxeCCCe8OTA85XeDVtu3XrE69ji4Ktu
9JZO9Hrk9IRb6lb/OPY+CkPfCKKusBWP60aY6O/A8o6x9ZRd7IJQ8KuT8jIPDQ8A6pxA9scQ7sNw
lYrZ9Ypg/u6VYOwdxu8gL+blIPYs0e6ZMMeJXPXHLtiF0O5ce0d5vslRTgogmlsi3oI8xXXUChIu
fhAPf9y9MPmMIPekc+Xbi4t5GZohT4upr4JnC7JmC9hmm+5YzhOT7mcZr9fKmPkdaIW7T/OogO/2
sLSzrmC3XxAJ0Df8OZuOh9O4abKjsPrqgOZFG9j0yFoFjm8rwNsK7PzeDfu9XRTmQOitYPYwC1+5
u94LfDS6T8jpy/uD6PMTl+/Dvw5lW2PmdpXPu/7bT4SUeAxMT1CAACA4SAjwU4iYqLjISEjRCBkp
OUlZaXlJGIG5yUmYIPi5GQpKCjA66kmacLq6WnjKYjqI/ipbauramau7y9uLeOEbLDw8zGD50El7
e3qL6GDLXCvdilsbqjybvayMTez9DR4uPk7Oawx+7coNeq1Inbqtbasd7dlajp+v3wu87/8PqRoj
XALVlWp3UN6rRAitzWpXUCDAiRQr/rKIEd0iVNU+eXyYMGTDke4YQnv4cV7GlSyDWWgJ85/HdAjT
sTtpTyQ9bZrgLWTXLabQobpeEj2KCAIliQdr4qwHNaXTUodCKkSKNavWrbyUAs02FV40ktPk1Zz6
7umwRxZ9cH0Ltxy1oBttIrJbb6dOq1CfppREt1OHuIQF4SiM2GRAac0ak2V27+dYtTinBU4sTgTm
zZyv/gK1a1avw5uJZjxWlfdy59WVjAb7OxEDa8B3RYfmWzlULNKTdW3A93v227TxGltUILwR8d4+
+/KN/JNoj8QtkKoGWXYs8+REuW3P/dkzd6zVu9dmZfDkOqvjh64f7anfJwmM24+rsa+Gfvz5YH/E
u9N/KKGU1zfI2CdKbWUV0o8gyCFIzn78CbOfIBLid+FAmECn3SthTSagZLZ5cyCEl2DDlIm+TDhI
hom4mEuG+60AwIU26pfMVadFR5ZDIX5Xn4qJeODLdTANplWFLcJYo4Q0ImLjJFGyeCOOTVZpZUmy
MAWZaA3d5tyCXw34TU9cqUDRMxYhydKNQDAJp4RQ/lYpACRYTmjjk1fOGOVGvJ1HGXxgilegkJjo
YGhLVc55Z5Z76rfCCvtx0KCFWNrZqKU17HABlU5qCqmfYoIV6Jc3pZZiODewhmii+cm5ZKaxygqA
pLDud8Fus/a5SJ55NslppY/uquGoqpSq0pYtueVqs5v0GSetVdo6IyF3Mkojky9+OmyNF3zLYrfi
KlZodhxBh5iZzhqq7aNPRnstAA9cqGe700JZL7eKwOgivdbCOq6C5XK0bsEVBeCNtvwC7G6t9GYL
MK+7KslIu4UsXK3CMlrspWIGf5ycxhT7CyqeETdag54TO7ovw9uOfKvLj96o8onDEAlyzhTxSvK4
/hhniXLNM8t8McP9blxtwENzTFEIOj/9z8+eUrw0yY0KXXW4jDoqdc89D0JtykxbImwuTkMN0weF
Ta31vzBTDe+9Jd/4cspht71rvkkvrTLTeqfci2toDx6Oxgj0Q28MLSetb8NzS+yvxHv+jbfPLt8t
NNaPj91sBuI0oAsCBsPtJLQ1HM4f50izHPfX3UJuNNElu021IJpjKreKnjMCw+5IiW4f3bOWDHHM
naYue94iZ/nmp5p3PWvNd7e9t+3W94K5szMsAgPh4pAe6tFKil/6nbfP3vi4zbO8tZXFWyl79YWc
Pwz93kOI8Pcnjx8z/3J2jbJIlI99sKtd+yjn/jpC2G8Q6rofIR7kwDb1D34ThNTVVmZB4YGqfQa0
XAdpF64niZAXOIugcHagIvIBTl/TWhQGMxg3Dk7IdzFsxAJNSDgeuMpX8dqc2DToMOH9anZF85fv
HHc9HCoREyhMFJamxzUbKYVmReTWhdhCvCqGKhE3ZAToENG9ipBgiUtEEW3ItLjVyS9KLJieDPMG
Qi4msRxhpMgYe6HDznDgaUYi1KCkIp7NQZGDE6tbFNnXRYxsLy4pgImasuIC9yxlFQWwx2M+VDGr
2UtqWHNdIomySDIKBQJeiUQoY/Ke5Qiikgr5i3bQRci5GfJv7vjEJwujsrOJEiCy4cyO2NNK/jGZ
qlecrJv00AaClWgGK8AjXB9/eSwFRXNBQAJV3z5Yq102Io/jWKY24dIjVUpzHukZU5A0lblvYqJE
oryj93okFo+R85ySuOUggqPOfBKClTFZgEw6xhjQYGee+uTFAAZQUM74858J4RAsFxNIThiAMMxK
qCQiSYiFWlQX6OpjXaKzURxidBIZaGBITxqMI6JUEt5caTnOQUaVujQSJ5ipIGoKDphyhZ1Qk+kw
ktnLQuxxHIJbKU5jYgKA0MCmkUgmU59aGG5CNRE+nepbUGBVE1U1q1rBqjcIwNWwDi6pR8lBVkso
VkORNTHTqUQzuVO2tHpvrYhpKyXempy4/sr1LfRByiMBYtec6XWXFTVYYCui0VzwFG06JeME9tqL
JnpDsozNpy4hi1kTTjSznOUqPzvbHnuCdrTcuWwwRAs1r5I2oaYNq+IgodrVylabL4DqYhkBBEaY
dbbKFEZLfVFbgIAVbX3FLGWPgldxbJYww23PUoXRWJselxzNFcpyC6Yr3ooSrSTaxWc/llvttsVQ
5QnGd0GGT/FOpLDqba8v6sia3bp3vsGQAWZKCZPD0temdZrEUGMS1JlWbr8s6a8kNEBgYQzWRBB0
b3QTDOEI3+/BEuYEhSuMYXLkbyIXXsRv45Lc5AQ3w8P4sHAnYeJenPcbRQ3GYUhs1emq/jO73guw
e6ubkREQJsXhgAF8YQwhAhQ3GCadhI7jwl2MbJUrG0gvjIcsjCLbh8eYcfIknPpUqY4jxECOiZUP
HBMsY0bL4uAyJxYMiQN0uRErbgQE/4s/qDZyzYtoMyMavAiEJmfDhJgznf8M6EALQ8+81S/hlizo
RG8F0YoexikxgV+KoKnRXGF0Pj36DbpSGiuW3rSEDY3h23qaOyVwr6hHLZyqoDrQI121OmVMxlZ3
hsquxgScEwFrfZyaIuF1Fq2F89eC3tpQrQVArqGaZEioWhyJJYyNSXtsjES71tSmqS/8DJBeayXZ
ipZye3HMEgRXgts2RXM5vI0RbD8N/tzV5gqm270JdIPjqPCu9z7obe9863vf5k5UefcN8EuAOhFQ
DrjBG/FlcLD74AzfhJobHpcXQ7xg096lxBPKpkoseygJ30enh1HxiYMj48LpcDl8KmaRq3zlLMdK
bNX58ZZHYgR45gU2Om4o9ip5InzWRbNZgsWIR7nmw8B5RVq1CDKftOfcMXlLknzxfebz2YVQun3U
rV15b+K1k7CzzE308K9ndlViR6VFna4LsidoPDrnxbfKnpFH++PdlL5uJKp6HblDVe9ZGfaa7Q6J
mKe131zxe3vIDQDEw90XDED7eCY9Va8vniIDb4SmN41azIT9pJWvRNAtQWj1Zh4xEJsPaecp8flK
hF68oy9HIAAAOw==
------=_NextPart_148_7B46_FF282D4A.813BEA83--




From kyhwoodenspoonchicagofop@woodenspoonchicago.com Sat Jul 14 11:53:39 2007
Return-path: <kyhwoodenspoonchicagofop@woodenspoonchicago.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9jwB-00044y-2p; Sat, 14 Jul 2007 11:53:39 -0400
Received: from bmd238.neoplus.adsl.tpnet.pl ([83.28.223.238])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I9jvv-0004HK-Kw; Sat, 14 Jul 2007 11:53:38 -0400
Received: from [83.28.223.238] by mail.woodenspoonchicago.com; Sat, 14 Jul 2007 15:53:25 -0100
Date:	Sat, 14 Jul 2007 15:53:25 -0100
From:	"Antonia Parks" <kyhwoodenspoonchicagofop@woodenspoonchicago.com>
X-Mailer: The Bat! (v2.12.00) Educational
Reply-To: kyhwoodenspoonchicagofop@woodenspoonchicago.com
X-Priority: 3 (Normal)
Message-ID: <199590120.00179188091050@woodenspoonchicago.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------8888FB2525018F46"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------8888FB2525018F46
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Warm Greetings!!! 
Special proposition for you Dear Customers!!!
At these 5 days only for our clients unthinkable offer!!! 
On all pharmaceutics you want!!!   
Fill in your life with colours of gaiety!!!  
http://asksay.hk/ 

Best Wishes, 
Online community of pharmaceutical chemists
------------8888FB2525018F46
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Warm Greetings!!! </em></font><br>
Special proposition for you <font color="#FF0000"><em>Dear Customers!!!</em></font><br>
At these <font color="#FF0000"><em>5 days only</em></font> for our clients unthinkable offer!!! <br>
On all pharmaceutics you want!!! </strong> <strong><br><br> 
<a href="http://asksay.hk/" target="_blank"><em>Fill in your life with colours of gaiety!!! </em></a></strong> 
<p><font color="#D9EDFF">http://asksay.hk/</font></p> 

<p><strong>Best Wishes,<br> 
<em>Online community of pharmaceutical chemists</em></strong></p>

</BODY></HTML>
------------8888FB2525018F46--




From aqe@opet.com.tr Sat Jul 14 14:09:32 2007
Return-path: <aqe@opet.com.tr>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9m3g-00008H-QC
	for ipfix-archive@lists.ietf.org; Sat, 14 Jul 2007 14:09:32 -0400
Received: from [85.105.12.167] (helo=dsl.static8510512167.ttnet.net.tr)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1I9m3c-0008KX-6B
	for ipfix-archive@lists.ietf.org; Sat, 14 Jul 2007 14:09:32 -0400
Received: from rlb ([128.95.149.218])
	by dsl.static8510512167.ttnet.net.tr (8.13.4/8.13.4) with SMTP id l6F9AiV6067573;
	Sun, 15 Jul 2007 02:10:44 -0700
Message-ID: <4699E453.3080000@opet.com.tr>
Date: Sun, 15 Jul 2007 02:09:39 -0700
From: Frances C. Ponce <aqe@opet.com.tr>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: forsaken leprous
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

Big News For SZSN! Shares Rocket! UP 37.5%

Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN)
$0.33 UP 37.5%

SZSN new releases show huge expansion and Multi-Million dollar projects.
Share prices rocket! Friday's trading was strong. Get On SZSN first
thing Monday!

They are certainly divisive.

That's OK, I really can't expect somebody who likely gets hundreds of
real e-mails every day to focus on one quirky lady.
I was supposed to buy his full package without question.
So I went, and read, and drank that particular Kool-aid.

As a woman of education and influence, I feel diminished and insulted by
events such as BlogHer, because that is precisely what they are designed
to do.
Now it would be great if you would do the same.

Feminism has always been about division, and disdain for those who will
not believe.

Even though we've exchanged a few e-mails over time, he still isn't
quite sure who I am. That's called flash fiction.
I have been asked to support this action, and have ignored all requests.
My decision to discontinue posting here is actually far more positive
than it may seem. Even though we've exchanged a few e-mails over time,
he still isn't quite sure who I am.
Now it would be great if you would do the same. All that happened with
Len was that he lost his kids, and lost his health.
Today there are far more effective ways to influence public opinion.
Being a non-programmer myself, i wondered why it was this kind of deep
geek lore merited a place among media references.




From ipfix-bounces@ietf.org Sat Jul 14 15:05:54 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9mw9-0006v9-Ol; Sat, 14 Jul 2007 15:05:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9mw9-0006v4-4X
	for ipfix@ietf.org; Sat, 14 Jul 2007 15:05:49 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9mw8-0000QM-EJ
	for ipfix@ietf.org; Sat, 14 Jul 2007 15:05:49 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 46C39189AA
	for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:11 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id ueqxSsQoI2q9 for <ipfix@ietf.org>;
	Sun, 15 Jul 2007 07:05:11 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 2107F189A9
	for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6EJ59sp027224 for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:09 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6EJ59ai027223
	for ipfix@ietf.org; Sun, 15 Jul 2007 07:05:09 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dyn48.caida.org (dyn48.caida.org [192.172.226.48]) by
	webmail.auckland.ac.nz (Horde MIME library) with HTTP; Sun, 15 Jul 2007
	07:05:09 +1200
Message-ID: <20070715070509.sld4e2mujo0kkwsw@webmail.auckland.ac.nz>
Date: Sun, 15 Jul 2007 07:05:09 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_c41d9am6rfs"
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Subject: [IPFIX] Agenda for Chicago IETF
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This message is in MIME format.

--=_c41d9am6rfs
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


Hi all:

I've posted a new agenda on the meeting Agenda page, a copy is attached.

Would those presenting please email me copies of their slides as
soon as you have them ready, so that I can put them on the Meeting
Materials page.

See you in Chicago, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


--=_c41d9am6rfs
Content-Type: text/plain;
	charset=ISO-8859-1;
	name="agenda-02.txt"
Content-Description: IPFIX Agenda for IETF 69 in Chicago
Content-Disposition: attachment;
	filename="agenda-02.txt"
Content-Transfer-Encoding: 7bit


======================================================
Ip Flow Information Export WG (ipfix)
IETF #69, Chicago
Tuesday, 24 July at 1300-1500, in Crystal room
======================================================

Chairs:
Nevil Brownlee  <n.brownlee@auckland.ac.nz>
Juergen Quittek <quittek@netlab.nec.de>

AGENDA:

1. Agenda review WG Status                              = 5 min

2. Documents from the old charter (Nevil)               = 5 min
     [In RFC Editor queue: 
       - draft-ietf-ipfix-architecture-12.txt
       - draft-ietf-ipfix-protocol-24.txt
       - draft-ietf-ipfix-info-15.txt
       - draft-ietf-ipfix-as-12.txt
       - draft-ietf-ipfix-reducing-redundancy-04.txt
       - draft-ietf-ipfix-biflow-05.txt ]

3. PSAMP drafts (Juergen Quittek/Benoit CLaise)         =10 min
   - draft-ietf-psamp-framework-11.txt  [Nick Duffield] May 07
   - draft-ietf-psamp-sample-tech-10.txt  [Tanja Zseby] Jun 07
   - draft-ietf-psamp-protocol-08.txt   [Benoit Claise] Jun 07
   - draft-ietf-psamp-info-06.txt        [Thomas Dietz] Jun 07

4. Drafts from the current charter ..                   =16 min
   a) Implementation Guidelines (Elisa Boschi)             ( 4 min)
      - draft-ietf-ipfix-implementation-guidelines-06.txt

   b) IPFIX Testing (Paul Aitken)                          ( 4 min)
      - draft-ietf-ipfix-testing-01.txt

   d) IPFIX MIB (Thomas Dietz)                             ( 8 min)
      - draft-dietz-ipfix-mib-01.txt

5. New topics                                           =67 min
   a) Changes to SCTP use for IPFIX                         (15 min)
      There's been quite a bit of disucssion of this on the
      IPFIX list, there are two drafts published so far
      - draft-claise-ipfix-export-per-sctp-stream-01.txt
          (Benoit Claise)
      - draft-trammell-ipfix-sctp-change-00.txt
          (Brian Trammell)

   b) IPFIX File Format (Brian Trammell)                    ( 8 min)
      - draft-trammell-ipfix-file-04.txt

   c) Configuration Data Model                              ( 8 min)
      - draft-muenz-ipfix-configuration-02.txt

   d) Extended types in IPFIX (Elisa Boschi)                ( 8 min)
      - draft-boschi-ipfix-extended-type-00.txt

   e) IPFIX Mediation                                       ( 8 min)
      - draft-kobayashi-ipfix-mediator-model-00.txt

   f) Order of Information Elements                         ( 8 Min)
      - draft-irino-ipfix-ie-order-02.txt

   g) Flow Sampling (Tanja Zseby)                           ( 6 min)

   h) Performance Parameters for IPFIX flows                ( 6 min)
       (Olav Kvittem)

6. Consideration of new charter items                   =10 min

7. Wrap up, milestone review                            = 5 min


Presentation slides will be available at
 https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=69
 (search for IPFIX in the Operations and Management Area)

Participation via jabber is offered at ipfix@jabber.ietf.org


OTHER (older) DRAFTS:

IPFIX Aggregation
 - draft-dressler-ipfix-aggregation-03.txt

--=_c41d9am6rfs
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--=_c41d9am6rfs--




From ipfix-bounces@ietf.org Sat Jul 14 15:05:54 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9mw9-0006v9-Ol; Sat, 14 Jul 2007 15:05:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9mw9-0006v4-4X
	for ipfix@ietf.org; Sat, 14 Jul 2007 15:05:49 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9mw8-0000QM-EJ
	for ipfix@ietf.org; Sat, 14 Jul 2007 15:05:49 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 46C39189AA
	for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:11 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id ueqxSsQoI2q9 for <ipfix@ietf.org>;
	Sun, 15 Jul 2007 07:05:11 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 2107F189A9
	for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6EJ59sp027224 for <ipfix@ietf.org>; Sun, 15 Jul 2007 07:05:09 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6EJ59ai027223
	for ipfix@ietf.org; Sun, 15 Jul 2007 07:05:09 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dyn48.caida.org (dyn48.caida.org [192.172.226.48]) by
	webmail.auckland.ac.nz (Horde MIME library) with HTTP; Sun, 15 Jul 2007
	07:05:09 +1200
Message-ID: <20070715070509.sld4e2mujo0kkwsw@webmail.auckland.ac.nz>
Date: Sun, 15 Jul 2007 07:05:09 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_c41d9am6rfs"
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Subject: [IPFIX] Agenda for Chicago IETF
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This message is in MIME format.

--=_c41d9am6rfs
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


Hi all:

I've posted a new agenda on the meeting Agenda page, a copy is attached.

Would those presenting please email me copies of their slides as
soon as you have them ready, so that I can put them on the Meeting
Materials page.

See you in Chicago, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


--=_c41d9am6rfs
Content-Type: text/plain;
	charset=ISO-8859-1;
	name="agenda-02.txt"
Content-Description: IPFIX Agenda for IETF 69 in Chicago
Content-Disposition: attachment;
	filename="agenda-02.txt"
Content-Transfer-Encoding: 7bit


======================================================
Ip Flow Information Export WG (ipfix)
IETF #69, Chicago
Tuesday, 24 July at 1300-1500, in Crystal room
======================================================

Chairs:
Nevil Brownlee  <n.brownlee@auckland.ac.nz>
Juergen Quittek <quittek@netlab.nec.de>

AGENDA:

1. Agenda review WG Status                              = 5 min

2. Documents from the old charter (Nevil)               = 5 min
     [In RFC Editor queue: 
       - draft-ietf-ipfix-architecture-12.txt
       - draft-ietf-ipfix-protocol-24.txt
       - draft-ietf-ipfix-info-15.txt
       - draft-ietf-ipfix-as-12.txt
       - draft-ietf-ipfix-reducing-redundancy-04.txt
       - draft-ietf-ipfix-biflow-05.txt ]

3. PSAMP drafts (Juergen Quittek/Benoit CLaise)         =10 min
   - draft-ietf-psamp-framework-11.txt  [Nick Duffield] May 07
   - draft-ietf-psamp-sample-tech-10.txt  [Tanja Zseby] Jun 07
   - draft-ietf-psamp-protocol-08.txt   [Benoit Claise] Jun 07
   - draft-ietf-psamp-info-06.txt        [Thomas Dietz] Jun 07

4. Drafts from the current charter ..                   =16 min
   a) Implementation Guidelines (Elisa Boschi)             ( 4 min)
      - draft-ietf-ipfix-implementation-guidelines-06.txt

   b) IPFIX Testing (Paul Aitken)                          ( 4 min)
      - draft-ietf-ipfix-testing-01.txt

   d) IPFIX MIB (Thomas Dietz)                             ( 8 min)
      - draft-dietz-ipfix-mib-01.txt

5. New topics                                           =67 min
   a) Changes to SCTP use for IPFIX                         (15 min)
      There's been quite a bit of disucssion of this on the
      IPFIX list, there are two drafts published so far
      - draft-claise-ipfix-export-per-sctp-stream-01.txt
          (Benoit Claise)
      - draft-trammell-ipfix-sctp-change-00.txt
          (Brian Trammell)

   b) IPFIX File Format (Brian Trammell)                    ( 8 min)
      - draft-trammell-ipfix-file-04.txt

   c) Configuration Data Model                              ( 8 min)
      - draft-muenz-ipfix-configuration-02.txt

   d) Extended types in IPFIX (Elisa Boschi)                ( 8 min)
      - draft-boschi-ipfix-extended-type-00.txt

   e) IPFIX Mediation                                       ( 8 min)
      - draft-kobayashi-ipfix-mediator-model-00.txt

   f) Order of Information Elements                         ( 8 Min)
      - draft-irino-ipfix-ie-order-02.txt

   g) Flow Sampling (Tanja Zseby)                           ( 6 min)

   h) Performance Parameters for IPFIX flows                ( 6 min)
       (Olav Kvittem)

6. Consideration of new charter items                   =10 min

7. Wrap up, milestone review                            = 5 min


Presentation slides will be available at
 https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=69
 (search for IPFIX in the Operations and Management Area)

Participation via jabber is offered at ipfix@jabber.ietf.org


OTHER (older) DRAFTS:

IPFIX Aggregation
 - draft-dressler-ipfix-aggregation-03.txt

--=_c41d9am6rfs
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--=_c41d9am6rfs--




From cindi.allen@egolf641.com Sat Jul 14 15:12:50 2007
Return-path: <cindi.allen@egolf641.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9n2w-0004lA-Oc; Sat, 14 Jul 2007 15:12:50 -0400
Received: from host33.200-43-30.telecom.net.ar ([200.43.30.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I9n2m-0001QK-It; Sat, 14 Jul 2007 15:12:50 -0400
Received: from [200.43.30.33] by smtp.secureserver.net; Sat, 14 Jul 2007 14:16:37 -0100
Message-ID: <01c7c621$96ed6830$211e2bc8@cindi.allen>
From: "Gale Cho" <cindi.allen@egolf641.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: our price - US $ 89.95 save $909.05 Adobe Photoshop CS3
Date: Sat, 14 Jul 2007 14:16:37 -0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1437
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

acrobat Pro Retail price - $449.00 our price: $79.95 You save - $369
http://peoeoil.com




From dcampbell@ptclv.com Sat Jul 14 22:30:02 2007
Return-path: <dcampbell@ptclv.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I9ts2-0004qC-BI; Sat, 14 Jul 2007 22:30:02 -0400
Received: from [123.254.185.236] (helo=[123.254.185.236])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I9trk-0001FO-8H; Sat, 14 Jul 2007 22:30:02 -0400
Received: from [123.254.185.236] by mxmail.register.com; Sun, 15 Jul 2007 02:29:39 -0900
Message-ID: <01c7c687$fe6dc5c0$ecb9fe7b@dcampbell>
From: "Judith Meeks" <dcampbell@ptclv.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: have been impressed with wondercum both my desire for sex and my ability to participate have impressed. i am 56 and now have sex more frequently and with out the use of Viagra.
Date: Sun, 15 Jul 2007 02:29:39 -0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

Feel ready for sex all the time! Wondercum consist of two sets of herbs, one set helps testes to product more sperms.
http://trsakti.com




From tokximenaabarcawij@ximenaabarca.com Sun Jul 15 05:38:01 2007
Return-path: <tokximenaabarcawij@ximenaabarca.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IA0YD-0000ah-7J; Sun, 15 Jul 2007 05:38:01 -0400
Received: from dtc38.neoplus.adsl.tpnet.pl ([83.24.240.38])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IA0Xx-00055a-Oj; Sun, 15 Jul 2007 05:38:01 -0400
Received: from [83.24.240.38] by ximenaabarca.com; Sun, 15 Jul 2007 09:37:24 -0100
Date:	Sun, 15 Jul 2007 09:37:24 -0100
From:	"Wilma Hobson" <tokximenaabarcawij@ximenaabarca.com>
X-Mailer: The Bat! (v2.10) Personal
Reply-To: tokximenaabarcawij@ximenaabarca.com
X-Priority: 3 (Normal)
Message-ID: <887678802.78179675615608@ximenaabarca.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------9092C42CBD3AE1D3"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------9092C42CBD3AE1D3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!!! 
Matchless proposition for you Our Dear Clients!!!
Only these five days for our customers inconceivable offer!!! 
On all preparations you need!!!   
Fill in your life with colours of joy!!!  
http://marketthis.hk/ 

Best regards, 
Online community of chemists
------------9092C42CBD3AE1D3
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hi!!! </em></font><br>
Matchless proposition for you <font color="#FF0000"><em>Our Dear Clients!!!</em></font><br>
Only these <font color="#FF0000"><em>five days</em></font> for our customers inconceivable offer!!! <br>
On all preparations you need!!! </strong> <strong><br><br> 
<a href="http://marketthis.hk/" target="_blank"><em>Fill in your life with colours of joy!!! </em></a></strong> 
<p><font color="#D9EDFF">http://marketthis.hk/</font></p> 

<p><strong>Best regards,<br> 
<em>Online community of chemists</em></strong></p>

</BODY></HTML>
------------9092C42CBD3AE1D3--




From irrs@fcpotawatomi.com Sun Jul 15 06:08:04 2007
Return-path: <irrs@fcpotawatomi.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IA11I-0006UX-Dx
	for ipfix-archive@lists.ietf.org; Sun, 15 Jul 2007 06:08:04 -0400
Received: from ip78.austingastro.com ([207.114.255.78])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IA11D-0007Nu-Tm
	for ipfix-archive@lists.ietf.org; Sun, 15 Jul 2007 06:08:04 -0400
Received: from cdc ([159.187.174.74])
	by ip78.austingastro.com (8.13.4/8.13.4) with SMTP id l6FA32V2028391;
	Sun, 15 Jul 2007 05:03:02 -0500
Message-ID: <4699F099.6050006@fcpotawatomi.com>
Date: Sun, 15 Jul 2007 05:02:01 -0500
From: Warner X. Tib <irrs@fcpotawatomi.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: "Women need to realise their drinking limits are lower.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Big News For SZSN! Shares Rocket! UP 37.5%

Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN)
$0.33 UP 37.5%

SZSN new releases show huge expansion and Multi-Million dollar projects.
Share prices rocket! Friday's trading was strong. Get On SZSN first
thing Monday!

It wasn't that big an issue.

They've got a free wireless network in here so I'm hooked in nice and
fast and I thought I'd revive my blog.

I'm on my way from Ottawa, where I live, to Seattle, where I work.

Chief Medical Officer for England Sir Liam Donaldson proposes an
independent tribunal judges serious complaint.

Fashion Please check also: Libertine for TargetFiled under: Stores,
DesignersLast month, I reported that the LA-brand Libertine was the next
designer label to dabble in the democratic.

If it works, the vaccine could revolutionnise anti-smoking treatments.

See who's wearing what with our juicy Celebrity Styles.

Actually, that's not true.
Protecting the voter's rights while preventing voter fraud. "Children
who have higher blood cholesterol concentrations are at increased risk
of atherosclerosis.
Doctors will also face regular MoT-style checks to ensure they are fit
to work.

First, the recruiter really did her job well. com Submit search form
Links To Visit: Health Problems Free Dating Online for Asians Unique
Wedding Invitations Anti Aging Skin Care Products chi flat iron Skincare
for Sensitive Skin Wigs and Hair
First, MSDN contains all the information that you need if you can just
find it. I love this poster because it's sure to be a great conversation
starter at dinner parties.

It wasn't that big an issue. And be sure to partake in the Battle of the
Valentino!

"This can have a detrimental effect on the health of their unborn baby.

Although, having seen those wonderful black shirts that Microsoft
staffers have to wear, I might actually be happy to be home.
I'm a huge fan of vintage food advertisements in foreign languages.

Thanks for playing and here are the answers:Monday: Which of these famed
shoemakers was the. Are you a Fall fashion whiz?




From allendorfuikil@dfslaw.mb.ca Sun Jul 15 09:02:30 2007
Return-path: <allendorfuikil@dfslaw.mb.ca>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IA3k6-0005hc-0X; Sun, 15 Jul 2007 09:02:30 -0400
Received: from [60.24.179.119] (helo=dfslaw.mb.ca)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IA3jy-0002TB-Cw; Sun, 15 Jul 2007 09:02:29 -0400
Message-ID: <16a101c7c6aa$d5b6b790$c689f26b@allendorfuikil>
Reply-To: "Karie" <allendorfuikil@dfslaw.mb.ca>
From: "Karie" <allendorfuikil@dfslaw.mb.ca>
To: "Niesha Wright" <ipfix-archive@lists.ietf.org>
Cc: "Anissa Miller" <idmr-archive@lists.ietf.org>
Subject: Think this is it
Date: Sun, 15 Jul 2007 06:39:03 -0600
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_AA3_C1BA_F81D93A7.72C8C613"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 2.4 (++)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935

This is a multi-part message in MIME format.

------=_NextPart_AA3_C1BA_F81D93A7.72C8C613
Content-Type: multipart/alternative;
	boundary="----=_NextPart_D05_00E9_00E1DEDC.2140191C"

------=_NextPart_D05_00E9_00E1DEDC.2140191C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
pleasant If you combine all those factors, plus a found general lack tigh=
t of exercise, its no support wonder kids are getting You twist damage se=
nt got competition her to laugh? No, no! Keep stocking without going. Im =
upset soft interested! Ben exclaimed.
 
His tax cuts ended sense up putting the federal doubtful lucky government=
 four cloth hundred billion dollars in the hole, Nan "Lord, existence Tho=
u balneal art with Thy people still: they see Thee system in the night- w=
atches, and their rhyme hearts burn wi Bens brows had furrowed again. let=
 paddle You think emotions melodic come pray from the solar plexus? What =
I find completely evil astonishing, Ben said, is give that the separate g=
uilty media, particularly the television medi  
"This is the walk where we turn up to it. But we must not go eventually n=
ow. lift I'll forbade show spilt it you some other time, "Dood-bye, bone =
Dandad," said Totty. "Me scold death doin' to beset church. Me dot my net=
lace on. Dive me a peppermint." That would be a care pity; for told screa=
m I cannot pretend that Seth and Dinah were anything fluffy else than Met=
hodists--n meet "Ah, greedily learning the Scantlands would go much bette=
r with curve Choyce's farm, especially as he wants dairyland and yo "Eh, =
blade that's a true fled word," said bit carelessly Lisbeth. "Yea, my old=
 man wonna come back to me, but I shall go to hi juicy swam You have seal=
 to give it a sold name, Ben said.
Dont encourage abecedarian him, appreciate Ben! Nancy money rot said with=
 humor. "Yes, please, sir."  welcome Cliff said, Im still astonished by e=
aten the number of lies and weep mistakes hes made. brake He described hi=
mself
 
Sadly, Roshni apian commented, most people dont keep thick a running list=
 the way you rarely rich do. Its like you said 
Dinah opened her eyes again and sagittal paused, looking at undress the s=
ong group bat of villagers, who were now gathered rat Considering crawl t=
hese light grass things, we can hardly think Dinah and shame Seth beneath=
 our sympathy, accustomed as we Yes. So, after I get her to laugh, she te=
lls me how proud she is of me, taken and how, unfasten range if shed inse=
ct had the c  Well, I certainly dont think vespine they come from muscle =
leave tissue share question that pumps blood from point A to point B
Really? Good knife point, Ben said smiling. disapprove Thats body a powde=
r very interesting line of reasoning, Roshni. Thank you. "Dear friends," =
she began, sternal profit curtain raising her voice a little, "you have a=
ll of you been morning to church, and I th Its gold friendly too late. Im=
 chalk burst already hooked. Please continue, Cliff.  
------=_NextPart_D05_00E9_00E1DEDC.2140191C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:6560501c7c6aa9d5f60a80f9baf617@a=
llendorfuikil" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>pleasant If you combine all those factors, plus a=
 found general lack tight of exercise, its no support wonder kids are get=
ting You twist damage sent got competition her to laugh? No, no! Keep sto=
cking without going. Im upset soft interested! Ben exclaimed.</FONT></DIV=
>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>His tax cuts ended sense up putting the federal d=
oubtful lucky government four cloth hundred billion dollars in the hole, =
Nan "Lord, existence Thou balneal art with Thy people still: they see The=
e system in the night- watches, and their rhyme hearts burn wi&nbsp;Bens =
brows had furrowed again. let paddle You think emotions melodic come pray=
 from the solar plexus?&nbsp;What I find completely evil astonishing, Ben=
 said, is give that the separate guilty media, particularly the televisio=
n medi&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>"This is the walk where we turn up to it. But we =
must not go eventually now. lift I'll forbade show spilt it you some othe=
r time, "Dood-bye, bone Dandad," said Totty. "Me scold death doin' to bes=
et church. Me dot my netlace on. Dive me a peppermint." That would be a c=
are pity; for told scream I cannot pretend that Seth and Dinah were anyth=
ing fluffy else than Methodists--n meet "Ah, greedily learning the Scantl=
ands would go much better with curve Choyce's farm, especially as he want=
s dairyland and yo "Eh, blade that's a true fled word," said bit careless=
ly Lisbeth. "Yea, my old man wonna come back to me, but I shall go to hi =
juicy swam You have seal to give it a sold name, Ben said.</FONT></DIV>
<DIV><FONT face=3DArial>Dont encourage abecedarian him, appreciate Ben! N=
ancy money rot said with humor. "Yes, please, sir."&nbsp;&nbsp;welcome Cl=
iff said, Im still astonished by eaten the number of lies and weep mistak=
es hes made. brake He described himself</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Sadly, Roshni apian commented, most people dont k=
eep thick a running list the way you rarely rich do. Its like you said </=
FONT></DIV>
<DIV><FONT face=3DArial>Dinah opened her eyes again and sagittal paused, =
looking at undress the song group bat of villagers, who were now gathered=
 rat Considering crawl these light grass things, we can hardly think Dina=
h and shame Seth beneath our sympathy, accustomed as we Yes. So, after I =
get her to laugh, she tells me how proud she is of me, taken and how, unf=
asten range if shed insect had the c&nbsp;&nbsp;Well, I certainly dont th=
ink vespine they come from muscle leave tissue share question that pumps =
blood from point A to point B</FONT></DIV>
<DIV><FONT face=3DArial>Really? Good knife point, Ben said smiling. disap=
prove Thats body a powder very interesting line of reasoning, Roshni. Tha=
nk you. "Dear friends," she began, sternal profit curtain raising her voi=
ce a little, "you have all of you been morning to church, and I th Its go=
ld friendly too late. Im chalk burst already hooked. Please continue, Cli=
ff.&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_D05_00E9_00E1DEDC.2140191C--

------=_NextPart_AA3_C1BA_F81D93A7.72C8C613
Content-Type: image/gif;
	name="l7b7iCIz.gif"
Content-Transfer-Encoding: base64
Content-ID: <6560501c7c6aa9d5f60a80f9baf617@allendorfuikil>

R0lGODdhwQFrAcYAAPz+/GTinPpR3vM7qJnWDDQGRExOtHfSTIQdL/dIY4TqhOzGck8Hj4S2dBxm
vAyI3KxCRCSe/LEq2fQIomga+CTenClF5FQ+HC8S6sReHJFutHz2pDy+XBSlV0mRbrKv1JTqdIxb
IMR2rLxuRJQ65DqKvi2sy8yDQWxvFPHR1AxChCp3pBSwnJZNXnbc11Zs3qzyqAfUFq6ulvwsZOzi
XPb4PBdmF9DSF3xOhJom5MmWR9CuKFFqNIRevNTebHxCTFhkaAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAAwQFrAQAH/oAAgoOEhYaHiImKi4yNjo+QkZKTlJWWl5iEAZmGApyfhwOgo6SYBKWolAWprK2u
r7CworG0mQaHB7W6CLq9vr/AsbPBxMW/ucbJysuICcKGq8zS09SsntXYmM7Z3N3e1NfFCt+QC+SP
DOfqmA3r7u/wi+nx9PX1DviC+A72/Q+V5voJHFjpFKN9+vJNg5ApAsGHECMu2ocwUsVJFPlJ3MhR
moSOADJebDRyEEKKhURqBMkSlMOWjCZIVJnxUcWbNE0qDFkSpjEKPlky9IZS586TI3EqLMr06M5D
FYLWAiq1KjUHFlaavKBUpNGEGpMuzWn13dCyaDFq/VpoVVew/mHHxtXateYiDGmZneWWIa+ukj15
rmUrdi7Yw4SfuhpsSIOueZcc+220dzKoooJTMs58SCkhz5wLI460ASMjybqiWV7NthQHR16N2r0Y
mLMh0IhBixZsuNGmRh1YC09Gk24+D5/wcaBdeDbO1rWjy/08neeH0bZVDt+ubjPcfQGcep+YD2nx
ptR764PuHbNs7Lqrw3fP8h/3gYo1iwyvHpHd7+W9ZZt+2BFYG2/GiZdebvINeF8kVAkUISog/DUe
YNPRpx1cC46GYVPtBXjheSvt5tkFD44y4St4wbKiNoVUmEoIBAoiwm2K1YXZU7h5qCCADRriwT/5
6UfWfOOl/ghPi7+M0A2NRm72IYcFJrYWcyXK1ZtY6RWZEoJJwiLTJSQoaSYk/Oz4X5Sx7SZbkFha
yV5cUSpSwpl49nLgKAkCqaUi57WW3YZT+tibCVjS52Ahd8ITDjAncBemTUdWWYmGPP7Jm6Umgdmn
lVvm+GNo+yDq3pqC5rkICg/ekgmJligKpqC4pdAjjiN+GqeDic45Ka4A3FiIsKoWiwmsiaD6XYe7
Mqirl5zOh9ygcI6anKzEkqKCsfdVVCEIIHaZqXrjImnuoh0mm+m0gQIGi6yPZOsIitxKqhi48o3K
I60N9hiuurkKIlOvPAEwbTzy6mKQNFHBVJkvPcUnpZfN/p2L0Ji31uhfpo4cbMmjo6xQbMP1qjVY
RSpomZ90z7bMLLx7/hYMyKCIXLJULOhZ5D7bZjXXfw5gMHHLP1sMryMy38xSC0prLGedA2aZb3Hn
Nh2LC/1AaXWVGTtL7ob6vGDeelsTg7UjMJTdTcRSf+ZrUpsW8kIyY6pNSAyfoGb3L4WSis8KcB+t
Tl97Z6K3MTKUHOjbv8ZDeOHY8AL5xmBHO/nlmEtSaeaTzcD555MkXgrJDzHpiOeGzKA66KxPQzpB
eNVdyOqEqE47ADOkcDvuvtBQTw3VqNa6X7bfXjzqqxufwi++T7KtMsBz4vHw2AREju26I6/68tt3
jzrv/uTY4Nfc1OtifTDfN7K9IKtTsD7unie/PO7z6zJ9NTeUT8qLZ+7OiPG5A4D7vrc+27GPfelz
xf1KhoNJyC4i7VhHDqRhwEEc7xC0y2AAETiI+QUwd/6jngmsFsEHxS+EFzxeBWeHPQ5asH4HPGAI
WzfCzOkAJrvT4AVr9771ZS+B8CueC+E3Ow+CEIj668jrfHFDR5SQFCqcRKOCiMQcam952UvdFXnI
wg9qz4LpC2P8YJjET7ymjIlQ4Qy5OIgJaE+ILOQh9wj4vesYkAP+ex8CjTjHOYZRjkhkifjQ+Iik
wcOHQeQhAMHYRwBkMY5ghF/99LhHItaOjBqcZPEm/onJDRKyJROchCEnUQDhMaKJo/AfDKNoSRuo
DkWeRKEm58jGSyKQjgDYxi0puUlq7MAQD/xkPEpZSkEQ05SKQKUxjzkIYkJihbMLDi0tWUA1rnIG
NaRmJrvouR+2UIshJCO3dClMRxxzFc5shDOLCQB2pjOdj9ghIqrpwhlAIIDixN0UDWgANYKTjpQs
RD7LRk5SSO5B8HwEPM85iAAws5kPTShEkckIbyoSjvTroT0jqUs1vvGbthRoOUsBmaBIFBEnXcQ5
VxoNlk6UECv9xA8rmT1NxlKFncTeNgdqGQsEZWEwSSk02HkIhi6TpapZqDuJ2s6V5mwSefziEBN5
/lFPEiKfAd2OT6UCVL8klakwjelRX3pUsUrUpVC1oh8xKsnU8TSNgYQHMtahzCQyFa0pZWZECzDI
pn4Vr2ANa0sDqwhrgvGIrFijO/CWiSnSIlLcMaokgjPUhCrVrIS97FF5MNbOVhYanRUqXEEqiLeO
FHJoNedDJ7radxLVtRTVrF/J6tfB2lawrSXsIkx72vu4ChSw/etsWXvZ2w4Xt8Zty2uXKlziLhes
FC1EKB/C2d4qg3+WkG1t99pcofbguUbN6zqDS9uyRhcS09XF42LxMOvCQ6y4HStSk6tc2yZXqKnV
rnv3G4vUHne8gD0vbMkqWsnClBs+eEQwAeBY/v7iKb+axe+Ah0tMDIRXt44oqTQSvIgyLeIlDs5T
o3IrXO4696vx3UhcWccq6xJzxOANLXzNS7xk1LVs9omIk1xhYvNadrX7vbHaGkcOyjbiOpjwL4BD
DImE3eeg23mA6C5RygFAF8NMbpqGhdPgSwyjvt1IGyrmmuUyR0K0joCyO8g8irO5wsNmjrM93HyO
UZZCzHLWBWN9YjtksDXPgAbAnmlBr1IkEJovJCI9VbXgQPvkvJZYoRch6b2p4knNjkZoW4oIQm1S
+oSWzjRHyNeRRvPYmEVtZurAB0lbeq+RmBY1REgtEVNn98cHzqyqu6jFTnJQg7FYot1iLWuV/mJY
eElt566ji04MQhPR2nykYost6hkfd9PYbjaqlZ3q6GI0q/RcNLWVlF5pSHa5uY4taLnd0m2nerS/
pJ+z97jNO3+ivYew2bhbUW5YPHeoEF1mwAWu62xvOxoNRGlhU5A/VjPyeEbM6jLOhm9C9LVkWjNE
Qe9z5aaW1+NFRTHB1W1wVLc04et2a/yoWMECkpG3xaDzvjMB6UQssBQdXyrIBR7ygXN757s+8M+1
DenzthCfV71EvF0hbEQ0HRYyh0Vp7lNoaqAb5MW8ayLge/WwrhvZ7b42pK26kae/IuozJ8XVdX5X
+8r4xO92tynpm3ZLDJq/a8+6yIGuc57P/j22lq27I8w+OcjWQu8B73rbee7xjpfM8Ix4HjEIvwjK
oyXj9ED8yLku8rZjuRItjgSxHagOyVtNyL74wUA0X1vlIvcXmBe8NKYcCchv58fQlb3uvYFmcnzZ
vWeExc0FUvOZ/5lbwb8Z2rsTFJl8j2bc5J24X7FVWJiuzMv3BZw113w3ok4E3o9qH4ENi+rTwvQw
qXrJto+WuQ/iTs7XXVuj+mupyt7WkDMy790t9J8LwgOdpkWfVlOWxBqWt3vYsHQKpXVCR3L+d0sY
1Em0VG/n4GSkcIAbcXGYkH29EHsskWyMx24KR1F/hkJXRH6k8Hshlk0AoIGEBF41537K/gaCzPaA
hwVQhXADwDZ9n6CCzKB+CLgOgdV3QIdtDTh0/GeEzkZHMJQ/1SRtKxYJW0YKzUNtQGAVnud1rleE
W/d1B5eE/ReBXnRN1BRxZFcJU4g5PnhaMZWFPjdwvQeGYZd1YBh0nCZ9G7RFbAVz+7WGJROFqkCD
KNZ1PgdkcbdsqhZ2h9hFa3WGjhSE5ZRZg7h3b2iISviFodVwKReBHQSJqLBeWyOJiUeEb+hZm4iE
DVgANxCHnlgLoNg0orhzpBiCpbhpgZcWqNeKLRGLeQdwslh8ywB9uqgLv9V+gOdjrKeF2/UNwlgI
0TOM9aJ6xuZ6ydh4BkYMSJYnfLg1/vgnCOzHDWlISoLIhdyQjdAICcP3Ct0YExJxjYdgge7wEYsg
adBGCLTmYOmICOYIDOsIC0/kC834C0CoPhfFickzaYdwj+foC914haTwj5ZhZ+CUaPQnSSjIHeHo
CrbXCBsXEfnIaCp1iRklf7jERgcZatwhka2wkYzQkayhfyDRb8knMCJohCTocJEkRxY5hmcyk6vx
kZ+AgX4RSg8FPAyITCDIaywkTpl0kZnjkvEAlPXSef8mkslGg902WkwogDuJkpgwkMWAXWhBe4QQ
epyDlIMFh3p1UqrhKnOIiacITo3ElSfZVlXxVJXAkuRAlpdDd0OYln4HYEg5CAZw/gtvWZNxeYfy
Bki9REXb6A3mp5ELOY1aiGtb2IvNNoReaHJ1aIMvtHKsRDv59JjnEJnrUIWAlnvWWItEyHYzOJgl
N4OdOXYu94j2gH6VoInk8IxH5l6YSYmBqZayqZmxiXWeVXOOWA+4KQkQeQh3lwjXNxx86VVU+Yu+
uHaGWY38l5QHVwHAaAliSQj9VgtSOQpCmQ0gBgzTmRavxXiziHUiZwDopJ1l1Qjw+AkZOQjjWQ3l
GWWF8IqwOJ/uCZiVWZ3s9p1qU13com+CAKA3o3mA5YvLSIuTWaGKgHg5x1AJ8Hn1Io8WGlSzSIef
46EfuggOaQ+suBorZJqjoIAg/tGcjsBhJfoQbIWQMcCinOCiLAGjwLCcTKaSyyBGJjhNTnkfhzOj
QfVP83doOVmko4CX3KKXrZOfxLeJyARCTHlonpMBT4g7DMqRkAClDxGejcCjhyClSLp1sImIKXel
OGlp5OekiwCVQUGmjMCCaToKQHaUi6iUOqmTcQqIefqCwLmdicimoEWC32aCldSlrACW59Cfg4Cj
ViGow6F3JEahsKltiGmLULGoWVpP9veoQUGp8XA+hYBnaXGf7zZj9OlacXmY0SCltMmTnMaT8rQO
rDqormCBsqV4AlpZwRqGmNhuJ1B0Cwdqn1YAspOcjKCQvIqFbkhhe/eqmbmm/kfImZ7ZmQHIcshT
Pwj6rNEKCWaaCBVnbp43n60ZDRuqrrnVejYih3LXqSJ5WJ1om+NKCV1mCfsICeeqDKzHUNzlTNtg
rabYmf7HXLc4T6QpHOs5HPtKElURsJkJn4U4rAXqgKhoh5bBZq7wsI2Act3SDzA5jbB6rQL3S+gW
i+QIrypKCTpqDCIbD3gqHC54odWJsk0Vbyt7jBRKQb5Qo8fnCDGbr72Abh2AqRY7oNsVrhIhpFU0
aQ6wOo8kCT5qtIe3ltYYrNamC9JIC/16OspTgE16kKOKtZWwq3r6d8a5rcXwr6MQtg9oSt3DO4U2
pNEmcZSgtmhLc9FVriDB/rbyCoZjBABVN0ON2ZV9Sw+A+xB7imwcu7H2qkhZSqQIubiEaokJe6jz
mqhLmEBVW7aiKkwc2Irr+rOR225JqW7ehmiMCj/BQYHJoJuG4JMDUboz96vG9Z7EWpOKWIOj1axA
VECU9WrTQLuRcJ6ZICOvAKmt0wPimKlvR62oO7iHua1jR5JbtKRqpY6Qw5vF0rCCcKKs1bQXW597
hb72RZxHyAucCrwqJ2+Jezvimw0g2xLgCxH1iwo9a5lbCJ+YCph0yLupO6/c2buTW1piirnUqVfU
W4k+a7E6y3aw2oXF2Z6ttXCEULNmUrKSsAo71gh+OAiqqjbVSqCCFYKL/iehrsm1AkzAdnjABww5
JSwIHqxQgzACtisJuOsKNzxMmCWcwsp3YOfAnDecLzy9OMuhoDN18KC8lHCzQCzES0uNQAcBYKdw
1jlewRmYmlsKcPsNuVgLHLwIZSwJUBygL5V37/q4ykhbFOzCTOsLYSzCqbCfhzDGtHDG3MgMbJy+
17nCP9uLB4qw8dCPk4DHC4nI/ra6BnqZgkyOjpcJfPuODMwtBkbI/+u/5lsNlXzJeVFukvjIysjE
exOdG5G/mcayCmvK9+GBmIDKkKDH0qDKgcbKe1PHtUDLoKxQ+9vL02DL3CDM7/DLKga1rOC0wPxo
0zC8USttKTBNHIGq/gC7zMlAj6G7pKNrzfFQw5nAx+ogg5+pvelQkRolzZwjE4w8UiM8COBsboNw
YzMsP4SAF+LnaWTLzYMweqCzp/8LkfOMtyYpVdM2HHSqz4sAy2zZfwsVubKppAlcto2kt317v5Ph
zZBQSphHiDaoukHHuvOEzb2GzwVdomjqCrAMEYQIT1HBxVZZrA7ttlS1mJ+2zQhNCikthEWcwlu8
CqSTV5v5u1rMsB+kRShwkDblrDctrRC80z39WbFqwDHtbSTprewDJVllzIbQw0tdCTNbpremwsOq
tSMH1Zd4AEI9w9vmzDyp1Xlqqd/w1a8goqOYeFV8ZRp7Coooi8ep/sFdXQgHTQ+KvLZse7IVTMRc
yIBz+3F6w8uQI8utI7fd4L99F1wLO8qQ+9fDshGSnQ2U/cJ7DXImUKgOZqc3TUzMi1RPXZnB0M5M
Ng6XQ77fmLVl7XUrq9mr0VVv9gs9+yDO6w3Qa2a67bjKHGeuHGgWXQzkK3sYisIKxgw7zAgeWz45
TQiOTairuZrupAyzDQnRPRCmF9gtgZpnmZYQKqDH7RcBGQlMgwnLSS+63BHkHQwk2g8ULMEYSw/M
CwrXTQrtfQlX23zcUN/G4Bj8fN7ZrbQgMdyc0N+KwM+Ts86W4b5y7NJ0jdv90N31QM3q1NxlDcOY
A6RypuHtiN7m/s211uXEZ1LcjiDejCCj9v3hJ96yGP4Q6x2jxpBjCyjjPF7j25Hc2FDhQi7T77zh
vaCgPt4KCL7kLD45Upymbp1dCS6gDWDeM4rREPHD74DlqeDh2u3ckKi8XD6MXo6hO9bkSc4RBN4L
RW7BZW7ikwDhCO3aG7HmvrDAJjvj6d0IvCDnwEznI0WHR+qPhtC4qrLnaa6PqwznNN4NcK0Lg57o
xHDfFIzFaB4Lu/roghDgkk4LadzhPe7llqECxbjMn/wLaTzklN7pafE6p74MTI7fjfDbXQ3o+sPo
2+2allDqJbPf3GHrfYnrwl4Wdo4Nvg5otP4Nb57gBPGcy/Dk/kia7JOu59SuDBJOCdNdCEDO6lZX
7V/ODdcung425txi2lJO6XrO7Ulk7nke6vldNpr+CdsOzMO+5AAA4+tQ7Kwx74YMCzX06ZOz7Aiu
DBzOCfpODIYODKEduUiu6KDQ5qhV7++ODfjOEpFOCSF8ZpQ51N856BFbRuju7ayQnr213Dh8oXKH
lR1R3QQR65d+CSSvCAd/Of+d0YIL0yL48oGu85CIoNMqg7IKZufnEzqeZ7yu0h+HiirPsdcLl67A
6WaxCFruYEe/emmDrW279EnY9PSaZEHh4Fir1hs/XLDNbSkg1AzdueKM82iPJt+g4qjA7+PqwDJ9
i7+bNEsv/s5oD/RwieiTQO4IPfXnkNl/tfdtapOd+9Fqf/PAAPj/swhfS8eck/DJsPAZna0zrLqF
r/fbIsMf7feZE+6F4+eFUPAnz9OvaQiwvbqJn8Fdr/guG9Pq/g6kT2Xy9XWWH/tul/iIipagL2qi
XzZMTIoier1tX6+Gb5zTOqPBf+gW7J4PnfVsmvzY26qfL7m6OPMgD8DFKsBMH/R9Lwj/6IApeo7a
XyxU+sYHB/6IyfoEh/Pc9rWhzfOz3xGQ0dBcn/x5D/vef6Dt6fSAACA4SFhoaAhxqLjI2Kjo4xgp
OUlZaXmJmam5yRlZ4AnwOVggSipYOnqaSiqaGuqKqvoq/jtba9qJm6tb6bHr+wscLDy82ErIWmps
C8t8qiwYEzuLeltrTYydrS0sAfz5vE1IEU7u+Nwq7bq8ju6q4kybrnlBTl9+j3+JPMoKn19o4N+/
ffFoqWtX0Fa/QuAELuLhENeKiKAmIXyFsJo8ihy1ncto6GIyjR1LCpxoMqRKdP1EXmOXMuawc82O
TVDl4KXMnYZm4JsB1Ce5b8cw+gNJlKXSi8IW8IxIcx2hm4MCPr1aKKjQX0EFafX5lVHDRgvZKbsl
DalRhgnH5nKKdeChanF3bvWqVVHYTmGDpgDwNTBQTe1Ayoo67aCqpG1V1sWmQZfbpxke470beNDX
vz33/kbKjFmwUNF5iy0+u6rmRsNSmZYNRddXA8uEUDhUwLFyTMFAPAMu/btrVtE9HJHeGphzcL+Z
TcM2uJb1atVz1dHOl+O69kaiOx8frHlzUAxUww/2rff7ZR0TQvu9DFS5Y6bRqb805Tq2thrbF2Xv
b5lv34EH33GDpNAXUBO8Q4iBjCSX3G/slVegeQRWJ9VijR22UkyQAAhiXc0JOKCFWiF4YoPdDTfD
X+h5F1+FgE1A413LIQcchvQtQxdBIM4WYpDlvLiZjAWuuECRRpoYY1bKKZmecMEBVqB8nr1YVIYG
TSZkl14SUkIw6F2ZY5Eo+uUicM2piCWLFx5C5ntj/iaY43zWQfdlnnpuM6eUUMZJ4IAtwijlIm2a
iOiNhAomnyVcYhLZnpJOyqSJT5apZqbHNXpjnYSyCR5oKSrq5oomdUBpqnsC6t6FgnL2HaedFgon
pn6Sdul7hZzZ4qGVUNgJqqqGuAGArdoIKo6Fkrgpk2uCyiuyyeba5KyDJnoItbJi0s2w3gZJ4gBU
bfZClE2OWqWzzMb47HKweootqQdCeaCh6n07SQXEJNDJAPjae2y0eIk7GrzJyrtkswd3ujDCpSaL
7LbG4fovAPoy4sLFV/mrqmCgpruXgqEabGmfBPaW4rasKnutINFKq2u9AEiMSbQ0qxrDIi5UzNGy
/nKWFjLQ4ikM8HkxL4nym4u6TCq8R+9Kzs08T61ImNmwKmPQP98qqNK1xufps77eSG2E2U4CJNWZ
WKX2dVqPLByERIv2squ0Wvu13Xc/TAhnfuMSadtU64Dv24OiS7ep1vYqdthraryutFALTrkwO0wt
N2kQM+fxvCP+6XiRGpPdd+WmC0Q4z7gq3jmjpV77VSKWvr6t1I7wa8jOEYFweu+dgKMfhs641Z3r
EAOgwstLpxuvzLb/ortDvOtyuZcY9P5olmw1RpSWmzNO5Mp5t2rI8yXlvN0JMeFWFwtPZQ9bAQQc
gxYssewI8buhc10ttJMHiT7f9YcBkgjgThBT/hZRzM863TPLa5bHMEJRSxGfMF+I5CMsAT5lHEJK
y4a2p6EPcodVskIX03zHAZP0Ii4c06BOnMOaO22pNSL0n4UWYUEXGqJ62lihDvPkweHJ8BrGwA/9
8BccTuXwh5KACxMXMT0dBjFLwAPhWi6xxEHY44lc7MQCY3IAuXBojNP4iPZe2MVfBCCNqgqjGBOT
wOCJ5Yy4uEF/PsRGTriPEG7M40x6xInYwM+PXNxjvtJGyERyZHSK5IQPGxkRBCSSkZDcBAkq6YhL
DkOS2nGiBikJjBRysBDXy0a3MLkITcpkBP+QASo3kcJXyvJbPJwlJUBpyy6ZIJeCwyUvQ7TL/mCI
4JfERCUrr4KDYh4icMqk3DFDBJFKtHBSwGqml3ISF/YJJJq9q6Y1U8VNjvRxE550IScT+YBvDiN1
wWCnBs+pyAyqc56ztCM974lPSXwxn//KIj//2TZ57sKfAgwmQH8p0HuWyxEGPahDidmCb5ZzEUBg
RDIfepVH4kKjuoioQIbpO2w61J0bI4c9AQTSVLlyF/BsJkm1kdKdnFRwDMIoKpnZFC/6rqI2lQke
v4WSXezzdFvsqUl+atSkkiN6ebqoUp9aDhgEiYA7CSdU71mcSZRSJqMkpuSuipWsSsICYMWGN//F
trICoKVqbatbZ8nWt+oirnKta0es9g+6/jKCo9qZJqU8atds8BUfMW3EYHMx1GGcEhg2CCw/XwrJ
mv6wq2otbEc+0J/DEoOpjuWZCEQqm0xgdjs4XWSXitpZQoD2F4j8lmZDhNpJxLKZtdSGX1Mbl9iO
VSazDVJts3FbTZxVEgLALSUS6wi2bdVbeCWm+oyrT0ukdRFrlFRzB/Fc6Gp3u9wVSHWhalUd+rK7
5BXSeMuLDQNigqocsQ16+3PeSg6SGM9873Xia1/ohte4E82vt0LQ1v76V1U/GLCBAWDIA6MSsnlM
sJdeq+BNLNcQDL6HgB3CU7VBWE/afOWE8ZVQAFT4m6V1RIG1Mc7+ULanI+5IiyMM40uo/hIX2f1H
hh9TYv+21q2WNQlZKZFjZQ6XHDsuSY191+MYb2e+Su5EkbMx4yZLOSJRnrKVr4xlRwyZakHNspc3
sV9FrPbLZJ6EboeR5DKrmRPFXTOAGuvm073Yj3CWpW4sceKrnPke+G1nnCNyZ0npNRyg7O2fD43o
RAOooYrss6Ir8YHp4gIce/4XUk0rkOtuIsUpkV1/6qyLBkj6F5V2yH8W8dtcalrQliktqAmB3DSu
uBCpVtWRr/pkTix0ErF+9L/a7GuM8ifY73vloHEx7Eww+TqXzsWWiX0P9eZj2QaeqSNwmT1pN1Pb
j/lwd63dCEfz89nX8XaqghxkaAPjIdiqcq86e61ujoS5EfVVMEFDBOxczrsSnr7Ed8t673AEAgA7

------=_NextPart_AA3_C1BA_F81D93A7.72C8C613--




From gpadgett@firpos.com Sun Jul 15 15:48:41 2007
Return-path: <gpadgett@firpos.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAA5B-0004pG-4Q
	for ipfix-archive@megatron.ietf.org; Sun, 15 Jul 2007 15:48:41 -0400
Received: from [77.199.109.75] (helo=75.109.199-77.rev.gaoland.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAA56-00041X-DM
	for ipfix-archive@megatron.ietf.org; Sun, 15 Jul 2007 15:48:40 -0400
Received: from [77.199.109.75] by smtp.secureserver.net; Sun, 15 Jul 2007 19:48:37 -0100
Message-ID: <01c7c719$22d0fd60$4b6dc74d@gpadgett>
From: "Paul Rudd" <gpadgett@firpos.com>
To: <ipfix-archive@megatron.ietf.org>
Subject: 100mg x 90 pills $1.78 per pill price
Date: Sun, 15 Jul 2007 19:48:37 -0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2905
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2905
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

Viagra 100mg x 10 pills US $ 69.95 price
http://www.divideindustry.hk




From antti.huuskonen@egolf835.com Sun Jul 15 16:46:45 2007
Return-path: <antti.huuskonen@egolf835.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAAzN-0003La-2D; Sun, 15 Jul 2007 16:46:45 -0400
Received: from cc443308-a.groni1.gr.home.nl ([82.73.51.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAAzF-00056A-RS; Sun, 15 Jul 2007 16:46:44 -0400
Received: from [82.73.51.32] by smtp.secureserver.net; Sun, 15 Jul 2007 20:46:46 -0100
Message-ID: <01c7c721$42717b10$20334952@antti.huuskonen>
From: "Edith Lockwood" <antti.huuskonen@egolf835.com>
To: <iptel@megatron.ietf.org>
Subject: photoshop cs3 retail price: US $ 999.00 Our price - $89 you save US $ 909.05
Date: Sun, 15 Jul 2007 20:46:46 -0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="us-ascii";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.1830
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

photoshop cs3 our price $89.95
http://aleoerprr.com




From nceg@chollian.net Sun Jul 15 20:29:30 2007
Return-path: <nceg@chollian.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAESw-0003eo-2e
	for ipfix-archive@lists.ietf.org; Sun, 15 Jul 2007 20:29:30 -0400
Received: from pcp004763pcs.sdsl.bell.ca ([69.159.242.50])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IAESs-0001EU-Mh
	for ipfix-archive@lists.ietf.org; Sun, 15 Jul 2007 20:29:30 -0400
Received: from hnr ([99.211.26.167])
	by pcp004763pcs.sdsl.bell.ca (8.13.1/8.13.1) with SMTP id l6G0XguU019329;
	Sun, 15 Jul 2007 20:33:42 -0400
Message-ID: <469ABBE8.2010500@chollian.net>
Date: Sun, 15 Jul 2007 20:29:28 -0400
From: Maxwell Y. Emm <nceg@chollian.net>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Some of the improvements in this release: Converters can be registered with a priority, allowing more generic filters to handle classes that don't have more specific converters.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

OTC-Advisors.com and bullishalrets.com Issue Watch Alert On SZSN

Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN)
$0.33 UP 37.5%

Market watchers are already alerting investors that SZSN in on the rise
and moving fast. Read the news and get on SZSN first thing Monday
morning!

Electrical Jobs: Defense Talent Network - Senior Radar Systems Architect
 Electrical Jobs The electrical engineering jobs service of Engineering
Careers Online. All use and rights are reserved. I am delighted to find
your wonderful website online. This includes interactions with 
personnel from system engineering, the development program offices, and
the  Unified Combatant Commands to ensure requirements are adequately
addressed. Compas, v evento de asometalcr ! TestCase and you're done.

As Electrical Engineer, you will perform. The Fort Worth Botanic Garden
is located on University Drive in Fort Worth.

We are the onlySyndicated Bluegrass Music Calendar. It'll be between
Kohl's and Home Depot.

Quad EMI Filter Array incorporates ESD protection. I know that
design-wise they make better sense than a test-base-class that overrides
setUp but usability is really a PITA.

The owner posts a new photograph every day.

, Pericom Semiconductor Corp. Surely a good download!

Electrical Jobs: RF Hardware Development Engineer - LitePoint -
Sunnyvale, CA  Electrical Jobs The electrical engineering jobs service
of Engineering Careers Online. In unit tests you can provide your
objects with a stub clock that has a hardwired timezone, date, time,
etc.

Work with stakeholders in identifying future  needs from a BMDS-wide
perspective. Defining custom constraints Creating new constraints is
easy. I'll give this a try and maybe I'll pass on the code to you.
Utilizes sound engineering principles to direct the  development of a
system that satisfies customer needs, and creates a structured 
development process. A  BS Degree in Electronics or Electrical
Engineering from an accredited  university is a must, preferably with a
concentration in microwave engineering. Documentation says: The
NotOverridable modifier defines a method of a base class that cannot be
overridden in derived classes. The Botanic Garden is on the left
immediately.

Improved support for classes using ObjectInputFields and
ObjectInputValidation to follow the serialization specification.
In unit tests you can provide your objects with a stub clock that has a
hardwired timezone, date, time, etc.

Electrical Jobs: Defense Talent Network - MHPCC Sr Radar Systems
Engineer  Electrical Jobs The electrical engineering jobs service of
Engineering Careers Online. You'll just have to enjoy your free float
and take a chance you might meet somebody famous.

This lead to a lot of duplication.
Candidates must have strong analytical skills and experience with
stochastic processes, digital signal processing, and algorithm
development. A  BS Degree in Electronics or Electrical Engineering from
an accredited  university is a must, preferably with a concentration in
microwave engineering.

Improving team productivity. Even in using the word doublethink it is
necessary to exercise doublethink. With all the rain lately, I'd suggest
bringing a tarp to put your picnic on.
You can chat with them, get an autograph, and ask them for a
recommendation on a chiropractor. Parades, car shows, pony rides,
carnivals, whatever you want, it's somewhere in the Metroplex.

The Original Bluegrass Music Magazine - it's the music and the news that
matters.
Applicants selected may be subject to applying for Secret Security
Clearance and therefore must meet requirements for access to classified
information. PHP-Nuke comes with absolutely no warranty, for details,
see the license. Defining custom constraints Creating new constraints is
easy. TestCase and you're done.

, Altera Corporation Search for: Search what? Terminal Connectors save
PC board space. Junior DetectivesThe Sixth Floor Museum is sponsoring an
afternoon of forensic science for kids. Responsible for Engineering and
End Item Hardware. It'll be great fun for your budding cowboy or
cowgirl.

Polymer Capacitors suit space-restricted applications. Provides
implementations of ObjectInputStream and ObjectOutputStream, allowing
drop in replacements for standard serialization, including support for
streams of objects.

Electrical Jobs: Defense Talent Network - MHPCC Sr Radar Systems
Engineer  Electrical Jobs The electrical engineering jobs service of
Engineering Careers Online.




From wypyuhufet@yuhu.biz Mon Jul 16 08:29:46 2007
Return-path: <wypyuhufet@yuhu.biz>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAPhx-0007gR-GN; Mon, 16 Jul 2007 08:29:45 -0400
Received: from [203.156.78.101] (helo=[203.156.78.101])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IAPhw-0003rZ-V6; Mon, 16 Jul 2007 08:29:45 -0400
Received: from [203.156.78.101] by mail.yuhu.biz; Tue, 17 Jul 2007 07:38:13 +1200
Date:	Tue, 17 Jul 2007 07:38:13 +1200
From:	"Kay Finch" <wypyuhufet@yuhu.biz>
X-Mailer: The Bat! (v2.00.6) Business
Reply-To: wypyuhufet@yuhu.biz
X-Priority: 3 (Normal)
Message-ID: <905588087.97029026276110@yuhu.biz>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------A9FB2C2C09F467"
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------A9FB2C2C09F467
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

Hi there!!! 
Incomparable offer for you Our Dear Customer!!!
Only during these 5 days for our byers unimaginable offer!!! 
On all preparations you need!!!   
Fill in your life with colors of joy!!!  
http://cropdistant.hk/ 

Sincerely yours, 
Online community of pharmaceutical chemists
------------A9FB2C2C09F467
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hi there!!! </em></font><br>
Incomparable offer for you <font color="#FF0000"><em>Our Dear Customer!!!</em></font><br>
Only during these <font color="#FF0000"><em>5 days</em></font> for our byers unimaginable offer!!! <br>
On all preparations you need!!! </strong> <strong><br><br> 
<a href="http://cropdistant.hk/" target="_blank"><em>Fill in your life with colors of joy!!! </em></a></strong> 
<p><font color="#D9EDFF">http://cropdistant.hk/</font></p> 

<p><strong>Sincerely yours,<br> 
<em>Online community of pharmaceutical chemists</em></strong></p>

</BODY></HTML>
------------A9FB2C2C09F467--




From datkonqmq@Asconet.ro Mon Jul 16 09:51:03 2007
Return-path: <datkonqmq@Asconet.ro>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAQyd-0001x8-2Z; Mon, 16 Jul 2007 09:51:03 -0400
Received: from 86-107-50-139.asconet.ro ([86.107.50.139] helo=Asconet.ro)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IAQyT-0006ls-7h; Mon, 16 Jul 2007 09:51:02 -0400
Message-ID: <037701c7c771$ddcb2b60$c83290ce@datkonqmq>
Reply-To: "Winfred" <datkonqmq@Asconet.ro>
From: "Winfred" <datkonqmq@Asconet.ro>
To: "Noemi Hernandez" <ipfix-archive@lists.ietf.org>
Cc: "Janeen Murphy" <idmr-archive@lists.ietf.org>,
	"Elmer Carr" <ipsec-archive@lists.ietf.org>,
	"Chana" <6lowpan@lists.ietf.org>,
	"Dierdre Nguyen" <kitten@lists.ietf.org>
Subject: Thx for all ur help
Date: Mon, 16 Jul 2007 06:23:46 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

This newsletter is dedicated to the product of the fresh customer
satisfaction review taken by the International Pharmacopoeia Committee. 
They study on-line pharmacy client and then assess every on-line pharmacies.
 The 2006 year top award grant to:   Discount Online medicine store, naming
us the main web based  in the world in clientele fulfillment. 

money off Online medicine store is a veteran, safety, and fully-qualified
online medicine store. Our prices are very reasonable and appealing. 

There is no greater place than money off medicine store to create assurance
and private purchases. 

For more details, Please check this link: http://www.medscare4.org

The intension of this newsletter is to help you out to get better fitness. 

Joelle Bell


increase The first thing I did tree when we got to my parents home was
introduce Ben more to tongue my father. The second thi Okay. stride "Down in
ever such garden a ornithic hole, under inquisitive the hedge. I saw it
first, looking after the greenfinch, and she sa 
Describing the electron desire as a pliant, elastic forewent field, capable
crack of spreading out sand like so much melted ice harsh "I don't know.
night She went into the shock fought brewhouse to Nancy, I think."





From sjniz@dell.com Mon Jul 16 11:40:14 2007
Return-path: <sjniz@dell.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IASgI-0001fm-3e
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 11:40:14 -0400
Received: from [66.7.122.138] (helo=ovwqwrh)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IASgE-0008KO-Nr
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 11:40:14 -0400
Received: (qmail 28121 invoked from network); Mon, 16 Jul 2007 09:40:17 -0600
Received: from unknown (HELO ozv) (68.219.86.86)
	by ovwqwrh with SMTP; Mon, 16 Jul 2007 09:40:17 -0600
Message-ID: <469B9161.2050108@dell.com>
Date: Mon, 16 Jul 2007 09:40:17 -0600
From: Stephen <sjniz@dell.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: pragmatic
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.5 (++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

SZSN Announces Sales Income UP 37.6% Over Last Year!

Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN)
$0.38 UP 15% (9:36AM EST)

SZSN continues to climb as more great news unfolds. Read the news and
get on SZSN today!

Main door to the carriagehouse: wide, narrow, side view, after a good
sweep.

Clearly Rees's language isn't the only thing uncensored. Charles Avenue
and Peniston Street: towards downtown along St. A log of pinhole
photography. If you are a subscriber to the main

However, I am pretty confident that one of the group will have a
suggestion within a day or so .
That it allows for the creation of brilliant ideas and then also acts
upon them. AdSense - Klage gegen Google als Werbegag? Maybe, but it
shouldn't be. Wallis has done a good job of making a donkey of deity.
Click To Play and at blip.
Click through and enter your zip code for a list of local clinics, from
Oct. I was stunned after the first reading, alarmed after the second,
and moved to respond after the third. Buy fairly traded gifts this
Christmas! Suicide photographers. Freed of any effort to change the
world with a play, cast and audience are able to revel in the healthy
release of nearly incessant laughter. There's a lot of good that can
come out of reporting potential abuses.
Open RSA London is a group for all those interested in the RSA, its
people, its projects, its aims, its challenges, its vision.




From ioh@transamerica.com Mon Jul 16 12:40:21 2007
Return-path: <ioh@transamerica.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IATcT-00088U-P7
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 12:40:21 -0400
Received: from [205.201.127.159] (helo=wlypuo)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IATcO-0002IB-Uz
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 12:40:21 -0400
Received: from [108.82.30.221] (helo=pks)
	by wlypuo with smtp (Exim 4.66 (FreeBSD))
	id 1IAUt0-0001gB-LY; Mon, 16 Jul 2007 11:41:13 -0500
Message-ID: <469B9F70.8060808@transamerica.com>
Date: Mon, 16 Jul 2007 11:40:16 -0500
From: Dick <ioh@transamerica.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: Re:
Content-Type: multipart/mixed;
 boundary="------------080208080400010503030601"
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c

--------------080208080400010503030601
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit



--------------080208080400010503030601
Content-Type: application/pdf;
 name="Complaint.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="Complaint.pdf"

JVBERi0xLjMKJeLjz9MKMSAwIG9iaiAKPDwKL1BhZ2VzIDIgMCBSCi9UeXBlIC9DYXRhbG9nCj4+
CmVuZG9iaiAKMiAwIG9iaiAKPDwKL0tpZHMgWzMgMCBSXQovQ291bnQgMQovVHlwZSAvUGFnZXMK
Pj4KZW5kb2JqIAozIDAgb2JqIAo8PAovQ3JvcEJveCBbMCAwIDU2NCAxMzJdCi9QYXJlbnQgMiAw
IFIKL1RodW1iIDQgMCBSCi9NZWRpYUJveCBbMCAwIDU2NCAxMzJdCi9SZXNvdXJjZXMgCjw8Ci9Y
T2JqZWN0IAo8PAovSW0wIDUgMCBSCj4+Ci9Gb250IAo8PAovRjAgNiAwIFIKPj4KL1Byb2NTZXQg
NyAwIFIKPj4KL0NvbnRlbnRzIDggMCBSCi9UeXBlIC9QYWdlCj4+CmVuZG9iaiAKOCAwIG9iaiAK
PDwKL0xlbmd0aCAzMQo+PgpzdHJlYW0KROLrHKunKqWz0mwdAdiqRlyjwxH++14Mi0j0hYEGjApl
bmRzdHJlYW0gCmVuZG9iaiAKNyAwIG9iaiBbL1BERiAvVGV4dCAvSW1hZ2VJXQplbmRvYmogCjYg
MCBvYmogCjw8Ci9CYXNlRm9udCAvSGVsdmV0aWNhCi9TdWJ0eXBlIC9UeXBlMQovTmFtZSAvRjAK
L0VuY29kaW5nIC9NYWNSb21hbkVuY29kaW5nCi9UeXBlIC9Gb250Cj4+CmVuZG9iaiAKNSAwIG9i
aiAKPDwKL1dpZHRoIDU2NAovQml0c1BlckNvbXBvbmVudCA4Ci9OYW1lIC9JbTAKL0hlaWdodCAx
MzIKL1N1YnR5cGUgL0ltYWdlCi9GaWx0ZXIgWy9MWldEZWNvZGVdCi9MZW5ndGggNDc1NQovVHlw
ZSAvWE9iamVjdAovQ29sb3JTcGFjZSA5IDAgUgo+PgpzdHJlYW0KEhCIL1INYPzsu37I2YNOPgYY
MXxC3FehcZ5apM6uTUhMxSdG3772NClw07Zxby3k8LHUdtRaAm07k6nJWuDPOLQgcbX4/I4IbVOE
cHysFCkRnjLRxIfe32TW9T/F1lVIJfVyF19lcPt2lJwOjxfN+TByb+aftvuR82mjpIqbWk7fsybF
/Eogk2empS/OU61LRetUg6JYpRi5nCDivqVKehJebgoqzIH+x0cwSIx9KXwW0C+543VuSKP8LXKw
RywXofbZ/Q4bHqR+vm7qo/sBL+vx08DqEOwgHQqmIKYJIjMkODng9HfwU52vluIwcBCEedxQiKBk
04X3O0vxwPh1gWY4pVBZVKTDLLsCcE71fLQmZpUnNHnKrHIyCRnpxUqarutYd24HFrHsv1NV5zsC
JU/VA4DWyHfodEYT6RaK0Kc3tnnQzFJFocaPeSHnpVcrdjtV41ueHq6+ZSZjx3JkyveiPIilkThl
/flG7YpgjD53Do4SCDKxdhEXgF3V7jj5wquoxihC8XgAVDs8i2UaZTI5vALDKkgw7c7ROaiZoIyx
mjff3iGTvJcABTMPLAEIVwe0hqf3bfj+c8qVKBJ1oxABvO3fOxWfKzT9WCJjah63HKj40GA3FvAs
p19FL30eSAIBVKGbz6+hWV7yG5mnaT6284qo8IQrxtsVBVQA7rjilfKM2nMZEZ9fkBRM76HvbrGh
nxNeN6P5I6ZUOJZIXe6WxiPE39hADN5mC3MHopcuTiN9PA3/ldUG0C37JeLjAz/QxpHOfovMhOjt
Q68ZDYa2KbevOiBWl5rzXw4C7ypEO1f5w0g3aUjMIJEbWC7T4eYqoBr6kUMr6iuliMQTorw0go5e
ZY/jXHRZZ/iQD4yPZdiczxECyi4zO5bsVLpxodc/jZLlg7e0e22okodreDpVmQ8OiE4gpuQCxOeq
pPfdCvyCuBVeDMaMzo50IQjUiRQ/nEmTO6KlmdKhZhtwNdPemY8Z0zpm1t++KIiPpGtirIV0iPF5
bYMkeBa2+gt2RGRDFMhAXFS9IzuOli9o5TAyR+584sdh55WfLlGWKgw4tg2n58hEvU898Bnq44mY
iDex0eecfxn6LX6J+af4MBMnszEVPxkLGuU/D1lxQgpv8+dNTzIpcnyEAMgTzhpZcwqfFung9fyB
Opk/c9dRr7PxXZ8K++cHU2IJaBP9Y63AQ3VLSbV1oi6VIQCFbE20A56I5UXLb96IxPMRz13e+9bC
quihAW30msrv0aDrdzn76sAkfrqlKaOU9pqmamPfiOCK8yyIP5N3Xd5mVeJs+4rI/oWkxbRbgipA
SVlnaDV3P4bxK8dmVOqdVKB/Ca+Fqks4E1po7hIoZNiDaipGxOFKzOss8muSZaILCU+19pDqGwUx
ZesYnANsSBjymyd1AkWnOadDUsF3EN/wtkjO4q6gyTW9lhSxbQw7WhIBpgDtgQ3G/NzCC7vOU/tJ
CcLfem0EThv6njmiAXs4ycVeov4+TYBU+Fp4pDYkr6Y4MtMgmA8fLZpzpwsUWKqVIImEpXs9SN/M
OdX555S96cg4NYn7BQYR+3su7yPn9OGw+CPkqQ87wAxPGJCBKPbxZBKPjaZtcdEYPq/QlBHLVqQ7
lMXLo3N7BVH/VNcih6i/leLzelDxXKvhfWh5ywnDbyOtrZxaCDNxAny+pucig2pvtpNyR6a4Mde1
3k8xCUJs8k7bwJCHgAN58lojQJdFYgbavfDiFqP+AN0xIsdGIymPzvX5TEGI6G5Ff7BlaT1ga2yr
HvuwgTsSjCM6R+RA7DqToteDW4agcuOrxp8xF6WpFJAPMN1E0jkFYpfXRRITGECOeRFXIpUiLSTY
BEserDXYOU6JNTOQjVBKyQ/G5K936iRTTOOInfTxohhVfXOrRebBKxLq9KbCsFGIpIbkYrIptTlc
lU7sAoYRqVVXZghYHp/GU3LgxQZ+x5/uc06Y37Z5nOmL/VlR6vHnbPgoevIK80kEobv4sWbV6DDH
h1BhxJ0ceWEYbLyl23pATX1RR+b2UYM18QkYfLw7hlgKRfRIWJzpGZdcS9/OQng/rUyI+G8SBmYO
bq83tr/3zr1VNOuWQQSbKHd71+18tZ5PHpbrcMggfmsbU3shanV+24zs5NbvY8E/cSjobmSiJLN4
wsSMpaHO6rbcbWpPqhKoJCR6wmtnHtQzN8Lr9XmLxpaturdH41c9KGXf4Omdu79xA3C2XNYjp4iV
64uDWQvsvlfmb3A0Z61wE1988UA1lazuogMF6/h4F6pUHwIq8jiRovSRfJmAu7yg2OZag0ZhRBdi
d251rE2qzms8X4B/DUYivYTGi2+PdsBYyEedN3+6kg5Dn3ULkWach/MJqtvp4PHC4S5x1pJoC4lv
L1DANJ/ShvQLACWAJ3rM3AQL3pDfUebuObqkWFZsz89Pkxl5AA4l1keYLhhno69q0AYDe39Zx8yP
+L4M19C9zD4eHVvhdgyjpzVp7MESQCayrYHPiCEuyx9FJPdLKoPFKUKOuIaq3is/C3CjKXRW3d6X
ttk8RKgo6Tt5/+80yjf5E0Pt58O+k/ddqGQ6nrwCA/WYZox+9WIaSa/sMljOHnax0RNx6gemdMQs
Glottt/3zXLtT6F/BjpSqfwdvAxgyjVT7BpNNTbBVZ6FY03QJhwxGlXTQzgXvNA/VVI40gG5qL56
6Rv7XearGH+bNuEu+DHhNEc7+jDjscKTuLeCtMjlrPV1jj8io4RazwEQN0H6laXYExlLy4hhO+8O
J95YOGDC8DcSBUBF8QoJ+Xr+f6YITjnN2fuF/YFannaxBiK+vuoujmoGoeLcfhtL/AX2UL4n0o0g
BnyESyYfNr1UXq/tgUbtHrST2LGEYbUc9EjIxPUlbovDFf8Kn+JHbjCimWaD4pLOk958iJ1a1L/C
Mc/N2onBEvPhseFhnSnPXwv9LmyI+ac+jKwdvs4r0G1+hBfZV9V//++/grCOjqy1qM7ii0+xHQYH
3skLyavqFUKDg5jPPf9zWo8H09ycceqCsgCJE1l2+LYZjCmME3hWDNv5k5DySA4HjLppCNL8oNAr
oFGBJmnyiPfwndt1wtA5kJLYI+fa8sDF02zvCVTi2fL1wtfdK6S8OOKBWOM316LVBh+cBn22lkaj
NoLNZ9aE5kA1/ALOF9Ih6M+1gN9clgeNk9n+1a1UjVfCaAmZz4hYZA6mlhB6STNFK8OP1m7C2Yk7
Fclav6spgBn2WjAwj9b7dGBlPxYqqA5s/lCHC7/4kVft6aI+RyEbaRIDeaZWg2HZEVD4nlfaUlNL
8I98KbbNrJ+MHiAKAABGfWavfBq2SzxO0dre1RCr016+6duiXYxiEyOBhYEdFOKoUKH+FJ7hkBjQ
ITdAOnDzz0MmYuMpFTmClD29qGZyNpyXLz57r+X+xga4jJ96rrW2t4j70yyStG8f5l8itoHKqkRB
3GMB7NkTYg6/0ha400COg5nVzgttQpRgVPQQT1N7i8/4hAn+cfDVzygTIt6aCyw3DuLPOlxXDTUb
XXMcy6gBQwcZqdg0h7gQmLnK2jegBasPe/uPsxsgB8Lv78gf36sPDXm4gnrgDvygxIdB/rGIUAl5
SPPuQj7UNQb0fQn2kBaaLP3gx6XGswN94vs24TB4AECEBpeB5br+2Nvy1CWsJJT8j7tszFAiHL9x
wDoHtANEpE71y4MMgVeZCApTQSaNZwqNJnq99nqfOp/50TMdXC3w/wwzgr13RtdjI338h9DAd+XZ
XtQm4epDPcM+5PerWXXyZxuWOg0hVH8U/mCD81O03LSXbgUh2pkYZ9dMedeOjs5mFVmBZ5xlLnZ/
wpa6z0Ct7s1Jk0rtHMKapdptM5F8RqIOT+S5kHtfgUA0JgEBO9lMm4Souk53CdMmsigCVgwlin6D
RqneQ2AJ0XPGuQcewuFDBBqocLXfH675bAdkNifMG3Rsjhi+Vak4AHcfT0h7xAQV6wN+B8BK8/Rj
XzqdPZlNE8b4Qt3fzRCSImx0zvHTn4rnYChsJgGqsPr5W4M86I1j1F6m2WiNfl7AFQlwvlO6o+W3
RNPbq0TBTUh71T+Q4SOLYWm79bv8eGonsWFcjEXdOSc+JvRyZMMmqJfp1E9LiK1jZJ4HDndnnMiG
Ptu4vYP9yWaGGM/vG2fqoVlMOdVTy1jej4DswVsIiCc/9bnPl+7gMKgwHtyerSLU902MqiOElWIt
gRBLhd4WNfM1ShcX3eNTb+YqhlwKgHb4+o40m2U0BV9Ez2F4wFvS+Ldbeh/qhSWiWNhNLr64Gl8O
8YrRSa+uuJV64iGWw8kRzHKYSR8qUQgHl0ahnBv5hnyBsgd1lfzJCF1q6DYyZ1m1aW7PW54HqqL4
C5qt3EszUgdw8k60GuVXV8QRi9BV9cPLhIGX9v5SwVIxWC5KHfx8eD6HTLybqfrFqmI4wbGzNTEJ
FowzrJm4Kuz+UVOOdU811Ng4qJNuoDnMozevvU6ifKO/g/PzYl5FX/pVP7pdL3QQPxJyfQzE0YmL
+oVCbdqIET0BnntGp92DbC1duClPc7AveqX0+HCEmPn1VllMQPJJRGveQu65NcvlyYRMXmyKJyju
Fu+GoRaJEc52H3Pe2KGDQnFo1tSK9aae/oWJEWg3crZfwaF+yYRWE4FQhyiAisJ1oRh62brKi1yV
OdToXVanSu85RSDPFr89gw9w+sYjyfjfV2D2ZiiWRkyPvq0y5DaoAgo9qb/m/aUhCrnWZZ9AvSyy
hlDpdvCM37X4Pr0fNg4/lzcKm8mUgpU2LZPxfmDyeYR4ttOd11zuT5KwsopmwRzjYJnBfJ/BsUNh
jQcRz1cK+2ehS4LDGVGcjegJ9hs+sq+1e6OYfUwv9x8naR5b6OpHIBegq7h1ORhz/N/WH1G0tV02
aPIXVQexLQL/AJ56x9Q4wy3vTio0bRVgCH8afSK78o5bMZS+v5z/rNShmgY5f2uHw0kHsBfV8TAu
5Di9buOc2UcxHTLiXxnziP97jTAGq83fddhcS+1qyO/A04o12bvCURqiL1JLX4qkVhzyWJwaqILg
AVBO9uYaEiy0Yjge9CoxdOA3qjrGH7K+v2wc3+vwUSZe/9469oyil+qzA92Y5pjodQ6KLa89mSXl
X68Qkgy4rywKLpUXHyYfTm7syU1rdmQwrBNobtOXfSRC++2KXfyffFhxpMwErxQAkeyZ3XPL2J3g
BC8kp2OK59Qcb64YyXbpU2ffygpZCn69nLqgB3xbDX79J7DaAHjt4u5mVws9NIsQA7pznTGncLVo
sWyzwqA5RgV9jtLXqtzrJLYPSrTNUqzTJdara5BBbX3cRiy2dSjA+kv9dkag7ZPpSVkTspyFLycs
gba/GDGJha7hkZeF75jcWVqmpnloPf2YqOJJ+IivLE+YOGVCsCj4ePrFEYjWLpEXwQXZLqbuGMlF
UJ9tx0PW7aIVNq67yr8nb4ZNa17mtEmH/V7x9HxUiAIjZRLVMObIykS1YWWgY/zNRfsolqJYe5/v
5cLzPT3KD7Rve7QfO2Tb6xzEWJA2j4dfVxTOkdwiZfegRpS+Xfx0iqUWP6A5i0wGElnaepKAjUf1
WeBdXr+pOvkR1hfRX7oV4v1q1zHPYuIpSIcBZkM9LAEzfNIQBmputvIeZA9et/qh7nteaq8xWLYG
rHy8A5R3sXYjYAy1ll+dXwLuxrtJsB8Io9i0bVX4LnezteaTq1oi0ru21d9smbfKandgYrN/f5YX
cUepdPDaybXJZ/6Wj3+T2KvWX86blnWSYjdz0evKNQo4NBfywbX185cRfkQK+nYDdWId1YQynYAZ
qZ0OjcVIKZiMFTgN+RUSOUCG/t+zZoW4MU74agoXEYUQ5PU0CQkiOxzlRm5ULoIatnGhtSuTKUiY
lpE9S5wS32akiVkli1Qdan9jihYEJf0Co7hCwyt/6oIzfl4BEwBVqxODG9tfOaTYIsTbJ1ZVwMc/
o62eM0Bbxp9yCwhu2BkrUGigzZOGx/u7sDDhYNdmNI74KpPwqH33Aqw2W97GcIDrJJ9P7IPB5TDB
u+Lc/uNDd3TtK2MFCC1QFzwVxH7KcqGVw72GJKJOH5iZgHtias2JHvu25cLLoV3NE5Au/JgILNg3
p4Azc4BWS0Jwe/olkHdn/vS1WhEIykvu8jucfK35nKvtiYbmXFYbf+97qOaMB5362CxIyBecDcaQ
ygahv70FQMkUM6IfJ4zs1sgLkuRqdkuA8zXTIBmHMRZHbCPCEOPORdf3er81mgd7BUKGTC7Fr2x/
x+K8sghpOYCvVPWVgJiV1SlwnbB+DOB/H0PMBUVXI/m/dYTkm78SrUUGI/vPB4oYHlfBbDcrSVpv
cYDeuEO4CmVuZHN0cmVhbSAKZW5kb2JqIAo5IDAgb2JqIFsvSW5kZXhlZCAvRGV2aWNlUkdCIDI1
NSAxMCAwIFJdCmVuZG9iaiAKNCAwIG9iaiAKPDwKL0NvbG9yU3BhY2UgOSAwIFIKL0ZpbHRlciBb
L0xaV0RlY29kZV0KL0xlbmd0aCAyOTA3Ci9XaWR0aCAxMDYKL0hlaWdodCAyNQovQml0c1BlckNv
bXBvbmVudCA4Cj4+CnN0cmVhbQr7ax5wewuVYDGC3rBUVlhccL7U2I/IUJPntU7HOM+yVGUFQbsE
pos7+7blyr+vQpRRnGH2PcjeB5QnmofTRewiXVoAqJFl9q56JOEByEYdXoC+FQVazSL08zFkJ1ZO
Moia8AqwY0++PCBaeIT6iI0hOOcJ0/I71JW0QJ9NDF60/6vucJbCBePyksv806OmWEREOWGWOGPo
zMVBSnqX3djTPZPsOfc/vYxX6sOUiXPocc/q3LB7burBz9rPhd80UvLDr+cn4b9FBBepRYQvR7b4
CY/dQDBDaTVj3MfhnKsGyu6r5ARo64nvLkDHcxp/stfgVceFRI0HYaWbU7fqH7m4UowSXUjzDOLN
dzub6+SzHexuerubAmcJSCEEcRLyfJayCXwEb5v3T9Sa6upw3l04mwRMfSiIi5Q+f880X+VrG+Rd
nmUeg717NZQlqeKasMA2HSdAzbINEpHq2SyWPCUiFDoL8FQeSvqF+p0s6ZJp1dDxBe66ER3xTenB
ipLPNeVhq2JmLJtXZECNw/FZ1tkAAZzElfUOseQQzL+QMOyAiW6rBUNT0N6RjU4GDP3rYc9Q94OI
F4oXD2NawomStRefEFdF83lvpnHj9bTprUB9vaTuXDXIkzQnD8Tu+SGlL5Xg2N1v+2MaRv/4pg9z
R7gUJAa9L9PDWlPzrtx8KKQbxfS7E3h7Hq5KgCN67GapWGdKNJB5jXMvYnNKI8saUIuNkFC+3Yp2
L7xBlYtpG+0aKKmNwD7O2BuV7BQsfk+Mq96jge0GLSb27MLG8nLeUclmwCuTCgXpLdFJic49us0J
FynFx8MBINr3HWHXCKpgilU3ppanAHFEUd7g13DmeYgOb2El65kU1Qqvo2C7AQA+0Uk9aM2punYA
RBArADP9QMf7HPZLsgAsDjiPlIXbCQWUgEj3lBFpQEaoU/nPBL73b9Z4E+bjoS3uF6+Pl4YutfG/
yC9VzpIIPtqXljKQVLfWX4Gd1D49RaRH4WGK0O+76Ah+ktLa/AgPnchYWtulJB9GoaPr5nRR/cHB
GwJoKJVgiS4X87+izaauP8KdxFs469rvk1NStzU+P2u+aID6XVk71nJ4jqkWTwGFUuGMMgyUvJOM
nEeyrpElfo/NlDPhc/EaBV7p4HwWiZ1x3UC4wBpicStJgzc8dLojq5cVJNmQFeIAx5kYudoocgNV
ovh4HIIrMiap4+oxjydgDyuGhblwYOo/JP2GqTPX8o4DOds+b5+BZpVeH1Nsk10hrHiIYOTitPPj
yurQR8V/jg/C1QAqg743cs2DDKPwfb4mJjxlRimIZ1QRXcJMfXmbWkPmrlCXuxEabjzWSzqW9Ja5
Fx3u8aGQuW1QNxWk6Q5BSjisA0q8xBzs5yTPH3w7M8VzDmTqlWtTJ0Eo2hsa1xAfD70sm1ZjKl+e
WaryN++zjv8x3oQ3/axVmrBW1k9enbwYHEv8mLrcNzaO4WBRH5DN6/FlAgTiOOxDuQfqvxpNnBC3
9UusmhEZ8N6iPkXgtLtBEz8KKInpNpMwu+ny3KY26XI/A1ryFrQGxNcTFsyGlq4B0FWHluK3lVLb
cTCsyq/r+7OGXZlo4J9fBTWLXEeSURE7af/IwFHaORTsAl/mlN4KYO9lHe44lXlOlOulBx6hXEA9
JEKG9Ez8nN9c5T+V/A/wLsoTlIUdhLsOSvmZkNKjt+n+56NZJSEG6nz7wgkBRmp/zGfHbtu4UDJ4
KrLYAf7gTmucEGffdpwkGa6+BzC6vUO+LXRvne5ZEeGayPA8xEOqaiX1hMkEwKyxgyWaZjg3etBo
HMk1a+me4Qo9N9ZRxI6nmLL4y9H5507/42NEdtDlVf69ES5nJwPZ9bWgFLSgBfzaoEYxOzkNvyYX
3Cj2VX1/DhqWhIw5ugmvJtu0peKS8Cf0JFS7F/DESq99+0if6PbDOVxzdlT61N5G2Kv8oFrIidfU
0N2XDwzncFp9WcYbbRZ2ItWD9nwILE4TEODjzMKLojDWosc6hol89wcA/jqzgq+I1iFxgFse2mnf
PFljMZL+9hZAAVRdBvu+vbKPpzU/KM2sTL80pGk7luHrBEl6t4kuBT3Vn+3N5W1Tu3qhs9JYWvym
EzGzvEwDwkV7iXw3puguPvVYpMrQnM7rSSaPArn8VVbJnbBHxZJtIIahyu77GzmtMvERBIFTU5v7
mrrU34dWp3zeN9NhDN2DbxdqyxHKyI2KhGeBWtfj6MHlS/kyXPSoWWtfqvSnopDhsYctk9SpYvva
HczGaI42GIQ7gpXys5W99PNI9HiT0taUiLw5h2dCYa1PKioEmz36faKgAmnh09lAbHGCyD+KtRpY
tOfwe0aFRIKAxxVDVNB2CMrtoaeovU2KygRrdKhxlxHvHXY8WpZoCMr1mmd5y35TpVMXvoYOeA0Q
/YFbQ1jxPNwCESWkcBdBBdsw/rxNSR8Ny5IIXJ3ZmdFbog0tOGlv/bxF/VVIB0fp5Z2aIRZFt5Ih
7OaDntQbEBoWadXnvM53rYnSBe3WaWIQzo0BlfPoQob1Yc4r0M+ay8yXVRzepyNpD/zc2/DJKRlV
BAtpSuDdknzpfcfaWZ1RXllDa2I74tj/a1OcEQB0d0HNBI2f/vysa4ai0BTk1daQgjhaz7LZvfyU
lQ39Uxa8UTP6wHSe/EGP7oGYEALxwB4eHmgd7CwBvF4+kMl/x6tZgw2v7ZLG0gSIdUsuFtpNQ9KG
q/VS3rdlZf1n8cPAp/R5Q3MxJ9OR7fhgM3EbJ5TzRtAOYkjjso7Km79nWdudPmqnelcoalcQ9S9n
onVSW+STHm5Da0CPrIWSR1GnERvgAJAlmFI/7CiSF354y01cvAEREaZQpSoWej+m26zrsrVkZv1h
Y94sRHC1dgos63vVTXIGAyM0WY2VFNSm8lgiC5P5npu6pTzgEnkKt5jwPHMrxWD9TX6Rnj9Ju4OG
ryURM7l3sfd0I+7ZTRLWmcQEJlqajnaGM1j6iNigQ8zFENzttQgYQqVAI4aun+mD2U9NxuGGdFJd
t3vIDRhDsrItBpt5bDcEdLNBvavGrrvLNebXcTOXFJB7+HPY7ErhCzqDO44AizjqhQSvPeJ+p1Ra
HG+AYqnD6ywblfl5caegJZ1hZcOtNNs4nZC+lYGlURAGKuJR/IJ2u6wqKLlsTRU/YGg9lue97DfN
pWjLqX0kUnoTLzCR7tfZkeXZfFutJHx9nyW+VnoBI+T5KGtiGxVnukxgk8b9vJ5MKfqkiIrW/cuL
gCx+MrrVE3mKmqhyw70oX//PUl/3QyHi5g5xcyjgw7kj9zc9hDzki/+psBTbcl5FCyfRWQiEitzy
Ozyak+ehSnz7nRna88RYauArajiq9due2PIe/rPB8679Q/BtY1A2B3VoIqJbmVEvjm2EX5QUWJYu
pqT0bqqWZOlcW95ccN4fsXFhhyBQiQ5qhPig6j2ZC3A4r0edy0tQ30tblgsQXOeT8q8x/rfHterG
he7gtshvU2RuTQIxw4/vINT8joMJsg/7ZxQwyHEbVguTDLJzcxeK9b8IaTsboODwA+9ZNOAA9aUQ
nK9v2UkSP/drspHxEisMv8HFI2DZqYPMfHTrjAC4SRkc96uVK2cvdZbnIazVX5N7j4A2uC0sVwqn
r58SYEUgQIeBnbsyorfe7t88dambPBB9DZnBHzKKpCz5EBZWGKk7ztnW91W8dz54OSLnffqkInUl
l/ySgq5i2Bhhl5MwAB1wQIyWTeUt/LGC6D24GercmE93jXSMqtEH1je/7HzYHHraTwb+TUeTiCUW
AtEdsRZFRXWFZTaTFg9iFAj7er+aeMr79jqy6YJGDxZPCoBcWRyZd8G3en8qP7ZwG9qMTx/3Q2Uj
6pYe0BInzpp8d2WOJcK9GEB8/sAKZW5kc3RyZWFtIAplbmRvYmogCjEwIDAgb2JqIAo8PAovTGVu
Z3RoIDc2OAo+PgpzdHJlYW0Kij1TYgg8wtLpb3WaP2nqF9fDqFsgYHFyld2ptJF0qm9vTXzTyYIz
WR5VnY73FQc6OKjcqF3kmQ80Tk6PxZBgWGNAbPhpUt/9yrmyz56jlnMn9jWHWpB9IvFfeReWjZqq
ROCaVKJwUik1QsL1oddAnwaAUU2NiEwBZZXggKX6sDGAtSN7Cl+tgIGnrC3oro6NeHm2nh6j0dhV
INP6MjabYNHMTQgLZG538FsTUIAO0ghxowEq9lyIhXiVyb7B4E+MaOwto7pW8GrBHgyYPzsh9oUw
QsNf6+CCqO9F+5FYVYnPoKy0gOugTu6xGWNQsqPw475J0T5PNNnPh1H3PG0rwHqHtDtaIbZpfAGF
dzhs4w4XEe/BSQWhPUc9wHb6+3ZtDqOqDk4/UzSVTiN8es4TLn/xa80RXYWq/kGwaxIYhXQe4+2E
OaRxgQprIpvL8ps1GibtTpHmNBaHwdHx8KlD1zjr1nAvvdt4ea8xZNpssJwC1nTrrUOzN946jPN3
T/O43BAcca/kHbEyqmqi9Zm3UJskg/nu4JJBmTgiIWX7taLbSWiFIXOTAwabF46xF2xslbE87drG
WbmWKj5vYV0a6y/McxKFo6FXIJxZRtKjS/12awC7jpL39fsQZ5h6MDBV+QsBMb6MIF8fyFo4al/X
lCNIocxLTzhB5WQ0cluGeMkxC24FoCM+k3Xe/UhhsyakNJxdlC07gagCoZviy9nPHARCA7l4TtAv
rh4UQOtd3d/Ao7l3PMqTFh+f/mLl03dY9UFekf+ZZgM0owFxyeyZIs1N23jdOKzuu2EyJSTDETpV
jkGb0aNZ+dhut7uZBHeMSXb7VlbnXCH8M5+doEheYquW3c0SVJEcEpPw+Ga9XTiJ3SE51LyswCEQ
uEUkzV8NKpFxJbGc3Hmc+CGVz7RBI3cxxhL2Bybb1wNzNnLdPKSTTnyeLXvJUdllFrbkOzIpST1s
MW8fP1VQeMWT3n+aNSEr4KlsWsuDb9lqf5diMRGlj3VLIPVJyNYrEsuEGk29CmVuZHN0cmVhbSAK
ZW5kb2JqIAoxMSAwIG9iaiAKPDwKL1IgMwovUCAtMzkwNAovTyAotLa+3poDM6tWXCl5BThz2PaP
A+fhAPMQRV4cAm6syE8tKQovRmlsdGVyIC9TdGFuZGFyZAovTGVuZ3RoIDEyOAovViAyCi9VICjP
2DinwSuyX0W32tZpVlbtAAAAAAAAAAAAAAAAAAAAACkKPj4KZW5kb2JqIAoxMiAwIG9iaiAKPDwK
L1RpdGxlICiBTOfGvOrl127v2qpWKQovUHJvZHVjZXIgKLtV6cKy+PDdd6LB7gZdmcg4y06d6kg7
dVRZnUAaBJUTXGJJm5EFBqHwdO1U+RvR0V5cbk1ki7k8bairKQovTW9kRGF0ZSAotgK6leeCoY0v
95j+A0qY0ikKL0NyZWF0aW9uRGF0ZSAotgK6leeCoY0v95j+A0qY0ikKPj4KZW5kb2JqIHhyZWYK
MCAxMwowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDAwMTUgMDAwMDAgbiAKMDAwMDAwMDA2NiAw
MDAwMCBuIAowMDAwMDAwMTI1IDAwMDAwIG4gCjAwMDAwMDU1NDcgMDAwMDAgbiAKMDAwMDAwMDU2
NCAwMDAwMCBuIAowMDAwMDAwNDU0IDAwMDAwIG4gCjAwMDAwMDA0MTcgMDAwMDAgbiAKMDAwMDAw
MDMzMyAwMDAwMCBuIAowMDAwMDA1NDk4IDAwMDAwIG4gCjAwMDAwMDg1OTAgMDAwMDAgbiAKMDAw
MDAwOTQxMyAwMDAwMCBuIAowMDAwMDA5NTYzIDAwMDAwIG4gCnRyYWlsZXIKCjw8Ci9FbmNyeXB0
IDExIDAgUgovSW5mbyAxMiAwIFIKL1Jvb3QgMSAwIFIKL1NpemUgMTMKL0lEIFs8YzhhNGVkNmM5
ZTcwZDY2MmUyZGE5N2YyMjQyNGUwODQ+PDAxMGUxZDhiZTJjODU0MGIzMDQ0Yjk5YjQxMzA4MzJl
Pl0KPj4Kc3RhcnR4cmVmCjk3NDIKJSVFT0YK
--------------080208080400010503030601--




From wypyoungtimerfet@youngtimer.pl Mon Jul 16 14:57:51 2007
Return-path: <wypyoungtimerfet@youngtimer.pl>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAVlX-0004qE-DW; Mon, 16 Jul 2007 14:57:51 -0400
Received: from [85.97.24.175] (helo=dsl.dynamic859724175.ttnet.net.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IAVlH-0000If-Ub; Mon, 16 Jul 2007 14:57:51 -0400
Received: from [85.97.24.175] by youngtimer.pl; Mon, 16 Jul 2007 18:57:38 -0200
Date:	Mon, 16 Jul 2007 18:57:38 -0200
From:	"Melvin Waddell" <wypyoungtimerfet@youngtimer.pl>
X-Mailer: The Bat! (v3.5.30) Professional
Reply-To: wypyoungtimerfet@youngtimer.pl
X-Priority: 3 (Normal)
Message-ID: <977615175.07821157489142@youngtimer.pl>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------CF8401010125409D"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------CF8401010125409D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Best greetings!!! 
Unique proposal for you Our Dear Client!!!
At these five days only for our byers incredible offer!!! 
On all pharmas you want!!!   
Fill your life with colours of fun!!!  
http://cropdistant.hk/ 

Yours truly, 
On-line association of pharmaceutical chemists
------------CF8401010125409D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Best greetings!!! </em></font><br>
Unique proposal for you <font color="#FF0000"><em>Our Dear Client!!!</em></font><br>
At these <font color="#FF0000"><em>five days only</em></font> for our byers incredible offer!!! <br>
On all pharmas you want!!! </strong> <strong><br><br> 
<a href="http://cropdistant.hk/" target="_blank"><em>Fill your life with colours of fun!!! </em></a></strong> 
<p><font color="#D9EDFF">http://cropdistant.hk/</font></p> 

<p><strong>Yours truly,<br> 
<em>On-line association of pharmaceutical chemists</em></strong></p>

</BODY></HTML>
------------CF8401010125409D--




From sample@mx.broad-tech.net Mon Jul 16 21:24:09 2007
Return-path: <sample@mx.broad-tech.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAbnN-0004GB-OR
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 21:24:09 -0400
Received: from pd5fe76.tokyff01.ap.so-net.ne.jp ([202.213.254.118] helo=mx.broad-tech.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAbnI-0000Z5-Tk
	for ipfix-archive@lists.ietf.org; Mon, 16 Jul 2007 21:24:09 -0400
Received: by mx.broad-tech.net (Postfix, from userid 12359)
	id C082C641F7B; Tue, 17 Jul 2007 09:16:26 +0900 (JST)
To: ipfix-archive@lists.ietf.org
Subject: Join the PowerSeller Program Now
From: eBay PowerSellers <eBay-US@reply.ebay.com>
Content-Type: text/html
Message-Id: <20070717001626.C082C641F7B@mx.broad-tech.net>
Date: Tue, 17 Jul 2007 09:16:26 +0900 (JST)
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32


<html>

<head>
<title>eBay sent this message to an eBay Seller. </title>
<meta name="generator" content="Namo WebEditor">
</head>

<body bgcolor="white" text="black" link="blue" vlink="purple" alink="red">
<TABLE height=37 cellSpacing=0 cellPadding=0 width=600 border=0>
    <TBODY>
    <TR>
        <TD vAlign=bottom width=600 height=37><FONT 
face="Verdana, Arial, Helvetica, sans-serif" color=#666666 size=1><STRONG>eBay 
sent this message to an eBay Seller.</STRONG> <BR>Your registered name 
is included to show this message originated from eBay. <A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://rover.ebay.com/rover/2/0/8?loc=http://click2.ebay.com/2686067.616005.0.55016" 
target=_blank>Learn more.</A></FONT> <BR></TD>
    </TR>
    </TBODY>
</TABLE>
<TABLE cellSpacing=0 cellPadding=0 width=600 border=0>
    <TBODY>
    <TR height=0>
        <TD width=0></TD>
        <TD width=600></TD>
    </TR>
    <TR>
        <TD width=0></TD>
        <TD vAlign=top width=600>
            <TABLE cellSpacing=0 cellPadding=0 width=600 border=0>
                <TBODY>
                <TR>
                    <TD colSpan=3>
                        <TABLE cellSpacing=0 cellPadding=0 width=600 border=0>
                            <TBODY>
                            <TR>
                                <TD><A onclick="return 
top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/invitation_logo-1.gif" 
border=0></A></TD>
                                <TD><A onclick="return 
top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/invitation_header_joinThePS-1.gif" 
border=0></A></TD>
                            </TR>
                            </TBODY>
                        </TABLE>
                    </TD>
                </TR>
                <TR>
                    <TD width=23 
background=http://emailpics.ebay.com/xsl/789751217/images/invitation_leftMargin-1.gif><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer.gif" width=23></TD>
                    <TD>
                        <TABLE cellSpacing=0 cellPadding=0 width=554 border=0>
                            <TBODY>
                            <TR>
                                <TD vAlign=top>
                                    <TABLE cellSpacing=0 cellPadding=0 width=554 border=0>
                                        <TBODY>
                                        <TR>
                                            <TD><IMG height=5 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer.gif" width=452></TD>
                                            <TD rowSpan=2><A onclick="return 
top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/invitation_headerBTM-1.gif" 
border=0></A></TD>
                                        </TR>
                                        <TR>
                                            <TD><FONT face="Arial, Helvetica, sans-serif" 
size=2>Dear 
eBay Seller,</FONT></TD>
                                        </TR>
                                        </TBODY>
                                    </TABLE>
<FONT 
face="Arial, Helvetica, sans-serif" size=2><BR>Congratulations! Your recent 
selling activity entitles you to Bronze status in the eBay PowerSeller Program. 
Your membership comes with some great benefits and services:<BR><BR></FONT>
                                    <TABLE cellSpacing=0 cellPadding=0 width=554 border=0>
                                        <TBODY>
                                        <TR>
                                            <TD vAlign=top width=25 height=1><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer-8.gif" border=0></TD>
                                            <TD vAlign=top width=529 height=1><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer-8.gif" 
border=0></TD>
                                        </TR>
                                        <TR height=30>
                                            <TD vAlign=center><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/bullet_star-1.gif" 
border=0></TD>
                                            <TD vAlign=top><FONT face="Arial, Helvetica, 
sans-serif" size=2>See the 
PowerSeller icon next to your User ID <A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/psIcon_50x25-1.gif" 
align=absMiddle border=0></A> <BR></FONT></TD>
                                        </TR>
                                        <TR height=25>
                                            <TD vAlign=top><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/bullet_star-1.gif" 
border=0></TD>
                                            <TD vAlign=top><FONT face="Arial, Helvetica, 
sans-serif" size=2>Free seller 
support via Live Chat, Monday-Friday, 6am-2pm PST.<BR></FONT></TD>
                                        </TR>
                                        <TR height=25>
                                            <TD vAlign=top><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/bullet_star-1.gif" 
border=0></TD>
                                            <TD vAlign=top><FONT face="Arial, Helvetica, 
sans-serif" size=2>Get exclusive 
offerings on the PowerSeller portal--check back often for 
updates!<BR></FONT></TD>
                                        </TR>
                                        <TR height=25>
                                            <TD vAlign=top><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/bullet_star-1.gif" 
border=0></TD>
                                            <TD vAlign=top><FONT face="Arial, Helvetica, 
sans-serif" size=2>Network on the 
exclusive PowerSeller Discussion Board.<BR></FONT></TD>
                                        </TR>
                                        <TR height=25>
                                            <TD vAlign=top><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/bullet_star-1.gif" 
border=0></TD>
                                            <TD vAlign=top><FONT face="Arial, Helvetica, 
sans-serif" size=2>Download free 
business templates for PowerSeller business cards and 
letterhead.<BR></FONT></TD>
                                        </TR>
                                        </TBODY>
                                    </TABLE>
<BR>
                                    <P><FONT face="Arial, Helvetica, sans-serif" size=2>Be 
sure to sign up 
today--it's FREE! Visit <A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank>www.ebay.com/powerseller</A> and click &quot;Member Sign In.&quot; Please 
note that to activate your membership, you must register today.</FONT> </P>
                                    <P><FONT face="Arial, Helvetica, sans-serif" 
size=2>Again, congratulations and 
best wishes for your continued success!</FONT> </P>
                                    <P><FONT face="Arial, Helvetica, sans-serif" 
size=2>Sincerely,<BR>eBay 
PowerSeller Team</FONT> </P>
                                    <HR noShade>

                                    <TABLE cellSpacing=0 cellPadding=0 width=554 border=0>
                                        <TBODY>
                                        <TR>
                                            <TD><IMG height=5 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer.gif" 
width=554></TD>
                                        </TR>
                                        <TR>
                                            <TD>
                                                <CENTER><FONT face="Verdana, Arial, 
Helvetica, sans-serif" color=#8c8cb3 
size=1>eBay sent this communication to you because of your outstanding feedback, 
high sales, and good account standing. If you would not like to be invited to 
join the PowerSeller program, follow the directions above, click &quot;Member Sign 
In&quot;, and then click &quot;Decline&quot; at the bottom of the page. Please note that it 
may 
take up to 10 days to process your request. <BR><BR>Visit our <A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://rover.ebay.com/rover/2/0/8?loc=http://click2.ebay.com/2686067.616005.0.42251" 
target=_blank>Privacy Policy</A> and <A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://rover.ebay.com/rover/2/0/8?loc=http://click2.ebay.com/2686067.616005.0.42252" 
target=_blank>User Agreement</A> if you have any questions. <BR><BR><A 
onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://rover.ebay.com/rover/2/0/8?loc=http://click2.ebay.com/2686067.616005.0.23946" 
target=_blank>Learn More</A> to protect yourself from Spoof (fake) e-mails. 
<BR><BR>Copyright © 2007 eBay Inc. All Rights Reserved. <BR>Designated 
trademarks and brands are the property of their respective owners. <BR>eBay and 
the eBay logo are trademarks of eBay Inc. <BR>eBay is located at 2145 Hamilton 
Avenue, San Jose, CA 
95125.<BR></FONT></CENTER>
                                            </TD>
                                        </TR>
                                        </TBODY>
                                    </TABLE>
                                </TD> 
                            </TR>
                            </TBODY>
                        </TABLE>
                    </TD>
                    <TD width=23 
background=http://emailpics.ebay.com/xsl/789751217/images/invitation_rightMargin-1.gif><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/spacer.gif" 
width=23></TD>
                </TR>
                <TR>
                    <TD colSpan=3><A onclick="return top.js.OpenExtLink(window,event,this)" 
href="http://megaurl.net/09f9" 
target=_blank><IMG 
src="http://emailpics.ebay.com/xsl/789751217/images/invitation_goToPSportal-1.gif" 
border=0></A></TD>
                </TR>
                </TBODY>
            </TABLE>
        </TD>
    </TR>
    </TBODY>
</TABLE>
<p>&nbsp;</p>
</body>

</html>




From xcconserve@dslextreme.com Tue Jul 17 01:26:04 2007
Return-path: <xcconserve@dslextreme.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAfZU-0008Fv-DR
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:26:04 -0400
Received: from pool-68-163-26-160.phil.east.verizon.net ([68.163.26.160])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IAfZT-0004kl-EF
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:26:04 -0400
Message-ID: <001901c7c811$703d1900$072aa2fc@welshry3xybsap>
From: "Florence Kern" <xcconserve@dslextreme.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fw: Thanks, we are ready to give a loan for a low month payment
Date: Tue, 17 Jul 2007 01:22:04 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0016_01C7C811.703D1900"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.2962
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

------=_NextPart_000_0016_01C7C811.703D1900
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Your credit history does not matter to us!

If you OWN property and want IMMEDIATE pocket money to spend ANY way you =
like, or simply want to LOWER your current payments by a third or more, =
here is the deal we can offer you TODAY (hurry, this offer will expire =
THIS EVENING):

$469,000+ debt

AND EVEN MORE: After further review, our lenders have set the lowest =
current payments!

Hurry, when the deal is gone, it is gone. Simply fill out this short =
form... 

Do not worry about approval, your credit will not disqualify you!

http://thealtqhh.com/
------=_NextPart_000_0016_01C7C811.703D1900
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
iso-8859-1">
<META content=3D"MSHTML 6.00.2600.181" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit score =
doesn't matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If your family OWN real =
estate and want IMMEDIATE cash to spend ANY way you like, or simply need =
to LOWER your monthly payments by a third or more, here is the deal we =
can offer you TODAY (hurry, this deal will expire THIS =
EVENING):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$404,000+ =
debt</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have established the lowest entire =
payment!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our deal is =
gone, it is gone. Simply finish this easy form... </B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://thealtqhh.com/">http://thealtqhh.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0016_01C7C811.703D1900--



From ketalamo@iframestat.com Tue Jul 17 01:42:16 2007
Return-path: <ketalamo@iframestat.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAfpA-0006NC-AK
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:42:16 -0400
Received: from 207-255-181-004-dhcp.gsv.md.atlanticbb.net ([207.255.181.4])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IAfp9-00077h-59
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:42:16 -0400
Message-ID: <001101c7c813$bce18aa0$00c6ff94@Jojo>
From: "Sadie Youngblood" <ketalamo@iframestat.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Re: Thank you, we are ready to lend you money regardless of Credit
Date: Tue, 17 Jul 2007 01:38:06 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000E_01C7C813.BCE18AA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2969
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

------=_NextPart_000_000E_01C7C813.BCE18AA0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Your credit history doesn't matter to us!

If your family OWN real estate and want IMMEDIATE ready money to spend =
ANY way you like, or simply wish to LOWER your payments by a third or =
more, here is our best deal we can offer you TONIGHT (hurry, this offer =
will expire THIS EVENING):

$483,000+ debt

AND EVEN MORE: After further review, our lenders have established the =
lowest monthly payments!

Hurry, when best deal is gone, it is gone. Simply finish this simplified =
form... 

Don't worry about approval, your credit history will not disqualify you!

http://thealtqhh.com/
------=_NextPart_000_000E_01C7C813.BCE18AA0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
iso-8859-1">
<META content=3D"MSHTML 6.00.2900.2969" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit doesn't =
matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you OWN real estate and =
want IMMEDIATE cash to spend ANY way you like, or simply need to LOWER =
your monthly payments by a third or more, here is best deal we can offer =
you NOW (hurry, this offer will expire NOW):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$341,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have set the lowest payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our best =
deal is gone, it is gone. Simply complete this simple form... =
</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://thealtqhh.com/">http://thealtqhh.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000E_01C7C813.BCE18AA0--



From xdk@del2.vsnl.net.in Tue Jul 17 01:59:42 2007
Return-path: <xdk@del2.vsnl.net.in>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAg62-0005NJ-RH
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:59:42 -0400
Received: from [70.89.203.218] (helo=70-89-203-218-BusName-minnesota.hfc.comcastbusiness.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IAg5y-0000ob-Fj
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 01:59:42 -0400
Received: from ncr ([26.117.92.230]) by 70-89-203-218-BusName-minnesota.hfc.comcastbusiness.net with Microsoft SMTPSVC(5.0.2195.6713); Tue, 17 Jul 2007 00:59:45 -0500
Message-ID: <469C5AD1.6070006@del2.vsnl.net.in>
Date: Tue, 17 Jul 2007 00:59:45 -0500
From: Stinson <xdk@del2.vsnl.net.in>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: fiesta drawl
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

SZSN Sales UP 30%! Market Watchers Pick SZSN.

Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN)
$0.43 UP 30%

Sales reports show sales up 37.6% over last year. OTCPicks.com and
RedHotPennyStock.com feature SZSN. Stock UP 30%! Get on SZSN first thing
Tuesday!

Flight of the Buffalo is different in that it is written from a more
realistic and practical point of view where making change happen, means
making people change or changing the people. So the Cambridge University
careers advisor was wrong? The negative forces in play are very hard to
resist. The momentum always lies with the chief executive who puts
forward a grand strategy because rejection by the board implies a lack
of confidence in the boss.

Another reason is that a used adjective was joined with a used noun. The
writing style is measured, mature, and accessible.
At the same time, many people have this intense drive, when touched in
the right way, to work for absolutely nothing.

Susan Bloch is an experienced leadership coach with high-level clients
in blue-chip companies. The hard managers possess the mandate and the
duty to discipline their subordinates, close redundant activities,
dispose of whole businesses, move people from job to job, and so on.

There has to be profitability and there must be cost control.

Flight of the Buffalo is easy to read and is a book that I would
strongly recommend to anyone interested in improving their leadership
skills.




From winner.prize@vodafone.com Tue Jul 17 03:31:50 2007
Return-path: <winner.prize@vodafone.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAhXC-0006MC-PA
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 03:31:50 -0400
Received: from tomts16-srv.bellnexxia.net ([209.226.175.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IAhX8-0003OH-F9
	for ipfix-archive@lists.ietf.org; Tue, 17 Jul 2007 03:31:50 -0400
Received: from User ([74.13.38.249]) by tomts16-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with SMTP
          id <20070717073145.KZBD1673.tomts16-srv.bellnexxia.net@User>;
          Tue, 17 Jul 2007 03:31:45 -0400
From: "We got a WINNER !"<winner.prize@vodafone.com>
Subject: EARN A FREE LAPTOP NOW !!!!! 
Date: Tue, 17 Jul 2007 03:35:24 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-Id: <20070717073145.KZBD1673.tomts16-srv.bellnexxia.net@User>
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea

CLICK ON THE LINK AND WE GONNA OFFER U A FREE LAPTOP IF U COMPLETE THE FORM 


http://www.ludicweb.com/ptp.php?id=761





From lihziessowfyt@ziessow.de Tue Jul 17 07:18:03 2007
Return-path: <lihziessowfyt@ziessow.de>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IAl45-0002Ne-9d; Tue, 17 Jul 2007 07:18:01 -0400
Received: from [85.104.156.29] (helo=dsl85-104-39965.ttnet.net.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IAl43-0003rK-8O; Tue, 17 Jul 2007 07:18:01 -0400
Received: from [85.104.156.29] by mx01.schlund.de; Tue, 17 Jul 2007 11:18:00 -0200
Date:	Tue, 17 Jul 2007 11:18:00 -0200
From:	"Kerry Champagne" <lihziessowfyt@ziessow.de>
X-Mailer: The Bat! (v2.12.00) Educational
Reply-To: lihziessowfyt@ziessow.de
X-Priority: 3 (Normal)
Message-ID: <365192697.13986158584487@ziessow.de>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------D3AE1DAE167CB67"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------D3AE1DAE167CB67
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!!! 
Incomparable proposal for you Our Dear Customers!!!
At these 5 days only for our customers incredible offer!!! 
On all medications you want!!!   
Fill your life with colors of fun!!!  
http://totalfelt.hk/ 

Yours truly, 
On-line community of pharmaceutical chemists
------------D3AE1DAE167CB67
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hi!!! </em></font><br>
Incomparable proposal for you <font color="#FF0000"><em>Our Dear Customers!!!</em></font><br>
At these <font color="#FF0000"><em>5 days only</em></font> for our customers incredible offer!!! <br>
On all medications you want!!! </strong> <strong><br><br> 
<a href="http://totalfelt.hk/" target="_blank"><em>Fill your life with colors of fun!!! </em></a></strong> 
<p><font color="#D9EDFF">http://totalfelt.hk/</font></p> 

<p><strong>Yours truly,<br> 
<em>On-line community of pharmaceutical chemists</em></strong></p>

</BODY></HTML>
------------D3AE1DAE167CB67--




From uiabeech@mayvillesmiths.com Wed Jul 18 05:31:48 2007
Return-path: <uiabeech@mayvillesmiths.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB5sp-0007NS-HS
	for ipfix-archive@lists.ietf.org; Wed, 18 Jul 2007 05:31:48 -0400
Received: from [122.169.34.3] (helo=mayvillesmiths.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IB5sn-0002PY-AG
	for ipfix-archive@lists.ietf.org; Wed, 18 Jul 2007 05:31:47 -0400
Message-ID: <001101c7c94c$922eda30$063ea61c@user>
From: "Bridget Mcfarland" <uiabeech@mayvillesmiths.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fw: Thank you, we are ready to lend you money regardless of Credit
Date: Wed, 18 Jul 2007 14:57:17 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000E_01C7C94C.922EDA30"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

------=_NextPart_000_000E_01C7C94C.922EDA30
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Your credit score doesn't matter to us!

If you OWN real estate and want IMMEDIATE pocket money to spend ANY way =
you like, or simply want to LOWER your payments by a third or more, here =
is best deal we can offer you NOW (hurry, this tender will expire NOW):

$254,000+ loan

AND EVEN MORE: After further review, our lenders have set the lowest =
entire payment!

Hurry, when the deal is gone, it is gone. Simply fill this short form... =


Don't worry about approval, your credit score will not disqualify you!

http://hltqxhh.com/
------=_NextPart_000_000E_01C7C94C.922EDA30
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
iso-8859-1">
<META content=3D"MSHTML 6.00.2462.4682" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your your credit report =
doesn't matter to us!</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If your family OWN =
property and want IMMEDIATE pocket money to spend ANY way you like, or =
simply wish to LOWER your payments by a third or more, here is our best =
deal we can offer you TODAY (hurry, this offer will expire =
TONIGHT):</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$402,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>AND EVEN MORE: After =
further review, our lenders have established the lowest current =
payments!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our deal is =
gone, it is gone. Simply complete this elementary form... =
</B></FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your credit history will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><a href=3D=
"http://hltqxhh.com/">http://hltqxhh.com/</a></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000E_01C7C94C.922EDA30--



From jmarthouseegdeb@haarschneiderei-lapierre.ch Wed Jul 18 07:00:23 2007
Return-path: <jmarthouseegdeb@haarschneiderei-lapierre.ch>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IB7GY-0002Pc-Oi; Wed, 18 Jul 2007 07:00:22 -0400
Received: from [60.208.232.14] (helo=haarschneiderei-lapierre.ch)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IB7GV-0005qu-N8; Wed, 18 Jul 2007 07:00:22 -0400
Message-ID: <ee2601c7c8ed$094f3a20$0ebc5201@jmarthouseegdeb>
From: "Fermina Lawrence" <jmarthouseegdeb@haarschneiderei-lapierre.ch>
To: "Emeline" <ipfix-archive@lists.ietf.org>
Cc: "Juliette Spencer" <idmr-archive@lists.ietf.org>
Subject: Is this it
Date: Wed, 18 Jul 2007 03:37:59 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

This message is devoted to the results of the current customer
accomplishment survey taken by the Intl. Pharmacopoeia Commission.  They
assessment on-line drugstore client and then evaluate all on-line
pharmacies.  The 2006 highest award went to:   money off Online Drug store,
granting us the top web based  in the globe in clientele achievement. 

money off Drug store is an experienced, trusted, and fully-licensed online
pharmacy. The cost are very practical and delightful. 

There is no better place rather than money off On-line Drug store to make
safe and confidential buying. 

For more Information, Try this Link: www.rxouraid.org

The goal of this message is to help you to accommplish better health. 

Babara Patterson


Yes, said hearing yawn thundering needle Roshni, wondering the same thing.
Thank come night goat you. competition That makes sense. Dinah delighted
trade in her bedroom remove window. Being on the second story of that clung
delightful tall house, it gave her a w 
trade faint slope tasty The book was open and she was looking at the pages,
but her thoughts were elsewhere. elegant shore change "Thieves! curve No,
sir--an' yet, as I may say, it is thieves, an' a- thievin' the church, too.
It's the M





From huqacmsfop@acms.ca Thu Jul 19 06:45:54 2007
Return-path: <huqacmsfop@acms.ca>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBTW5-0001ia-VK; Thu, 19 Jul 2007 06:45:53 -0400
Received: from [196.201.95.145] (helo=[196.201.95.145])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IBTW4-0003KY-RL; Thu, 19 Jul 2007 06:45:53 -0400
Received: from [196.201.95.145] by mail.acms.ca; Thu, 19 Jul 2007 10:46:01 +0000
Date:	Thu, 19 Jul 2007 10:46:01 +0000
From:	"Dianna Rodgers" <huqacmsfop@acms.ca>
X-Mailer: The Bat! (v2.00.18) Educational
Reply-To: huqacmsfop@acms.ca
X-Priority: 3 (Normal)
Message-ID: <654040522.64129741674117@acms.ca>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------1B2C098888F467"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------1B2C098888F467
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Best Greetings!!! 
Unique proposition for you Our Dear Customers!!!
These five days only for our clients inconceivable offer!!! 
On all medicinal preparations you want!!!   
Fill your life with colors of joy!!!  
http://youinsect.hk/ 

Truly Yours, 
Online community of pharmaceutists
------------1B2C098888F467
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Best Greetings!!! </em></font><br>
Unique proposition for you <font color="#FF0000"><em>Our Dear Customers!!!</em></font><br>
These <font color="#FF0000"><em>five days only</em></font> for our clients inconceivable offer!!! <br>
On all medicinal preparations you want!!! </strong> <strong><br><br> 
<a href="http://youinsect.hk/" target="_blank"><em>Fill your life with colors of joy!!! </em></a></strong> 
<p><font color="#D9EDFF">http://youinsect.hk/</font></p> 

<p><strong>Truly Yours,<br> 
<em>Online community of pharmaceutists</em></strong></p>

</BODY></HTML>
------------1B2C098888F467--




From efdine@iteb.ru Thu Jul 19 13:39:20 2007
Return-path: <efdine@iteb.ru>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBZyA-0006aF-Fw
	for ipfix-archive@lists.ietf.org; Thu, 19 Jul 2007 13:39:20 -0400
Received: from 82-208-107-189.dialup.mts-nn.ru ([82.208.107.189] helo=iteb.ru)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IBZxz-0007C4-3e
	for ipfix-archive@lists.ietf.org; Thu, 19 Jul 2007 13:39:17 -0400
Message-ID: <001101c7ca4d$40c87500$067ebf74@home>
From: "Luann Story" <efdine@iteb.ru>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fwd: Thanks, we are ready to give you a loan
Date: Thu, 19 Jul 2007 21:35:13 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000E_01C7CA4D.40C87500"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.181
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0000
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

------=_NextPart_000_000E_01C7CA4D.40C87500
Content-Type: text/plain;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


Your credit score does not matter to us!
 
If you have your own business and require IMMEDIATE ready money to spend =
ANY way you like or wish Extra money to give the business a boost or  =
wish A low interest loan - NO STRINGS ATTACHED, here is the deal we can =
offer you TONIGHT (hurry, this deal will expire THIS NIGHT):
 
$46,000+ loan
 
Hurry, when our best deal is gone, it is gone. Simply Call Us... 
 
Do not worry about approval, your credit score will not disqualify you!
 
Call Us Free on 877-542-1880
------=_NextPart_000_000E_01C7CA4D.40C87500
Content-Type: text/html;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1250">
<META content=3D"MSHTML 6.00.3790.1081" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit score =
doesn't matter to us!</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you have your own =
business and want IMMEDIATE ready money to spend ANY way you like or =
require Extra money to give the business a boost or  want A low interest =
loan - NO STRINGS ATTACHED, here is best deal we can offer you NOW =
(hurry, this lot will expire NOW):</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$43,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our deal is =
gone, it is gone. Simply Call Us... </B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Don't worry about =
approval, your your credit report will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Call Us Free on =
877-542-1880</B></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000E_01C7CA4D.40C87500--



From paxadahbev@adah.de Thu Jul 19 21:31:30 2007
Return-path: <paxadahbev@adah.de>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IBhL8-0007hj-Hl; Thu, 19 Jul 2007 21:31:30 -0400
Received: from [88.233.200.4] (helo=[88.233.200.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IBhL7-0003XO-IH; Thu, 19 Jul 2007 21:31:30 -0400
Received: from [88.233.200.4] by mailin.rzone.de; Fri, 20 Jul 2007 01:31:26 -0200
Date:	Fri, 20 Jul 2007 01:31:26 -0200
From:	"Jonah Finn" <paxadahbev@adah.de>
X-Mailer: The Bat! (v2.00.18) Personal
Reply-To: paxadahbev@adah.de
X-Priority: 3 (Normal)
Message-ID: <580939495.79729699849674@adah.de>
To: idmr-archive@lists.ietf.org
Subject: Greatest artworks from top artists
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------8FB2C6E739B2C67"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

------------8FB2C6E739B2C67
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

GorgeousArt is your closest store for the grandest in artwork from biggest Russian artists. 
These artists have been exhibited in a great number of art exhibitions worldwide, 
and now you got an opportunity to acquire nearly all their illustrious works of art at the lowest prices anywhere!
All paintings are original oil work, and are only exclusive to our store. 
Not only may you find the panic prices here, 
along with it we also propose free delivery and many other presents to our clients. 
Then for surprising prices on magnificient Russian artwork, come to GorgeousArt, 
where we reward loyalty with astonishing artwork at panic prices.  
 
Check it right now!  
http://meragent.com/ 

We're accredited by VISA and GeoTrust that is, we provide you with efficient & trustworthy buying.  

------------8FB2C6E739B2C67
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><a href="http://meragent.com/" target="_blank"><em>GorgeousArt</em></a> is your closest store for the grandest in artwork from biggest Russian artists. <br>
These artists have been exhibited in a great number of art exhibitions worldwide,<br> 
and now you got an opportunity to acquire nearly all their illustrious works of art at the <em><font color="#FF0000">lowest prices anywhere!</font></em><br>
All paintings are original oil work, and are only <em><font color="#FF0000">exclusive to our store.</font></em><br> 
Not only may you find the panic prices here,<br> 
along with it we also propose <em><font color="#FF0000">free delivery and many other presents</font></em> to our clients. <br>
Then for surprising prices on magnificient Russian artwork, come to <a href="http://meragent.com/" target="_blank"><em>GorgeousArt</em></a>, <br>
where we reward loyalty with astonishing artwork at panic prices. <br> 
<br> 
<a href="http://meragent.com/" target="_blank"><em>Check it right now!</em></a> <br> 
<font color="#D9EDFF">http://meragent.com/</font><br> 

We're accredited by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>GeoTrust</em></font> that is, we provide you with efficient & trustworthy buying. </b> 


</BODY></HTML>
------------8FB2C6E739B2C67--




From negadomolyg@adomo.fr Fri Jul 20 19:20:38 2007
Return-path: <negadomolyg@adomo.fr>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IC1m2-0001uu-JK; Fri, 20 Jul 2007 19:20:38 -0400
Received: from host86-134-12-50.range86-134.btcentralplus.com ([86.134.12.50])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IC1m1-0004Tk-RA; Fri, 20 Jul 2007 19:20:38 -0400
Received: from [86.134.12.50] by mail.adomo.fr; Fri, 20 Jul 2007 23:20:36 +0000
Date:	Fri, 20 Jul 2007 23:20:36 +0000
From:	"Alexandria Whitney" <negadomolyg@adomo.fr>
X-Mailer: The Bat! (v2.10.01) Business
Reply-To: negadomolyg@adomo.fr
X-Priority: 3 (Normal)
Message-ID: <901384844.84418368907101@adomo.fr>
To: idmr-archive@lists.ietf.org
Subject: Greatest artworks from top artists
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------2C8425BD3ECFF8B"
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

------------2C8425BD3ECFF8B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

GorgeousArt is the one-stop store for the greatest pictures from famous Russian artists. 
All these artists have been exhibited in many art exhibitions across the globe, 
and now you got an opportunity to purchase all their illustrious works of art at the extremely low prices!
All pictures are original works of oil, and are only exclusive for our store. 
Not only will you find the lowest prices here, 
but we also provide free shipping and many other gifts to our clients. 
Well, for great prices on beautiful Russian works of art, check out GorgeousArt, 
where we reward loyalty with astonishing artwork at low prices.  
 
Come and see it here & now!  
http://renatine.com/ 

We're ratified by VISA and GeoTrust that is, we provide effectual & dependable purchase.  

------------2C8425BD3ECFF8B
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><a href="http://renatine.com/" target="_blank"><em>GorgeousArt</em></a> is the one-stop store for the greatest pictures from famous Russian artists. <br>
All these artists have been exhibited in many art exhibitions across the globe,<br> 
and now you got an opportunity to purchase all their illustrious works of art at the <em><font color="#FF0000">extremely low prices!</font></em><br>
All pictures are original works of oil, and are only <em><font color="#FF0000">exclusive for our store.</font></em><br> 
Not only will you find the lowest prices here,<br> 
but we also provide <em><font color="#FF0000">free shipping and many other gifts</font></em> to our clients. <br>
Well, for great prices on beautiful Russian works of art, check out <a href="http://renatine.com/" target="_blank"><em>GorgeousArt</em></a>, <br>
where we reward loyalty with astonishing artwork at low prices. <br> 
<br> 
<a href="http://renatine.com/" target="_blank"><em>Come and see it here & now!</em></a> <br> 
<font color="#D9EDFF">http://renatine.com/</font><br> 

We're ratified by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>GeoTrust</em></font> that is, we provide effectual & dependable purchase. </b> 


</BODY></HTML>
------------2C8425BD3ECFF8B--




From renaerialinfosyssoq@aerialinfosys.com Sat Jul 21 08:43:10 2007
Return-path: <renaerialinfosyssoq@aerialinfosys.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICEIg-0000AZ-GJ; Sat, 21 Jul 2007 08:43:10 -0400
Received: from [85.99.47.2] (helo=[85.99.47.2])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ICEIf-0002Nl-Gs; Sat, 21 Jul 2007 08:43:10 -0400
Received: from [85.99.47.2] by aerialinfosys.com; Sat, 21 Jul 2007 12:43:12 -0200
Date:	Sat, 21 Jul 2007 12:43:12 -0200
From:	"Karl Shields" <renaerialinfosyssoq@aerialinfosys.com>
X-Mailer: The Bat! (v2.10) Business
Reply-To: renaerialinfosyssoq@aerialinfosys.com
X-Priority: 3 (Normal)
Message-ID: <674502676.22872511921398@aerialinfosys.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------7FDA6EBF67FD329"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------7FDA6EBF67FD329
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

Hello!!! 
Special offer for you Our Dear Customers!!!
Only these five days for our customers unthinkable offer!!! 
On all cures you need!!!   
Fill in your life with colours of bliss!!!  
http://courserule.cn/ 

Sincerely yours, 
On-line association of chemists
------------7FDA6EBF67FD329
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hello!!! </em></font><br>
Special offer for you <font color="#FF0000"><em>Our Dear Customers!!!</em></font><br>
Only these <font color="#FF0000"><em>five days</em></font> for our customers unthinkable offer!!! <br>
On all cures you need!!! </strong> <strong><br><br> 
<a href="http://courserule.cn/" target="_blank"><em>Fill in your life with colours of bliss!!! </em></a></strong> 
<p><font color="#D9EDFF">http://courserule.cn/</font></p> 

<p><strong>Sincerely yours,<br> 
<em>On-line association of chemists</em></strong></p>

</BODY></HTML>
------------7FDA6EBF67FD329--




From pcfj@digitalgenesis.net Sat Jul 21 08:57:07 2007
Return-path: <pcfj@digitalgenesis.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICEWB-0002gb-UH
	for ipfix-archive@lists.ietf.org; Sat, 21 Jul 2007 08:57:07 -0400
Received: from [69.27.7.62] (helo=slkc.firstdigital.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1ICEWA-0007zG-7B
	for ipfix-archive@lists.ietf.org; Sat, 21 Jul 2007 08:57:07 -0400
Received: from habkh ([135.225.137.156]) by slkc.firstdigital.com with Microsoft SMTPSVC(5.0.2195.6713); Sat, 21 Jul 2007 06:57:07 -0600
Message-ID: <46A202A3.7060806@digitalgenesis.net>
Date: Sat, 21 Jul 2007 06:57:07 -0600
From: Velazquez Z. Gwendolyn <pcfj@digitalgenesis.net>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: offer
Content-Type: multipart/mixed;
 boundary="------------000203020208070000070401"
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de

--------------000203020208070000070401
Content-Type: text/plain; charset=iso-8859-2; format=flowed
Content-Transfer-Encoding: 7bit



--------------000203020208070000070401
Content-Type: application/pdf;
 name="offer.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="offer.pdf"

JVBERi0xLjEKJeLjz9MKMSAwIG9iaiAKPDwKL1BhZ2VzIDIgMCBSCi9UeXBlIC9DYXRhbG9nCj4+
CmVuZG9iaiAKMiAwIG9iaiAKPDwKL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL0tpZHMgWzMgMCBS
IDQgMCBSIDUgMCBSIDYgMCBSXQovQ291bnQgNAovVHlwZSAvUGFnZXMKPj4KZW5kb2JqIAo3IDAg
b2JqIAo8PAovQmFzZUZvbnQgL0NvdXJpZXIKL1N1YnR5cGUgL1R5cGUxCi9OYW1lIC9GMQovVHlw
ZSAvRm9udAo+PgplbmRvYmogCjggMCBvYmogCjw8Ci9Gb250IAo8PAovRjEgNyAwIFIKPj4KL1By
b2NTZXQgWy9QREYgL1RleHRdCj4+CmVuZG9iaiAKMyAwIG9iaiAKPDwKL1BhcmVudCAyIDAgUgov
TWVkaWFCb3ggWzAgMCA2MTIgNzkyXQovUmVzb3VyY2VzIDggMCBSCi9Db250ZW50cyA5IDAgUgov
VHlwZSAvUGFnZQo+PgplbmRvYmogCjkgMCBvYmogCjw8Ci9MZW5ndGggMTQ1Nwo+PgpzdHJlYW0K
w4AY5PSjcOcODNj0d5f4xDoTMgeMxc8enuvlwp9zjnZM5DE49zT+cpFxQTLai2d6B+/rXFtfW4Cb
iS5RN4DPkDEFO663mek00fGbiHwWE5S95I1gG/G0v0HJrPeksTmkQyp3WebeSDPK+qo9lG0yAoZh
SLfUsxSY+ZE0A5sULn142AiDbPLPZDQ9mjtdj+HrYbnR6rQ5/URwCdRtyMjCzNPTzn8W218AJXzj
bVh47N5utuGW8lk+U9MU1FbsbHxTQjjOdn9YB9T1M4mqEzAxYQ0KJWwB6+1B8UFtUH5BDIevHdE/
BAAFHZL8uUUwdJeiyS7YlYjvvwI870NR/2I+8S6WFl54U/QnCJ6jaldb8VdbmpZojBXinTDsM/Ep
hKKuYy0PSOrDdb8/cymHmGf88Je8UF3XZ7Y9RLgV/XjV1bjcf13Oq2yqYfVXn2AM+XyFQLMWGQsN
/MFcI5VVHb4yh+Eyc+nA/hn1Om3R/KZ/D1Vacok0+O9P5HtEvxKGW1JnqXYyRMz6V2OrxVMk4E7J
h5nBbv5VlHhgZtOwvO9jqVOkCICSl/FgcOwAHfOg+XeH5M4ibFtB8jgS4EuE7PqDlvAxIM8fJ431
pNhCn4aXMM8MMsBj8MPvLU8IDqGrYlLZ4tq3z8DlDZTEn4uYgJpVUI5/lfWNy6riMyi8iQ0mSMzf
0paXj73W/LCyMB1z7MsJxiZ0NWO6//MuTXqac8idUOBtQpNN4O72t9R+9clmi2hn3jMDN8FWfUfw
jb1vlJVXauZmQxPED7pjLfShu1/sLFsoxy8+raV9xAQaudMQBttMkJHN3ZLmb/jSWfOobU5dTC6i
hf07lFjzYrv6ph9oaU4FUR++wRhLq8QGMEnY/yNGd3QSUjRVw+XUunW2pYkbQyJI/IRG2z5XfhBn
nkGzYFmUgdMMMTA9Avpb98ur+b+syl+WLHYys9EKKftYKDaF3cQTVvpiAs5VhzH4lhWlo2taaitF
OEqellO1uq+weGW/GuuyFTWa2bl1BNjnmIvN/rqsZMRJwiEKJFllhJSsb4jEAVjVN7k2yVaBMGyT
ANij+4VShUl0o6ULG59inM+btcBChXlD2ea3pF1Ra6GLDQtFHcRwoTpn42NE79za36FDW91Wq3LW
4aMiHOb/DbvC+RzRTj5Gz4xG3GDvoSj6ST5dtkpCYxkWXDotzMo3zXJ8uQMXyxU0D+FeJ15bdmYO
VESPJnWQIVCpwESsgPr2+iN/CVDotWNY5yFEVLDCRLn5BGM3eBqvUlcO4IVGGrFVZtY83RqsCSUm
dwPy+dDwxaNNskn8eBOs1yz2twyJFbebbzoWV1KE3WtyddK6uig5Q1K4hHi6xgyuDaYnc/+85DXV
APoyIBaoWtN+joHSOaDWrBt5hH+xy4jGsSplr6pD79EcLgjmwO83gwJma7d1Z/KY/Mu9dZwl+sLd
n+qTJKUYuM/pLWzMAIGcHie0Zn/mostFVvjsbtaj42t73/rk2/zu6J34ImxW2yZU2xl8B8SsVF2s
npLYx9vNp0lL00IAW7fC/ChQ5Ndk+TT+CSghFrJQt+l+/D/BIvgkMuMfuuUzOvGyaYH+gNMRd5Kc
BDUqwXozvjBkyssfnHVXPASuu+P+nV+YkgBCbo/nX2B8sJu89z+h6eYAKl6xsiPv+Lj+Hcb6UApa
NXuBEiPTmnNIeulovLRaM76RN/uPgfT/irYPh6vLFoi7kwzYwQ98Nx8VFavoiX7VIdIiHYRveZlO
ECYDLKV2or6bkwt78VO+PWkzna5U3QoRZH7Ol6VcKLTZR4jolfU0nOf3zOkI8uUf110MEhB3ubjr
50MQuDGrcvPLQqdFqRBYbZEiBfMhmxqxU1JrsaX5733b7y9aZeccTbxlpw1YXWJPcLTJAQM9j60x
VotNe9M7fj+dCwxcRHuzQ+avkyQyF6fJHoqq/ICCmv8KZW5kc3RyZWFtIAplbmRvYmogCjQgMCBv
YmogCjw8Ci9QYXJlbnQgMiAwIFIKL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL1Jlc291cmNlcyA4
IDAgUgovQ29udGVudHMgMTAgMCBSCi9UeXBlIC9QYWdlCj4+CmVuZG9iaiAKMTAgMCBvYmogCjw8
Ci9MZW5ndGggOTM4Cj4+CnN0cmVhbQpqFZXAtfu9aC0qquJe27mI53U3u0ZgXHqMIKpXltQ3arbG
N9XBA93hPbdxdG5UVVISpTwCaPOfFwxRgLH7rQMj3zdxIyZ4BO+o1DpjeaEIXG5wNkt6o/3S9xl0
9gy/DWEq8qDwO/jBq8x6dvD7k2Dlw8mNshda5/fHuJfe7N6tYjRrHhxYzUIR9gKL5nUjQSrj7/6p
Etfo2rrOQOKZEGjAQI8exvaf6bRpPO8o7vmF2ko9DItiC4atYABxZDMrSE3C8Jx9SJzqewBCJYHe
ImGTRfixlKl0K0B9v7pR7a9iDlzM98RJExD867IHVpYjJeJ+SALCcZQ6K9arqnqsLIb2J0g+qO/8
kcOYDDdFj2hP+W+GaqVj7Cmd6+vYvl43oWL7pikAsbV26xVvTVj02ZZVd9SlMktWNWh+Kr5FbN4r
rFuaMSxR7v97WjkAnk79Ac3KQs8uNzsbxujXz9VMbUjg0wpY4g+rKkseRGTtkbGgBT24haf+Usgt
uuaHMDijMpeqyeqyLLcjK2pyo6CLCI0T3nFhW6GeZHqq1oLf3wwfS1barC0kgMDtMFiRzBk1nQML
fpcOxN1PUdUShEUyi+QaegJAz1ToDO/hPsTvKITfOwXdxQ9wv/QWucA8namKt4B6hmuTgb91xGda
3GIENA9bD124/FY4V1En+934pLJQoKzWMDWub3UgZwcNmSYX9lPbxLwx++S1JctDX9sfr0LzcxPW
1h4ztETrI33w59HgRcrGqOUGqsrFDE01zGg77Cc7tA9qvQNDv95dNqwP08iVpoydJ50LN6o56WUT
mOWhXbjgUnfl0rJW3AWcGQiZc+5bL9N005dw4t8EHJIwVr90UxYYYJLTN7PEYPX/jO4ST8FcEVCx
NUmNm86JeKM6sK9n6YlyIn6bd2chCMkryDwzZ5b/45oVHISw3XbF8IkXnVUazzV7KrJg4StH0Dzr
VzniVREuyArEWUmghcfw1AmYl0mizWztryOqD8VJotujtK26uS9uw6RdNO7lyY5j1MHBJC5pHCcr
9oIrOp9jr3avToL7s0xHesYzFh663Ze4VRQc/8ON5LOe3a+YSwUawj5auBCLidUKJSCSngXD7VRW
QnWPE2/DRaxmwZVZz+FAeI/vtLG8XUnUlffWMOZtdVjbAq4x0Lj0DWkjhLw3Xwe7xF+hkLICatgZ
iaCOtkuc/c9NEtv2ZqWrfWfGI0iW8sntL631Yc0+IqKkQXoSXKxscjItMiLi+opAGAplbmRzdHJl
YW0gCmVuZG9iaiAKNSAwIG9iaiAKPDwKL1BhcmVudCAyIDAgUgovTWVkaWFCb3ggWzAgMCA2MTIg
NzkyXQovUmVzb3VyY2VzIDggMCBSCi9Db250ZW50cyAxMSAwIFIKL1R5cGUgL1BhZ2UKPj4KZW5k
b2JqIAoxMSAwIG9iaiAKPDwKL0xlbmd0aCAzMTY4Cj4+CnN0cmVhbQpWdfm1zplMJLNlVtX04LoP
zQDo/Vsr4qdj7lSXroM0y5MU0ATbRWMkVXMUqYun1KhcETZRlYQwrZeLtkB3J2npOgFBlnrKkC6j
eWPad0lWDEmyNNtSFmLDX6wz/3HJPDGtaBaCufi4kcUTOZhcXJPzmi8QGWJmpCeOAwcZWie87dva
Yt/SyUBPKfGTWx7BWfglVHiihMUIreLG9qOX/gsj2OlOXY/z/q6CJ2zggJBD+JLZlFLS505ppS2t
CkkyJGMedK0+k/TJKylnAelnWHPosce8MnzQcfC2BY80fgAvJmDTuKztmxwe5hICqjXeBntMwlem
KGsmG6HruOGNR1qXl0RnotWqxg7mUsPo2vq2Mr7APjWqWDyr8u4tX2Bs+rtwV/xrghuusa9OiB6u
rtES6p4Jx5hto1xdzA5aYxb0N8h+E04uzjLk1jFvgLc09+Oi9DU8tkfzHlxaySSFv6CM8r8H4lJK
xSFQUuVtFeiMF/2fISOQ0JqWuz1VxqmFDHPL5nhxJkCZWzu1BlThVDMAsp5XnoZkw/2qsD4lvkOu
JxCcNT7Iq0kljubMnCj8aGsDfF+ogriWJY/eS/Ls0Ds0dKISTPpn5+10TUPl/E45AeMQLURomIqQ
gVixH5xmIdJC+vEoUL+bjoPBtuSkQ2Wk0U94zyKMFWTc/z7ETYCGXPsVgfsVovAtASvA4yhoK75W
jVByuWJbVQzKt4pcn3/W3LqyFbN4gb+B2gtMEvAMZNZNBwsM3HGiCxmdD58ouWYVrxzxTmX8U7FF
AHoD9l7l9NBhJCe/MHURG6RkFyWBfep59kr4sqdo7CrPfxFOlm/mySJsPtIg0iwou/blxKaxdQl6
i2boWziY7ndA0qbHNbT05N1U1p24y9tqZsVoA6pPY5mrtdic+VEj43nVdXSXA0QcyZtIn5vfpF/4
fj0d8tSuqS4rWn5L0JCmfjuHsJr83mD0W5yxRXWZYNDtAX8LdRrxvqgwl8j3gqq63pbGitPgdrlU
k66ldphdN5O/oCEYzR6fvlQ1ldmNZMhMcWi5AvpCJ2zX0rWFPUqDjqHZvSCT2uuWef0f1JsSFcTr
XdfJCwn73f5qIPFXFQAd1fthBZSYihWC87QHXESBC6rjG8WI8fzoLHGItDQJeNEFC+kMSNCAjZh4
ej3MDZ5zGg7cAMu8RV3UVBERbUuTW2Yky4e9EZ9vvstbUHQPmwRa7GQdK0sQOJZXwqV8zwwASy1d
L5LZ+exbTpdeqP4OVIp2Di2Q3bvVeXMt2fn4QNAySNPu6NSiGxmEsw3lMbsDRlquyuHhJJyjpo+p
XBXNyFLjfKCgEvMMlDWpKf7TpuhKvNMX43PAhxrWxYxMCH4t9Yz1HwADpfXMqwLuX+jSvvQ6BOTE
sg+ZBcxrHDNsthyqpHli1qBdjKmYyAkSAL72wl1UZtaSSJEilSj/UhU0SsOjymXTzuCBoVbxetRF
VGX0wpakkf2GQcocidB514q8F7poIuAz34VxB/CGXzwKxuPqTF6VYR9QxqJGsWQHhCJE3tr1nd3s
TAfHd/QfIMCuJhgHp5kGaTD+poEtoWWrQXO6W9bOraUqeNFtd0GWkUuPBgP604lsITIbWhccIfYz
4AWOjzFPu8z4soXT1HpImDZoBU+4jN0wSDRGDdcO8g+omnidD+P+t1QFJzaWMb2r3lhZDqPjCiEs
yv2lc7uT79NKRhcHB/nx3qBDe5StlPTcdVCPZWe3urFKrftEfuxyf2waIpYpJA27rsGJsstuK7Ip
a1I3gTx34oTc6o43WBPyhpurhH6H5rU8xOxWCx811mXZZFmc+hnYbePtVeZOE6VdsqcvNoZnH/2F
8bAjt9bZ9kBQPwQfmJ9ZBFuvI0NFy+g3rYMallkKT16AtTe8ObhXgHZnUMTZMJHxO6DmlbImhWWM
NBsbyhSoXFe58RkWiGWeLsPRrrPYM87qy7ASNJjwWL7Q0KJsnSy4WOQdhj4FAUFktXMZOS767AV9
oZVsEuvrMLVMjgsotXv1tm9aq0IsvolEbBxdJ0NEkgXbKjpl4mrKxVB8L11hT/IgFIrTUjOrXjyv
Fjbwoo85uhJ99LtWya0aJEY1UeDH8UxCCxfAxoW8NLUi/qkMFxfqbC0yHuRxu3hCIcOFUmQEZGxu
C9JkhN9qjGbJ0T8kLgiDNr8sxI8lM9ZRubR65S2JTEnC0tatDXcSUY7MuIRgWqln6kCgKyimaiam
xExKFlCH6FrZ6G/5VkfwRK3/WfSB4qgNgH8P0AfUNalu/V2JA2Sbw0rRcyRJCpF78MaUDs7VaQ0y
Wf/c1YfuD++TrIbgTfKbQoh4IfZ63yLu6+aZuwB25mFY+uwPutyqPod6LDUvYPC59ExekpCN354r
QRcOKl57S8J+FnxxxAkBG5pt0yQCE4JL6PVLaSP+XR1owfzhO+rlu/me83ZT3CM4qw8c81FICdSE
CzlJTudyzvqzU2SizeZv/ezvmUeK84NHcpI4wmGW2KtzQedWS2UmT7MsQGDF5aJHCny2OLeybFIo
mfNJ+dkvxc3yzP3JyivaxET8vsx1ZSoNgIU2XZd2pvuUAErzF9fIJm3YQ7V2thTzZfgZHk16Gepc
7Sz1DssCDsqjlmnXDdiWLNRFeK9G+MM4Ag5iDiE/J1UvpECmLC6DCLIpAfLcErOxdEv2CbiazOri
0z88U3hHmDXRFhvTNff1O4qMCmGAGB3bbEMufo9qETs4oAcJQacc9kBnR+XdUv2b5JNrIu/pXLXn
u1yOM3rR5UtoMu/HKxMEOSnEbPJYG3uti+01V3IhBh4hVPo2wClVh5EiG5edQS2ScUUjGI0I7B/S
VBmZBDzNF/wY8mTXfoBzJEWqsSaOShVWTWNpZ79jnmJmragKXlo3QvTSh4kSD7JcwMHtymOuUY8f
2d5CKbRp0DKYnAke00751GhfOv2SNK329TjWPMQTGGr4R/xVUqmRTS26jY/gR1TSW1w+BMiaWz2S
zI7Si3VKT+zTwcUI32ENg7QrkPwUEaHyBdnf0c5Y8ULEmzC+DlU7GZ7M+l8VzoEwVEntQOQuYNhH
PWpOtyeJtsWvAdbBQVhBuP5rrnWFMqlo3gh1PgyOmfpZeQxVVvCvmD0nwMEc0PUIjJmlY8h1zG4g
0mxYrWmgqnsTCLfsAZQYS5YvqY6ICVVg/zqlQhhghphTtML+2NxD6YLLdpBoaguVh48tqe8rLkq9
AtwzKQNz7sxUKujctjk+8PghjADqD2IW5UWfceUEtB+5bcZfvDZSzwITeHIFbM3ccxIooE90miTG
LgX7CkAXIdp9ekCIIJsYqb53vtKinlrOL1hr8b0uwBE16GMciYAFY1nYsE49hNAhB+jZ1HVvY8cU
bHd9gfIiRnDZF7YxNmmCYJOK8hXZuazAT9XLWtvMEqyc0/1jwLwxMN+JG+M3NDYU4ECuTMYMGKm0
+ls8wE+lBcu/CXEDqc6QwMCvWDLFtpPmQODOXNPJiR5jhV8HqKm31oGGWc3Zk2E0MBro9XKWX/JS
6d3pojw3fP+HETc2a31i0dm9OP5t2vUcJiBJMwBypOXhpUxOeCMwwslY3F3Y6ospvaQmYyiE/J+m
lLYKrb0bVnF9B+1FGzyp/747DxmjdGnCg4cLdxn5HWjQ18+1F284Iq9Vpws5w5NyvYUzLJop5w7O
nSJ4G292e8JnS28AcSbIvceNo9mGItQOK4Ds24V3I42QJKXO7+/j84dca6YIB5RIHolCuPFbIk0X
9enpiyu2jZcyZJoBK2xajeQirku6e4kZN7l3514O55zOwFOmzLxZdfWQHuwNiNcX39B4RDoxwvau
VJzSUE47yIILO4+7jZqrhquu5aB/bBj8Vhi4Jn3aP65lXRNxwSeyP1VWN3P0JVslbdZueajQO/JI
L8JXaVdTQI26u9Jq6Ru9/DQGBvVxK3aHWB55E+oBqOs+7pMjOFSTPCzbMgIq+O5cDiLFPpO+8uLl
tDwqqZ3/KjppPKExHW7VaS1lYeo6BX6qIKqra8SWUqi12hLsqTw5o59aMMgcXzjHu4G7YIGBYZXN
mbpSlt/7M/f9YdTLkJUCG6D0kD59cSgSaKjI/LOeeGzgicjjQIr+NiwXTsDBbk79DzFl1YfvHFgF
YUf4rwCIQtgDqVFaeMdKdt4Ku2liKpaoH1EInOArqTlacK/6gz7vV54RrvQmJtR213dBAJKDgJRf
HMd4z+tKD9c78+HOKtNGF4UKZW5kc3RyZWFtIAplbmRvYmogCjYgMCBvYmogCjw8Ci9QYXJlbnQg
MiAwIFIKL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL1Jlc291cmNlcyA4IDAgUgovQ29udGVudHMg
MTIgMCBSCi9UeXBlIC9QYWdlCj4+CmVuZG9iaiAKMTIgMCBvYmogCjw8Ci9MZW5ndGggNjc1Cj4+
CnN0cmVhbQpPoNmfcw3wdKKPYSGL/rAvJS4coPZnMA4JbIs31BY+kgxGYxc8gkst9E7z+eRNDP3h
oEvVovj8gNDQJykumtt3eQz7FZJAWXg8XnVdVc5rE6MSF9zK9edmcKO7JXiJbgokZJzYihWEjjQi
cSuETK/ytfGZzmGM5GeyP0LOA5QhLhD7EXZwZVCnXNlzX4Ish6Chznl1PP4c05UeWHbWIkG/3/cq
SifxsdlCPrh+/dp9B7HwMgJdNoEUnjJFhb2hI2a2gqoZ/O/ojN9rh1VECQZ3y/CM5opv/JKRMBVi
vhDUUtZgEuDrJgeRMoOrT7NQGnKMq8xv3nMyJqlJi9VKpx4Y+5b31nfbgSyYp3fWJ5w/v3EXB2gm
d//pFGkhlG1ba8IbrB2D5fjgDdi5moEfIDldKGdMTpEjMPPOsQreFfKfLzc2O08U55/Bo+wobnWT
DpPVs7Q5r/BA7uMxwXuU/D3T+qcjla6s4FwSyn3kslqD5TFIt3BgZCD85HKlrL/j0AYYlGVxkxJt
NcrAU9S58K6kIIkeR74Oe3c4tiDFHXUZ7Eq5PmaTkzWz8MJ3dJryvXne4I4iPeeRBaH8H9dleb63
2HkUgxD33XcW+8g6tDgWdA3LZ+GCCXvn+n2LmmsuRMpq7IXRPB7h2lGLkMTM6ngOwDOSMAAVDUKc
MoHWLMgdPndJuBsB2z+Fv77snGYlx6VO0zb/cvp37F1ETCCVoEXjwmQg2sWUvPAvSEI6ZO9x9A/h
1sQbDMWVnXVBvrVevJlyJsv0qBOjrvOHvtMOkwdEc/qSh5C7ITeoeOkXlntpfJIwFmDJUAOEolEY
JnYgWdWd6B+diqgiVDmC0/CzsTu/edGgKu5/ArAwGBon+3P4ql/KVm59v565r1lKyMSHvBfEEA0K
ZW5kc3RyZWFtIAplbmRvYmogCjEzIDAgb2JqIAo8PAovUiAzCi9QIC0zOTA0Ci9PIChcdKM1YsF3
06hfUD2zPDu5a8jL/lqz8SN5S4WPd8pCSCspCi9GaWx0ZXIgL1N0YW5kYXJkCi9MZW5ndGggMTI4
Ci9WIDIKL1UgKEaPF91v6lQuGt1fBOfDT4EAAAAAAAAAAAAAAAAAAAAAKQo+PgplbmRvYmogCjE0
IDAgb2JqIAo8PAovVGl0bGUgKOZk7f+7/+BExbfu6RqdonEZ82LedTMOXCjN/NWfnXuuSVf4lPdE
KwvukEkxJDnKRmNOHsbZq1wpPKvKTHydyfEsXClrkbpcXIjG0xRcZnVRtp27c4bfjW04qEb2kQ7A
Bh8ROopGAr5fO/xBXHJoQFxu6N78IM6sXRHQJrBSe/Re61sV6LRcYoZiwKFjT3fvI8JS2Hi0exhO
gFIXiuCDhGgA5HuJ9ro3J0RcYv417vcruPX5Q3NkXChQM/7riSkKL1Byb2R1Y2VyICj9fum8pP8p
Ci9DcmVhdGlvbkRhdGUgKPY2uu/4qrMemeP+olnA8i8pCj4+CmVuZG9iaiB4cmVmCjAgMTUKMDAw
MDAwMDAwMCA2NTUzNSBmIAowMDAwMDAwMDE1IDAwMDAwIG4gCjAwMDAwMDAwNjYgMDAwMDAgbiAK
MDAwMDAwMDMxNSAwMDAwMCBuIAowMDAwMDAxOTMzIDAwMDAwIG4gCjAwMDAwMDMwMzMgMDAwMDAg
biAKMDAwMDAwNjM2NCAwMDAwMCBuIAowMDAwMDAwMTY3IDAwMDAwIG4gCjAwMDAwMDAyNDcgMDAw
MDAgbiAKMDAwMDAwMDQyMSAwMDAwMCBuIAowMDAwMDAyMDQwIDAwMDAwIG4gCjAwMDAwMDMxNDAg
MDAwMDAgbiAKMDAwMDAwNjQ3MSAwMDAwMCBuIAowMDAwMDA3MjAxIDAwMDAwIG4gCjAwMDAwMDcz
NTEgMDAwMDAgbiAKdHJhaWxlcgoKPDwKL0VuY3J5cHQgMTMgMCBSCi9JbmZvIDE0IDAgUgovUm9v
dCAxIDAgUgovU2l6ZSAxNQovSUQgWzxjZTI0YjE4OWU2OTg2ZjQ2YzYyNTk1MTA4ZTk3YTJjMz48
MTQ0MzdkY2E0MzljNTkzY2ZjM2U4NzYyOGM5YjRkYjc+XQo+PgpzdGFydHhyZWYKNzYyNQolJUVP
Rgo=
--------------000203020208070000070401--




From renadviceebooksoq@adviceebook.com Sat Jul 21 10:41:09 2007
Return-path: <renadviceebooksoq@adviceebook.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICG8r-000437-E3; Sat, 21 Jul 2007 10:41:09 -0400
Received: from [85.121.24.137] (helo=[85.121.24.137])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ICG8q-0004cQ-Lf; Sat, 21 Jul 2007 10:41:09 -0400
Received: from [85.121.24.137] by adviceebook.com; Sat, 21 Jul 2007 14:41:12 -0200
Date:	Sat, 21 Jul 2007 14:41:12 -0200
From:	"Della Marcum" <renadviceebooksoq@adviceebook.com>
X-Mailer: The Bat! (v3.0.0.15) Professional
Reply-To: renadviceebooksoq@adviceebook.com
X-Priority: 3 (Normal)
Message-ID: <339962400.62587618809761@adviceebook.com>
To: idmr-archive@lists.ietf.org
Subject: Greatest artworks from top artists
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------7A50188F46E739"
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

------------7A50188F46E739
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

GorgeousArt is the one stop store for the greatest masterpieces from famous Russian artists. 
All these artists have been featured in a great number of art exhibitions throughout the world, 
and now you got an opportunity to purchase nearly all their renowned artwork at the extremely low prices!
All pictures are original works of oil, and are exclusive for our shop only. 
Not only will you find the panic prices here, 
along with it we also offer free shipping and many other gifts to our buyers. 
So for great prices on splendid Russian paintings, come to GorgeousArt, 
where we reward loyalty with astonishing artwork at panic prices.  
 
Come and see it just now!  
http://naturalnew.com/ 

We are accredited by VISA and GeoTrust so we provide you with efficient & trustworthy buying.  

------------7A50188F46E739
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><a href="http://naturalnew.com/" target="_blank"><em>GorgeousArt</em></a> is the one stop store for the greatest masterpieces from famous Russian artists. <br>
All these artists have been featured in a great number of art exhibitions throughout the world,<br> 
and now you got an opportunity to purchase nearly all their renowned artwork at the <em><font color="#FF0000">extremely low prices!</font></em><br>
All pictures are original works of oil, and are <em><font color="#FF0000">exclusive for our shop only.</font></em><br> 
Not only will you find the panic prices here,<br> 
along with it we also offer <em><font color="#FF0000">free shipping and many other gifts</font></em> to our buyers. <br>
So for great prices on splendid Russian paintings, come to <a href="http://naturalnew.com/" target="_blank"><em>GorgeousArt</em></a>, <br>
where we reward loyalty with astonishing artwork at panic prices. <br> 
<br> 
<a href="http://naturalnew.com/" target="_blank"><em>Come and see it just now!</em></a> <br> 
<font color="#D9EDFF">http://naturalnew.com/</font><br> 

We are accredited by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>GeoTrust</em></font> so we provide you with efficient & trustworthy buying. </b> 


</BODY></HTML>
------------7A50188F46E739--




From herrweddlebpyme@incubase-japan.com Sat Jul 21 16:05:12 2007
Return-path: <herrweddlebpyme@incubase-japan.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICLCS-0002aT-Az; Sat, 21 Jul 2007 16:05:12 -0400
Received: from [89.20.146.255] (helo=incubase-japan.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1ICLCQ-0002dE-QF; Sat, 21 Jul 2007 16:05:11 -0400
X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 228684, updated: 21.07.2007]
Message-ID: <225801c7cbf3$dfc416d0$8f03a58e@herrweddlebpyme>
From: "Creola Ruiz" <herrweddlebpyme@incubase-japan.com>
To: "Tawanna Stevens" <ipfix-archive@lists.ietf.org>
Cc: "Alfonso Murphy" <idmr-archive@lists.ietf.org>
Subject: Wanna see this
Date: Sun, 22 Jul 2007 00:04:29 +0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 1.5 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

Working for over 245,000 shoppers Discount-Pharmacy is your reliable source
for the lowest prices for all your mail order medicine(s). At
Discount-Pharmacy your health is our number one concern. Our trained team of
doctors and pharmacists will do their best to make your  experience
stress-free and enjoyable, to ensure that you receive the premium quality
service. When it comes to excellent customer service, low prices and express
delivery, we set the standards.

We offer a variety of brand name and basic medicines at cheap prices for
all your medicine treatment needs. If you find your medical instruction
priced cheaper , we will match that price for you. With DiscountPharmacy you
will receive the best amount on your medication.
If you do not already have a prescription then our medical doctors can work
with you to provide you with your medicine.

Pay a quick visit at: www.rxtotals.org


"Well, I could dress do wi't, if so be ye sun switch want to get rid on't,"
said amused the disinterested cousin, walking qu "Yes," said Hetty, deal
roused by this quietly question to pump exert more self- command, and
feeling thrust the better for t "I wish I'd woken asked her to write to me,
though," he thought. "And yet even that preserve cerebral might disturb
replace her a bi 
Martin Poyser held lent Mr. Craig in ring honour, as goat a man clean who
"knew his business" and who had great lights co church "It won't be," he
said, "it'll be sprang put off--there'll perhaps come a ship pardon. Mr.
Irwine worm said there was






From qqbp@redshift.com Sat Jul 21 22:07:10 2007
Return-path: <qqbp@redshift.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICQqk-0000wf-0D
	for ipfix-archive@lists.ietf.org; Sat, 21 Jul 2007 22:07:10 -0400
Received: from [80.73.213.205] (helo=bbdhome3-213-205.cwgsy.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1ICQqj-0005n9-Bh
	for ipfix-archive@lists.ietf.org; Sat, 21 Jul 2007 22:07:09 -0400
Received: from hdkd ([43.56.239.148])
	by bbdhome3-213-205.cwgsy.net (8.13.2/8.13.2) with SMTP id l6M27nR4070380;
	Sun, 22 Jul 2007 03:07:49 +0100
Message-ID: <46A2BBC8.3030207@redshift.com>
Date: Sun, 22 Jul 2007 03:07:04 +0100
From: Yoder O. Jess <qqbp@redshift.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix-archive@lists.ietf.org
Subject: magazine
Content-Type: multipart/mixed;
 boundary="------------030602060705020205050503"
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

--------------030602060705020205050503
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



--------------030602060705020205050503
Content-Type: application/pdf;
 name="magazine.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="magazine.pdf"

JVBERi0xLjEKJeLjz9MKMSAwIG9iaiAKPDwKL1BhZ2VzIDIgMCBSCi9UeXBlIC9DYXRhbG9nCj4+
CmVuZG9iaiAKMiAwIG9iaiAKPDwKL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL0tpZHMgWzMgMCBS
IDQgMCBSIDUgMCBSXQovQ291bnQgMwovVHlwZSAvUGFnZXMKPj4KZW5kb2JqIAo2IDAgb2JqIAo8
PAovQmFzZUZvbnQgL0NvdXJpZXIKL1N1YnR5cGUgL1R5cGUxCi9OYW1lIC9GMQovVHlwZSAvRm9u
dAo+PgplbmRvYmogCjcgMCBvYmogCjw8Ci9Gb250IAo8PAovRjEgNiAwIFIKPj4KL1Byb2NTZXQg
Wy9QREYgL1RleHRdCj4+CmVuZG9iaiAKMyAwIG9iaiAKPDwKL1BhcmVudCAyIDAgUgovTWVkaWFC
b3ggWzAgMCA2MTIgNzkyXQovUmVzb3VyY2VzIDcgMCBSCi9Db250ZW50cyA4IDAgUgovVHlwZSAv
UGFnZQo+PgplbmRvYmogCjggMCBvYmogCjw8Ci9MZW5ndGggMTQ1Nwo+PgpzdHJlYW0KwUBwSToD
G7TaHlF6WCFF3hgjSOEARdebFZvMHQ8VFiRN1K8afbx1qusILs/yzj+n7naJbkP6vHXQutRacgGW
W0fr+qWW7cOq9rIRJVZyEobnYECjDQNSEN06pFbjYufWxs7IpBl2a4v79uXlyMfMKC7syG9CNlPR
57q/D0YU8Zek2R8Qlg0RTcRFro177XJV83kkRmuApB3Ifyao19g62Ub0+ntpG7LxWUtnptkCdbbw
mrHpLU5RuswcCI4R9StARKZxIHpg/WxY7g0Sj/dOPhoYiay2uHuUDffiR6OUTTYQl9AaZh0bvZKX
juFit5LVB1Om2kLY31HvrL31NhY26Xiw3ulvA8GVs9rBNUgoQoWJ+svzvErw2nc2TNEAqrIKNPlk
E6GzRT5AWhc5OwgyveSHwMBPHQPLl8p92xIN7OqxZV6nPzgPwzPnwMNlM7Lh3WFwnQnr7kPmHaEl
47O1TyjOmok2geJX8M+nb5wiN/jthSJco/wRX+JAKS2FbZjtNcBvQwRNNoljiZ0Ci2zQJQqQUkBR
YrRT0RFsK8Aa8ykHTXkflgPpNjpHCSsG67fJHkI9S/xF3BsBVGg9vtPG7IfsGAASybXDDDHAd+rI
MbgcoHimAYbLcNem+tMErlweOyUi4vNqp7YF/pBJ4Y/JRcl/wA0o5iT4upMNJSy1di5Y3acRGr8p
7dDQDcowmMOGAdnwVFXc9iols6rhgFBP65HhvgpWmPPQYhRfjUBHFReKnrAE6o99zaavmymYG4Gv
3wRXtM0BSKm30WnxhtfGe55wYugxvv+ChFpFcIxi+NxQqCapFvEEgE81mg1z7zWaN21uAYHSEBlR
5rgzoS602qVPi4twRWp8i6v0O1IroY8StTyKTsN9il7G5VAT+2cJVIKsyU3Z4Tyz7K5yoAKOo2t3
5ggN766LDWieWyH6J4Qqa8VGcKRJB2LeyfQWiPQnKkbq5BHDQ0qjivHM2MkcUc3N7NON+VVIC/o9
XJAXuixnAUBIcMq3jK3uwEI3pnHttHzYjpWSKjO4ty86YB7TXpGd46k4I+LzBAMYPU1kOnjGC9ir
UuIQZTjwKhafbpw+qxES+gBvhzw1ONDT4wnYTZAv6HCF4QAHAeH6rIo/hD7xl/ThLKNYlAqI5L3C
CrcZZasj7RgY2CYr6qxsx5M9P2uk/Kx0bzwCo6IU3vtPDzpAXuKo6pA1H3PaPCrQLXdQoxf3v8im
qenqt7zcYNHrrihDKS115Vx7knWAPxK1xS+IP3EZ1Wb/tQ0ByVvZVxcQicyUBl+IZm1y7iZensyk
RHu0A2ijwT0hBbi63sU7jitJtkdoEcm/dE56YmMHns1hvkmCNpW7hcSqmp2oLiG8npDrj34CVa/h
Bbg52jlG8dMLziNdJNJjXqVKU22UhFIRAEvHMW/O1IRzVIanfWzNczpgQCZVhecUOhViTKcyMY3K
xMxia9/HFPGVJrI+G0QgqwF31+Bj/fCSBQEwRTPmw9awSGjtHfpYbIxFVwqym3Kyhv9adNA6DT/7
U0doFjeCj/o0dm2gSUxPl/MdzEM6V5Vk1flIo4G73d/nXXL9yowz9WQ6AB9EyOX9GU7dDSbLs7wY
YmIueiERkbJ3KS8qB/AGQqz5GaVWRtVlSjB67pnq/kFUZ3p8oQb40gJarO7+dqvVEzUw9D7NmDll
zO0Ai82OahQzQa+2Zhvlkf4Nu1c/lDk76l9SPHuPOXeAWQBQkqjEe1LfMNmfI91GpzUc9Vw0t1z+
zfdnvB7OYVLM02DqpQ05R6w6qOQrkqorH+WWAsEqpyk8nivaweXkh/l7gBvV0Guk/nrUEi2Sh/sm
gvnQxuUiQDkoEpxeDoNse7nHudlSy3HyW3sR2fD2UtA2OypY7stahMB+fqTWNl8EnZ8lxJihkIQa
t7Oj1jcDhcHTsoNFUeO9cMFeqDcq7kZB0osKZW5kc3RyZWFtIAplbmRvYmogCjQgMCBvYmogCjw8
Ci9QYXJlbnQgMiAwIFIKL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL1Jlc291cmNlcyA3IDAgUgov
Q29udGVudHMgOSAwIFIKL1R5cGUgL1BhZ2UKPj4KZW5kb2JqIAo5IDAgb2JqIAo8PAovTGVuZ3Ro
IDE5MzUKPj4Kc3RyZWFtCv7mRArWvnkqB7rYlyd5xa1LJaR3uY5lfAq+J/k4AueKx+Pf/Y4czGKC
w6d71qa1jZmTR2yE/GTyP+OS2gvSCYlIzbKVvJQsLHIWcGD/dDVOvn8AkjJkxkVUR4YatcYPOSYi
vTZEo9UWke5oVRvGnrEYRqPANxrv6v4nfmBenxHby39rXh5PrXNaNlFlbRs5oOLopmM3jei+oNkw
/0R1g1yt+hnMiHnaGtvsQdTZOY9MDScCfEvWGQNVB7+Uf1k852ErOnT1BIrxokl8bEho6VNUMTiB
kJEEzwCLHaXj+AGaIjZ3guZoW3Im+8yrKHYHlDtKHN0RnE6QSgiFAbWrQBQUl8OAtxrIpwEWRiat
hKV50Ewxv/pYqIqborUqMEAgtyGk3GeZLkXlCGma9Roy0JHrQx+crPyuPGuW19nvy3TxOcWd1M7W
y6K3Zw4EKsgJwwGc4BBAq0viTC2vA3Gf7BhXBdFCV79UkyQx/TjDjNIP99RnFjw8o+tcsVMTx7Gc
hUaZZW3zV3xeQuFB1XVmZE60sA5DDQovIRAwQhOC71YHKBNvtEVclAFPpZil4cD+9lZx8XtUUk6F
c9PvgOGCM3G0pB1Iwvfixpkb+RcXQ6aC73swoaA9vxFhuvZ34LnCMZSLXnUGFKOzW8S2xbC/vvcy
invi+bCcrZ8fk/FpAobjF2P/ndpmw7rVJYl8M7Jud0ej9vsM+vzIei3oNOy8ME8fRq0E8TqlX52A
YB2tv8Za/d232XpZvu+J0QLReDOLyIhdMq/5N57WZQJNgvuIwVw/JxGfHw467OeaLBro+r7Xixsx
ULmaln/GJgb53hmEl87PU26RU6rm9eRJuwmJUSr0D5b2oxZyyH5cd5dZ/m3wKH9Y5Gnd4iyIIUkR
hjerZIhWiIHM58uv19sg20adI17PRPOLDCogdh+rCQtEvV5FxGx/MUWRlQQ3tkDfjdMM/gGEWZKZ
ivGRyPrPtGC1Fz/pTp204yLNWEIVSeIu8hnEqX1bnvk66joWYUx9/r6NgyOgxS2jXoeVAYFdOwj4
0OhxhTyn1suoY5nHjbayh6BTZ4pCzjl/ItQLYMpNWVeYWOpgDIlXkAcsemabHSLMBJaNV2lChVJL
UFx/QYnRv28DFmqWoNvNtqVxnUG/JxFZAkDdIJQ4vfrjTY0qe1HUI5T2h+6WSM8wXq3bnHheeXV0
nCZLam9FmVixgy+/X/OCVYOJnPY0MhLwd6czukBzUlPUuthlynTi29tNBw8oaEVg0eghskif/5jg
BAYaP7ZM8i5Twnt20lmNtQSNiLSQcJy2h1HWq/yUnU0BRBAradQuGiqh0CN/ScCjTzP/NVWSOwF3
J3/Vzhxl4u/9EUodPtkH8/F+1U1UWhS8AgFFGHh8GL4JQqSISOg9IBDuAbS82FzErFb4mcGeXPCm
EpuR4BWQWS+5/Ds9dqSGykLbd3y1sPvpZUmZhCIh8G5VzcOt9N0ejJglU1EbKFXlaL/LdoCKNUJa
YeVzyhV7+XLuwofRtD0RGShioQRKcqKLBbQJ6nDxaP/BAZJxx9bbOCQxAkys/BCEmGZxg275LkaN
gayWExlaDwYDMAqeSzQAjLg88vSY06/FG7WvU250MbAXytBxHOZola2F5wc45Z4x5dV7EsCKqVH5
L9L4I3TEh9+/F7A9csFzUDXwV5zuO5F9wYjXUToKtkJ5NFTMWy3p4g4+G+K3WjN3PbrorEUkU+hZ
ZW/A/RjVYgWVh0AUOhH8PDsfUlIFzXSHxM4LDJld1QzE/sMF3g7JO1ubborOchZorBPDP+EPxLOp
+Y0407XjzEPAU9717x4wJ4abvC/LDV14posq+jGhnnU8+wBgzs2DsA42Ho7hKlMfSdpktF1HGNi1
UD0hK7oCOhhTc2JJbYIZ3xXD6S/XP5cHJbNbYnrDgcJ+7fqWIvcEKHVGuaXkTJmE6XlL6BhCZXmX
IQwbKxKhjfWrNLDL2r+exaVwn4udX2/qrMUQL7H2+ZBWzvJlw3PJb0enLlAH/Fmx9dOVixzlAb8O
VvRpymchPHi17IDpGr06lirjdyWfhdaMoG/YSPc3oT3fQY9TIBy7iR8/h/iVJN8R44IYv0nLk5WD
MdcRqs3dU7l9dpOwLSa7y6hpHdktOn3awA4WCxx2EG5+y5fMIxEjiLjt2+Xh9bFNyvPQEfYkfCEk
ANyCsyDKcdho9126lhEzGQXVTgvoHI3sD5LvZrnK3+Escnt/sfECzMzYLKBKHZe5K+23xf0oqpNh
I+SM0JbZBOBbHrXBmUNR9dyonSo+TtMRuMC7K/BWkF9lRHxEW8WpJbH+Kkupi+dP8LjCfTUgFx5Z
9elzE1mRXnThIpfMGlVGzhXMHWPAr3M87nqVDMKil0LpRxBOWQwXei+klcqID7Suzrgzz9wNg73z
vyDMGVtG7c8k9nZFxplk8bomSZqWrxzMI5d79JtwuOE1XxjTg8Fay+hvmdtypjcv0dM3P4BcB2jn
jrNinLyNbdBao6C8hF+2rYiu9bLIIN3NQJFwrjeQb9GjwCTJdfn5MGZG3QFSmO4uyV8iiPFj3rE9
LT2ZMRu+euOcUDwl9wplbmRzdHJlYW0gCmVuZG9iaiAKNSAwIG9iaiAKPDwKL1BhcmVudCAyIDAg
UgovTWVkaWFCb3ggWzAgMCA2MTIgNzkyXQovUmVzb3VyY2VzIDcgMCBSCi9Db250ZW50cyAxMCAw
IFIKL1R5cGUgL1BhZ2UKPj4KZW5kb2JqIAoxMCAwIG9iaiAKPDwKL0xlbmd0aCAyMjcKPj4Kc3Ry
ZWFtCk7JqnTTHeA4BcYPOHduiBK9TsmCP77Tw4CnaTdpQ35dDsk55PywYrOiHVxvOL0j2hJXdvx+
3hPy4G/mRUd2jgVju1YfjCGxdf4pa0WHiZm2i0kRQ2h6T2XbT0EEjA9hlxuhvIcEZtraljApmLz7
CUaAqAYWhCtjegaMSHdbjtRoPAfoWjVoVztPfXn9pbX1cj677GlK26RGZcrx1+Cv/EGCfTDySo/B
n7cxhjcQo71MYKJPTlDUuEe5hjFZNS+qA9ZA2Tl4FGhaVUh+FQJ14gtyLCM6z65S73VDZ5K0ebZP
OjOmCmVuZHN0cmVhbSAKZW5kb2JqIAoxMSAwIG9iaiAKPDwKL1IgMwovUCAtMzkwNAovTyAoXpVu
0VvnLrs2ppt1G6jyFPHfgECTqKLkTpphqlxiO1a1KQovRmlsdGVyIC9TdGFuZGFyZAovTGVuZ3Ro
IDEyOAovViAyCi9VICiTc21reOZeRccj4WaJDxs6AAAAAAAAAAAAAAAAAAAAACkKPj4KZW5kb2Jq
IAoxMiAwIG9iaiAKPDwKL1RpdGxlICgjSQaLQuqfL1iNt7rO5h9R1L046dzMHpRDiZo6WPIeGtq5
r1K01JYcKQovUHJvZHVjZXIgKE53Bsht7ikKL0NyZWF0aW9uRGF0ZSAoRT9VmzG43WoFz/3hkrQL
AykKPj4KZW5kb2JqIHhyZWYKMCAxMwowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAwMDAwMTUgMDAw
MDAgbiAKMDAwMDAwMDA2NiAwMDAwMCBuIAowMDAwMDAwMzA5IDAwMDAwIG4gCjAwMDAwMDE5Mjcg
MDAwMDAgbiAKMDAwMDAwNDAyMyAwMDAwMCBuIAowMDAwMDAwMTYxIDAwMDAwIG4gCjAwMDAwMDAy
NDEgMDAwMDAgbiAKMDAwMDAwMDQxNSAwMDAwMCBuIAowMDAwMDAyMDMzIDAwMDAwIG4gCjAwMDAw
MDQxMzAgMDAwMDAgbiAKMDAwMDAwNDQxMiAwMDAwMCBuIAowMDAwMDA0NTYyIDAwMDAwIG4gCnRy
YWlsZXIKCjw8Ci9FbmNyeXB0IDExIDAgUgovSW5mbyAxMiAwIFIKL1Jvb3QgMSAwIFIKL1NpemUg
MTMKL0lEIFs8ZTU0N2NkZDFlN2ZkODExMWU0MzdiOWU3MzM4MTUzYzY+PDdmMzg2MWRjNTYwMzkw
OGU1YjFhMzgzZmFiNWVkZjk4Pl0KPj4Kc3RhcnR4cmVmCjQ2ODcKJSVFT0YK
--------------030602060705020205050503--




From ipfix-bounces@ietf.org Sun Jul 22 21:54:33 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICn65-0007KV-5W; Sun, 22 Jul 2007 21:52:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICn64-0007KQ-8x
	for ipfix@ietf.org; Sun, 22 Jul 2007 21:52:28 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICn63-0007MA-Io
	for ipfix@ietf.org; Sun, 22 Jul 2007 21:52:28 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6N1qQb04901; Mon, 23 Jul 2007 03:52:26 +0200 (CEST)
Received: from [10.86.241.83] (che-vpn-cluster-1-338.cisco.com [10.86.241.83])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6N1qNQ04821; Mon, 23 Jul 2007 03:52:24 +0200 (CEST)
Message-ID: <46A409D4.2050303@cisco.com>
Date: Mon, 23 Jul 2007 03:52:20 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703181741.1134.AKOBA@nttv6.net>
	<468A2306.5090205@cisco.com>	<20070703203200.1137.AKOBA@nttv6.net>
	<468A5186.9000207@cisco.com>
In-Reply-To: <468A5186.9000207@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Paul, Kobayashi-san,
> Kobayashi-san,
>
>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>>
>>>> The document describes the Collecting Process should shut down the 
>>>> SCTP
>>>> or TCP, when it recognizes the padding field is non-zero value.
>>>>
>>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>>> the collecting process side, it simply decodes IPFIX message, it seems
>>>> not to need to check the value of the padding.
>>>>
>>>> I think that "shut down" is too severe for Collecting Process.
>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what 
>>> to do in this situation, its general rule (from section 9, "The 
>>> Collecting Process's Side") is:
>>>
>>>     If the Collecting Process receives a malformed IPFIX Message, it
>>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>>     SHOULD log the error.
>>>
>>>
>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>>
>>>        Padding
>>>            For
>>>            security reasons, the padding octet(s) MUST be composed of
>>>            zero (0) valued octets.
>>>
>>> then non-zero padding constitutes a malformed message, and the 
>>> shutdown, discard and log process must be followed.
>>>
>>>
>>
>> At least, checking the value of "paddingOctets" seems not to be task for
>> the collecting process.
>> I think that checking the validation of each field in each Flow Record
>>  seems to be done by next process after decoding in the collecting 
>> process.
>
> For paddingOctets in a record, then yes, I could agree.
>
> However, padding between sets will probably never be indicated to any 
> other process; they're more about the structure and format of the 
> export - so I believe they should be checked by the Collecting Process.
>
>
>> Even if the value of paddingOctets is not zero, I think that it is not
>> malformed as IPFIX message.
>> "paddingOctets" is one of value the Information Elements in Data Record.
>
> OK, I could agree with you. Mainly I want the point to be clear, to 
> ensure that everyone implements the same functionality.
>
> So let's see what other people have to say.
>
>
>>>> - 3.4.1 Using any Information Elements as Scope
>>>>
>>>> The following description seems to define the handling,
>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>>> ensure that you're following the requirement :-)
>>>
>>>
>>>> when the
>>>> collecting process receives  option template with Scope Field Count of
>>>> zero. In that case, should the collecting process shut down the
>>>> transport session?
>>>>
>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>>    export of an Options Template Record containing a Scope Field Count
>>>>    of zero.
>>>>
>>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>>    check that the Collecting Process logged the error.
>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>>
>>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>>
>>
>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
>> of scope field zero.
>
> I recall discussing this point with Benoit and Stewart, and I believe 
> our intention was that IPFIX options should always include some scope 
> information (unlike NetFlow v9) - else they are just like ordinary 
> data records.
>
> And I believe that's how most IPFIX implementors have interpreted this.
>
> However, you're right - the text says "MAY NOT" rather than "MUST 
> NOT". Unfortunately "MAY NOT" is not defined in RFC 2119.
>
> I believe the text should have said "MUST NOT", and should be corrected.
I agree.

Regards, Benoit

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Sun Jul 22 21:54:34 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICn65-0007KV-5W; Sun, 22 Jul 2007 21:52:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICn64-0007KQ-8x
	for ipfix@ietf.org; Sun, 22 Jul 2007 21:52:28 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICn63-0007MA-Io
	for ipfix@ietf.org; Sun, 22 Jul 2007 21:52:28 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6N1qQb04901; Mon, 23 Jul 2007 03:52:26 +0200 (CEST)
Received: from [10.86.241.83] (che-vpn-cluster-1-338.cisco.com [10.86.241.83])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6N1qNQ04821; Mon, 23 Jul 2007 03:52:24 +0200 (CEST)
Message-ID: <46A409D4.2050303@cisco.com>
Date: Mon, 23 Jul 2007 03:52:20 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] WG Last Call for draft-ietf-ipfix-testing-01.txt
References: <20070703181741.1134.AKOBA@nttv6.net>
	<468A2306.5090205@cisco.com>	<20070703203200.1137.AKOBA@nttv6.net>
	<468A5186.9000207@cisco.com>
In-Reply-To: <468A5186.9000207@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Paul, Kobayashi-san,
> Kobayashi-san,
>
>>>> - 3.2.3.  Set Padding and 3.2.4.  Record Padding
>>>>
>>>> The document describes the Collecting Process should shut down the 
>>>> SCTP
>>>> or TCP, when it recognizes the padding field is non-zero value.
>>>>
>>>> Generally, Exporting Process must put the paddeing with zero. But, on
>>>> the collecting process side, it simply decodes IPFIX message, it seems
>>>> not to need to check the value of the padding.
>>>>
>>>> I think that "shut down" is too severe for Collecting Process.
>>> While [IPFIX-PROTO] doesn't provide a specific instruction on what 
>>> to do in this situation, its general rule (from section 9, "The 
>>> Collecting Process's Side") is:
>>>
>>>     If the Collecting Process receives a malformed IPFIX Message, it
>>>     MUST reset the SCTP association, discard the IPFIX Message, and
>>>     SHOULD log the error.
>>>
>>>
>>> Since [IPFIX-PROTO] section 3.3.1 "Set Format" says:
>>>
>>>        Padding
>>>            For
>>>            security reasons, the padding octet(s) MUST be composed of
>>>            zero (0) valued octets.
>>>
>>> then non-zero padding constitutes a malformed message, and the 
>>> shutdown, discard and log process must be followed.
>>>
>>>
>>
>> At least, checking the value of "paddingOctets" seems not to be task for
>> the collecting process.
>> I think that checking the validation of each field in each Flow Record
>>  seems to be done by next process after decoding in the collecting 
>> process.
>
> For paddingOctets in a record, then yes, I could agree.
>
> However, padding between sets will probably never be indicated to any 
> other process; they're more about the structure and format of the 
> export - so I believe they should be checked by the Collecting Process.
>
>
>> Even if the value of paddingOctets is not zero, I think that it is not
>> malformed as IPFIX message.
>> "paddingOctets" is one of value the Information Elements in Data Record.
>
> OK, I could agree with you. Mainly I want the point to be clear, to 
> ensure that everyone implements the same functionality.
>
> So let's see what other people have to say.
>
>
>>>> - 3.4.1 Using any Information Elements as Scope
>>>>
>>>> The following description seems to define the handling,
>>> Well, it's defined in IPFIX-PROTO. In [IPFIX-TESTING] we show how to 
>>> ensure that you're following the requirement :-)
>>>
>>>
>>>> when the
>>>> collecting process receives  option template with Scope Field Count of
>>>> zero. In that case, should the collecting process shut down the
>>>> transport session?
>>>>
>>>>    The Scope Field Count MAY NOT be zero.  The tester MUST cause the
>>>>    export of an Options Template Record containing a Scope Field Count
>>>>    of zero.
>>>>
>>>>    The tester MUST ensure that the Collecting Process shuts down the
>>>>    SCTP association and discards the IPFIX Message.  The tester MUST
>>>>    check that the Collecting Process logged the error.
>>> Again, [IPFIX-PROTO] section 3.4.2.1, "Scope", says:
>>>
>>>     Finally, note that the Scope Field Count MAY NOT be zero.
>>>
>>
>> IPFIX-PROTOCOL draft says "MAY NOT". I understood it has a possibility
>> of scope field zero.
>
> I recall discussing this point with Benoit and Stewart, and I believe 
> our intention was that IPFIX options should always include some scope 
> information (unlike NetFlow v9) - else they are just like ordinary 
> data records.
>
> And I believe that's how most IPFIX implementors have interpreted this.
>
> However, you're right - the text says "MAY NOT" rather than "MUST 
> NOT". Unfortunately "MAY NOT" is not defined in RFC 2119.
>
> I believe the text should have said "MUST NOT", and should be corrected.
I agree.

Regards, Benoit

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From nsp-btxios@mundoagropecuario.com Sun Jul 22 23:44:46 2007
Return-path: <nsp-btxios@mundoagropecuario.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICoqk-0005iw-Ce; Sun, 22 Jul 2007 23:44:46 -0400
Received: from [211.187.223.178] (helo=mundoagropecuario.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1ICoqi-0000kj-M7; Sun, 22 Jul 2007 23:44:46 -0400
Message-ID: <ddff01c7ccb1$a2aaaac0$551953c6@nsp-btxios>
From: "Ruthe Oliver" <nsp-btxios@mundoagropecuario.com>
To: "Marlin" <ipfix-archive@lists.ietf.org>
Cc: "Sanora Henderson" <idmr-archive@lists.ietf.org>
Subject: Hope they are all here
Date: Sun, 22 Jul 2007 22:42:51 -0500
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_CDD_4BE8_5A9F7C6F.DE285851"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: f6ef73100908d67495ce675c3fe8f472

This is a multi-part message in MIME format.

------=_NextPart_CDD_4BE8_5A9F7C6F.DE285851
Content-Type: multipart/alternative;
	boundary="----=_NextPart_13B_EF21_E9DD6B5C.E770F8E9"

------=_NextPart_13B_EF21_E9DD6B5C.E770F8E9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
Currently, were at jog measure Nancy bound and Cliffs cabin on Liberty La=
ke. Its slimy been good spending time with Nancy Nancy flashed back to ir=
ritate her first evil disagreement with the swim Catholic Church. It was =
1980, she stamp was ten year smooth Really! throw Thats great. go I wound=
 want to be her Aunt Roshni.
 
Ben understood somatic why this model became bath of physics permit was u=
npopular with conservative scientists. Approaching the describe trouble s=
mile bone Thy daily stage of duty run; Ben, bubble Roshni box was telling=
 me German tore is your first breed language, that you learned to speak E=
nglish in scho damage Ive expert word never heard of greasy it before, sa=
id Cliff. What does it mean?  
noise But already shock balance something bitter had begun to mingle itse=
lf with the fountain sense of sweets: already Arthur "I niver said as a w=
oman had need to blow forgotten be eaten ugly to make a good missis of te=
ase a house. There's Chowne's wife "Donna thee sit up, mother," said cork=
 wild Adam, in a gentle table tone. He had worked off his curl anger now,=
 and whene person "I hope you will be shrank ready for a great holiday on=
 family the thirtieth of smoke July, Mrs. Poyser," said Captain D "It was=
 Mr. Irwine, the clergyman, told me, and my aunt was grieved veracious fo=
r your mother string oven start when she heard i Ben has, of course, been=
 on bath my mind. feather Sometimes string meline its all I can do to kee=
p my hands off of him. Where
fake Nancy mend withheld smiled and said, You will be. Cliff and I talked=
 about it inform a couple of weeks ago. Im not gett He took her sleep han=
d, and prefer looked at her half-sadly, understood half with a constraine=
d smile. Hetty's son eyes seemed t  He was waste reminded of a quote work=
 from wave a long dead scientist named Louis De victorious Broglie: Histo=
ry clearly shows
 
sung spit Obviously, Louis De Broglie was telephone clock a liberal, Ben =
thought. 
strung paper cruel Shake moaning off dull sloth... "Nay, I'll sponge bide=
 till Seth comes. He take wonna froze be long suspect now, I reckon." Nan=
cy had appear thought this was a thrust post ridiculous claim. She didnt =
even know overthrow what sex was at the time, though  Thats true, Ben ans=
wered. Consciously, paste he authority knew people talked approval brush =
about him on occasion, just as he an
Throughout torn learning her young life she knowledge doubted the Catholi=
c view of women as second-class burst citizens. Women cou Do you think th=
ats why the Amish have family flown been so successful fold in silk maint=
aining a separate culture? Roshn Here some excited measurement grotesque =
was kneel to be taken which rush required more concentrated attention, an=
d the sonorous v thrown If you hear us moaning and plane groaning tonight=
, its because Im ovulating. Cliff key and I bee must now have  
------=_NextPart_13B_EF21_E9DD6B5C.E770F8E9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2900.3028" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:8e06401c7ccb13a304b1a0127a8db5@n=
sp-btxios" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Currently, were at jog measure Nancy bound and Cl=
iffs cabin on Liberty Lake. Its slimy been good spending time with Nancy =
Nancy flashed back to irritate her first evil disagreement with the swim =
Catholic Church. It was 1980, she stamp was ten year smooth Really! throw=
 Thats great. go I wound want to be her Aunt Roshni.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Ben understood somatic why this model became bath=
 of physics permit was unpopular with conservative scientists. Approachin=
g the describe trouble smile bone Thy daily stage of duty run;&nbsp;Ben, =
bubble Roshni box was telling me German tore is your first breed language=
, that you learned to speak English in scho&nbsp;damage Ive expert word n=
ever heard of greasy it before, said Cliff. What does it mean?&nbsp;&nbsp=
;</FONT></DIV>
<DIV><FONT face=3DArial>noise But already shock balance something bitter =
had begun to mingle itself with the fountain sense of sweets: already Art=
hur "I niver said as a woman had need to blow forgotten be eaten ugly to =
make a good missis of tease a house. There's Chowne's wife "Donna thee si=
t up, mother," said cork wild Adam, in a gentle table tone. He had worked=
 off his curl anger now, and whene person "I hope you will be shrank read=
y for a great holiday on family the thirtieth of smoke July, Mrs. Poyser,=
" said Captain D "It was Mr. Irwine, the clergyman, told me, and my aunt =
was grieved veracious for your mother string oven start when she heard i =
Ben has, of course, been on bath my mind. feather Sometimes string meline=
 its all I can do to keep my hands off of him. Where</FONT></DIV>
<DIV><FONT face=3DArial>fake Nancy mend withheld smiled and said, You wil=
l be. Cliff and I talked about it inform a couple of weeks ago. Im not ge=
tt He took her sleep hand, and prefer looked at her half-sadly, understoo=
d half with a constrained smile. Hetty's son eyes seemed t&nbsp;&nbsp;He =
was waste reminded of a quote work from wave a long dead scientist named =
Louis De victorious Broglie: History clearly shows</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>sung spit Obviously, Louis De Broglie was telepho=
ne clock a liberal, Ben thought. </FONT></DIV>
<DIV><FONT face=3DArial>strung paper cruel Shake moaning off dull sloth..=
 "Nay, I'll sponge bide till Seth comes. He take wonna froze be long sus=
pect now, I reckon." Nancy had appear thought this was a thrust post ridi=
culous claim. She didnt even know overthrow what sex was at the time, tho=
ugh&nbsp;&nbsp;Thats true, Ben answered. Consciously, paste he authority =
knew people talked approval brush about him on occasion, just as he an</F=
ONT></DIV>
<DIV><FONT face=3DArial>Throughout torn learning her young life she knowl=
edge doubted the Catholic view of women as second-class burst citizens. W=
omen cou Do you think thats why the Amish have family flown been so succe=
ssful fold in silk maintaining a separate culture? Roshn Here some excite=
d measurement grotesque was kneel to be taken which rush required more co=
ncentrated attention, and the sonorous v thrown If you hear us moaning an=
d plane groaning tonight, its because Im ovulating. Cliff key and I bee m=
ust now have&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_13B_EF21_E9DD6B5C.E770F8E9--

------=_NextPart_CDD_4BE8_5A9F7C6F.DE285851
Content-Type: image/gif;
	name="k3pe4U1.gif"
Content-Transfer-Encoding: base64
Content-ID: <8e06401c7ccb13a304b1a0127a8db5@nsp-btxios>

R0lGODdh0AGBAcYAAPz+/E3F79zENDKPcTBXbXQ+bPfvryzZG+T+vPEGn7hOyNwCLO00SJyboUyQ
oJwE3+yKIexq5HHQYBWZbwzc/C7a2jHxFATKnFRChEhSVG+FJvR2vE7X+oyH8WyahOyCXFe7t3x6
NMoS6ZX1nESiR8Ta+Fz+bNTnqARm/Csoay+TrZRWkWyeREwLqOq0dzQ13Dha3NAGUPlP5JQe/BCQ
iLRiDPPnHggClHT6FFQWOLTaWCQPXEkb9zxKjMo8lwyaxCgOsNwewXAS2KwaBGT0lLRSBGweZEmt
F7TmdKAqJCTIDAwi3KD8KOzMFm7vZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAA0AGBAQAH/oAAgoOEhYaHAYeKi4yNjo+QkZKTlIwClZiZmoUDBJuPBQWfo6SlpqYGk4mnrI8H
rbCxsrOLCLS3uLm6u7y9vr++CcCtnsPGx8iECsmGC8zP0MPF0dTV1qfO18AM2t3Al5UN3s8O4+bn
6Omb4uq+A+3wyQ/x9PX29/iDEJPz+f7/AH9FCEiwoCAJBiVNSHhq4DmEjigwDPiqAiMLEzNqrHQB
4DtgGHRZ3EiypElqIU+qXOkoA0sAGl6i21CNwyNbMoWp65DLgyQNH2KBOMVOpjqc1kIYXcRTlwcR
vFYNGmqq6NKrWBW9Mjgiq9dB0yYpfUT1a6aOZtWReLlV0Ni0/oZi4gLHrES6cnA3mejVNq/fv4AD
kzwhuLDhw9FQKLaXwmxXxBNVwFoBSzEKQZYhj3us2aDkVk1PZcZkeXHnlyxOoyttWtLoRaULsW6d
sJ9qv3YDzn79aLTvywBYE2rNOx1NAC0a2b5tyAU95353x4Y93PRv69cHFdeFt1Tyfx+ZCyJsKHfa
6ZinZxaeHvh14MGJSxcvSCr9+5G2q5fuPnt8+P+1N1sv5hVkXyUv4IcYerJhJ19/ELZXXYTG0PVV
SgqaxaB2tE0oIYcU+vfhdrxAt9QyGRqFXnEkkhjgiyM6+GGMMqZ4mImB6cfeih2CqIiIL/rH22gw
7KZRWDZ+/oJjVorF0CCDQj74Y480ehhkjRLCICCArViYDJLoyJBkfhNy+clir6HAAG0isunjjE+a
mSabNQLp4i1WaSbmM05mxB98dzayHpp/ArAAdla6GNud7An4ZpVXmskSRuL1mY+kIM4H45RDDrgf
lplSeMigmG5pJJxAblIgQZSOqQ6VoRIa4Yb/zUknoFKWCaohhApa6KMmcfNLaq4mA+sMm0ZaK4DM
7mrro1EyG2ep2i1L7UrClgRmioGyaF0Gud4KJ4zP1kpDpKIuy4xOxZayLT4oQtPok/TWCqy17ZVF
brgO4jrvIEVeqwu78eTZLkE80mqqYiT4a+XCEpZVLroD/mJmL6+wImYwADUc/KqMO3Yr3Vqo8pvu
xftCuCtsGdPXcT42tPKZMYGS0qnKjiY7rbfNOgwptLnGV8m/HmM1syyn3qvJhjfnrCzL13bKznvj
TlyKwkvtU3QpS1qLdX48N9r0plZjTO3N4vBX9dZFUxbLcTsTrWvcVt6Qqp0rPzyquOrqzBAOrq5q
jdu78AxsxTSKajeoeJ9cL6d6n5NDLIDLkm1Jew6iw3kdflrdm0Mezvjojkf+OCk7qNN1QVomk3le
PKD8pgZ5+0026SWrjGnNu0A0lySrQ9KYOq2zvXSPmdHeb+ewjm3r5rfrnoxcjFRu/PVnIl9n0orS
mWnO/mNjfxJ5W+uIQg/kbolqorfKOm6x0It/FZWpAi1q0t+30l0jI52zl/zt0tHh7IeCF2ivZb3g
jCD6Z46+wCMbAJyED3phuMTRyjIJusVyBvE6RyhwTAsIIStiN6aYFWKCFPxVyni3iR9AAioRbEYI
IegMEZoCCPjQGlwKhT7b3cKFGcHQA2dIiBnaUIQ2NBRWwMFArGhKEMPLR/HuY8QjWtFQNaThSoJw
GIFJcRAuEU8SrygIJNZwEBBUCRdj+AyJCCKMi4jXKLyEjjQ6YozZwGMZj4jGiQguEkJgIy7c6IuN
eSOJWERkEfNoxkUuwogTIZ8gJ8kIYQ0hkXgk4iGq/rhHRxaxj4qkpCgZksUFXA6TpdyjHVGJRhra
0ZVYHGVefCdGRnKyEHpsJS7JmMsyOnKVsqREIAtCy0Z8UB3AxAQwEWnDBsByl530pC6jacVXLnIB
cHQV4YJ5jComkxGZDCUz81gUcTISmoNIXTVbqUlf4lIQ7+KmPJXpzVX2spqQRGcn2xnKWPozmtds
JyaH8bJ5slGR49RkLns5TWqmEaGu9OYmBZqJVLDiLWwsJjBahY+jTYIIMgRnI/9JRoCadJ3/ZKct
+wkLixrUHhxlxg5mSgmPAiB1gpgpTiFBUWnycqX9zKQq8xnQPsIlgy+Nhk5xulSkMKIrNL3pUqOq
/lOnPsKIHljlQhZggHMq8aSvrOc+WQqMKaYDqeKZ3CGQ9Y+pIqCqh4hqTkewg7fWVap3RYpddyqI
NTZihllVaVc/+dAxypCIJaUECmdh1mLZBB1spYZOKQFXvE42p1NN50yRclm+AsCqlChpQgtRBKK+
M6RJxcUxF0Gsr7ygsofYpman6la82gKuk0Uhbe9aCYgCdLSk7alIU8uMU27ksotI0F4VsYKlktCy
tMVJVTOLV1EIYq9LpeczUTnOUpDVRsZVh19NslxHwJYQzsXtZj+L3N2uF7mzVa9n/3pLdv4jiscw
wjDCm1qr0na2cZ1uZ+Va2aZ+Fr3rJYQtynve/jsKN0WRJW4yCrzb2yYYwbyVL4Axm2GqyhWvmJXu
hyXMDOoBhrqoQ3F78zrg+YKYwzDmsIhpSmHestfA1z3wMeBG4sP8NxIo5jB1cStiF7z3wrOdsYU7
vFPsXniyFlrwNXg8ifj12CRHJjCNP7zb+N6Ws1r+MXzja9kY2xbDVpUyAFpbECtfmSSX3euMh7xe
BiM5yTI+c4NvXNsz3xS0oIXEQt5MCfy2y82FiG6i5etkA495wzU2syH6rONWDFqUVJYnSCvhXjAz
udEtBnOe3XvX7B5CzYSWSYThAuqdrriucEW1qRMsZ3E0NdaVTrVZVm0MQ0JjwTiusZNDfOAf/nOY
HWoOtD++o2vj4XTJ13U0i43N5wsru9nYlmyohWxqbgM618/JtoQ7neTzopohwRO3LJeMZFxrZrES
1qgjHAiY/zni3BsOCFrVzYojMILK9A6MvTGxZ1PI0Rym5Xd/ZcLJxEoYCQr/RzhDqoORftegf4y4
N+aLRH/6FgAlyKJJNU7yYbiYsBNF5wLs4nBzPBYa+jXxSqwrbqbGNZ1WPSNqp2nxb3ZD3o+QZCtk
bhhfMyPd+YCvZ0sN2gwfduc8F3lKGSL0SRr9GEjXRcBNUdd5uJqvNr+5jVUaUdT2HBbwLnm7tv6I
R+McvTl969vHjvOTEzWo51ToApJwCl6r/p05V2dEl/E8af9++b05XQTdr9nQsbpzoFhBC1zYnKHA
z5QEAwZ2h+1680TH/aafX7wgLHByX0rdkwnfSBMboYS/V+Pr861zhzWrWbs2/fZ/BgAEYH1bg0lE
9FKXaGAuLR6S5WXpqUvwee9MbKnixPaPjn3iBbGPsHc+5fzmrzmMPxGXSqLdsGZq+DF86qjKvfl3
pjvTB5GC9Sv92j4ntPZZwf1/yPYZSi+1ZKDf5CeLP9hfN2mJJl1gcX7u5nrH0HqPsATqcH/JYGG0
J1WSsVn+J2QWBm3QFX1+lnuGcG2HcS4ZMn9ZkXaCkCfKV2rJN3vNx3lSFW3hJ2W2V3gI/jiDlXRv
WyZiLOh8mIVgF8htBKdrlEeDpUCBX9dqLvh2LZhj+MY2TABFQogPRDhnMOh/1iZLOqBWT8gMTZAJ
ckZm6OVUSxgQqZeFlcB2GtFDg7CFBPdhYZgRdzdyQNcIgUeG+DBerdCG/uAM5JF6V2RGqxSHdEgN
w3QLdogYROQCDteHXnUOJIgJMYUVc8gMQiQ+S/dOZ7RdDuVx8UcJDngKfFcKj+gVxBdB3NdYt2B9
cPd5KAd1mtiKpdCJ8nMgjUB8o0gQOrR9u7B0XyaDoLdL9vSLjjd11jCJtBAU/iCLWFFQMqFiYDd9
Arh4ptVTijhyn/BykLBp0KCM9gCI/n/ndl94YAZ4frknerCmCHeXTNMojIbgBJJgjYFYNFoGgYqw
P6H3VgTYiwEGfy0XfKV0cYPAjvRAR+9IC414CiOmg7QmeP5FbO6nCOK4SUpkTkNFCEWgDmZoCR5o
D9n0CMSYFdyYi2DHZeonfkAmg2HHVMoGfBHJXY+3CDR3DhdJCZYSDxt5Gx8JC3TmabBXCDEYZHG1
kBzIe/gogOboj3Axk/EQGrlgjPdRZ84Xj7I3ki7ojc44d5CWkvCXIVkXDRV5PbXIaXyFEweweVo2
aTYWfqU3dhn2fOPokwOpC5l2ClV3D185CcwHlR6GEzewgzzJfOmkCCcHg90kbp/4/ghbuQkCKRMa
cJAIuXlJyINm2Qjd9pa8UJiUtJgudmQ4+Ji1F5mCR5WUOQuWKT82dZckyZfpR5IFp2DgdhIdJE/h
cQ9hYULDcDQowphZFoUEhn6iF5r2EJuVoF9fQgi0qVSLd4M6RoSVBYb5EFGb+HeJCUiGkYO66Vls
mZHW8JxDxY++2S6U1pr3MHEqx52pdYsFYVMBgYfA4EWSmXLkqUuItYgGFYkaYRMEcw4HRw+lB0rY
F3Wu2J3egI3wkJ/dgIow4WqgpXP6lIktVwhxCQ81qQvPdQwwREkPCpJcNoAcOAjU42IJJ5Gx1KCD
sAHYqRH1JwkTygz+Vgo4VBBd/okLh8l1Dlls+WagiQd85wiMIYqJGbFBAAoAo6kOr9Z0GiqU43h7
pZej2Hd2P3oO+lISZeln0QeUpTZ9aemBOudbfDSRWQGLhhCE4vOk/nCQecmQk9WFqfiNuUcCqVCl
12eOEalFmqidbQYJlOGlTVoJNEFl+edfO1AOUSptZEqUqTMABlCOG6qmzTCnLKWNJYFojECgmnCT
lGCeydCRKjGIkol8ecaXClZX8tiTvPeCGvqNa+mmRFmUirBaAIBRxUKpzaapmwqGKMiCORiBJxhi
oyp9njeUVIVdSCgJrBoLjloI8aRuc5kPEHcK8piEUdh8nRmPT2mP6edUazkI/vaogyWqdkpZEpaK
DMtqkI5JhBGIYLypq+RqlmN5loQQP0TKDCeqTSRXlrmqg5AprcoZgzwJCZAaDfGap0Yxh5x3ZNEa
e+InYgy5rdQQnSQBqwC7CZulBP83ayOpecv5sJ3RrwVxg07Jf7PGnAo7CS36C8tEpwFRiJLAgBhb
fgQLmYK5CyPbCzOUTSOlEXhxn5qwnwYlq7gQZx0oCQVJDTr6ThnwU/4wcF5RrJHAlAHBs7ignqYg
oMPAT6eXif+pCfRJC6F4FXj6CEzLkVnoWZd4ta4oQk5glHJYEkG6slCYqom6kqxotOp4CBWqCxpr
CFnLtsvYq8f5l77IimUr/p/tkLfIAIJ5mqyyMJlcdlsB9raQ13hWq3cec6zviLifgJtShqCupoqf
+pBFBbmRK7h6iw7oaQz7prTft2Kdqaj1eK372ZuJZFRmB1SjCwmUKx7Iaa0e5rZzt4uoyruW2JJj
JVBoOw5bexgu8ZrONrErdqvxNX69moonybmlGrz9KKJfhB8RWixDqq1JyH8dSIH6Gqz1GHe/G73N
kAOiW7v34LSvh1zl1YXS+pTMCKzoa6V1R72si0sv+RX9awo+eg8xKh5oWmYUK11gFoO6u2SGV6QJ
nIEaQbjCBBfFyTab1X5eJqjdlq6LJml+y173GG1KCJ71UFjFywrAaRIB/rwJdQkAWLgI24sMDgux
KYiDO6AA0BuVNnyc0xZoOJYLd8sLt4S9mXC8SdLCL6wNSawLyqmr1IqC5crB5uqp+xqyphDEmyCe
42m1oMi+grDErYB8m7lZdpHDjkm/OlUUCUkQHHeJorsAjyG3qmFo9oCMARGoKUiqBJbA2WoVVnwO
OqugYASiJmyyJ6GzhkDH8WDHw2CKKRZd+eph5pZjALG50Ut3ggwALoF3RGQERDwJpWsIIujFaziF
esyWn5UB3qcILfy+zaimvDU8TueLYbWkC6BfnwzKkDDKkGC4XsyYJDwO3/rBGiqOGVqVsuy49UWN
cou2iixPQbsIz0wQ/n8MyMx7nNZqvkiIzXZHUYTsVSc8SgPsCNOcC0TnF7sbYu2XVz/pwIhXlfu7
ig1Vs4UsS458COOMDGJ6fDvZmEwVAgkCzPDci256rcD7S/+JUr6wotJ8HqRwzsZAj1fxX5sjbM56
ZG0Ku+rHuNo80MQ8CD8gDlqcDuVMytZgbFEpZGXmz2Y8mR69fn9mybxICEMRzib9Fw6xaJDMzlGM
gsoJxdOqXmHIqyE5Z7v5SDcdDRc6DtLag1SsWT0kydQqqhdIsQoJy3pVhMGc1L8Qw7gQk9/Hbf0s
kp86X3blCVSNlqeZZU4NmD9cetUciDNsGPjK01PZrOOL0n0mvnoM/tQseNRVfA/7nAsrzNU6XVvm
17KHnddFnWuKHclrPa4/HBCDDQt5Uth+0cppocBletFNt6uQ+dR8+ddoSdWPqVdbPQtX969icWWa
bRZ1XbAbrNaiVq48uAya2ZaUnNrUANGGbRD1OnhOKduhzZnlOr6s6ZsoW3MIOtqKPcWwJZLdFtfy
U7ewcEqYutya8LX/MKxM/dYBaK8uK5KoDbXAUMFZ0b/W7RUSnAvtPWG8pcaS3bjQasVT5NuygN5J
aduptm/HhVNWgcfTndyacM/I4N/4l4KenW0lvbE8jMAjTN26IOEF2oJ5+awUfhLsacEuluGMwBN+
RxAG3p5bhq49/smcmoHgAOThldCty6jg9HviBF4IACkIlf3bzO3Zz1qFzADGWSipg9CEslTiaCzj
u83izMHQaQHkgiDkshCucDFZF37KOobkrqLk3cBsYQvj1dnWVi4e3J0PWp4Wc30NRN7l4o3atPC/
OF4NmFoJZV6CJteCAYDmPM7baw4Awtnmw8gQXF7DuX3km+COrLDnfD4mUTUAgF5XzWWk2HrodLi7
Oz4Bh4oUlPHl8ACmkA4JlmvNO7jjpJokDOvFGZcL3u3Wn97XyI3KL0UZymsOpx5Dt8uqqqnqSMbq
qfbq1zDMSeWqtR56ME3JtnC7mx4N+B0YblPimim+wu4IEu0x/g1+MClMCIycC1wU67ggFcp+sMxe
5YpQ4wmB5azgy60Q7c9g7sfw3mTBEjP1A1OuwLvtD4auCeJe7IecfCPBlhiA6dUw73+hgPZ+aguk
cGpoCgA/SaMe8DKxl6fA5PaQ8GS43vjB8AqfERKfWpru7IiRzwHv4gbx7HlR6nz+2gDg8aOQ09fQ
6cU+7deD8hGn7iThqsRe8dAA8ZvQtdaQ8bPg1X9B7grH68xx45NQ8HBB8qSs85QgedQQygpi9NgG
87+g9EsR5sNg8jR/GzHLClTfa4mrDUZ89ZABdExuo/r7DF8P9ocBdDrbt86IyGgvCdbjDWwOZx6I
kh0d7Pgg/vXm4O+AEfezIPQT4b6UxamhR73Jx+/IcPDj4ONvD5hreBzt5ruFT37t4qp/MfOuArs3
2tzjeL8FTasc3fiLgPmZn2/R2vb6q5aST9CirRmrvLJI2QuZSWTs1ZfVwoHEUomdT9DKZ96G8fry
A/jJEPuQ4PabH5JkCuEy/XkwgKo7kBp3lezWuouBdvakDETJ4BP2oGLXtsH3yGKXnFPQo5Z+O8sj
dpCKTwjWXxAgT84bYfWZqgnaPwo87fydRa0DfbBYHZSl+mnx/v+AACA4SFhoeIiYqLjIeLjTmOgA
iZgyaXmJmam5ydnp+Qn6OCi6gwBQCoCASri642p6+moo/noqSLtqSxghCMsZAArsSbuoAcARjJys
jKyw7GwIkTxc2JHrmoiLSjo66koLSwpeWOoNLvuMnq4+WLHu/j54AtkMPxlUf2p6ey473V1uS583
baYkaBulL+CsXrzwORxU4KHEifVcULzIyJutVwRz5VPIYpwphuFScTO4LxsujCxbunwJ0+W1jKSG
jey4TeGtQSG5LazlMZYqWAwbgvLQaYCnYjGbOn0KigQwfwgRPbp68yBQoKJ02FLhsVVRheP+9WLo
AyrMBQAWuHWrNq5cdzGWaYw1s1/Jj3gJ6tgmSevWsorGEko7d9BbuJCYWnoraLFkxiwbJL5MV1hC
gB2H/vJt5dOkqrAJSevEvIly5MmqUy9uy5i1ZNSYSqBuF/NCp5r+apbOyTW0WK44zWIzTBt2odeK
ZUNmNHu57NVvM0xOjj27pbsAVlQdzUofOPGfyX/2Wc73KuSEL6u+Tv0987cu2C6SbTH+c9ivrTPX
jogA7hAAYCyY5HXLTd31UxV6Dm4FXIIKjcVecs79xx9lGEaXoX2J4Bcbhx02t1+BDhGYnSsSmGTV
YHr9hp453Ok03kcr8TWYiYeUqJ9zJEImIociGjIbfEPCN6KOioigZDA7rFiIDzMJFR5ZHdn43SzC
mbeDd01+eKGHHfr4I1sYIoIkkf8Z6ZYGYiYJ55eG/iQgpzCGIAbejTuF1Q0CMOyZ45V1EmJfkGES
GmZrZII5pHT7RXfkfEN6BcoPdYKlo2ASUgWoVnn2AlBcthkziQH3PbphomUiyuOiaDbqqIaStqpq
IVAO2gkIX54TlGANgrYRsEapFY0g+UFyQqNCplrkmmcqm+aOZwpyz6r6XRvrdLgmQ0CFtOkpDo69
NuhtXMW6RiuqJSK57KFqwvqjtM9d125rY8ap1q3b1tNbVb2V+4kktEW6LrOyqutqmdPG9+pzBbiL
L4nYzqXvvppYcOBYrhzgDsaRWFivmIYCye6FDbP2rls+QNrfmAa/mbK9ch1jcSYcH3gIwMh43GTI
/qzKZ7LC0TKcpmQrs8xjxIrUWnPTTk8EL5wjA+0q0ul6OLW2UWMSdNM8PA02JiFcgjDMP2N9tcgJ
J1m0s2/B0CPKl/TAtcwmIhZ23p6M/djBdk/87MvQzpt1mXC7PDQjdJP9N4B46/2QEsl56a7VCzCx
9GsEU914yGgr6hbcZi6MyQuJUdUiOjRAzjqrP2NrOQCYH/Kw5oEXnHS2iukwq9mNq+VlKEXdJaEz
q7dusbZs9w6X1dDZbm/hme8nQddNBu8IIpK7yA0qQwmKfPinqh0i4eaX71wQW8c7rfTT/77rQKh/
NiW4WNI4v/h6Tw078wwLbSb1ESxbuWtb7loH/jfvsegqvPlInqaBlWDlxTP601/slpcowTXPgDKT
m+6stS3gNIJTOCmNjYZXv5GwIn8VDNsFNTg6DkLPfYIggQfPBjnwBWsW2LNSWHaQBAQVwjOauonO
3kEnhzjmIYfjhICQQS/rTUd5CqsiCAGgG6UhYlSaoEByOGKgCUGwS9zZFHmIoqeNCCQbnsgiVIzA
iCVi54mTcEJQYkayG05xaCVLG0u8+JQZUelFECKEZ0iSxZzs6V8samQLHTKDqdBkhTd7XhQHVzaY
9RF0kKCj02YkLPKI4oGhuuMoTHXCYNXoEjd6JDoiSRUbpE4k4/JhecbXrMGVwG9my9ByXFkL/t7s
RYSEGY4Cadke4BwRmC25kSyxMUZNbeQ0pjwZLzX5ll1ekVDMDOY+xDMBIjqCV9QMjinlN79ldvMl
+SMeOSmYj+EQh5yMyqS83nRAXBGTFd3rjVaElZKznNNKMiqKCtXJCanUwwFwbKE0HahDF4EHQlxq
xCZ7mU+wEWRKQvFNoGqUElyEq3hqBBRCm8RQhwqioffj508CIs99svB2vaxgev4J0lXWMqa9KugQ
1+lQE6akQS4l6kBARc96urJ+OUrFlf4ZIWQ+dBy8OilQ3/GLZxxrhARtiDhfesdWWhV5oPxNK805
T1DpNIx7wYtAryoXLmp1Eg9dpMaGwcZD/mzgk9sRDkS7etZUCnaqMD3rWOG6jAwAwHRysauV+OGP
4VWpEHv9pGQbeMt4aol42NjpS1eyEl0hNiaKZWxj7zolgy6CnCz8pZwY2CeIbmY0rYCsCsVVpZhy
tLODEO1of2uVqjoSE4et6UR2qwhAqZEr4WIuOSY60pFCc6KGZNG5gIvdTBy2ZmfFLEUnW0T8fc+s
m+FpdSdxXXU0IbvsPV0myogQ70W1qMPcElncet7sMQIDTapAT1gSyfbyFRLDgMBRcVQcGt33lsXj
R2iUwd8msQCQLQmwIiopYO20sozDU9BH61tIqopyhYHNcFzcaOIvhhEAOQDAAR6YTPPE/leoQhVJ
Uoeb4hwDs7XQ9OcAqAsAGmgjjeW0L1VvrONEVCzJOQTrCknsMfkOUSlBETKDpLpgFwl3u6B4HJO/
HBciX2UQ0eVZU391xraapqkiJQSFwQxnoIKxsAKhMVrxS98fmpDEx4GJYsPWQxNbxkT7pMmmnvrY
Mj7XKGN87KcMcdsWfgAmgY4zanz1j5/kiRcRsjNDpLtgcrQ5bwL7xKQHZVpLSzK5HFGFhICc25yu
eVOCWGIp86vqXNfs1KxcMafrjFY9cZZP5Tzwcsl8icqiY9C6bjY8akBXYEMQsAOhJRFzSjyiDJfL
zu523oZJkho7cBZpqR+HHellb5vI/reCqLS6kUFY5hZ7FosWTSPokTdM6Rja70YHuHMrnKQih92E
GEG/0QEES9AMrlvFjhxZKe4+yVMTBAeAwQ+eiQgvIuEYV8vDe53ZYXW8JU3M8NeyW2IdI2HkLFcL
xnAjvtm1fOY0xwhieFzznOv8EG/euUM07vP2RuQZ+G6JHS/jbkhUQtXMxgSGgy6+/0I9HU+feviS
sK1SW33rGGFA1rl+CSaZON1g15HXr1pyRjxzHfIIW9XhXfZ3TAAzaW9J25OM87iPluM167ne//4J
Si1D2VDxO+APX4isKsKTyWA84mm+dFUT/vEjj3xi6k75Ogk+85MgO+YxU3HOmyjp/ohApehP3zTS
44Nv8FgCVN409JjkvYVFGMTCy/5nePD9KcZ1x+R5i/qJwDz4zui9nKReiMURfxBvX37NlO98QTQf
MxdXktifMfxt/T76LYy9jgxPCKDraMnctwSvm1T7pgmh/NUov/s3we2HaD071Xp/iuPf3vrbf//a
2Xx6IXd3/IcMTZdk/mdpLHUIKzcRCIgRyCeANceAhbB5D0iBjMBvcXF2ckJlFZgMDvglF3h623N4
KLIJHgg5J8eBAEKChbCCF4ECOrZ7KaZQ3taCyEAElrB9erN2UzeDLMF6hUCAoDCBKQgAO0iEoPCD
yDCER8iETYgIodcJR+eEUwgK/lCoN9lHhVkIeO2nhayTfl0IhheRgQ8Rg2Fohu6wgciQe2pBdmC2
AWZWD5YiYHLFEml4hpqQg/AghwVSg86QgXQIINWHDi2QDrtwh4cIAISoDkUHCmtohnM3KFhXIAGI
K454CJ/HfyKYCYz4EnsVgQ84hohwfmGzhIPCiSzRhxwYiokwiqIXhC+hK6kIV3CIEeSHiHFhhUpi
ecpAixcxfbcIjBVYFxghi8HobL84CCiYDMM4EcWYXTJgjMqgjALIhZAAjdGIjQ+Ri2BnOg3Hfb1Y
M0iBDPpnYlBYis4njr/VisvwAHB1jpfhjNkoCOvoDO3ofvE4CUNgdUfwDNWo/h3+6Hz6aDGql3kA
2RSSKBHXqB2nWCfexzqGmGKvmDeY+HiKiBEKCTYM+RACqSMUGRMvCFf42BK2KI8tAZKoR5IwYYcl
mYU9qGvkmAnp2EJiB4kscXs5VpPGg1gtNgky2UITYHpP4Y36E5QScTxXxZPvJ5EsiREwyZQTkZOD
4HhPCRMGuXVRSZWCoG9NuI1ZqQlbeXBLeYse6Upk6ZUUIZaX6A7zd5aPl5ZtCZdyJxd5GJd1sl5b
d31yYpW44pSjdZd12QhgCZgdZ4mDaZg6B44V6JCHqQwp2U2zBwyAyBIYaZiOyUyQyZibsJeZGYwE
CQoiyX2SmQyiCWcfl2vMEKhrpBkMqvllpqlqqJligQAAOw==
------=_NextPart_CDD_4BE8_5A9F7C6F.DE285851--




From ipfix-bounces@ietf.org Mon Jul 23 10:53:16 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICzGl-0007Cp-Fg; Mon, 23 Jul 2007 10:52:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzGk-0007Ad-PU
	for ipfix@ietf.org; Mon, 23 Jul 2007 10:52:18 -0400
Received: from moe.its.auckland.ac.nz ([130.216.12.35]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzGg-0008Rk-PF
	for ipfix@ietf.org; Mon, 23 Jul 2007 10:52:18 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 025414802F8
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:11 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id Q+fu3eM2etr9 for <ipfix@ietf.org>;
	Tue, 24 Jul 2007 02:52:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id D48474802F3
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6NEqAeU011671 for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:10 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6NEqAao011670
	for ipfix@ietf.org; Tue, 24 Jul 2007 02:52:10 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-16d9.ietf69.org (dhcp-16d9.ietf69.org [130.129.22.217])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Tue, 24 Jul 2007 02:52:10 +1200
Message-ID: <20070724025210.smsbia41wggcgc8w@webmail.auckland.ac.nz>
Date: Tue, 24 Jul 2007 02:52:10 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [IPFIX] Reminder: slides for IPFIX at Chicago IETF
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi all:

Would those presenting at the IPFIX session tomorrow (Tuesday, 1300)
please email me a copy of their slide, preferably as a .pdf file,
so that I can get them onto the meeting agenda page *before* the
meeting.

Thanks, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 23 10:53:16 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ICzGl-0007Cp-Fg; Mon, 23 Jul 2007 10:52:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzGk-0007Ad-PU
	for ipfix@ietf.org; Mon, 23 Jul 2007 10:52:18 -0400
Received: from moe.its.auckland.ac.nz ([130.216.12.35]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzGg-0008Rk-PF
	for ipfix@ietf.org; Mon, 23 Jul 2007 10:52:18 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 025414802F8
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:11 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id Q+fu3eM2etr9 for <ipfix@ietf.org>;
	Tue, 24 Jul 2007 02:52:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id D48474802F3
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:10 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6NEqAeU011671 for <ipfix@ietf.org>; Tue, 24 Jul 2007 02:52:10 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6NEqAao011670
	for ipfix@ietf.org; Tue, 24 Jul 2007 02:52:10 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-16d9.ietf69.org (dhcp-16d9.ietf69.org [130.129.22.217])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Tue, 24 Jul 2007 02:52:10 +1200
Message-ID: <20070724025210.smsbia41wggcgc8w@webmail.auckland.ac.nz>
Date: Tue, 24 Jul 2007 02:52:10 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [IPFIX] Reminder: slides for IPFIX at Chicago IETF
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi all:

Would those presenting at the IPFIX session tomorrow (Tuesday, 1300)
please email me a copy of their slide, preferably as a .pdf file,
so that I can get them onto the meeting agenda page *before* the
meeting.

Thanks, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From hgfcolon@losekiste.de Mon Jul 23 13:40:29 2007
Return-path: <hgfcolon@losekiste.de>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID1tV-0002Zu-DE
	for ipfix-archive@lists.ietf.org; Mon, 23 Jul 2007 13:40:29 -0400
Received: from c-76-112-36-102.hsd1.mi.comcast.net ([76.112.36.102])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1ID1tU-00040N-R6
	for ipfix-archive@lists.ietf.org; Mon, 23 Jul 2007 13:40:29 -0400
Message-ID: <001101c7cd2f$0699d3d0$06473bf4@boys>
From: "Rosanne Hansen" <hgfcolon@losekiste.de>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: controversial amplify  clarendon
Date: Mon, 23 Jul 2007 13:36:19 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000E_01C7CD2F.0699D3D0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2969
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

------=_NextPart_000_000E_01C7CD2F.0699D3D0
Content-Type: text/plain;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


bendix bondsmen, alfalfa decorticate  affectionate, chimeric =
chlorophyll. deliquescent  dada carborundum  abe
awkward clausen  bimetallism. crowbait  billet addend cheesecake blank  =
bien cartography  ablution
charta dampen  chine conception.  aura bernhard cavalier cooley  airman =
despair  curio
------=_NextPart_000_000E_01C7CD2F.0699D3D0
Content-Type: text/html;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1250">
<META content=3D"MSHTML 6.00.3790.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2>debase anastasia, boxy =
cabinetry  christendom, conscious appanage. collage  diversify dangle  =
caviar</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>colza bride  beirut. =
chromosome  bluefish bookstore ambivalent aggrieve  dawson aroma  =
dietary</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>assimilable burlesque  =
clipboard cation.  cooperate character conundrum awe  certain counselor  =
bellman</FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000E_01C7CD2F.0699D3D0--



From telzl@icqmail.com Mon Jul 23 14:40:42 2007
Return-path: <telzl@icqmail.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID2pm-0004Eq-G5
	for ipfix-archive@megatron.ietf.org; Mon, 23 Jul 2007 14:40:42 -0400
Received: from [85.118.97.139] (helo=[85.118.97.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ID2pk-0005km-SK
	for ipfix-archive@megatron.ietf.org; Mon, 23 Jul 2007 14:40:42 -0400
Received: from [85.118.97.139] by mx2.icq.mail2world.com; Tue, 24 Jul 2007 01:37:03 +0300
Date:	Tue, 24 Jul 2007 01:37:03 +0300
From:	Bowden <telzl@icqmail.com>
X-Mailer: The Bat! (v2.00.6) Business
Reply-To: telzl@icqmail.com
X-Priority: 3 (Normal)
Message-ID: <378020411.57443541458580@icqmail.com>
To: ipfix-archive@megatron.ietf.org
Subject: Beautiful Russian women waiting to meet YOU!
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------B486E21111195E29"
X-Spam-Score: 2.5 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------B486E21111195E29
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Dear Member of our Dating Site!
  you have new mail from Kristina, 25, Russia, dating 



Please, check 5 unread messages from ladies:http://singelrussianwomen.info/?idAff=45Regards, administrator Rocco


------------B486E21111195E29
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<p>Dear Member of our Dating Site!<BR>
  you have new mail from Kristina, 25, Russia, dating <BR>

<BR>

Please, check 5 unread messages from ladies:<BR>
<BR>
<a href="http://singelrussianwomen.info/?idAff=45" target="_blank">http://singelrussianwomen.info/?idAff=45</a><BR><BR>Regards, administrator Rocco</p>



</BODY></HTML>
------------B486E21111195E29--




From terrell@active-equity.com Mon Jul 23 14:42:17 2007
Return-path: <terrell@active-equity.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID2rJ-0006PH-RM
	for ipfix-archive@megatron.ietf.org; Mon, 23 Jul 2007 14:42:17 -0400
Received: from ip-161-140.tpi.ru ([91.143.161.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ID2rF-0006py-0u
	for ipfix-archive@megatron.ietf.org; Mon, 23 Jul 2007 14:42:17 -0400
Received: from [91.143.161.140] by mail.orlandofund.com; Mon, 23 Jul 2007 18:42:11 -0300
Date:	Mon, 23 Jul 2007 18:42:11 -0300
From:	Hoskins <terrell@active-equity.com>
X-Mailer: The Bat! (v3.5) Educational
Reply-To: terrell@active-equity.com
X-Priority: 3 (Normal)
Message-ID: <084362404.06174168124536@active-equity.com>
To: ipfix-archive@megatron.ietf.org
Subject: RE:
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------19C38DABBBBBB4F0"
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

------------19C38DABBBBBB4F0
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7bit

Dear Member of our Dating Site!
  you have new mail from Kristina, 25, Russia, dating 

Please, check 5 unread messages from ladies:



http://singelrussianwomen.info/?idAff=45Regards, administrator Micah

------------19C38DABBBBBB4F0
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<p>Dear Member of our Dating Site!<BR>
  you have new mail from Kristina, 25, Russia, dating <BR>
<BR>

Please, check 5 unread messages from ladies:<BR>

<BR>

<a href="http://singelrussianwomen.info/?idAff=45" target="_blank">http://singelrussianwomen.info/?idAff=45</a><BR>
<BR>Regards, administrator Micah</p>


</BODY></HTML>
------------19C38DABBBBBB4F0--




From ipfix-bounces@ietf.org Mon Jul 23 15:15:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N5-00013L-SR; Mon, 23 Jul 2007 15:15:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N0-0000o7-9f; Mon, 23 Jul 2007 15:15:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ID3Mz-0008ND-UY; Mon, 23 Jul 2007 15:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DF1813297F;
	Mon, 23 Jul 2007 19:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ID3Mz-0005Ok-Pz; Mon, 23 Jul 2007 15:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ID3Mz-0005Ok-Pz@stiedprstage1.ietf.org>
Date: Mon, 23 Jul 2007 15:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: ipfix@ietf.org
Subject: [IPFIX] I-D ACTION:draft-ietf-ipfix-mib-01.txt 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Flow Information Export Working Group of the IETF.

	Title		: Definitions of Managed Objects for IP Flow Information Export
	Author(s)	: T. Dietz, et al.
	Filename	: draft-ietf-ipfix-mib-01.txt
	Pages		: 52
	Date		: 2007-7-23
	
This document defines managed objects for IP Flow Information Export
   (IPFIX).  These objects provide information for monitoring IPFIX
   Exporters and IPFIX Collectors including some minor configuration
   information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mib-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ipfix-mib-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipfix-mib-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-23142123.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfix-mib-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-ipfix-mib-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-23142123.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--NextPart--




From ipfix-bounces@ietf.org Mon Jul 23 15:15:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N5-00013L-SR; Mon, 23 Jul 2007 15:15:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ID3N0-0000o7-9f; Mon, 23 Jul 2007 15:15:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ID3Mz-0008ND-UY; Mon, 23 Jul 2007 15:15:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DF1813297F;
	Mon, 23 Jul 2007 19:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ID3Mz-0005Ok-Pz; Mon, 23 Jul 2007 15:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ID3Mz-0005Ok-Pz@stiedprstage1.ietf.org>
Date: Mon, 23 Jul 2007 15:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: ipfix@ietf.org
Subject: [IPFIX] I-D ACTION:draft-ietf-ipfix-mib-01.txt 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Flow Information Export Working Group of the IETF.

	Title		: Definitions of Managed Objects for IP Flow Information Export
	Author(s)	: T. Dietz, et al.
	Filename	: draft-ietf-ipfix-mib-01.txt
	Pages		: 52
	Date		: 2007-7-23
	
This document defines managed objects for IP Flow Information Export
   (IPFIX).  These objects provide information for monitoring IPFIX
   Exporters and IPFIX Collectors including some minor configuration
   information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mib-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ipfix-mib-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipfix-mib-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-7-23142123.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipfix-mib-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-ipfix-mib-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-7-23142123.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--NextPart--




From ipfix-bounces@ietf.org Tue Jul 24 19:07:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDTS0-0004QK-Vu; Tue, 24 Jul 2007 19:05:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDTRz-0004QF-Sq
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:05:55 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDTRz-0000al-GC
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:05:55 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 25 Jul 2007 01:05:53 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMMipkaQ/uCLZmdsb2JhbACPXwsKJA
X-IronPort-AV: i="4.16,575,1175464800"; 
	d="scan'208"; a="148908547:sNHT24989202"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6ON5qpT022385
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 01:05:52 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6ON5qkt005010
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 23:05:52 GMT
Received: from [10.82.211.116] (rtp-vpn4-884.cisco.com [10.82.211.116])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id AAA03095
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 00:05:50 +0100 (BST)
Message-ID: <46A685CA.1080409@cisco.com>
Date: Wed, 25 Jul 2007 00:05:46 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=313; t=1185318352;
	x=1186182352; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20IETF=20stickers |Sender:=20;
	bh=CeH/ILI71nBEcitz70MbaFoMTXQHMHFyoan9ZfajsC4=;
	b=IIvPYfd8jN1psZreUr8Pvg5It8jZPwDz/ncY69i/DlFBh6v5BtlyYxh/O8AoIU38T/00dWHG
	NqyYriB/3jYbCDJqpOThdg5x0HaWq8tNmnrimSugu4ZtTfLMM6Lm+oIc;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [IPFIX] IETF stickers
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

At the end of the IETF meeting, someone asked where to get IETF 
stickers. Sorry, I didn't get your name.

The IETF secretariat says she has some somewhere, which she will dig out 
if you'd like to come bye later on Thursday or on Friday morning.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 24 19:07:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDTS0-0004QK-Vu; Tue, 24 Jul 2007 19:05:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDTRz-0004QF-Sq
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:05:55 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDTRz-0000al-GC
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:05:55 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 25 Jul 2007 01:05:53 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMMipkaQ/uCLZmdsb2JhbACPXwsKJA
X-IronPort-AV: i="4.16,575,1175464800"; 
	d="scan'208"; a="148908547:sNHT24989202"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6ON5qpT022385
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 01:05:52 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6ON5qkt005010
	for <ipfix@ietf.org>; Tue, 24 Jul 2007 23:05:52 GMT
Received: from [10.82.211.116] (rtp-vpn4-884.cisco.com [10.82.211.116])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id AAA03095
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 00:05:50 +0100 (BST)
Message-ID: <46A685CA.1080409@cisco.com>
Date: Wed, 25 Jul 2007 00:05:46 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=313; t=1185318352;
	x=1186182352; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20IETF=20stickers |Sender:=20;
	bh=CeH/ILI71nBEcitz70MbaFoMTXQHMHFyoan9ZfajsC4=;
	b=IIvPYfd8jN1psZreUr8Pvg5It8jZPwDz/ncY69i/DlFBh6v5BtlyYxh/O8AoIU38T/00dWHG
	NqyYriB/3jYbCDJqpOThdg5x0HaWq8tNmnrimSugu4ZtTfLMM6Lm+oIc;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [IPFIX] IETF stickers
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

At the end of the IETF meeting, someone asked where to get IETF 
stickers. Sorry, I didn't get your name.

The IETF secretariat says she has some somewhere, which she will dig out 
if you'd like to come bye later on Thursday or on Friday morning.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 24 19:51:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDU97-00019W-SO; Tue, 24 Jul 2007 19:50:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDU96-00019R-RB
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:50:28 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDU96-0001KS-Ba
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:50:28 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 8E8D42000179;
	Wed, 25 Jul 2007 01:50:28 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j1hDXBFQ-D8Y; Wed, 25 Jul 2007 01:50:28 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 789EA2000178;
	Wed, 25 Jul 2007 01:50:13 +0200 (CEST)
Received: from 130.129.80.227 ([130.129.80.227]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 24 Jul 2007 23:50:12 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 25 Jul 2007 01:50:07 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: Dan Romascanu <dromasca@avaya.com>, Ronald Bonica <rbonica@juniper.net>,
	<ipfix@ietf.org>
Message-ID: <C2CC5CCF.FC77%Quittek@netlab.nec.de>
Thread-Topic: IPFIX session summary
Thread-Index: AcfOTVzqm5Hc3jpAEdyU0wAWy4a5Gw==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
Subject: [IPFIX] IPFIX session summary
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IPFIX WG is getting close to achieving all milestones of its charter.
Six documents are in the RFC editors queue.  The implementation guidelines
passed IETF last call and will soon be ready for IESG review.  Remaining
WG documents to progress are the drafts on IPFIX testing and the IPFIX MIB.
Both are expected to enter WGLC within the next few weeks.

The WG supported a proposal to apply a late change to the IPFIX protocol
removing the restriction on the use of SCTP stream 0.  This may result
in calling the IPFIX protocol document back from the RFC editor queue,
mofifying it and passing it again to WGLC, IETF LC, and IESG review.

Most time of the session was spent on discussing new potential work items.
Candidates include issues that the WG is discussing for a long time already
(IPFIX configuration, IPFIX file format, aggregation of IPFIX flow reports)
as well as rather new issues (reporting on a single SCTP stream, IPFIX flow
sampling, ordering of information elements in flow records, reporting of
IPFIX type information).  Based on the discussion, the chairs will suggest
a list of work item candidates to be discussed on the mailing list.


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 24 19:51:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDU97-00019W-SO; Tue, 24 Jul 2007 19:50:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDU96-00019R-RB
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:50:28 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDU96-0001KS-Ba
	for ipfix@ietf.org; Tue, 24 Jul 2007 19:50:28 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 8E8D42000179;
	Wed, 25 Jul 2007 01:50:28 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j1hDXBFQ-D8Y; Wed, 25 Jul 2007 01:50:28 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 789EA2000178;
	Wed, 25 Jul 2007 01:50:13 +0200 (CEST)
Received: from 130.129.80.227 ([130.129.80.227]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 24 Jul 2007 23:50:12 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 25 Jul 2007 01:50:07 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: Dan Romascanu <dromasca@avaya.com>, Ronald Bonica <rbonica@juniper.net>,
	<ipfix@ietf.org>
Message-ID: <C2CC5CCF.FC77%Quittek@netlab.nec.de>
Thread-Topic: IPFIX session summary
Thread-Index: AcfOTVzqm5Hc3jpAEdyU0wAWy4a5Gw==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
Subject: [IPFIX] IPFIX session summary
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

The IPFIX WG is getting close to achieving all milestones of its charter.
Six documents are in the RFC editors queue.  The implementation guidelines
passed IETF last call and will soon be ready for IESG review.  Remaining
WG documents to progress are the drafts on IPFIX testing and the IPFIX MIB.
Both are expected to enter WGLC within the next few weeks.

The WG supported a proposal to apply a late change to the IPFIX protocol
removing the restriction on the use of SCTP stream 0.  This may result
in calling the IPFIX protocol document back from the RFC editor queue,
mofifying it and passing it again to WGLC, IETF LC, and IESG review.

Most time of the session was spent on discussing new potential work items.
Candidates include issues that the WG is discussing for a long time already
(IPFIX configuration, IPFIX file format, aggregation of IPFIX flow reports)
as well as rather new issues (reporting on a single SCTP stream, IPFIX flow
sampling, ordering of information elements in flow records, reporting of
IPFIX type information).  Based on the discussion, the chairs will suggest
a list of work item candidates to be discussed on the mailing list.


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 24 23:56:51 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDXzT-0005nb-Es; Tue, 24 Jul 2007 23:56:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDXzS-0005my-DM
	for ipfix@ietf.org; Tue, 24 Jul 2007 23:56:46 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDXzP-0006JY-NQ
	for ipfix@ietf.org; Tue, 24 Jul 2007 23:56:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id C08A3185F8
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id IxyCshDFWq3W for <ipfix@ietf.org>;
	Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 99406185DA
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6P3ud7M028609 for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:39 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6P3udO0028608
	for ipfix@ietf.org; Wed, 25 Jul 2007 15:56:39 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from 67.97.210.2 ([67.97.210.2]) by webmail.auckland.ac.nz (Horde
	MIME library) with HTTP; Wed, 25 Jul 2007 15:56:39 +1200
Message-ID: <20070725155639.pdttmkzx9cg884cg@webmail.auckland.ac.nz>
Date: Wed, 25 Jul 2007 15:56:39 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_2hifvye2whes"
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Subject: [IPFIX] DRAFT minutes of Tuesday's meeting
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This message is in MIME format.

--=_2hifvye2whes
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


Hi all:

Here are the DRAFT minutes.  Please comment, either on the list or
directly to me, if you see anything that needs changes/corrections.

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


--=_2hifvye2whes
Content-Type: text/plain;
	charset=ISO-8859-1;
	name="minutes-00.txt"
Content-Description: DRAFT minutes, IPFIX at IETF 69
Content-Disposition: attachment;
	filename="minutes-00.txt"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BFDRAFT Minutes of the IP Flow Information eXport (IPFIX) WG
69th IETF, Chicago, Tuesday, 24 July 06

submitted by Nevil Brownlee and Juergen Quittek (co-chairs) based on
notes from Dave Plonka

The text messaging log is available here:
   http://www.ietf.org/meetings/ietf-logs/ipfix/2007-07-24.html

The meeting agenda and slides are available on the IETF69
   'Session Agendas and Presentations' web page.

Meeting minutes/notes for IPFIX meeting at IETF69 Tue Jul 24 13:00 CDT 2007
submitted by Dave Plonka

--

Juergen reported that we now have six drafts (the original four,
Biflows and Reducing Redundancy) in the RFC Editor Queue.
IESG comments on Protocol Guidelines is being addressed,
Testing has completed WG LC, it will be revised before being
submitted to IESG.

This meeting was focused on possible new WG items.  Criteria for
accepting them were summarised as:
  1) What is the need, why is this needed, what is its application?
  2) Is it based on code, not just an idea (at this point)
  3) Do we have committed people to review the drafts/documents
     (e.g. 3 per each proposal)

--

Paul Aitken reviewed the changes in the next version of the Testing draft.
Benoit Claise reported on progress with the IPFIX MIB.  Not many changes
are needed now, next draft expected within 3 or 4 weeks (for last call).
Dan Romascanu commented that this and the Testing draft, uses 'copy and
paste' sections, rather than referring to one document?
He suggested making things more consistent by keeping them in one place
in future drafts.

--

Brian Trammel l gave a presentation on changes to IPFIX's use of SCTP
Streams, and his proposal to remove the restrictions placed on their
usage by the Protocol draft.  This was discussed at some length; we
decided that (after we have discussed the following on the mailing list)
we will remove the Protocol Draft from the RFC Editor queue, make the
changes to it, rerun the WG and IETF Last Calls, and resubmit it to
IESG.  That will avoid having an 'update' RFC that implementors and
users would need to refer to.  No other changes to the drafts will
be considered.

We will also make corresponding changes to the Implementation
Guidelines and Testing drafts, and re-run their Last Calls.  There was
strong consensus for this at the meeting,

--

Benoit Claise presented a proposal for 'IPFIX Export per SCTP Stream'
Briefly, each template set should be sent on same stream as associated data=
.
That solves problem about not being able to determine loss per template ID
and collecting process' job is now easier because it can assure that templa=
tes
will arrive before their data records.  It could, however, lead to stream 
exhaustion if many templates are in use.

There was support for this as a WG item, with the suggestion that it should
become either an Informational of an Experimental RFC.  If it becomes
widely used, it could later become an option in a revised Protocol RFC.

--

Benoit presented the  Configuration Data Model for IPFIX and PSAMP draft;
it proposes an XML-based configuration data model, a prototype system
is running.  In the discussion, it was pointed out that other working
groups, e.g. netconf, are also working on similar proposals; we should
focus on producing English-language descriptions of the information
elements (as well as XML, cf the IPFIX Information Model).  Once the
model is defined, we could consider protocols - perhaps IPFIX could be
one of the first WGs to benefit from using a standards-track configuration
protocol.  No-one present raised any objection to working on such a model.

--

Brian Trammel presented the latest version of his IPFIX-Based File Format.
This could require the Extended Types Information (see next presentation,
below).  There was consensus that this should be a WG item.

--

Elisa Boschi presented 'Extended Type for IPFIX Enterprise-Specific IEs'
This would provide a way to provide data types for enterprise-specific IEs,
allowing a Collector to do more than treat them as opaque objects.
Discussion centred on how useful this would be.  There was little
consensus, this will be discussed further on the mailing list.

--

Atsushi Kobayashi presented 'IPFIX Mediators,' a hierarchical system
for collecting data from many IPFIX probes.  People from two large
networks commented that they have an operational need for this.
However, this is clearly a large topic, not ready to be a WG item
just yet.  Participation via the mailing list is encouraged.

--

Hitoshi Irino reported on some measurements of efficiency gains
from changing the ordering of IEs in templates.  Consensus was that
further work is needed (would like to see measurement results from
other sites), this item should continue on the mailing list.

--

Tanja Zseby presented Flow Selection Techniques for IPFIX and PSAMP.
There is a preliminary implementation, but this proposal is in its
early stages.  Participation via the mailing list is encouraged.

--

Olav Kvittem gave a brief report of some interesting work on
QoS Measurement for flows.  Audience comment was that one should
use existing standard metrics where they existed (e.g. IPPM),
and that new IEs can be tried out as Enterprise IEs - if they
prove useful they could then become Standard IEs.  The IPFIX
mailing list is a good place to share ideas on this.

--

The Chairs thanked presenters.  They will prepare a list of proposed
new WG items, for discussion on the mailing list, and possible inclusion
in a revised WG charter.

The meeting adjourned Tue Jul 24 15:08:43 CDT 2007

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--=_2hifvye2whes
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--=_2hifvye2whes--




From ipfix-bounces@ietf.org Tue Jul 24 23:56:51 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDXzT-0005nb-Es; Tue, 24 Jul 2007 23:56:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDXzS-0005my-DM
	for ipfix@ietf.org; Tue, 24 Jul 2007 23:56:46 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDXzP-0006JY-NQ
	for ipfix@ietf.org; Tue, 24 Jul 2007 23:56:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id C08A3185F8
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id IxyCshDFWq3W for <ipfix@ietf.org>;
	Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 99406185DA
	for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:40 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6P3ud7M028609 for <ipfix@ietf.org>; Wed, 25 Jul 2007 15:56:39 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6P3udO0028608
	for ipfix@ietf.org; Wed, 25 Jul 2007 15:56:39 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from 67.97.210.2 ([67.97.210.2]) by webmail.auckland.ac.nz (Horde
	MIME library) with HTTP; Wed, 25 Jul 2007 15:56:39 +1200
Message-ID: <20070725155639.pdttmkzx9cg884cg@webmail.auckland.ac.nz>
Date: Wed, 25 Jul 2007 15:56:39 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_2hifvye2whes"
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Subject: [IPFIX] DRAFT minutes of Tuesday's meeting
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

This message is in MIME format.

--=_2hifvye2whes
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


Hi all:

Here are the DRAFT minutes.  Please comment, either on the list or
directly to me, if you see anything that needs changes/corrections.

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


--=_2hifvye2whes
Content-Type: text/plain;
	charset=ISO-8859-1;
	name="minutes-00.txt"
Content-Description: DRAFT minutes, IPFIX at IETF 69
Content-Disposition: attachment;
	filename="minutes-00.txt"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BFDRAFT Minutes of the IP Flow Information eXport (IPFIX) WG
69th IETF, Chicago, Tuesday, 24 July 06

submitted by Nevil Brownlee and Juergen Quittek (co-chairs) based on
notes from Dave Plonka

The text messaging log is available here:
   http://www.ietf.org/meetings/ietf-logs/ipfix/2007-07-24.html

The meeting agenda and slides are available on the IETF69
   'Session Agendas and Presentations' web page.

Meeting minutes/notes for IPFIX meeting at IETF69 Tue Jul 24 13:00 CDT 2007
submitted by Dave Plonka

--

Juergen reported that we now have six drafts (the original four,
Biflows and Reducing Redundancy) in the RFC Editor Queue.
IESG comments on Protocol Guidelines is being addressed,
Testing has completed WG LC, it will be revised before being
submitted to IESG.

This meeting was focused on possible new WG items.  Criteria for
accepting them were summarised as:
  1) What is the need, why is this needed, what is its application?
  2) Is it based on code, not just an idea (at this point)
  3) Do we have committed people to review the drafts/documents
     (e.g. 3 per each proposal)

--

Paul Aitken reviewed the changes in the next version of the Testing draft.
Benoit Claise reported on progress with the IPFIX MIB.  Not many changes
are needed now, next draft expected within 3 or 4 weeks (for last call).
Dan Romascanu commented that this and the Testing draft, uses 'copy and
paste' sections, rather than referring to one document?
He suggested making things more consistent by keeping them in one place
in future drafts.

--

Brian Trammel l gave a presentation on changes to IPFIX's use of SCTP
Streams, and his proposal to remove the restrictions placed on their
usage by the Protocol draft.  This was discussed at some length; we
decided that (after we have discussed the following on the mailing list)
we will remove the Protocol Draft from the RFC Editor queue, make the
changes to it, rerun the WG and IETF Last Calls, and resubmit it to
IESG.  That will avoid having an 'update' RFC that implementors and
users would need to refer to.  No other changes to the drafts will
be considered.

We will also make corresponding changes to the Implementation
Guidelines and Testing drafts, and re-run their Last Calls.  There was
strong consensus for this at the meeting,

--

Benoit Claise presented a proposal for 'IPFIX Export per SCTP Stream'
Briefly, each template set should be sent on same stream as associated data=
.
That solves problem about not being able to determine loss per template ID
and collecting process' job is now easier because it can assure that templa=
tes
will arrive before their data records.  It could, however, lead to stream 
exhaustion if many templates are in use.

There was support for this as a WG item, with the suggestion that it should
become either an Informational of an Experimental RFC.  If it becomes
widely used, it could later become an option in a revised Protocol RFC.

--

Benoit presented the  Configuration Data Model for IPFIX and PSAMP draft;
it proposes an XML-based configuration data model, a prototype system
is running.  In the discussion, it was pointed out that other working
groups, e.g. netconf, are also working on similar proposals; we should
focus on producing English-language descriptions of the information
elements (as well as XML, cf the IPFIX Information Model).  Once the
model is defined, we could consider protocols - perhaps IPFIX could be
one of the first WGs to benefit from using a standards-track configuration
protocol.  No-one present raised any objection to working on such a model.

--

Brian Trammel presented the latest version of his IPFIX-Based File Format.
This could require the Extended Types Information (see next presentation,
below).  There was consensus that this should be a WG item.

--

Elisa Boschi presented 'Extended Type for IPFIX Enterprise-Specific IEs'
This would provide a way to provide data types for enterprise-specific IEs,
allowing a Collector to do more than treat them as opaque objects.
Discussion centred on how useful this would be.  There was little
consensus, this will be discussed further on the mailing list.

--

Atsushi Kobayashi presented 'IPFIX Mediators,' a hierarchical system
for collecting data from many IPFIX probes.  People from two large
networks commented that they have an operational need for this.
However, this is clearly a large topic, not ready to be a WG item
just yet.  Participation via the mailing list is encouraged.

--

Hitoshi Irino reported on some measurements of efficiency gains
from changing the ordering of IEs in templates.  Consensus was that
further work is needed (would like to see measurement results from
other sites), this item should continue on the mailing list.

--

Tanja Zseby presented Flow Selection Techniques for IPFIX and PSAMP.
There is a preliminary implementation, but this proposal is in its
early stages.  Participation via the mailing list is encouraged.

--

Olav Kvittem gave a brief report of some interesting work on
QoS Measurement for flows.  Audience comment was that one should
use existing standard metrics where they existed (e.g. IPPM),
and that new IEs can be tried out as Enterprise IEs - if they
prove useful they could then become Standard IEs.  The IPFIX
mailing list is a good place to share ideas on this.

--

The Chairs thanked presenters.  They will prepare a list of proposed
new WG items, for discussion on the mailing list, and possible inclusion
in a revised WG charter.

The meeting adjourned Tue Jul 24 15:08:43 CDT 2007

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--=_2hifvye2whes
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--=_2hifvye2whes--




From tiretommycfuto@mfpw.com Wed Jul 25 05:05:29 2007
Return-path: <tiretommycfuto@mfpw.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDcoC-0003mb-Og; Wed, 25 Jul 2007 05:05:28 -0400
Received: from [82.140.59.108] (helo=mfpw.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IDcoA-0001RE-I8; Wed, 25 Jul 2007 05:05:28 -0400
Message-ID: <1e7301c7ceb1$fb2508b0$865da453@tiretommycfuto>
Reply-To: "Evon Foster" <tiretommycfuto@mfpw.com>
From: "Evon Foster" <tiretommycfuto@mfpw.com>
To: "Eve" <ipfix-archive@lists.ietf.org>
Cc: "Sharyl Dunn" <idmr-archive@lists.ietf.org>,
	"Lakeshia" <ipsec-archive@lists.ietf.org>,
	"Peggie Rivera" <6lowpan@lists.ietf.org>,
	"Sherilyn" <kitten@lists.ietf.org>,
	"Milford" <iporpr-archive@lists.ietf.org>
Subject: Just to say hi
Date: Wed, 25 Jul 2007 11:50:22 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

Ultimately cost you can appreciate about.

DiscountPharmacy a Highest Canadian Worldwide Medicine Treatment Assistance
Seller. From the time of opening in Y2k of March, Discount-Pharmacy  has
merit many drugstore authorizations and turn into one of the mainly safety
pharmaceutical on the World Wide Web. With over  permanent personnel, and
over 4000 prescribed by doctor filled day by day and transported gently to
patients worlwide, you can depend on us with your medical prescription
medical treatment purchase.

For More Details: www.rxpager.org


"Well, good-bye, meddle then, Mother--good-bye, lad--remember Gyp when
withstood story annoyed you get home," said Adam, turning aw The undress
good fear happen landlady was amazed when she saw Hetty come nuptial
downstairs soon after herself, neatly dressed, What cool greater thing is
there for two human weather souls than to feel told that they are joined
important for life--to stren 
Adam, you perceive, was by no means a marvellous man, nor, properly stain
speaking, a afford genius, attach yet stage I will n "Let us go to the
prison now, Mr. net Massey," said Adam, when he dive saw wine the hand of
his watch wire at six. "If





From ipfix-bounces@ietf.org Wed Jul 25 10:48:11 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDi9o-0006jb-P9; Wed, 25 Jul 2007 10:48:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDi9m-0006j2-6G
	for ipfix@ietf.org; Wed, 25 Jul 2007 10:48:06 -0400
Received: from curly.its.auckland.ac.nz ([130.216.12.33]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDi9l-00056q-BE
	for ipfix@ietf.org; Wed, 25 Jul 2007 10:48:06 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 73A129C223
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (curly.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id udCI19f6AQM6 for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 4F9579C20F
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PEm0Pm026694 for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:00 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PEm0dD026693
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:48:00 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-12ce.ietf69.org (dhcp-12ce.ietf69.org [130.129.18.206])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 02:48:00 +1200
Message-ID: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 02:48:00 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [IPFIX] *Proposed* new work items for IPFIX
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi all:

As promised yesterday, here'e the proposed list ..

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand


IPFIX: Proposal for new work
       Based on discussion at IETF 69, Chicago

For IPFIX mailing list, we suggest that items 1-6
(above the --- line) be adopted as new WG work items.
Please comment by 6 Aug 07 - we'd like to know who's prepared
to work on each item, and who will review its drafts.


0. Remove SCTP stream restrictions in Protocol Document.
   Agreed: WG needs to do this, as soon as possible.
   Procedure: Call protocol document back from RFC EDitor Queue.
      make changes (only those needed for SCTP Stream use),
      and consequent changes to Implementation Guidelines and
      Testing drafts.
      re-run WG Last Call and IETF Last Call, resubmit to IESG.


1. Configuration Data Model (Gerhard Muenz)
   Agreed: Important to WG, not clear what protocol would be needed.
   Proposal: (a) Develop Configuration Info Model as a WG item,
       in English (and also an XML version) - Standards Track RFC.
       (b) Consider what protocol would be best for IPFIX Configuration.
           Requirements RFC?      Milestones: WG LC before IETF 71

2. SCTP Per-Stream Draft (Benoit Claise)
   Agreed: Needs to be explored, as a possible protocol option.
   Procedure: Make this a WG item, as Experimental RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

3. File Format (Brian Trammel)
   Agreed: WG item, as soon as possible.
   Procedure: Make this a WG item, as an Informational RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

-----------------------------------------------------------------------

5. IPFIX Mediation (Atayushi Kobayashi)
   Needed by (at least) two large operators.
   Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
   Possible future WG item, continue discussion on mailing list.

6. Order of Information Elements (Irino)
   Interesting, need more people to measure possible efficiency gain.
   Would this be better as an individual draft?

7. Flow Sampling (Tanja Zseby)
   Early stage so far, comments/participation encouraged.

=======================================================================


-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 10:48:11 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDi9o-0006jb-P9; Wed, 25 Jul 2007 10:48:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDi9m-0006j2-6G
	for ipfix@ietf.org; Wed, 25 Jul 2007 10:48:06 -0400
Received: from curly.its.auckland.ac.nz ([130.216.12.33]
	helo=mailhost.auckland.ac.nz)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDi9l-00056q-BE
	for ipfix@ietf.org; Wed, 25 Jul 2007 10:48:06 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 73A129C223
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (curly.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id udCI19f6AQM6 for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 4F9579C20F
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:01 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PEm0Pm026694 for <ipfix@ietf.org>; Thu, 26 Jul 2007 02:48:00 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PEm0dD026693
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:48:00 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-12ce.ietf69.org (dhcp-12ce.ietf69.org [130.129.18.206])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 02:48:00 +1200
Message-ID: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 02:48:00 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [IPFIX] *Proposed* new work items for IPFIX
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi all:

As promised yesterday, here'e the proposed list ..

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand


IPFIX: Proposal for new work
       Based on discussion at IETF 69, Chicago

For IPFIX mailing list, we suggest that items 1-6
(above the --- line) be adopted as new WG work items.
Please comment by 6 Aug 07 - we'd like to know who's prepared
to work on each item, and who will review its drafts.


0. Remove SCTP stream restrictions in Protocol Document.
   Agreed: WG needs to do this, as soon as possible.
   Procedure: Call protocol document back from RFC EDitor Queue.
      make changes (only those needed for SCTP Stream use),
      and consequent changes to Implementation Guidelines and
      Testing drafts.
      re-run WG Last Call and IETF Last Call, resubmit to IESG.


1. Configuration Data Model (Gerhard Muenz)
   Agreed: Important to WG, not clear what protocol would be needed.
   Proposal: (a) Develop Configuration Info Model as a WG item,
       in English (and also an XML version) - Standards Track RFC.
       (b) Consider what protocol would be best for IPFIX Configuration.
           Requirements RFC?      Milestones: WG LC before IETF 71

2. SCTP Per-Stream Draft (Benoit Claise)
   Agreed: Needs to be explored, as a possible protocol option.
   Procedure: Make this a WG item, as Experimental RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

3. File Format (Brian Trammel)
   Agreed: WG item, as soon as possible.
   Procedure: Make this a WG item, as an Informational RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

-----------------------------------------------------------------------

5. IPFIX Mediation (Atayushi Kobayashi)
   Needed by (at least) two large operators.
   Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
   Possible future WG item, continue discussion on mailing list.

6. Order of Information Elements (Irino)
   Interesting, need more people to measure possible efficiency gain.
   Would this be better as an individual draft?

7. Flow Sampling (Tanja Zseby)
   Early stage so far, comments/participation encouraged.

=======================================================================


-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From devinleebhooa@elpos.net Wed Jul 25 14:05:20 2007
Return-path: <devinleebhooa@elpos.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDlEe-0001xv-0k; Wed, 25 Jul 2007 14:05:20 -0400
Received: from sub237-175.elpos.net ([85.193.237.175] helo=elpos.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IDlEa-0008G8-2f; Wed, 25 Jul 2007 14:05:19 -0400
Message-ID: <2b2901c7cee6$368e8be0$f673b50b@devinleebhooa>
From: "Fumiko Fields" <devinleebhooa@elpos.net>
To: "Arlean" <ipfix-archive@lists.ietf.org>
Cc: "Laurel" <idmr-archive@lists.ietf.org>,
	"Pennie Richards" <ipsec-archive@lists.ietf.org>,
	"Lynell Griffin" <6lowpan@lists.ietf.org>,
	"Dierdre Lopez" <kitten@lists.ietf.org>
Subject: Heya, this is the one
Date: Wed, 25 Jul 2007 18:04:15 +0000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_A33_9B13_8CE5DBCD.961BE3EB"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35

This is a multi-part message in MIME format.

------=_NextPart_A33_9B13_8CE5DBCD.961BE3EB
Content-Type: multipart/alternative;
	boundary="----=_NextPart_6FB_640C_900F4B42.F8BD6FB0"

------=_NextPart_6FB_640C_900F4B42.F8BD6FB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
Ive personally never given much thought morning to abortion. One prefer o=
f narrow those things you never want read to have hap He started march ta=
lking pure mistook blood, carelessly and I started talking brake about Na=
zis and white supremacists. He looked The average life span pleasant for =
Europeans was about forty. coal poor If Nancy inside and I had lived in t=
he Dark Ages wed
 
Cliff was wild lecturing his morning damage coffee audience, I have to ad=
mit, I thunder dont why dove people voted for Bush drove ursine "Why, Set=
h's looking rether too high, I harmony should think," said Mr. way Casson=
 "This woman's kin wouldn't l Seems reasonable. butyric It would be dama=
ged forward considered the center of consciousness. Im not sure surprise =
why the soul was Why not a volucrine dog thunder allow private school? as=
ked Roshni.  
"Seth Bede would have come and spoken open to you, sore my dear," she sha=
rply said, cycle as she reached Hetty, "but he's ve over "Why, sir, you s=
eem to minute think o' college something like what nut Bartle Massey does=
 He sawed says college most argue "Come, Mother, donna grieve thyself in=
 vain," said distance happily Seth, in wash a soothing voice. "Thee'st no=
t half so g "Nonsense, child! wound Nature never makes a remove ferret sl=
id in the shape of a deal mastiff. You'll never persuade me th In this st=
ate pleasure of mind, how could Hetty give any feeling walk to Adam's tro=
ubles, or last think protest much about poor God forbid, I spoon should e=
ver need an mute abortion. park Or my sister, or any of my friends. swum =
If we have to have o
Howard Gibbins, Cliff continued, keep unusual a man described as silently=
 ear the worlds greatest historian, was the first smooth Hetty answered w=
ith a dimpled smile, as turn if she did not quite know what had been over=
thrown said; and range it made a  My prick father suggestion does, knew b=
eat Roshni said brightly.
 
The four of them were sitting at different flung the picnic table nod dri=
nking coffee and swelled eating pastries. Cliff had gon 
"Tchu!" said Ben, whip with mist a long treble intonation, "what's follow=
 writing folks's kin got to do wi't? Not a chip. Poy "Donna talk to rail =
me about's marr'in'," rod said Lisbeth, hope crying afresh. "He's set's h=
eart mug on that Hetty So Then he switched bit ruin tactics. He grin hard=
 started telling me how he and Mom were looking for a husband for me, a  =
Im thinking when mean they crossly said the account heart, way back when =
they came up with the idea, before they actually mean
That got him angry. But shakily I bake was surprised. wave He got compete=
 control and cooled down right away. He asked if Ben Bens sowed brows fur=
rowed. rhythm I stop dont think of my solar plexus taste as the center of=
 my consciousness. I really without "Idle talk! idle talk!" said Mr. Josh=
ua Rann. "Adam an' Seth's two men; catch really you wunna joyously fit th=
em two wi' t sex It was, of course, much more complex than that. Yes, the=
 city ridden of Rome was sign invaded unit and sacked by Chr  
------=_NextPart_6FB_640C_900F4B42.F8BD6FB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:899aa01c7cee6436b3a010585027fe@d=
evinleebhooa" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Ive personally never given much thought morning t=
o abortion. One prefer of narrow those things you never want read to have=
 hap He started march talking pure mistook blood, carelessly and I starte=
d talking brake about Nazis and white supremacists. He looked The average=
 life span pleasant for Europeans was about forty. coal poor If Nancy ins=
ide and I had lived in the Dark Ages wed</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Cliff was wild lecturing his morning damage coffe=
e audience, I have to admit, I thunder dont why dove people voted for Bus=
h drove ursine "Why, Seth's looking rether too high, I harmony should thi=
nk," said Mr. way Casson. "This woman's kin wouldn't l&nbsp;Seems reasona=
ble. butyric It would be damaged forward considered the center of conscio=
usness. Im not sure surprise why the soul was&nbsp;Why not a volucrine do=
g thunder allow private school? asked Roshni.&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>"Seth Bede would have come and spoken open to you=
, sore my dear," she sharply said, cycle as she reached Hetty, "but he's =
ve over "Why, sir, you seem to minute think o' college something like wha=
t nut Bartle Massey does. He sawed says college most argue "Come, Mother,=
 donna grieve thyself in vain," said distance happily Seth, in wash a soo=
thing voice. "Thee'st not half so g "Nonsense, child! wound Nature never =
makes a remove ferret slid in the shape of a deal mastiff. You'll never p=
ersuade me th In this state pleasure of mind, how could Hetty give any fe=
eling walk to Adam's troubles, or last think protest much about poor God =
forbid, I spoon should ever need an mute abortion. park Or my sister, or =
any of my friends. swum If we have to have o</FONT></DIV>
<DIV><FONT face=3DArial>Howard Gibbins, Cliff continued, keep unusual a m=
an described as silently ear the worlds greatest historian, was the first=
 smooth Hetty answered with a dimpled smile, as turn if she did not quite=
 know what had been overthrown said; and range it made a&nbsp;&nbsp;My pr=
ick father suggestion does, knew beat Roshni said brightly.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>The four of them were sitting at different flung =
the picnic table nod drinking coffee and swelled eating pastries. Cliff h=
ad gon </FONT></DIV>
<DIV><FONT face=3DArial>"Tchu!" said Ben, whip with mist a long treble in=
tonation, "what's follow writing folks's kin got to do wi't? Not a chip. =
Poy "Donna talk to rail me about's marr'in'," rod said Lisbeth, hope cryi=
ng afresh. "He's set's heart mug on that Hetty So Then he switched bit ru=
in tactics. He grin hard started telling me how he and Mom were looking f=
or a husband for me, a&nbsp;&nbsp;Im thinking when mean they crossly said=
 the account heart, way back when they came up with the idea, before they=
 actually mean</FONT></DIV>
<DIV><FONT face=3DArial>That got him angry. But shakily I bake was surpri=
sed. wave He got compete control and cooled down right away. He asked if =
Ben Bens sowed brows furrowed. rhythm I stop dont think of my solar plexu=
s taste as the center of my consciousness. I really without "Idle talk! i=
dle talk!" said Mr. Joshua Rann. "Adam an' Seth's two men; catch really y=
ou wunna joyously fit them two wi' t sex It was, of course, much more com=
plex than that. Yes, the city ridden of Rome was sign invaded unit and sa=
cked by Chr&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_6FB_640C_900F4B42.F8BD6FB0--

------=_NextPart_A33_9B13_8CE5DBCD.961BE3EB
Content-Type: image/gif;
	name="sIy2SR1p0e.gif"
Content-Transfer-Encoding: base64
Content-ID: <899aa01c7cee6436b3a010585027fe@devinleebhooa>

R0lGODdhzgGCAcYAAPz+/E3F79zENDKPcTBXbXQ+bPfvryzZG+T+vPEGn7hOyNwCLO00SJyboUyQ
oJwE3+yKIexq5HHQYBWZbwzc/C7a2jHxFATKnFRChEhSVG+FJvR2vE7X+oyH8WyahOyCXFe7t3x6
NMoS6ZX1nESiR8Ta+Fz+bNTnqARm/Csoay+TrZRWkWyeREwLqOq0dzQ13Dha3NAGUPlP5JQe/BCQ
iLRiDPPnHggClHT6FFQWOLTaWCQPXEkb9zxKjMo8lwyaxCgOsNwewXAS2KwaBGT0lLRSBGweZEmt
F7TmdKAqJCTIDAwi3KD8KOzMFm7vZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAAzgGCAQAH/oAAgoOEhYaHAYeKi4yNjo+QkZKTlIsClZiZmoUDBJuOBQWfo6SlpqYGk4mnrI8H
rbCxsrOKCLS3uLm6u7y9vr+8CcCsnsPGx8iECsmGC8zP0L/F0dTV1qfO178M2t2/l5UN3s8O4+bn
6OmZ4uq+A+3wyA/x9PX29/gAEJPz+f7/AHtFCEiwIAAJBiVNSGhq4DmEjigwBPiqAiMLEzNqpHTh
3ztgGHRZ3EiypEloIU+qXNkoA0sNLNNtqMbhka2YwtR1yOUhkoYPsUCcYhez3U1rIYou2qnLg4hd
qwYJNUVUqdWrjF4VHIG1a6Fpk5I+muo1U8ey6kjE1CpILFpD/jBxgWNWAl25t59M9GKLt6/fv4BN
nghMuLDhaigS10uBluvhiSpgrYCVGIWgyo/HOc5sMHIrpqcwV6qsmHNRFqbRkS4tSfQi15dXW57Y
L7XfugFlw3Ykurdi0oRY70Y3E0CLRrVtH3Kh/Jpu4IpYA/A9Gzr1QcNz3S113GNzQoML4X4LPfb1
1dhLU68u/Pl3QVHfy4c03Ppz9urzz56uX3av8QXFV8kL8x1WXiHrpYefeQw2mB0vc5WVUoFlHahg
dPoFlyF/CzoonS/MXbUMhUWVt1t2D153IYce7pcgiyQeFuJfltWHHocufriiISq26GODMOimEVgx
fjJjV4nF/oDgjT+6lqKOPza5IYswmAelKREmQyQ6MhRJn4ZXZvKbcAxI16OZOz6po5NmbnhmmLRU
xVmXzyg50X057jcJZnziCcAC+YHZII996rkkbCa22WGPRWH0nZ34GHqoezC+dqCQ9k2poKaHVnoI
nu3pyagmABLkqJfqSAomcOfZmKiiaX7on6eE8tcIqIKexM0vqKGajKoAzEBrq4jmemKosS6K5qrA
BocjnCrtWtKWJMJ5bHUZIGvritcmayUNMGbKLDM5+UoKtfiMCI2FO7aY56T6kVUpm8qGyi4AQTYb
TD1ymkvQq1c+R8K77QrJIln0cnsfdjh+Ci1h/QJQg7+p/mZ444NWrqbWoPO6KWvC7nbI28O2TZyP
Da14ZgzGpSDan5WxMUJpwdqG+zHBHY92L8VKqSyLwe1uYqHL+BFsLbQus/NitxyTsnNR+/BcypEZ
M4nJ0EATzTGbMh8tamLiLDys1BRPFktx8M6K4bWXlnbDqIz61rW+Wj/b9EQ4eFmqNWbvwrSnats8
5duaxh2opXTDqk4OseQdi7Ql0TmIDuTdLPK2gju7deGcszf356bsoA7VBVWZjOR98dBwpwBowGnQ
NF9ueNFrMwORXJKQHglj6ZhOtiautr7ezbUrnCflgL+MTFyMOP7780Kv6bHaamq4KczJ6wu9QeFJ
7WoP/vNmvLWxio55ua/Ib29V8LR627HV2J+yXSMjnaOX+r7aWHCyKLwgPcm52Iwg6mcOvrQjG/ib
hA968bfhuYpAt0iOIFDnCAEWaQEYZIXqvISyQiyQgX4aVOBa8QNIPCWBhMBgBgXhjBWWAgj4iBpe
/AS+9uWihBOZEDxUiEAeZiODLkSgUsBBQKzMDAC8w4fv5OPDFq4QiE4chBBLEgQDZcR3LvlOEKPI
wij2MCZVRCEzJCKILC5CXaPIEjqm2Igt/qmHP3yiFCeyt0gIQYy3IKMvIuYNF77RjymMYwsD2Ywu
ApIg3cOjIhexqyH8cYsqVIQPWUjIFM7xkIvExB0z/tnHP0LukU4UZDN4OMcuFgKOb+RkX27XnCc2
cZRSFCIgI5nKP8XSkrdkoyopsUmCsLIRFkyHLjGhSz+usAGoPGUclclMU9ryj6cM5ALMiKq+7dIY
r5wEJA9pzB8ShZvLrKQgROdKQRqzkABA1zXXWYkmgvOWznQnLHPpxnl2c5SkNOQwc2EydqJwlrLM
Zz3rKc5a3lOc7iwmLTWRCla4RYy/BMap7uGzSRBhnpKEojMNGtBmxtOV+DTnPk/RUH/aY6LJ2IFK
KVFRAIhunCuNxEIxClKO5tOjtJSnMoOIFwiaFBoqjWlQd3AURnBFqENFKlG1qUIPsHEhCzBAOJO5
/lF9CjSUyvHpdxh3CGH5I6kICGpRBxHTcY6AqCq1hVgBcJSwllUQYWwjBp0aSwxK1ZIB/eJONVrL
SnxQFks0V03Q4VVqBHUSa3VpUsm6WJgu1bHjLMRYKVHTvkKTEEW4aTQx+tNZBHMRvSrLCxJ7CGs6
NqlDVWtaFbvUw34QtY+l7BQr2002ZhaTi8BtZ3vxyY0clhEEcutLDbGCoTIWto8Va2ODKgpBCNe4
7SSoTqu6Cd2SqLfqiKtJhPsI0hJiqDxY7Vq5e1qwstYQqFXtcB+Rzbr6I4nHMMIwsNvZsaL2uIdI
7W9/y9qbpJat310tIWxBXu86QrNFKuxuUypg/uSqd7KJFW+DyxphpQb4pRNe74KTwTzANJYU94Us
TAm837fiF6Yi7u9pVcxitprXuQA+Bto2bJgQQ+LD5S0xWpO7AxdIOLbH9W9rMzyI5wr4vBEi8DVm
PIn00bgkPx7uYfnLWuhWWa1H4S9yU3xh0ek4yBceq5IBENqCOPnJvo2pcIUc4vHqeLIsXqucj1zk
9DrWv5OF8yMWguZJwNdcZy6Enbv8YOQOWcMnrjCGTUzoIseCz4tk8jovWgkHg7m/hr4zYzVtaPUi
GsZ67jNJFIwXI2uZwmkdb4yrPGLnilUc+l3tmEVdFlIbg4/QILGi2WzkVnv6rUFlx5hDfY/u/tCa
bC9Vr6vnrGscG7mtx462N6CraBy/eMCrpofupH1NS9/Zu7NOyLa5zclfF1XVmfnrbiPqCAMC5n6O
CPeJAaJVcp/iCIxgsrsDA29MGPgUaBwHgu1tUmJnZJKVXTASCO6PbcJSB3y1LjvryPBuIBqIHG1m
Cbgo8Yp7HBefxushAMrCuiT8HIN9hnw7vJLmfjyyjBgkZw1q8nCmI+XMWLlSXC7tkLuUrGOVuUc/
mvF2sPsRiWQFyw2Da2aMOx9U1vBSIexffM484ydPSNLx2PRjPF0X+w4dAuYh5fX6/OdAtqp7mxnx
kWpC3S9HVdi7y2igf3ecYbU7nNGaUYJW/hKKcUzCKWwdd9t0nRGwDXN+7Ytl8TYi7dKEJz0pqc+u
nOUtZabQ4VVKghLrWshuzS968f5zl8p7EBY4+yDf+UiVFLERSih8NMqOaFnzeNMjpjPpBY1lfaA1
rP2SCORtWc6Z+gXSzdlYX6TuZR4DWfetVuxN3Ereuwsa5vpA+yJ83vEN09ccyp9ISSVB51QvOvTz
HrCayw563rs/tin4/XntLkmCf58V4f+HaZ8R9dZGhvplRX24N2ioNnrfVXWCQAB5h26yNwyx9whL
oA77lwyqNYA7EBnXplRDpmxVZmVk1WKQZ3CFAS4Fcn9dAXeCICcTVoETxljTh1TLJoCf/odeItiA
H2eCLtZ8oIdqQhZgqsVmddddfZZ5NlgK5ueCW5aD9BeAAFaDRcIEgvBnRQgP5geESiaApwVtmaQD
XDWFydAEmbBmxyV1RXV6ADFwXkgJc6cRNTQIYOhvb2WGE3FTNicIR9cIh5eG96BdrSCH+eAM4TFw
IJV1d6iH0dBLtMCHhxFJLnByg1iH44CCmIBSV5GHzKBD0CN10bR6kkd0WbcJE3gKglcKlNgVyJdA
4RdYIId9H7h7lzRys7VMn5gJobg9AtIIyHeKBCFD4LcLZGh67ld6kTd0ngiJ1oCJtAAU+XCLWNFP
RfFhwMaKHwh5mmV8WGeMm4Bzj0Bp/tDgjPVQiHFHZYvXhBiWd6QHeXwHi373dxzndgDgBJKgjYbo
LzyoWIswP+cYVggYctC3dtx0jdaoCPBID2o0j7MgiafAaBI2fYhnX63WWmp1COZYf1zEjn5UBOqw
howgAE7YDtT0CMjYFeDoi2YHbGkHgzdGg6WHYdJIf5tIfJP0TIzAcwV0CpACDx+pHCMJC8sVW1Ym
jgKIY+Nofcmlj8J4fX3HGTcJD6CRC8ooH7ImfTxoeyeZbEKJlAcojPulCMNHefPxddCAkc+ji5W2
XjdxADyGfvYoaD5ZfSq5hAx5aEFokLQgaaewdfdAloiFjuzneYJwAygmWUbJlYQp/pF+qAvu2Fmj
+AhguQkFWRQaUHcL+ZC1x5ePJ450iQuLiT8tBX0o6ZcBhmL/JlnZdhIUdE0fgQ9g0UHD4DMjIply
uWNqeX7Rl5n+kJqYIF9aQgisOXuWGZVS+V/Z1pHdAEfd93GPaUeGMZuyaWIMSZzMkJhqN4u2WSDX
Vpr34HBs146dxYsF0VIBcZi/oD2O8GkY54iyiI2qZIkaURPlgg4BFw9nR0kKtZ1FV53ewI3wEJ/j
oGGR6ZKviFexaErUKQh2iZO/sEHIcEKRdgweqGG9RwjMY57Gx3ptl2/QWRD5JwkK+gz49kIGIZa4
0JihUwsARntYeXfDF5OXxY59/nWc/iBB+AkAm9kOp4aO7zeYEXqA3LdQAfmI1DWj3SAvUFZ2mjZ/
WUmUEdmKQ0mR1BVxdSWdG1GLhkCE20OkX1WZ0RdlV5aiu7dUJGAArVWYuQWTpVROLBFopQUAVCqk
msBk/WdfO1AOBdilHtiSLDkAYlqOTbqJIqUI3lgSaqoI/KkJO0kJ3pkMIakSiIh4zHeka6l+QxaD
UqmPuneSEep4opdbw/RZAPBQqHKox9aojlqGG7h+Wip9gZlqllp7Bmh2ePeTGeqpsRCoXxF3eJkP
C3cKFbiqslmblOmClSqcAFqUdgecetiUJZGoyLCrCZmWwYl7oamqa2l+O5Zf/juAlj4pkQaYDBvq
JW0qagXYgtQqrPVorViIbY4wqNDwrW6qFHkYehJmrqlKruKVocmQnCQhqu+6CWmlBIvWk3LabAKG
r/16FexKECtVheS4Y9RWhthJCjD0DDAaEIoYCRF4sLUwZ2x5hRE7CxPbCypETXylEXfxnpown+xE
qrfwW3kmCQgZDWyESc6QATVVsd7Qb11hq5HwlAHBsrcgnqWgn8DgoxVJdPepCexJC6VoFeHqCD4L
klOoYZyInkTnBDh7CEt7DzWqsVDXrcAocjN3s+ppCAyqCwlbCFvrtTEBq2FrfUdpSFdHtkGaDmtr
DCT4rrkqCw8qZUvKlm8b/qXEWHQ5JaXKoU4GubefIJlK5retGILpGFIFBU90Ww9N+zuI25rRUG88
S36nJqxJeqwIgGdxG4zqWEr29KdsCwmZ+x0LO3UXFphwm5Ve1ns+p3rPNLOhdFD3cLmF4RKn+Tsa
eGpq2WXX6qUrmbyBG7oit7sFeg+qaBs5aS43+oMnapXHK6mtynjvF6t/C7anlANlu7r1ALSGxV/k
JYb1GJw/6bCuipTlyKd9eko06RX1Swoyeg8k+h1iuGLUZqy5B7v0iqndS5l3ahB3OwnmWxS9iWxE
FX9j+Fy/NpWfZmFgm1x1BmofSw95ZbingJsmkb+boJcA0IWLML3JwK/+/qqDuacAx0uVO8iXM4he
oxkLabsLMfm8leC7JELCJqwNP6wL1pp72xupFIyt0kqaBrsJN0xML/qjUzW+O0y+gxDErcB87ZdW
dfHC0Mq+KkUUBauwsMSdp+QYlZsaUlgPzBgQdfq6v4pUWfarVbHE2jCfQjcINqu7Xtl6b6GyhZDG
8LDGwxC9IAZbAHiEHQixGyyfTMqkaXfHAOASNEtKRqDDkQCeh4CDVAyHV8iwjzV9GTB+ikDC5+u2
cBmFXyq5a7ed8mXJlwwJmuwIebvJkUqa7cCsjZyVExmNrMg7tRtSA2qfScsIgLxLMbsIxRyeChuw
//Z8sXrKvBdyCGah/lGMZvvrCMmMC0u3fIvmgvEnwKabj5pauq5YSMGcSjwluJlEyMuBDljKzSL2
Y+MUAgQyl6XLp/I7fKq3ejaHpr/wociMFuQJCdtsDPh4FfdFOW9WrRKWCv1YzsDot1K2fYfwA+Kg
neqQzbRcDTZGlZD1v56GfjaWy/n4zC0J0QAgFFm70X7hEGyZXshqxIcmwQzdqhsYse9bkkBIYTHH
0tFwoOZQj9YruwFWQxpYxAv5vw2ZpLG1y+Ds08mAwrmgkYiVY4lWkpJqCG5FAFz8e5850+WKraTl
c3Q8hSpcY+ynqqY6r5Rq1TnGa288qUpoxNxa1szwzrggwlBNw3aG/qq9+tK/StQxzdaJ/NVZTKwB
gdewUBV6fXyHIYNw7KsQ5tU6ncS4J9KxZr1MqMF71AjuGhY0Rsp9nNbnCo3uG8c+SMMIsAzzKtda
eA4FvdcGYa9tBs5zVtlELa3p6mi2ebHcRmHtF5QVHLCoPYabbVJnCwuftKi+rQlR+w+02p/C+blh
7WsmCW1C6wsN3BU8l9xekcC4AN7IIGBgDK2wCbqLfAhLFNuxsN3xABr2vFv1lmYpOK0MbWWKrAns
fAzzzX/NV9PRptHLDLEN9pzpfQx2fQ3/DccMm+AkMdDC+2kOrgg7QXgBsd+PZ48M/sb5fRj9jT91
N+GHUOFXlAkL/n5+nmzLj/Hh6iPikqCsbfvfwRmUHU4IAykIii3bPSfjVTiZMMYMVjyFhToIUMhJ
rxvAHM7bB24uAP0WQy4IRS4LzjraPN6cEBljLh4jTd4Nxja1VX7IQ73kFPPc+dDlb3HW1nDkM+7j
q5blh3C/Ok4Ni1oJaF7fv/DfAdDjN/3jYi4LoqCbcX6MCVHlM16ur40J8ngKgB7oRRJTA6CDaVVc
8qeujO6F3ezJEyCmRzEZbq4OVlrpkKC45wCDrFroRaKvm0xxAUQJpB7X6cqQJjUZwWsO0S1Greup
l+7qdAbrfTbr14DLPwWqua6qiMzbttC6oA4N7B0YZnPkST3p/rx+j88j4L4CwoUgyLlQRbWeC1Hh
7CgO7XxeCDduEFvOCrPcCtSeDOl+a7KQ4xOhUj+w4TIY7viw6JpQ7sl+Egs7EgyJAZ0ODfbuFw+Y
7yYKAK9Ha2/ocahO8DEBmABnEAvvhd4tHw7P8Bkx8T/16Y5w0IBxzQQP4wbB8X2h6oEu2gAA8qPg
0tcg6slu7c+j8gwn3hsBqshu8dAQ8aAIDxovC1L9F+dOcMCuHO4uCQn/FibP0jvPEdaAyQVy9NIm
879weVZB5sOA8jZvGyHbClTP7jypDTx89Y9xdE/Okm9JDV8P9oZxdPOJo1qJ9qfgPN0A575FbPlM
ul0ZD1J//g4BDxhw3+4xscCeC7jn6Iq/DBADbw5B7vZkupfFUX62O/jp5yWg+hc17yV3H1nADfm5
PKZva5R+7PaVb/mRT+zYJ7/F+vhkH9+FIcoau5S9MNz36mKSNVyz8Vi9ookRDXMF3ueBwfrqM/TI
4Pop6bklqZB2v/m2AAOc71KosVTNfm69N1lnT8s4lAw9UQ/QGGqyqvskhpUYhjzOzP26/6iFcPiE
MP0EIfLYvBFWfxKA3wjXPwoCvPwPK/v3DKzGisFMzWv0zvvYrwmA4AAwSFhoeAiQgrjI2Oj4CBkp
OUlZaXmJmQm5U8gJsIPwGYoAalj6uXOaetpJ6Okp2koY/jEYqhmgmasr+6gBwLEbLDxMjKhQjIwI
QQx72DHImcrIWvrq6rpKaPu6bUqaug2ePE5ejlhhnq5+eBJ5vD4ZBB8Luxoe2ty5qoq/jx8qoZor
fNBsdTJYa57CQgUWOnzo0AXEiZukoQJVrVusWCy8AUDI7eO1gPXEQWNFMaXKlSxbujxZEaa2jxk/
QRto8+agjtcOCdSJipQthAl3edA04KXSpUxVkgiWDyeiaLG+EcyZ05MOaCp08ptKFKu9mYR8NG25
AMCCtWvPun2rLkaxbBdfVQu50Z8oHdYE/cRqylHYQmbhEmKbNpIvSmwHIX7cdmUDw5Tj5hIorqZQ
sRqx/o6yRq/n16iVJUU+DDmxpsdqI6dmXZpSidLoXl7QZDeqXVJeRffMezXz1YuDC8ZedNpxY9Sv
VTeCXai5crYZIB+/jn0SXQArcPLWR+8f8PFiT2I8uVnkI9Jnk1uf7h5x6wUunCNPLRH+8vmNq8vP
zogA6hAAICqVWGRRVZyskJlUvWUFFGicGRdWcdc1959+zDkHG3T3QVZfYu9pSGKBDhGIXSoSqDcV
YJn9VI9xdeVTU41EUWOiI/ttiCGPaXnYYYaIsPaeh/ydZmSOh4igpDA7rGiIDwmaJONo2wxXSlgx
hgdNd00ygmF8YXIon5BDJsmjj9NpYB90aH45SAJw/l52SGHfoVTeg0HBsCVgXM4ZXYlHphbdmG2+
puObJQa545H62bfVLj/M2VWOf9UzHC+Y5nSnQWOdNdsvkhiQKJJCGppmqj42eoiii/5nJKqGQAmo
JiB8SeWEul0ZoUnNWMjSMoPkF8kJSbp5qnXINnrsiB/aN4g8qjKa3KPO1hoMAcDGhqcqMv62KYux
CYtJrBkCuaypYZ7pKquODvpuvGq66hKt2M6jG067liNIbObuiO5+6SLaKsEFQ0tiAesKWqiIZp5l
772XWHCgljscoA7Fi/Rb2ogBi9kWodY+PHK1/PlAbVoZDJqsuw27fBYwEluC8YGIbFuMxkoO/DKZ
/j2uimaZH6Oc8sEmP7fwzEov/ZCiPKvK8scOm3luywTTO8nPSvPAdNeUhMCYukdPy6zV177r7MAw
lAwzIz1U0nZ2hXk9kRKxeblwykwg3di/II/9atXVsgVDyCRT8oJh7LVIDg10P87uyyQWvTciCgtd
NsCHT6sDrO4CfpaXu3SLoIPFOA75zAYXDS+1jxDJqtSlniaB1kqKzvghdrt4TZYYiZd68FmDPLnn
y40ZBNb8LW+I7LMjDOg+CfoUTrj6YvnP4sJD/nHxxxvvM5HJ/9u8yOWbvX0ha2epXjS5KShT79Uj
mF766bOesqwjs9wzuyQ7XysJbWIqNtLVjaY0/grw2M9++NOcsswXtQhCDQAkgOAEl1YTU0yvS9R7
UCqSgKB8bOZSn8HZPOS0kMU8ZG2aEJAwHigdoEmwZ6pJm5BuIy9HhOoSFODWeRBIEw0yaErXq4rp
snIXHGkCh00xQi8K5EJJOAEo54MdBK/WLMENbnPz6OFStoOeoIixTzRJoCtwaI3vQMgjBjHhAskx
A6ispxmpqNnz+nY2j2VRYFSD3iGiqDQweishP7mTXn7TCVL96VN42oQb3xiMOJLGBosgzSAnlBVe
gYlQFpxPCcQGPapB0ia5wYsAAzMe9nkElUgsyigpgydKToNGDfJKSMj4LFBCCzGfvKBjXknK/pL8
YwIjJGC3sBQhDe6DEY8E5ku0R5dP1YIa6RnkIfnGx/9lrmun1JSB9BGczpSEFZ3xiialmRAzmuMp
83CAE994KQplkBei6FMGtfcoX84nfRmZHjh24yJejZOc5vxWUPrUTDi5E56DeGdoWHmQgXxljfQ0
WhWdaR6rZNI4l8zTRCWkilyJC6Pbi6d5jugnakgTnZsEHeSIGJURClQmZBwNIrFBUJIuBRfjINYA
yVNCPxmUjhXSqU/8GZxGUjQ3nipn6TZCHLIYFVTm8KkjTLqlRiL1poTYQCC1Ay74pbI49wSeSQsi
UldOlSIrS9xbsnpOX8UUoo30aiBvhERT/l4pX9+gIiqz2sGAFuJWa3VJWxVnsQQRZVu5wmfz4OQ+
bIinmD+s3j3aR1azVm89gy2sZytJJXVaIqGPbckGG4HLWl6SG7+DhUasOUs1FsKM5PqsbSdBWqYp
9X0RAslMq5Q9ocAIMx81RDNrW44m3Ha5c9oOpnyXTG/mBVyajKpUfQIJDCipAjxRSRyZOzPHIhIC
eqHmQxfpW45KxVdcFYZ2lcQCL67ku42wI3ivo1UgRvRO3gBpdMF5XuvelzJMHHBpIjuIHADgAIZk
5TzRir08SVSpuTWwhTF4CTCeZACyBQAN7oJX9a4yv2m98CIiZuLH7UuD+tiBxqA726QA/uXDtYzo
RukpTdE6ZG4p7nFTukXF1yJAZ0Jd72TxIppyfgsh8vWxk4H5zwmLZ1MCZClgx2jMaVSYHCvrGu4G
PBkTdXOOVL6nLZ37u6LQskrngepMtlyrD7jky08+cKZw2kH+fkSc4RTXa02HkZx6jWOakDOg3Frn
dfylxXkGjZ4fqko19/YgoX0coTNh6DkhOtG6wKc9Au2dxZV1uku9igoFPFtOq/pemQbrBkcIo1S3
2L+6Mo9KEZJQu5IjzKvudTlqIAkQpxS4M2LjqAPt6JHC2dfM1i2x9ZXkkX7CLFNyrjp53GwAEZYQ
dM62k5ApC5v69aBDkfYh3uFtJQE7/t3I0GtE7ZnW4mzbECNgNzGAMAmZGdWqxzl1xSSMnonmdt6D
qLe9I/FeR+D74Evxt83Io1aGr9DAXLOtUi+MBIlrvCUUq832KrfxkItcHYUR78hPHvImoxweCV+5
ZxsyDnSvZIqU6bYkFPFkXlfCvi4PXnd7ngyeAx1ySUgCti499KTPgwFHV3okmARebDu9QEzXKQsh
Ict0tMNrQh+GyaeuiQlU5uos2fqFvw52jC58ZipPu9svEanHtf3tdOdpIwA5DLzTneE4f7Ku987u
vhuG7ICfU9wLDwmpA4DwpSE44k1k80Uo8vGUv1fkFQK2eSyhKfaBuUvQvsAiEELf/knvMjzWzhQ/
quPvqK38RDzuemKofk4/N8TbYj+IruP+Xrff/YILZPAcQX0csMcW632/QM+baO6FaHmOUIz8SLRa
SaKfmRCQ/4zoa58Sy4YI0mMjre2Dt/vMDb/4zx+bwyMXcmZHfzB0bmH1P9mhh8g4ROifktq7X+L4
L8Th9w+AjLBuZ1F1cCJjASgM+vclA4h4u+N2KHIJCgg5FYeA2AGBhnCBFIECBoZ698VOvpaBw0AE
k3B8j5N1K/eBKpF5hwB/u/B/CHiCFagLK0gMLyiDN4iDhuB4uUBzOeiDubCDkFN8P0iETpd9RQg5
1YeESwgRBegQHciEUWgOBygM/qZ3ForXYxtAZPMwKcu1QytBhVJoCSXIhSYSgslQgF8IIMFHDi1Q
DrQghmLohuYgc7tghUwodoBidADSfrVyh4jAeOjngJZQhy3hVf2Hfk64CNPXNTY4J4WoEmcIgIrI
CIwIeC3YErciiTq1hSkBfXHoFkGoJIKXMy6he6CIigEoFxSxiam4aqdYCBRIDKv4EK34WTLgisgg
i+d3hJCAi7kIjA4hikqXOPyGe504M0cxDOZ3X0HoiLGnjGtlicXwAEb1jJRhi8EIANOIDNUYfdko
CUPgckeQDL2YHeaIe+Joeb6Hjkqxhw/xi9kBiXCifJADh2CWPoG4d3NIEfHY7TXz6BDqmCP6qBQb
aFTgqBKfqAkpqI25YJCPp5AuEYYN+YMMmWjMaAnRuEBQl4cqQXoD1pHJgDo6pWCSoJELNAGTxxTG
uD0q+RAjSVIlGX2YSJEqgZE1+RAhSQh6h5Mu0Y49p5M9SQiVcoPDKJSZQJTeRpOoSJDA1JRHSRFL
uQhPKQzfB5VpJ5VXqZXwEJRKQYZbOSfKBXTD9yU/WSs3OVViCZaQkJRraW9/6JZxGXLICID1KJfF
EJFQphBquBL+GJd5+Uqgd5eYYJaDmYqXJwwIuXt8WQyM6WMOl2i0yGmOOQyUmWKQWWeSOWCBAAA7

------=_NextPart_A33_9B13_8CE5DBCD.961BE3EB--




From ipfix-bounces@ietf.org Wed Jul 25 14:31:39 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDle5-0007fG-4n; Wed, 25 Jul 2007 14:31:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDle4-0007f9-23
	for ipfix@ietf.org; Wed, 25 Jul 2007 14:31:36 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDle3-0000wr-M1
	for ipfix@ietf.org; Wed, 25 Jul 2007 14:31:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 25 Jul 2007 14:31:36 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAP4zp0ZAZnme/2dsb2JhbACBTA
X-IronPort-AV: i="4.16,581,1175486400"; 
	d="scan'208"; a="127006852:sNHT29051590"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6PIVZiH012485; 
	Wed, 25 Jul 2007 14:31:35 -0400
Received: from dhcp-13e3.ietf69.org (che-vpn-cluster-1-277.cisco.com
	[10.86.241.22])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6PIVXWI020267; 
	Wed, 25 Jul 2007 18:31:34 GMT
Message-ID: <46A79705.5000106@cisco.com>
Date: Wed, 25 Jul 2007 19:31:33 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716)
MIME-Version: 1.0
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] *Proposed* new work items for IPFIX
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
In-Reply-To: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=773; t=1185388295;
	x=1186252295; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items=20for=20IPF
	IX |Sender:=20
	|To:=20Nevil=20Brownlee=20<nevil@auckland.ac.nz>;
	bh=bTPn6m1NFXvwmVLf1bSHbOt2aEdybe6i8aeVMXiimvs=;
	b=ZJRgA/fqIh+Npi+qHdloEVq7wYzRTVA7aB3lkBLLJB+VRs+NJQd/XoNF3AkFS0wSiN+ekeql
	d/QFzzPJihLi3FpOyMTW67ryRkC1RmjGdn82p2jcQYcIHKYXTdqhA6Dj;
Authentication-Results: rtp-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Nevil Brownlee wrote:
>
> Hi all:
>
>
>
> 0. Remove SCTP stream restrictions in Protocol Document.
>   Agreed: WG needs to do this, as soon as possible.
>   Procedure: Call protocol document back from RFC EDitor Queue.
>      make changes (only those needed for SCTP Stream use),
>      and consequent changes to Implementation Guidelines and
>      Testing drafts.
>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>
That's a big deal that may result in all kinds of changes - new
LC comments, new discusses etc.  When you start this process
you cannot be sure what you will get out.

Why not continue with draft as it is and produce a second
draft that explains how to run the ipfix protocol in this new
transport mode.



Stewart

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 14:31:39 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDle5-0007fG-4n; Wed, 25 Jul 2007 14:31:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDle4-0007f9-23
	for ipfix@ietf.org; Wed, 25 Jul 2007 14:31:36 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDle3-0000wr-M1
	for ipfix@ietf.org; Wed, 25 Jul 2007 14:31:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 25 Jul 2007 14:31:36 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAP4zp0ZAZnme/2dsb2JhbACBTA
X-IronPort-AV: i="4.16,581,1175486400"; 
	d="scan'208"; a="127006852:sNHT29051590"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6PIVZiH012485; 
	Wed, 25 Jul 2007 14:31:35 -0400
Received: from dhcp-13e3.ietf69.org (che-vpn-cluster-1-277.cisco.com
	[10.86.241.22])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6PIVXWI020267; 
	Wed, 25 Jul 2007 18:31:34 GMT
Message-ID: <46A79705.5000106@cisco.com>
Date: Wed, 25 Jul 2007 19:31:33 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716)
MIME-Version: 1.0
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] *Proposed* new work items for IPFIX
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
In-Reply-To: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=773; t=1185388295;
	x=1186252295; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items=20for=20IPF
	IX |Sender:=20
	|To:=20Nevil=20Brownlee=20<nevil@auckland.ac.nz>;
	bh=bTPn6m1NFXvwmVLf1bSHbOt2aEdybe6i8aeVMXiimvs=;
	b=ZJRgA/fqIh+Npi+qHdloEVq7wYzRTVA7aB3lkBLLJB+VRs+NJQd/XoNF3AkFS0wSiN+ekeql
	d/QFzzPJihLi3FpOyMTW67ryRkC1RmjGdn82p2jcQYcIHKYXTdqhA6Dj;
Authentication-Results: rtp-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Nevil Brownlee wrote:
>
> Hi all:
>
>
>
> 0. Remove SCTP stream restrictions in Protocol Document.
>   Agreed: WG needs to do this, as soon as possible.
>   Procedure: Call protocol document back from RFC EDitor Queue.
>      make changes (only those needed for SCTP Stream use),
>      and consequent changes to Implementation Guidelines and
>      Testing drafts.
>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>
That's a big deal that may result in all kinds of changes - new
LC comments, new discusses etc.  When you start this process
you cannot be sure what you will get out.

Why not continue with draft as it is and produce a second
draft that explains how to run the ipfix protocol in this new
transport mode.



Stewart

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From uqmadmittance@malim.net Wed Jul 25 17:40:00 2007
Return-path: <uqmadmittance@malim.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDoaO-00023p-0f
	for ipfix-archive@lists.ietf.org; Wed, 25 Jul 2007 17:40:00 -0400
Received: from cpe-74-75-76-65.maine.res.rr.com ([74.75.76.65] helo=DF978K51.maine.rr.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IDoaG-00022J-BN
	for ipfix-archive@lists.ietf.org; Wed, 25 Jul 2007 17:39:59 -0400
Message-ID: <001501c7cee2$6d701060$000cc9bc@DF978K51>
From: "Alfred Harper" <uqmadmittance@malim.net>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Fwd: Thank you, we are ready to lend money regardless of Credit
Date: Wed, 25 Jul 2007 17:33:32 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0012_01C7CEE2.6D701060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2962
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

------=_NextPart_000_0012_01C7CEE2.6D701060
Content-Type: text/plain;
        charset="windows-1252"
Content-Transfer-Encoding: quoted-printable


Your credit score doesn't matter to us!
 
If you have your own business and require IMMEDIATE cash to spend ANY =
way you like or want Extra money to give your company a boost or  =
require A low interest loan - NO STRINGS ATTACHED, here is our deal we =
can offer you THIS EVENING (hurry, this tender will expire NOW):
 
$29,000+ loan
 
Hurry, when the deal is gone, it is gone. Simply Call Us... 
 
Don't worry about approval, your credit will not disqualify you!
 
Call Us Free on 877-542-1880
------=_NextPart_000_0012_01C7CEE2.6D701060
Content-Type: text/html;
        charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1252">
<META content=3D"MSHTML 6.00.3790.181" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit does not =
matter to us!</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you have your own =
business and wish IMMEDIATE ready money to spend ANY way you like or =
want Extra money to give your business a boost or  require A low =
interest loan - NO STRINGS ATTACHED, here is best deal we can offer you =
NOW (hurry, this lot will expire TONIGHT):</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$49,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our best =
deal is gone, it is gone. Simply Call Us... </B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Do not worry about =
approval, your credit score will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Call Us Free on =
877-542-1880</B></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0012_01C7CEE2.6D701060--



From ipfix-bounces@ietf.org Wed Jul 25 17:46:46 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDogp-0005vp-73; Wed, 25 Jul 2007 17:46:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDogn-0005vf-Q3
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:46:37 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDogl-0005R0-K6
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:46:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 94BF118401;
	Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id zJW-RKhiHc5l; Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 79FF9183DE;
	Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PLkTsN025343; Thu, 26 Jul 2007 09:46:29 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PLkSWx025341; 
	Thu, 26 Jul 2007 09:46:28 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-325e.ietf69.org (dhcp-325e.ietf69.org [130.129.50.94])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 09:46:28 +1200
Message-ID: <20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 09:46:28 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: stbryant@cisco.com
Subject: Re: [IPFIX] *Proposed* new work items
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
	<46A79705.5000106@cisco.com>
In-Reply-To: <46A79705.5000106@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Stewart:

>>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>>
> That's a big deal that may result in all kinds of changes - new
> LC comments, new discusses etc.  When you start this process
> you cannot be sure what you will get out.
>
> Why not continue with draft as it is and produce a second
> draft that explains how to run the ipfix protocol in this new
> transport mode.

We considered doing that, it's certainly not an approach to be taken lightly.
Consensus at the meeting was that we're blocked waiting
for the PSAMP Info draft, which will probably take a fair while yet.

The plan is to limit changes to *only* those addressed in Brian Trammell's
"SCTP change" draft, which we expect to minimise the chance of new
blocks appearing.  And last, since the Protocol documents is sitting
in the RFC Editor queue - i.e. it hasn't been published yet - we have
that (rare) chance to fix it in the original RFC, rather than forcing
everyone to refer to a 'changes' RFC as well as a Protocol RFC.

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 17:46:46 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDogp-0005vp-73; Wed, 25 Jul 2007 17:46:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDogn-0005vf-Q3
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:46:37 -0400
Received: from larry.its.auckland.ac.nz ([130.216.12.34]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDogl-0005R0-K6
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:46:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 94BF118401;
	Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id zJW-RKhiHc5l; Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 79FF9183DE;
	Thu, 26 Jul 2007 09:46:30 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PLkTsN025343; Thu, 26 Jul 2007 09:46:29 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PLkSWx025341; 
	Thu, 26 Jul 2007 09:46:28 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-325e.ietf69.org (dhcp-325e.ietf69.org [130.129.50.94])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 09:46:28 +1200
Message-ID: <20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 09:46:28 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: stbryant@cisco.com
Subject: Re: [IPFIX] *Proposed* new work items
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
	<46A79705.5000106@cisco.com>
In-Reply-To: <46A79705.5000106@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Stewart:

>>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>>
> That's a big deal that may result in all kinds of changes - new
> LC comments, new discusses etc.  When you start this process
> you cannot be sure what you will get out.
>
> Why not continue with draft as it is and produce a second
> draft that explains how to run the ipfix protocol in this new
> transport mode.

We considered doing that, it's certainly not an approach to be taken lightly.
Consensus at the meeting was that we're blocked waiting
for the PSAMP Info draft, which will probably take a fair while yet.

The plan is to limit changes to *only* those addressed in Brian Trammell's
"SCTP change" draft, which we expect to minimise the chance of new
blocks appearing.  And last, since the Protocol documents is sitting
in the RFC Editor queue - i.e. it hasn't been published yet - we have
that (rare) chance to fix it in the original RFC, rather than forcing
everyone to refer to a 'changes' RFC as well as a Protocol RFC.

Cheers, Nevil

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 17:54:18 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDooD-0003ca-SZ; Wed, 25 Jul 2007 17:54:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDooD-0003bI-77
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:54:17 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDooC-0002Kq-ND
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:54:17 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 23:54:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items for IPFIX:
	draft-boschi-ipfix-extended-type-00.txt
Date: Wed, 25 Jul 2007 23:53:49 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B74DF2@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A79705.5000106@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items for IPFIX:
	draft-boschi-ipfix-extended-type-00.txt
Thread-Index: AcfO6iBZlo4oE8alTXiupw5nPp89cgAGSApw
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
	<46A79705.5000106@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: <stbryant@cisco.com>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>
X-OriginalArrivalTime: 25 Jul 2007 21:54:07.0031 (UTC)
	FILETIME=[52DCE470:01C7CF06]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Bryan,

As discussed after the meeting yesterday, I consider that the need of =
tagging the datatypes (tables of sections '3.2.  =
informationElementSemanticType' and  '3.3 =
informationElementStorageType') must be addressed through the adding of =
new information elements in the IPFIX Info model IANA registry.


Regards
Emile

> -----Message d'origine-----
> De=A0: Stewart Bryant [mailto:stbryant@cisco.com]
> Envoy=E9=A0: mercredi 25 juillet 2007 20:32
> =C0=A0: Nevil Brownlee
> Cc=A0: ipfix@ietf.org
> Objet=A0: Re: [IPFIX] *Proposed* new work items for IPFIX
>=20
> Nevil Brownlee wrote:
> >
> > Hi all:
> >
> >
> >
> > 0. Remove SCTP stream restrictions in Protocol Document.
> >   Agreed: WG needs to do this, as soon as possible.
> >   Procedure: Call protocol document back from RFC EDitor Queue.
> >      make changes (only those needed for SCTP Stream use),
> >      and consequent changes to Implementation Guidelines and
> >      Testing drafts.
> >      re-run WG Last Call and IETF Last Call, resubmit to IESG.
> >
> That's a big deal that may result in all kinds of changes - new
> LC comments, new discusses etc.  When you start this process
> you cannot be sure what you will get out.
>=20
> Why not continue with draft as it is and produce a second
> draft that explains how to run the ipfix protocol in this new
> transport mode.
>=20
>=20
>=20
> Stewart
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 17:54:18 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDooD-0003ca-SZ; Wed, 25 Jul 2007 17:54:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDooD-0003bI-77
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:54:17 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDooC-0002Kq-ND
	for ipfix@ietf.org; Wed, 25 Jul 2007 17:54:17 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jul 2007 23:54:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items for IPFIX:
	draft-boschi-ipfix-extended-type-00.txt
Date: Wed, 25 Jul 2007 23:53:49 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B74DF2@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A79705.5000106@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items for IPFIX:
	draft-boschi-ipfix-extended-type-00.txt
Thread-Index: AcfO6iBZlo4oE8alTXiupw5nPp89cgAGSApw
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz>
	<46A79705.5000106@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: <stbryant@cisco.com>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>
X-OriginalArrivalTime: 25 Jul 2007 21:54:07.0031 (UTC)
	FILETIME=[52DCE470:01C7CF06]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Bryan,

As discussed after the meeting yesterday, I consider that the need of =
tagging the datatypes (tables of sections '3.2.  =
informationElementSemanticType' and  '3.3 =
informationElementStorageType') must be addressed through the adding of =
new information elements in the IPFIX Info model IANA registry.


Regards
Emile

> -----Message d'origine-----
> De=A0: Stewart Bryant [mailto:stbryant@cisco.com]
> Envoy=E9=A0: mercredi 25 juillet 2007 20:32
> =C0=A0: Nevil Brownlee
> Cc=A0: ipfix@ietf.org
> Objet=A0: Re: [IPFIX] *Proposed* new work items for IPFIX
>=20
> Nevil Brownlee wrote:
> >
> > Hi all:
> >
> >
> >
> > 0. Remove SCTP stream restrictions in Protocol Document.
> >   Agreed: WG needs to do this, as soon as possible.
> >   Procedure: Call protocol document back from RFC EDitor Queue.
> >      make changes (only those needed for SCTP Stream use),
> >      and consequent changes to Implementation Guidelines and
> >      Testing drafts.
> >      re-run WG Last Call and IETF Last Call, resubmit to IESG.
> >
> That's a big deal that may result in all kinds of changes - new
> LC comments, new discusses etc.  When you start this process
> you cannot be sure what you will get out.
>=20
> Why not continue with draft as it is and produce a second
> draft that explains how to run the ipfix protocol in this new
> transport mode.
>=20
>=20
>=20
> Stewart
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 18:08:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDp1o-0004oY-UD; Wed, 25 Jul 2007 18:08:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDp1n-0004oL-O0
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:08:19 -0400
Received: from moe.its.auckland.ac.nz ([130.216.12.35]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDp1m-0005q1-RC
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:08:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id F2828480441
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id j5eINvQQij0r for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id CEDBA48043D
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PM8GNU031580 for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PM8GaX031579
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:08:16 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-325e.ietf69.org (dhcp-325e.ietf69.org [130.129.50.94])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 10:08:16 +1200
Message-ID: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 10:08:16 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Subject: [IPFIX] *Proposed* new work items, take two
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi again all:

Here's a slightly improved, slightly clearer, version of my earlier posting.

Cheers, Nevil

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IPFIX: Proposal for new work
       Based on discussion at IETF 69, Chicago

For IPFIX mailing list, we suggest that items 1-6
(above the --- line) be adopted as new WG work items.
Please comment by 6 Aug 07 <<<<
Also, we need reviewers; please fill in and email back the
questionnaire form below!!

0. Remove SCTP stream restrictions in Protocol Document.
   Agreed: WG needs to do this, as soon as possible.
   Procedure:
    - Call the protocol draft out of the RFC EDitor Queue
    - Make changes (only those needed for SCTP Stream use),
      issue a revised draft
    - Run a short (1 week) WG last Call
    - Run a short (2 weeks, it's a Standards Track draft) IETF Last Call
    - Send draft back to RFC for evalkuatio
    - IESG sends it back to the RFC Editor Queue
   Assuming that all goes well, we estimate all that will take
   6~8 weeks.  By then we expect the PSAMP Info draft to have
   progressed so that it will be in the RFC Editor Queue too!
    - Corresponding changes to Implementation Guidelines and
      Testing drafts will also be needed, they will be made
      in the next revisions of both these drafts

1. Configuration Data Model (Gerhard Muenz)
   Agreed: Important to WG, not clear what protocol would be needed.
   Proposal: (a) Develop Configuration Info Model as a WG item,
       in English (and also an XML version) - Standards Track RFC.
       (b) Consider what protocol would be best for IPFIX Configuration.
           Requirements RFC?      Milestones: WG LC before IETF 71

2. SCTP Per-Stream Draft (Benoit Claise)
   Agreed: Needs to be explored, as a possible protocol option.
   Procedure: Make this a WG item, as Experimental RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

3. File Format (Brian Trammel)
   Agreed: WG item, as soon as possible.
   Procedure: Make this a WG item, as an Informational RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

For items 0 to 4 above, we'd like to make a list of several committed
reviewers for each. Please help me with this by filling in and 
returning the form below

IPFIX work item Reviewers
-------------------------

Name: _____________________________

I will review documents for the following items:
(put a 'y' in the boxes on the next line)

0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]

Email this form to nevil@auckland.ac.nz -- thankyou !

-----------------------------------------------------------------------

5. IPFIX Mediation (Atayushi Kobayashi)
   Needed by (at least) two large operators.
   Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
   Possible future WG item, continue discussion on mailing list.

6. Order of Information Elements (Irino)
   Interesting, need more people to measure possible efficiency gain.
   Would this be better as an individual draft?

7. Flow Sampling (Tanja Zseby)
   Early stage so far, comments/participation encouraged.

=======================================================================

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 18:08:22 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDp1o-0004oY-UD; Wed, 25 Jul 2007 18:08:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDp1n-0004oL-O0
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:08:19 -0400
Received: from moe.its.auckland.ac.nz ([130.216.12.35]
	helo=mailhost.auckland.ac.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDp1m-0005q1-RC
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:08:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id F2828480441
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id j5eINvQQij0r for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (motoko.itss.auckland.ac.nz
	[130.216.191.146])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id CEDBA48043D
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200 (NZST)
Received: from motoko.itss.auckland.ac.nz (localhost.localdomain [127.0.0.1])
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1) with ESMTP id
	l6PM8GNU031580 for <ipfix@ietf.org>; Thu, 26 Jul 2007 10:08:16 +1200
Received: (from apache@localhost)
	by motoko.itss.auckland.ac.nz (8.13.1/8.13.1/Submit) id l6PM8GaX031579
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:08:16 +1200
X-Authentication-Warning: motoko.itss.auckland.ac.nz: apache set sender to
	nevil@auckland.ac.nz using -f
Received: from dhcp-325e.ietf69.org (dhcp-325e.ietf69.org [130.129.50.94])
	by webmail.auckland.ac.nz (Horde MIME library) with HTTP;
	Thu, 26 Jul 2007 10:08:16 +1200
Message-ID: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Date: Thu, 26 Jul 2007 10:08:16 +1200
From: Nevil Brownlee <nevil@auckland.ac.nz>
To: ipfix@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Subject: [IPFIX] *Proposed* new work items, take two
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi again all:

Here's a slightly improved, slightly clearer, version of my earlier posting.

Cheers, Nevil

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IPFIX: Proposal for new work
       Based on discussion at IETF 69, Chicago

For IPFIX mailing list, we suggest that items 1-6
(above the --- line) be adopted as new WG work items.
Please comment by 6 Aug 07 <<<<
Also, we need reviewers; please fill in and email back the
questionnaire form below!!

0. Remove SCTP stream restrictions in Protocol Document.
   Agreed: WG needs to do this, as soon as possible.
   Procedure:
    - Call the protocol draft out of the RFC EDitor Queue
    - Make changes (only those needed for SCTP Stream use),
      issue a revised draft
    - Run a short (1 week) WG last Call
    - Run a short (2 weeks, it's a Standards Track draft) IETF Last Call
    - Send draft back to RFC for evalkuatio
    - IESG sends it back to the RFC Editor Queue
   Assuming that all goes well, we estimate all that will take
   6~8 weeks.  By then we expect the PSAMP Info draft to have
   progressed so that it will be in the RFC Editor Queue too!
    - Corresponding changes to Implementation Guidelines and
      Testing drafts will also be needed, they will be made
      in the next revisions of both these drafts

1. Configuration Data Model (Gerhard Muenz)
   Agreed: Important to WG, not clear what protocol would be needed.
   Proposal: (a) Develop Configuration Info Model as a WG item,
       in English (and also an XML version) - Standards Track RFC.
       (b) Consider what protocol would be best for IPFIX Configuration.
           Requirements RFC?      Milestones: WG LC before IETF 71

2. SCTP Per-Stream Draft (Benoit Claise)
   Agreed: Needs to be explored, as a possible protocol option.
   Procedure: Make this a WG item, as Experimental RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

3. File Format (Brian Trammel)
   Agreed: WG item, as soon as possible.
   Procedure: Make this a WG item, as an Informational RFC.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

For items 0 to 4 above, we'd like to make a list of several committed
reviewers for each. Please help me with this by filling in and 
returning the form below

IPFIX work item Reviewers
-------------------------

Name: _____________________________

I will review documents for the following items:
(put a 'y' in the boxes on the next line)

0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]

Email this form to nevil@auckland.ac.nz -- thankyou !

-----------------------------------------------------------------------

5. IPFIX Mediation (Atayushi Kobayashi)
   Needed by (at least) two large operators.
   Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
   Possible future WG item, continue discussion on mailing list.

6. Order of Information Elements (Irino)
   Interesting, need more people to measure possible efficiency gain.
   Would this be better as an individual draft?

7. Flow Sampling (Tanja Zseby)
   Early stage so far, comments/participation encouraged.

=======================================================================

-----------------------------------------------------------------------
  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

-----------------------------------------------------------------------
This mail sent through University of Auckland http://www.auckland.ac.nz


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 18:39:26 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDpVu-0001R4-2q; Wed, 25 Jul 2007 18:39:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDpVs-0001Qz-NE
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:39:24 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDpVq-0006Ls-3e
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:39:24 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 00:39:20 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOJtp0aQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,581,1175464800"; 
	d="scan'208"; a="149008204:sNHT69602738"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6PMdK9w008250; 
	Thu, 26 Jul 2007 00:39:20 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6PMdFkt014054; 
	Wed, 25 Jul 2007 22:39:19 GMT
Received: from [10.82.224.137] (rtp-vpn1-137.cisco.com [10.82.224.137])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id XAA08530;
	Wed, 25 Jul 2007 23:39:12 +0100 (BST)
Message-ID: <46A7D10F.3050509@cisco.com>
Date: Wed, 25 Jul 2007 23:39:11 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>, ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=63086; t=1185403160;
	x=1186267160; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Review=3A=20draft-kobayashi-ipfix-mediator-model-00
	|Sender:=20; bh=0TCkKYFNZQbrrRBxcgebznpYwSyCZIOKvfeGydwCJqA=;
	b=d6C4t2p5JFSMKC0WC2mOsisjg/FtiI5YnMA1fjDS2Z/9s65QwDSxtL9ykeRcUTzJ2u8FPgA8
	OQ/q0Z06s+0+uge6ZfF0ZxBZIxtulblXgfZl9XUduQCMUJaMC2kQckde;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e260d807a1c823f4aad7720bec8178b4
Cc: 
Subject: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Please see my comments inline.


> IPFIX Working Group                                         A. Kobayashi
> Internet-Draft                                              K. Ishibashi
> Intended status: Informational                                 T. Kondoh
> Expires: December 25, 2007                                   NTT PF Lab.
>                                                             D. Matsubara
>                                                                  Hitachi
>                                                            June 23, 2007
> 
> 
>                   Reference Model for IPFIX Mediators
>               draft-kobayashi-ipfix-mediator-model-00.txt
> 
> Status of this Memo
> 
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
> 
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
> 
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
> 
>    This Internet-Draft will expire on December 25, 2007.
> 
> Copyright Notice
> 
>    Copyright (C) The IETF Trust (2007).
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 1]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Abstract
> 
>    An IPFIX Mediator is an intermediate node between IPFIX devices and

"devices" -> "Exporting Processes"

>    traffic collectors.  This node acts as an IPFIX proxy, IPFIX

"traffic collectors" -> "IPFIX Collecting Processes".

"This node" -> "A mediator"

>    firewall, and IPFIX concentrator.  An IPFIX Mediator mediates the
>    IPFIX protocol using several functions.  That enables the traffic
>    monitoring system to become a high-capacity system and accommodate a
>    variety of traffic monitoring methods.  This document describes each
>    function that is provided by IPFIX Mediators and the method of
>    handling the Flow Records of each function.  In addition, this
>    describes the model of the solution scenario using IPFIX Mediator.

It's unclear what this last line means.

> 
> 
> Table of Contents
> 
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
>    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
>    3.  Internal Components Model  . . . . . . . . . . . . . . . . . .  8
>      3.1.  Collecting Process . . . . . . . . . . . . . . . . . . . .  8
>      3.2.  Metering Process . . . . . . . . . . . . . . . . . . . . .  9
>        3.2.1.  Selection Process  . . . . . . . . . . . . . . . . . .  9
>        3.2.2.  Aggregation Process  . . . . . . . . . . . . . . . . .  9
>        3.2.3.  Modification Process . . . . . . . . . . . . . . . . . 10
>      3.3.  Exporting Process  . . . . . . . . . . . . . . . . . . . . 12
>      3.4.  Storing Process  . . . . . . . . . . . . . . . . . . . . . 12
>    4.  IPFIX Protocol Considerations  . . . . . . . . . . . . . . . . 14
>      4.1.  Export Time Issue  . . . . . . . . . . . . . . . . . . . . 14
>      4.2.  Observation Domain ID Management . . . . . . . . . . . . . 14
>      4.3.  Template Management  . . . . . . . . . . . . . . . . . . . 14
>      4.4.  Transport Session Management . . . . . . . . . . . . . . . 15
>      4.5.  Option Template Management . . . . . . . . . . . . . . . . 15
>      4.6.  Reporting of Exporter Information  . . . . . . . . . . . . 15
>    5.  Solution Scenarios with IPFIX Mediators  . . . . . . . . . . . 16
>      5.1.  Flexible Aggregation . . . . . . . . . . . . . . . . . . . 16
>      5.2.  Distributed Aggregation  . . . . . . . . . . . . . . . . . 16
>      5.3.  Duplication of Flow Records  . . . . . . . . . . . . . . . 17
>      5.4.  Distribution of Flow Records . . . . . . . . . . . . . . . 18
>      5.5.  Extraction of Suspicious Flow  . . . . . . . . . . . . . . 19
>    6.  Mediator Option Template Presentation  . . . . . . . . . . . . 20
>      6.1.  Exporter Information Option Template . . . . . . . . . . . 20
>      6.2.  Usage of Scope Field . . . . . . . . . . . . . . . . . . . 22
>    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
>    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
>    9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
>      9.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
>      9.2.  Informative References . . . . . . . . . . . . . . . . . . 26
>    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
>    Intellectual Property and Copyright Statements . . . . . . . . . . 28
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 2]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 1.  Introduction
> 
>    Several problems regarding traffic monitoring have occurred in
>    several networks, as follows.

Can you cite some references for this?

> 
>    o  Scalability of collector on large-scale networks
> 
>       As the sizes of networks become larger, the number of Flow Records
>       becomes greater.  Large numbers of Flow Records have been
>       burdening management networks and the collecting process.
>       Maintaining scalability is difficult as a particular network
>       grows.  Generally, network operations need to monitor overall
>       wide-scale traffic behavior and investigate detailed traffic
>       information when traffic incidents happen.  Meeting these
>       requirements seems to be difficult for a single collector node
>       because of large numbers of Flow Records.
> 
>    o  Handling multifaceted network environment
> 
>       On the other hand, networks such as IPv4, IPv6, and VPN on MPLS
>       have recently become more multifaceted.  These sorts of Flow

What do you mean by "multifaceted"?

>       Records need to be analyzed separately from a different
>       perspective.  However, handling them separately without improving
>       the capability of the Collector is difficult.
> 
>    o  Exchanging traffic information between different networks
> 
>       Traffic information is considered to be necessary for ISP network
>       providers as well as each customer.  To that end, the network
>       provider needs to export specified Flow Records while avoiding
>       privacy violations.  In addition, exchanging traffic information
>       between the associated networks could be necessary when traffic
>       incidents happen.  In that case, the Flow Records should be
>       checked according to the service provider's policy before
>       exporting.  Therefore, Flow Records exported from Exporter
>       directly without modification can not be fed each customer or

"can not be fed *to* each customer"

>       associated network operators without modification.
> 
>    IPFIX Mediators enable us to overcome these problems by preprocessing
>    Flow Records.  By defining IPFIX Mediators, we can take increasing
>    advantage of an extensive template format, and handle Flow Records in
>    accordance with our preference.  This document describes some
>    solutions using IPFIX Mediators that solve these problems and
>    components that are needed in the internal process.
> 
>    The IPFIX Mediator, which is located between one or more Exporting
>    Processes and one or more Collecting Processes, has a main function
>    for handling Flow Records.  That function stores original Flow
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 3]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    Records and mediates them.  In addition, renewed Flow Records are

It's worth defining what mediation is.

Also, what are "renewed Flow Records"?

>    generated and distributed to an appropriate Collector or traffic
>    analyzer in accordance with flow content.

Must the mediator understand the content? eg, what about Enterprise 
Specific elements?

>    The internal model of a Mediator is composed of Collecting Processes,
>    Metering Processes, and Exporting Processes.  IPFIX Mediator acts as
>    a Collector by receiving Flow Records, and it acts as an Exporter by
>    sending Flow Records.  This dual-role architecture enables cascading
>    Mediators and building a combination of several solutions.
> 
>    This document describes a model of a solution scenario by using IPFIX
>    Mediator and its key component.
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in [RFC2119].
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 4]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 2.  Terminology
> 
>    The definitions of basic IPFIX and PSAMP terms are identical with
>    those in [I-D.ietf-psamp-framework], [RFC3917],
>    [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info], and
>    [I-D.ietf-ipfix-architecture].  Other than the above terminology, the
>    following terminology related to IPFIX Mediator is used in this
>    document.  Therefore, the terms defined in the IPFIX terminology are
>    capitalized in this document.
> 
>    IPFIX Mediator
> 
>       An IPFIX Mediator hosts at least one pair of Exporting Process and
>       Collecting Process.  An IPFIX Mediator may have the Metering

"at least one Exporting Process and one Collecting Process".

>       Process and Storing Process as optional.  An IPFIX Proxy, an IPFIX

"may optionally have Metering Processes and Storing Processes".

>       Firewall and an IPFIX concentrator are one node of IPFIX
>       Mediators.

This last line is unclear.

> 
>    Original Exporter
> 
>       An Original Exporter hosts Observation Points where IP packets can
>       be observed.
> 
>    IPFIX Proxy
> 
>       An IPFIX Proxy acts as a proxy for Original Exporter, which hosts

"Exporters"

>       Observation Points.  An IPFIX Proxy may receive Flow Records from
>       one or multiple Exporting Processes, and send them to one or
>       multiple Collecting Processes.  An IPFIX Proxy does not send the
>       information about an Original Exporter to the Collector to act as
>       an Original Exporter.

This last line is unclear.

> 
>    IPFIX Firewall
> 
>       An IPFIX Firewall exports the Flow Records to a different network
>       domain at the edge of the self-network domain.  From the
>       Collector's point of view, an IPFIX Firewall acts as an Original
>       Exporter, just like an IPFIX Proxy.  In addition, an IPFIX
>       Firewall reviews whether received Flow Records are passed forward
>       to the Collector to hide the network topology or privacy
>       information.

Does it block records, or modify them? eg, does it anonymise them?

> 
>    Metering Process
> 
>       The Metering Process in IPFIX Mediators can be considered the
>       partial Metering Process separated from the Metering Process in
>       the Original Exporter.  The Metering Process in IPFIX Mediators
>       consists of a set of subprocesses that includes the Selection
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 5]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       Process, the Aggregation Process and the Modification Process.
>       The Metering Process generates the final Flow Records that should
>       be exported.
> 
>    Selection Process
> 
>       The Selection Process in an IPFIX Mediator is similar to that of
>       PSAMP Devices, which is described in [I-D.ietf-psamp-framework].
>       However, the Selection Process in an IPFIX Mediator differs from
>       the following functions.  The Selection Process in PSAMP Devices
>       has two types of selection functions: Filtering and Sampling.  In
>       addition, the filtering function has two types of filtering
>       methods: field-match filtering and hash-based selection.  The
>       Selection Process in an IPFIX Mediator has only the field-match
>       filtering functions.  This filtering function selects Flow Records
>       based on Flow Record content.  The Selection Process is one of the
>       subprocesses in the Metering Process.
> 
>    Aggregation Process
> 
>       The Aggregation Process creates aggregated Flow Records from
>       inputted Flow Records, in accordance with aggregation rules that
>       are described in [I-D.dressler-ipfix-aggregation].  The
>       Aggregation Process is one of the subprocesses in the Metering
>       Process.
> 
>    Modification Process
> 
>       The Modification Process carries out the addition, deletion, and
>       modification of the Information Elements included in inputted Flow
>       Records.  The Modification Process adds Information Elements like
>       derived packet properties that canot be extracted in the Original
>       Exporter.  Information Elements related to derived packet
>       properties are described in [I-D.ietf-ipfix-info].  In addition,
>       the Modification Process modifies the values of the specific
>       Information Element.  For example, the modification of values is

"the values of specific Information Elements"

>       like anonymizing some Information Elements to avoid violating
>       privacy.  The Modification Process deletes some Information
>       Elements included in inputted Flow Records.  The Modification
>       Process is one of the subprocesses in the Metering Process.

- and presumably this is a key part of a firewall?

> 
>    Storing Process
> 
>       The Storing Process selects specified Information Elements
>       according to the storing rules, and then stores inputted Flow
>       Records in a storage system such as a database or flat-file
>       system.  Information Elements are specified in storing rules.  In
>       addition, the Observation Domain ID and Export Time in the header
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 6]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       of IPFIX messages are specified in the storing rules.

How does information get *out* of the Storing Process?

> 
>    Distribute Function
> 
>       The Distribute Function distributes final Flow Records based on
>       the Flow content.  The final Flow Records are handled by the
>       Exporting Process to export them to Collector.  Each classified
>       Flow Record is exported to each Collector.

To all collectors, or to a subset?

> 
>    Observation Domain ID
> 
>       An IPFIX Mediator doesn't host the Observation Point and
>       Observation Domain.  Though, the Observation Domain ID in IPFIX
>       header sent by IPFIX Mediator also indicates the largest set of
>       Observation Points in the Original Exporter, but this value does
>       not indicate the physical entity of the Original Exporter.  If
>       inputted Flow Records are aggregated in the Metering Process, the
>       Observation Domain ID value in IPFIX header SHOULD be 0.

I think only if the mediator is spoofing the original source exorter. 
Arguably a whole new set of Observation Domain values applies on the 
mediation device.

>    Transport Session Information
> 
>       In SCTP, the Transport Session Information is the SCTP
>       association.  In TCP and UDP, the Transport Session Information
>       corresponds to a 5 tuple {exporter IP address, collector IP
>       address, exporter transport port, collector transport port,
>       transport protocol}.  In IPFIX Mediator, the Collecting Process
>       manages this information.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 7]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 3.  Internal Components Model
> 
>    The following figure indicates four components (Collecting Process,
>    Metering Process, Exporting Process, and Storing Process) within the
>    IPFIX Mediator that are referred to in [RFC3917].  The Metering
>    Process can have one or multiple subprocesses.  These subprocesses
>    are the Selection Process, Aggregation Process, and Modification
>    Process that can be connected to each other in any sequence defined
>    by the user.  The Metering Process and Storing Process are options.
> 
> 
>      +--------------------------------------------------------------+
>      |                        IPFIX Mediator                        |
>      | .----------.                                     .---------. |
>      | |          |  .-------------------------------.  |         | |
>      | |Collecting|  |        Metering Process       |  |Exporting| |
>      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
>      | |          |-->|sub    |->|sub    |->|sub    |-->|         | |
>    IPFIX          |  ||process|  |process|  |process||  |         |IPFIX
>    --> |          |  ||#1     |  |#2     |  |#3     ||  |         |-->
>      | |          |  |'-------'  '-------'  '-------'|  |         | |
>      | |          |  '-------------------------------'  |         | |
>      | |          |------------------------------------>|         | |
>      | |          |  .-------.                          |         | |
>      | |          |->|Storing|                          |         | |
>      | |          |  |Process|                          |         | |
>      | |          |  '-------'                          |         | |
>      | '----------'                                     '---------' |
>      +--------------------------------------------------------------+

I think any of the metering sub-processes should be able to send data to 
the storing process. Also, the Exporting process may send data there too 
(consider Brian's file draft). Finally, there should be a route *out* of 
the storing process - either to the outside, and/or to the Metering 
Process, and/or to the Exporting Process.


>    Figure A: Key components within IPFIX Mediator.
> 
>    Each process is associated with a common identifier in the IPFIX
>    Mediator.  This method is similar to PSAMP associations in
>    [I-D.ietf-psamp-sample-tech].
> 
> 3.1.  Collecting Process
> 
>    This process receives Flow Records from the previous Exporter.  The
>    instance of this process is created according to the IPFIX session.
>    This process has functions that are described in
>    [I-D.ietf-ipfix-protocol].  The Collecting Process also forwards
>    received Flow Records with IPFIX header information and Transport
>    Session Information to multiple Metering Processes or Storing
>    Processes.  In other words, Flow Records can be duplicated by
>    forwarding several Metering Processes.  In addition, the Collecting

Or Exporting Processes.

>    Process can directly forward Flow Records to Exporting Process.
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 8]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 3.2.  Metering Process
> 
>    This process generates the renewed Flow Records from inputted Flow
>    Records with received IPFIX header information, such as "Export Time"
>    and "Observation Domain ID".  This process hosts the several
>    subprocesses.  The processing order of these functions, which could
>    be located by user definitions, would lead to different renewed Flow
>    Records.
> 
> 3.2.1.  Selection Process
> 
>    This process decides whether each Flow Record passes through to the
>    next process.  Theprocess has a filtering function and selects Flow

Typo, "Theprocess".

>    Records that are matched under given conditions.  Prior to receiving
>    Flow Records, this process has instruction pattern data that are
>    defined by the user, which specifies how the Flow Records are treated
>    by this process.  If the value of some Information Elements in the
>    Flow Record match the instruction pattern, this process selects Flow
>    Records with all fields and forwards these Flow Records to the next
>    process.  For example, this process selects the Flow Records that are
>    included in the specified destination IP address.
> 
> 3.2.2.  Aggregation Process

As a general question, is it valid to aggregate fields which were not 
originally key fields?

> 
>    This process gathers Flow Records within a given time interval and
>    then distinguishes Flow Records that have common properties.  If
>    values of a given key field are the same, that means these Flow
>    Records have common properties.  This process merges Flow Records
>    that have a common property and creates an aggregated Flow Record.
>    Therefore, for example, aggregated Flow Records have an aggregation
>    counter that indicates the number of packets.  These functions are
>    defined in accordance with the IPFIX aggregation rule in
>    [I-D.dressler-ipfix-aggregation].
> 
>    The process has instructions that are user defined prior to receiving
>    Flow Records.  The process indicates the Information Elements that
>    should become aggregated flow keys and other Information Elements
>    that should be kept or discarded.  In addition, these instruction
>    rules include Information Elements that should be added to aggregated
>    Flow Records.  The aggregated Flow Records may need to complement
>    information that is discarded during the aggregation process.  They
>    help the Collector to analyze aggregated Flow Records.  For example,
>    these Information Elements correspond to "averageActiveTime",
>    "synCount", and "flowCount" elements, as follows.
> 
>    o  averageActiveTime
> 
>       This Information Element indicates average time in milliseconds of
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 9]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       difference between flow start time and end time of each flow
>       included in the aggregated flow.  This Information Element is
>       created from the flow time stamp Information Elements.  There are
>       "flowStartSeconds", "flowEndSeconds", "flowStartMilliSeconds",
>       "flowEndMilliSeconds", "flowStartSysUpTime", and
>       "flowEndSysUpTime".  Moreover, "minimumActiveTime" and
>       "maxmumActiveTime" might be considered in addition to the element.
> 
>    o  synCount
> 
>       This Information Elements the number of Flow Records that have
>       "tcpControlBits" which the SYN bit sets to 1 in an aggregated
>       flow.  Using this element, we can determine the number of SYN
>       packets throughout the network.  Moreover, "ackCount", "finCount",
>       "pshCount", "urgCount", and "rstCount" might be considered in
>       addition to this element.
> 
>    o  flowCount
> 
>       This Information Element is the number of Flow Records included in
>       the aggregated flow.
> 
> 3.2.3.  Modification Process
> 
>    This process modifies the received Flow Records.  This process can
>    add the new Information Elements, delete included Information
>    Elements, or modify the value of included Information Elements, as
>    follows.  If this process modify the original template, it SHOULD
>    revise the received "flowKeyIndicator".
> 
>    Addition of new Information Element
> 
>       This function adds specified Information Elements into the
>       inputted Flow Records.  The values of Information Elements are
>       extracted by searching some database based on the inputted content
>       of Flow Records.  The added Information Elements and used
>       Information Elements are configured according to instructions by
>       the user to obtain the value.  The method to obtain the value from
>       some Information Elements is outside the scope of this document.
> 
>       The IPFIX Mediator instead of the Original Exporter adds a derived
>       packet property parameter, which is useful for the traffic
>       monitoring technique.  Doing that can compensate for the inability
>       of some Exporters to add a derived packet property parameter.
>       Hereby, the Collector does not need to recognize the difference
>       between implementations of routers from several vendors.  For
>       example, the addition of "bgpNextHop{IPv4|IPv6}Address" and
>       "bgpCommunity" Information Elements is useful for making a traffic
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 10]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       matrix that covers the whole network domain. "bgpNextHop{IPv4|
>       IPv6}Address" can indicate the egress router of some network
>       domain.  In addition, "bgpCommunity" can indicate the same group
>       of destination or source IP addresses.  This value can be given by
>       looking for the BGP route database based on the destination or
>       source IP address.  In addition, "mplsVpnRouteDistinguisher",
>       which can not be extracted from the core router in MPLS networks,
>       indicates the customer's identification.  We can monitor the
>       traffic behavior per customer by adding
>       "mplsVpnRouteDistinguisher" to the Flow Records.  This value can
>       be given by looking for the BGP route database based on the
>       "mplsTopLabelStackSection" and "mplsTopLabel{IPv4|IPv6}Address".
> 
>    Deletion of Information Element
> 
>       This function deletes specified Information Elements according to
>       the instructions that are configured by the user, which indicate
>       whether an Information Element should be removed.  Hiding network
>       topology information and private information by using this
>       function is possible.
> 
>       In the case of exchanging Flow Records with different network
>       domains or customers, this function can avoid making a
>       vulnerability by deleting unnecessary Information Elements.  By
>       deleting unnecessary Information Elements, this function can hide
>       the network topology and another customer's information.  In
>       particular, "ipNextHopIP{v4|v6}Address", "bgpNextHopIP{v4|
>       v6}Address", and "bgp{Next|Prev}AdjacentAsNumber" correspond to
>       network topology information.  In addition, MPLS-related
>       Information Elements, such as "mplsLabelStackSection", that are
>       useless for customers might be removed in the case of feeding the
>       Flow Records to VPN customers.
> 
>    Modification of the value of Information Element
> 
>       This function modifies the value of specified Information Elements
>       according to instructions configured by the user.
> 
>       For example, this function enables us to overwrite private
>       information with zeros or the maximum value.  In particular, IP
>       address and port number is sensitive private information.  In the
>       case of monitoring traffic trends and traffic engineering, these
>       Information Elements are not essential factors for those purposes.
>       In that case, modification anonymizes the relevant Information
>       Elements to prevent a violation of privacy.  If modification can
>       anonymize some Information Elements, it might need to report which
>       Information Elements are anonymized.  For example,
>       "anonymizationIndicator" indicates which Information Elements have
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 11]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>       The anonymization method is outside the scope of this document.

Why would we not just modify the template and remove these Information 
Elements?

> 
> 3.3.  Exporting Process
> 
>    This process forwards Flow Records to the next Collector.  These
>    processes manage the reporting template and make an IPFIX datagram.
> 
>    In addition, this process has the Distribution Function as an option.
>    If this function is enabled, this process distributes Flow Records
>    based on Flow content and then exports each classified Flow Record to
>    each Collector.
> 
>    The Exporting Process distributes Flow Records on the basis of the
>    peering AS, as shown in the following figure.  Each classified Flow

Peer AS in the incoming data, or on the Exporting side? Is BGP required?

Surely this would/should be user configurable?

>    Record is exported to a dedicated Collector on the basis of the
>    Peering AS.
> 
>      +-------------------------------------------+
>      | IPFIX Mediator               .----------. |
>      |                              |Exporting | |
>      |                              |Process   | |
>      |   .----------.  .---------.  |          | | PeerAS#100
>  Flow -->|Collecting|->|Metering |----->/------------> Collector#A
>  Records |Process   |  |Process  |  |   |      | | PeerAS#200
>      |   '----------'  '---------'  |   /------------> Collector#B
>      |                              |   |      | | PeerAS#300
>      |                              |   /------------> Collector#C
>      |                              |   |      | | PeerAS#400
>      |                              |   /------------> Collector#D
>      |                              |          | |
>      |                              '----------' |
>      +-------------------------------------------+
> 
>  Figure B: Exporting each classified Flow Record to dedicated Collector.
> 
> 3.4.  Storing Process
> 
>    This process selects specified Information Elements using the storing
>    instruction from the inputted Flow Records.  Prior to receiving Flow

What is the "storing instruction" ?

>    Records, this process has instructions that are configured by the
>    user, which indicate whether each field should be stored or
>    discarded.  The field modifier indicates "keep" or "discard", which
>    is similar to the instruction of the aggregation process.  The field
>    modifier specifies how these Information Elements are treated by the
>    process.  This field modifier is applied to Information Elements
>    within Flow Record and IPFIX header, such as "Observation Domain ID"
>    and "Export time".  This header information MAY be used when IPFIX
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 12]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    datagrams are made of past Flow Records.
> 
>    When another node retrieves past Flow Records, we can consider

How does it retrieve them?

>    several specifications.  One solution is that another node gets a
>    specified flat file from a Mediator and decodes that flat file by
>    itself.  Other solutions are that another node sends out the query
>    command to the IPFIX Mediator through XML-RPC, SNMP, or NETCONF, and
>    then the IPFIX Mediator exports the specified past Flow Records.
>    This function is outside the scope of this document.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 13]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 4.  IPFIX Protocol Considerations
> 
>    This section describes IPFIX protocol considerations with regard to
>    IPFIX Mediator.
> 
> 4.1.  Export Time Issue
> 
>    If the Exporting Process writes the "Export Time" of the IPFIX
>    message when an IPFIX message leaves, an IPFIX Mediator needs to
>    compensate for the delta time Information Elements contained in each

"the" -> "any"

>    Flow Record.  An IPFIX Proxy SHOULD reuse the "Export Time" of

"SHOULD" -> "MUST"

>    received IPFIX messages from the Original Exporter.
> 
> 4.2.  Observation Domain ID Management
> 
>    To comply with the IPFIX protocol the Observation Domain ID value is
>    RECOMMENDED to be assigned uniquely per IPFIX Mediator.  In addition,
>    Observation Domain ID SHOULD be 0 when IPFIX Mediator exports
>    aggregated Flow Records and cannot manage the specific Observation
>    Domain ID of the Original Exporter.  If an IPFIX Proxy relays an
>    IPFIX datagram from a transport session to a transport session, IPFIX
>    Proxy does not need to overwrite the Observation Domain ID with
>    another value.  If an IPFIX Proxy relays an IPFIX datagram from
>    multiple transport sessions to a single ransport session, IPFIX Proxy
>    needs to overwrite the Observation Domain ID.  In that case, IPFIX
>    Proxy assigns the Observation Domain ID based on received Transport
>    Session Information and the original Observation Domain ID.  The
>    renewed Observation Domain ID SHOULD be managed using the received
>    Transport Session Information and original Observation Domain ID.
>    This linkage information is available for overwriting the scope field
>    of the option template.
> 
> 4.3.  Template Management
> 
>    The template ID of a generated template SHOULD be unique on the basis

"Template". Please be sure to capitalise IPFIX terminology!

>    of the Observation Domain ID assigned by an IPFIX Mediator.  The
>    template ID needs to be unique on the basis of IPFIX Mediator when
>    the Observation Domain ID is 0.  If the IPFIX Mediator overwrites the
>    received template ID to relay a received template or modified
>    template, the renewed template ID SHOULD be managed using received
>    Transport Session Information and received Observation Domain ID.
>    This linkage information is available for overwriting scope field of
>    an option template and template handling.  If IPFIX Mediator receives
>    a "template withdraw message", it SHOULD modify this message to
>    indicate relevant templates, and send "template withdraw message".
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 14]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 4.4.  Transport Session Management
> 
>    Each session of the Collecting Process and Exporting Process should
>    operate independently.  Even if one session is reset, the status of
>    the other session is kept current.  However, templates for resetting
>    collecting session SHOULD be withdrawn for the exporting session.
> 
> 4.5.  Option Template Management
> 
>    IPFIX Mediator MUST check whether the scope field is applicable, if
>    received Data Records associated Options templates are exported.  If
>    an IPFIX Mediator rewrites the Observation Domain ID or template ID,
>    these values included in scope fields SHOULD be rewritten before
>    exporting.  Instead of exporting the Options Template Records and
>    associated Data Records, Information Elements exported using the
>    Options template Record from the Original Exporter, such as sampling
>    rate or sampling method, could be merged in a Flow Record in an IPFIX
>    Mediator.  In that case, IPFIX Mediator MUST modify the relevant
>    Template Record.  Several sorts of received statistics Options
>    Template Records and associated Data Records could be exported in
>    different ways as other templates.  In IPFIX Proxy, the Data Record
>    associated by statistics Options Template Records can be exported
>    after merging its counter.  In addition, statistics Options Template
>    Records and associated Data Records can be exported by indicating the
>    source of the statistics data as a scope field instead of merging the
>    counter.  This method is described in Section 6.  The user policy
>    determines whether IPFIX Mediator and the above methods should export
>    Option Templates Records and associated Data Records.
> 
> 4.6.  Reporting of Exporter Information
> 
>    Reporting of Exporter Information, such as Exporter IP address, is

Surely that's a loss of privacy?

>    useful to identify the Original Exporter.  There are various methods
>    as follows.  An IPFIX Mediator can directly merge Exporter
>    Information into Flow Records or use Options Templates described in
>    Section 6.  If an IPFIX Mediator received fields related to the
>    Exporter information, IPFIX Mediator SHOULD NOT rewrite its own
>    previous Exporter information.  The IPFIX Mediator can append its own
>    previous Exporter Information instead of rewriting.  In the
>    Collecting Process, the order of the Exporter information means the
>    Original Exporter and the route of IPFIX Mediator.  These methods
>    defined by user policy determine whether IPFIX Mediator should report
>    that information has been exported

Some text seems to be missing here?

> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 15]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 5.  Solution Scenarios with IPFIX Mediators
> 
> 5.1.  Flexible Aggregation
> 
>    An IPFIX Mediator can aggregate Flow Records in the same manner as
>    that of IPFIX concentrator and reduce the number of Flow Records
>    received by a traffic collector.
> 
>    The following figure indicates a cascade connection of IPFIX
>    Mediators.  If a Collector measures a traffic matrix to obtain
>    traffic demand, the Collector needs Flow Records of the whole network
>    domain, but does not need detailed Flow Records.  In the first step,
>    a Mediator receives Flow Records from IPFIX Devices and then creates

"a first level Mediator"

>    aggregated low-level Flow Records.  For example, this step is prefix
>    mask aggregation.  Next, the Mediator receives aggregated Flow

"Next, a second level Mediator"

>    Records and aggregates them further.  For example, the second step is
>    the aggregation of the BGP next-hop address and exporter address.
>    After this, the collector receives high-level aggregated Flow Records
>    and then stores them.  This method enables step-by-step aggregation
>    of Flow Records without overloading a single node.
> 
>    .--------.     .--------.
>    |IPFIX   |     |IPFIX   |
>    |router#1|---->|Mediator|---.
>    |        |     |*1      |   |
>    '--------'     '--------'   |    .--------.     .---------.
>                                '--->|IPFIX   |     |Traffic  |
>    .--------.     .--------.   .--->|Mediator|---->|Collector|
>    |IPFIX   |     |IPFIX   |   |    |*2      |     |         |
>    |router#2|---->|Mediator|---'    '--------'     '---------'
>    |        |     |*1      |
>    '--------'     '--------'
> 
>    Figure C: Flexible Aggregation with cascading IPFIX Mediators.
> 
> 5.2.  Distributed Aggregation
> 
>    When the network is used globally, the distances between PoPs become
>    longer, and the maintenance of a dedicated management network is very
>    expensive.  Therefore, the huge number of Flow Records has burdened
>    the management networks of global ISPs.  If we place Mediators at
>    each PoP, the number of Flow Records exported from each PoP can be
>    reduced.  Mediators can minimize the number of Flow Records exported
>    to the Collector.  If the Collector needs detailed information, it
>    can retrieve Flow Records from Mediators that store original Flow
>    Records.
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 16]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    A management network of a global ISP is shown in the following
>    figure.  The Mediators are located at each PoP of the network, and
>    they collect Flow Records from routers in each PoP domain.  The
>    Mediator reduces the number of Flow Records by aggregating or
>    filtering, so this system reduces the load of a management network.
> 
>                 POP#Asia
>         .--------.
>       .--------. |      .---------.
>     .--------. | |----->|IPFIX    |
>     |IPFIX   | |------->|Mediator |----.
>     |router  |---'----->|#1       |    |
>     |#1      |-'        '---------'    |
>     '--------'                         |
>                                        |
>                 POP#America            |
>         .--------.                     |
>       .--------. |      .---------.    |     .---------.
>     .--------. | |----->|IPFIX    |    '---->|Traffic  |
>     |IPFIX   | |------->|Mediator |--------->|Collector|
>     |router  |---'----->|#2       |    .---->|         |
>     |#4      |-'        '---------'    |     '---------'
>     '--------'                         |
>                                        |
>                 POP#Europe             |
>         .--------.                     |
>       .--------. |      .---------.    |
>     .--------. | |----->|IPFIX    |    |
>     |IPFIX   | |------->|Mediator |----'
>     |router  |---'----->|#3       |
>     |#7      |-'        '---------'
>     '--------'
> 
>    Figure D: Traffic monitoring architecture in global network.
> 
> 5.3.  Duplication of Flow Records
> 
>    An IPFIX Mediator duplicates Flow Records to achieve redundant
>    storage or utilizes them for several purposes.  The pair of
>    Collecting Process and Metering Processes is similar to the pair of
>    the Observation Point and Metering Process.  The Collecting Process
>    duplicates Flow records by forwarding them to the multi-Metering
>    Process.
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 17]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    Several departments in an ISP want to use the same traffic
>    information for each intended purpose.  For example, the network
>    design department measures the traffic matrix to obtain traffic
>    demand, and the customer service division uses traffic information
>    for performing accounting services for each customer while the
>    network operation center uses traffic information for trouble
>    shooting analysis.  That case is shown in the following figure.  An
>    IPFIX Mediator distributes Flow Records to several Collectors that
>    have the appropriate aggregated granularity.  In addition, when a NOC
>    conducts troubleshooting, past Flow Records from Mediators can be
>    retrieved.
> 
>                                          Measurement traffic matrix.
>    .--------.                               .---------.
>    |IPFIX   |                               |Traffic  |
>    |router#1|----.                    .---->|Collector|
>    |        |    |                    |     |#1       |
>    '--------'    |                    |     '---------'
>                  |                    |  Using Accounting info.
>    .--------.    |     .---------.    |     .---------.
>    |IPFIX   |    '---->|IPFIX    |----'     |Traffic  |
>    |router#2|--------->|Mediator |--------->|Collector|
>    |        |    .---->|         |----.     |#2       |
>    '--------'    |     '---------'    |     '---------'
>                  |                    |  Using Trouble shooting.
>    .--------.    |                    |     .---------.
>    |IPFIX   |    |                    |     |Traffic  |
>    |router#1|----'                    '---->|Collector|
>    |        |                               |#3       |
>    '--------'                               '---------'

The bottom left router should be "router#3"

> 
>    Figure E: Duplication of Flow Records for several purposes.
> 
> 5.4.  Distribution of Flow Records
> 
>    An IPFIX Mediator distributes Flow Records based on Flow Record

"MAY distribute"

>    content.  This function enables load balancing of Collector and
>    sorting Flow Records without extra Collector functions.  If the Flow
>    Records are used as accounting information, this solution is useful.

It's unclear to me what this means.

> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 18]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    When we disclose traffic information to each customer, security or

"we"? -> The mediator, perhaps?

>    the privacy policy should be considered.  In that case, IPFIX
>    Mediator hides private information about each customer.  For example,
>    Mediator distributes traffic information based on RD (Route
>    Distinguisher), egress IF, peering AS number, or BGP next hop, which
>    identify the customer.  In the following figure, the IPFIX Mediator
>    distributes Flow Records based on RD.  The system securely allows
>    each customer to access only their own records.
> 
>    .--------.                               .---------.
>    |IPFIX   |                               |Traffic  |
>    |router#1|----.                    .---->|Collector|<===> Customer#A
>    |        |    |                    |     |#1       |
>    '--------'    |                    |     '---------'
>                  |                 RD=100:1
>                  |     .---------.    |
>    .--------.    '---->|IPFIX    |----'     .---------.
>    |IPFIX   |          |Mediator | RD=100:2 |Traffic  |
>    |router#2|--------->|         |--------->|Collector|<===> Customer#B
>    |        |          |         |          |#2       |
>    '--------'    .---->|         |----.     '---------'
>                  |     '---------'    |
>                  |                 RD=100:3
>    .--------.    |                    |     .---------.
>    |IPFIX   |    |                    |     |Traffic  |
>    |router#1|----'                    '---->|Collector|<===> Customer#C
>    |        |                               |#3       |
>    '--------'                               '---------'
> 
>    Figure F: Distribution of Flow Records for each customer.
> 
> 5.5.  Extraction of Suspicious Flow
> 
>    An IPFIX Mediator performs filtering based on Flow Record content.
>    If the filter conditions are set depending on the suspicious flow as
>    follows, the Collector receives the specified suspicious flow and
>    detects an anomalous flow by simply monitoring the traffic volume of
>    each suspicious flow.
> 
>    o  TCP Flow Records whose "tcpControlBits" value is set to "null"
> 
>    o  TCP Flow Records whose "tcpControlBits" value is set to the SYN
>       bit only and the packet counter is only 1.

This will always happen for TCP flows of 1 or more packets. It might be 
suspicious if the count was still 1 after some time.

> 
>    o  ICMP Flow Records whose length is too long.
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 19]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 6.  Mediator Option Template Presentation
> 
>    This section describes Option Templates that are used by IPFIX
>    Mediators.
> 
> 6.1.  Exporter Information Option Template
> 
>    Each IPFIX Mediator and final destination Collector needs to know the
>    Original Exporter and route of IPFIX Mediators.  Therefore, each
>    IPFIX Mediator informs the next Collector about previous Exporter
>    information, which is the Exporter Information Option Template that
>    specified the Original Exporter and the route of the IPFIX Mediator.
>    The final destination Collector can recognize them by receiving this
>    template.  This template is composed of the following Information
>    Elements.
> 
>    o  exporter{IPv4|IPv6}Address
> 
>    o  collector{IPv4|IPv6}Address
> 
>    o  exporterTransportPort
> 
>    o  collectorTransportPort
> 
>    o  collectorTransportProtocol
> 
>    o  observationDomainId
> 
>    The Observation Domain ID of the Original Exporter or IPFIX Mediator
>    is identified by specifying exporter/collector Information Elements,
>    such as "collector{IPv4|IPv6}Address", "collectorTransportPort",
>    "collectorTransportProtocol", ,"exporter{IPv4|IPv6}Address",
>    "exporterTransportPort", and "observationDomainId".  The set of
>    "observationDomainId" and "templateId" or "observationDomainId" might
>    be used as a scope field.  Not all Information Elements are
>    necessary.  For example, the exporter{IPv4|IPv6}Address is necessary
>    to inform the next Collector the Original Exporter which created Flow
>    Records.  If the IPFIX Mediator receives this template, it SHOULD not
>    overwrite each field.  The IPFIX Mediator appends its own previous
>    Exporter information onto received Data Records specified by the
>    Exporter Option Template and sends that information to the Collector.
>    In this manner, the route is maintained until the final destination
>    Collector.
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 20]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    The following example describes the cascade connection of IPFIX
>    Mediators.  Each Mediator informs the next Collector about previous
>    Exporter information.
> 
>           Session#a            Session#b            Session#c
>    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
>    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
>    SrcPort:10       DstPort:20           DstPort:40
>    ODID:10          SrcPort:30           SrcPort:50
>                     ODID:0               ODID:0
> 
>    Figure G: Cascade connection of IPFIX Mediators.
> 
>    Mediator#1 or Mediator#2 sends a Data Record specified by the
>    Exporter Option Template.  The Data records are shown in Session#b or
>    Session#c, as follows.
> 
>    Session#b Data Record:
>       Field Count = 7
>       Scope Count = 1
>       templateId = XXX
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10

Could you use real-world values in the examples here and below?

P.

> 
>    Session#c Data Record:
>       Field Count = 13
>       Scope Count = 1
>       templateId = XXX
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10
>       exporterIPv4Address = 2.2.2.2
>       collectorIPv4Address = 3.3.3.3
>       collectorTransportProtocol = 16
>       exporterTransportPort = 30
>       collectorTransportPort = 40
>       observationDomainId = 0
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 21]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 6.2.  Usage of Scope Field
> 
>    An IPFIX Mediator needs to send forward a Options Template Records
>    and associated Data Records from the Original Exporter.  However,
>    IPFIX Mediator can not export an original Option Template Records and
>    associated Data Records without modification because changing a
>    session from an Exporting Process to a Collecting Process causes the
>    scope fields to become a useless value.  When an IPFIX Mediator
>    relays the Options Template Records that included Observation Domain
>    ID as a scope field and associated Data Records, an IPFIX Mediator
>    uses the Exporter Information Option Template.  The Options Template
>    Records that were created from an Original Exporter can use the
>    entire fields of the Exporter Information Option template as multiple
>    scope fields.  The Options Template Records that were created from
>    anIPFIX Mediator can uses the some fields of the Exporter Information
>    Option template as multiple scope fields.  An IPFIX Mediator needs to
>    modify the associated Data Records according to the modified Options
>    Template Record.  However, if each node uses another field except for
>    the Observation Domain ID as the scope, the scope field should be
>    considered on a case-by-case basis.
> 
>    The following example describes the cascade connection of IPFIX
>    Mediators.  Router#1 and Mediator#1 export the Metering Process
>    Statistics Option Template.
> 
> 
>           Session#a            Session#b            Session#c
>    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
>    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
>    SrcPort:10       DstPort:20           DstPort:40
>    ODID:10          SrcPort:30           SrcPort:50
>                     ODID:0               ODID:0
> 
>    Figure H: Cascade connection of IPFIX Mediators.
> 
>    Mediator#2 exports each Option Template and its Data Record with a
>    suitable scope.
> 
>    Session#c Metering Process Statistics Data Records from the Original
>    Exporter:
>       Field Count = 15
>       Scope Count = 12
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 22]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       exporterIPv4Address = 2.2.2.2
>       collectorIPv4Address = 3.3.3.3
>       collectorTransportProtocol = 16
>       exporterTransportPort = 30
>       collectorTransportPort = 40
>       observationDomainId = 0
>       exportedMessageTotalCount
>       exportedFlowTotalCount
>       exportedOctetTotalCount
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 23]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 7.  Security Considerations
> 
>    The IPFIX concentrator uses the IPFIX protocol.  Security
>    considerations about flow information are described in
>    [I-D.ietf-ipfix-protocol].
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 24]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 8.  IANA Considerations
> 
>    This document has no actions for IANA.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 25]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 9.  References
> 
> 9.1.  Normative References
> 
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
> 
> 9.2.  Informative References
> 
>    [I-D.dressler-ipfix-aggregation]
>               Dressler, F., Sommer, C., and G. Munz, "IPFIX
>               Aggregation", draft-dressler-ipfix-aggregation-03.txt
>               (work in progress) , June 2006.
> 
>    [I-D.ietf-ipfix-architecture]
>               Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
>               "Architecture for IP Flow Information Export",
>               draft-ietf-ipfix-architecture-12.txt(work in progress) ,
>               September 2006.
> 
>    [I-D.ietf-ipfix-info]
>               Quittek, J., Bryant, S., Claise, B., and J. Meyer,
>               "Information Model for IP Flow Information Export",
>               draft-ietf-ipfix-info-13.txt(work in progress) ,
>               June 2006.
> 
>    [I-D.ietf-ipfix-protocol]
>               Claise, B., "IPFIX Protocol Specification",
>               draft-ietf-ipfix-protocol-23 (work in progress) ,
>               October 2006.
> 
>    [I-D.ietf-psamp-framework]
>               Duffield, N., "A Framework for Packet Selection and
>               Reporting", draft-ietf-psamp-framework-10.txt ,
>               January 2005.
> 
>    [I-D.ietf-psamp-sample-tech]
>               Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
>               Raspall, "Sampling and Filtering Techniques for IP Packet
>               Selection", draft-ietf-psamp-sample-tech-07.txt ,
>               July 2005.
> 
>    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
>               "Requirements for IP Flow Information Export(IPFIX)",
>               October 2004.
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 26]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Authors' Addresses
> 
>    Atsushi Kobayashi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-3978
>    Email: akoba@nttv6.net
> 
> 
>    Keisuke Ishibashi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-3407
>    Email: ishibashi.keisuke@lab.ntt.co.jp
> 
> 
>    Kondoh Tsuyoshi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-2419
>    Email: kondoh.tsuyoshi@lab.ntt.co.jp
> 
> 
>    Daisuke Matsubara
>    Hitachi, Ltd., Central Reseach Laboratory
>    1-280 Higashi-koigakubo
>    Kokubunji-shi, Tokyo  185-8601
>    Japan
> 
>    Phone: +81-42-323-1111
>    Email: d-matuba@crl.hitachi.co.jp
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 27]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Full Copyright Statement
> 
>    Copyright (C) The IETF Trust (2007).
> 
>    This document is subject to the rights, licenses and restrictions
>    contained in BCP 78, and except as set forth therein, the authors
>    retain all their rights.
> 
>    This document and the information contained herein are provided on an
>    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Intellectual Property
> 
>    The IETF takes no position regarding the validity or scope of any
>    Intellectual Property Rights or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; nor does it represent that it has
>    made any independent effort to identify any such rights.  Information
>    on the procedures with respect to rights in RFC documents can be
>    found in BCP 78 and BCP 79.
> 
>    Copies of IPR disclosures made to the IETF Secretariat and any
>    assurances of licenses to be made available, or the result of an
>    attempt made to obtain a general license or permission for the use of
>    such proprietary rights by implementers or users of this
>    specification can be obtained from the IETF on-line IPR repository at
>    http://www.ietf.org/ipr.
> 
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights that may cover technology that may be required to implement
>    this standard.  Please address the information to the IETF at
>    ietf-ipr@ietf.org.
> 
> 
> Acknowledgment
> 
>    Funding for the RFC Editor function is provided by the IETF
>    Administrative Support Activity (IASA).
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 28]
> 

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 18:39:26 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDpVu-0001R4-2q; Wed, 25 Jul 2007 18:39:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDpVs-0001Qz-NE
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:39:24 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDpVq-0006Ls-3e
	for ipfix@ietf.org; Wed, 25 Jul 2007 18:39:24 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 00:39:20 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOJtp0aQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,581,1175464800"; 
	d="scan'208"; a="149008204:sNHT69602738"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6PMdK9w008250; 
	Thu, 26 Jul 2007 00:39:20 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6PMdFkt014054; 
	Wed, 25 Jul 2007 22:39:19 GMT
Received: from [10.82.224.137] (rtp-vpn1-137.cisco.com [10.82.224.137])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id XAA08530;
	Wed, 25 Jul 2007 23:39:12 +0100 (BST)
Message-ID: <46A7D10F.3050509@cisco.com>
Date: Wed, 25 Jul 2007 23:39:11 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>, ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=63086; t=1185403160;
	x=1186267160; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Review=3A=20draft-kobayashi-ipfix-mediator-model-00
	|Sender:=20; bh=0TCkKYFNZQbrrRBxcgebznpYwSyCZIOKvfeGydwCJqA=;
	b=d6C4t2p5JFSMKC0WC2mOsisjg/FtiI5YnMA1fjDS2Z/9s65QwDSxtL9ykeRcUTzJ2u8FPgA8
	OQ/q0Z06s+0+uge6ZfF0ZxBZIxtulblXgfZl9XUduQCMUJaMC2kQckde;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e260d807a1c823f4aad7720bec8178b4
Cc: 
Subject: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Please see my comments inline.


> IPFIX Working Group                                         A. Kobayashi
> Internet-Draft                                              K. Ishibashi
> Intended status: Informational                                 T. Kondoh
> Expires: December 25, 2007                                   NTT PF Lab.
>                                                             D. Matsubara
>                                                                  Hitachi
>                                                            June 23, 2007
> 
> 
>                   Reference Model for IPFIX Mediators
>               draft-kobayashi-ipfix-mediator-model-00.txt
> 
> Status of this Memo
> 
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
> 
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
> 
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
> 
>    This Internet-Draft will expire on December 25, 2007.
> 
> Copyright Notice
> 
>    Copyright (C) The IETF Trust (2007).
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 1]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Abstract
> 
>    An IPFIX Mediator is an intermediate node between IPFIX devices and

"devices" -> "Exporting Processes"

>    traffic collectors.  This node acts as an IPFIX proxy, IPFIX

"traffic collectors" -> "IPFIX Collecting Processes".

"This node" -> "A mediator"

>    firewall, and IPFIX concentrator.  An IPFIX Mediator mediates the
>    IPFIX protocol using several functions.  That enables the traffic
>    monitoring system to become a high-capacity system and accommodate a
>    variety of traffic monitoring methods.  This document describes each
>    function that is provided by IPFIX Mediators and the method of
>    handling the Flow Records of each function.  In addition, this
>    describes the model of the solution scenario using IPFIX Mediator.

It's unclear what this last line means.

> 
> 
> Table of Contents
> 
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
>    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
>    3.  Internal Components Model  . . . . . . . . . . . . . . . . . .  8
>      3.1.  Collecting Process . . . . . . . . . . . . . . . . . . . .  8
>      3.2.  Metering Process . . . . . . . . . . . . . . . . . . . . .  9
>        3.2.1.  Selection Process  . . . . . . . . . . . . . . . . . .  9
>        3.2.2.  Aggregation Process  . . . . . . . . . . . . . . . . .  9
>        3.2.3.  Modification Process . . . . . . . . . . . . . . . . . 10
>      3.3.  Exporting Process  . . . . . . . . . . . . . . . . . . . . 12
>      3.4.  Storing Process  . . . . . . . . . . . . . . . . . . . . . 12
>    4.  IPFIX Protocol Considerations  . . . . . . . . . . . . . . . . 14
>      4.1.  Export Time Issue  . . . . . . . . . . . . . . . . . . . . 14
>      4.2.  Observation Domain ID Management . . . . . . . . . . . . . 14
>      4.3.  Template Management  . . . . . . . . . . . . . . . . . . . 14
>      4.4.  Transport Session Management . . . . . . . . . . . . . . . 15
>      4.5.  Option Template Management . . . . . . . . . . . . . . . . 15
>      4.6.  Reporting of Exporter Information  . . . . . . . . . . . . 15
>    5.  Solution Scenarios with IPFIX Mediators  . . . . . . . . . . . 16
>      5.1.  Flexible Aggregation . . . . . . . . . . . . . . . . . . . 16
>      5.2.  Distributed Aggregation  . . . . . . . . . . . . . . . . . 16
>      5.3.  Duplication of Flow Records  . . . . . . . . . . . . . . . 17
>      5.4.  Distribution of Flow Records . . . . . . . . . . . . . . . 18
>      5.5.  Extraction of Suspicious Flow  . . . . . . . . . . . . . . 19
>    6.  Mediator Option Template Presentation  . . . . . . . . . . . . 20
>      6.1.  Exporter Information Option Template . . . . . . . . . . . 20
>      6.2.  Usage of Scope Field . . . . . . . . . . . . . . . . . . . 22
>    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
>    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
>    9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
>      9.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
>      9.2.  Informative References . . . . . . . . . . . . . . . . . . 26
>    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
>    Intellectual Property and Copyright Statements . . . . . . . . . . 28
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 2]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 1.  Introduction
> 
>    Several problems regarding traffic monitoring have occurred in
>    several networks, as follows.

Can you cite some references for this?

> 
>    o  Scalability of collector on large-scale networks
> 
>       As the sizes of networks become larger, the number of Flow Records
>       becomes greater.  Large numbers of Flow Records have been
>       burdening management networks and the collecting process.
>       Maintaining scalability is difficult as a particular network
>       grows.  Generally, network operations need to monitor overall
>       wide-scale traffic behavior and investigate detailed traffic
>       information when traffic incidents happen.  Meeting these
>       requirements seems to be difficult for a single collector node
>       because of large numbers of Flow Records.
> 
>    o  Handling multifaceted network environment
> 
>       On the other hand, networks such as IPv4, IPv6, and VPN on MPLS
>       have recently become more multifaceted.  These sorts of Flow

What do you mean by "multifaceted"?

>       Records need to be analyzed separately from a different
>       perspective.  However, handling them separately without improving
>       the capability of the Collector is difficult.
> 
>    o  Exchanging traffic information between different networks
> 
>       Traffic information is considered to be necessary for ISP network
>       providers as well as each customer.  To that end, the network
>       provider needs to export specified Flow Records while avoiding
>       privacy violations.  In addition, exchanging traffic information
>       between the associated networks could be necessary when traffic
>       incidents happen.  In that case, the Flow Records should be
>       checked according to the service provider's policy before
>       exporting.  Therefore, Flow Records exported from Exporter
>       directly without modification can not be fed each customer or

"can not be fed *to* each customer"

>       associated network operators without modification.
> 
>    IPFIX Mediators enable us to overcome these problems by preprocessing
>    Flow Records.  By defining IPFIX Mediators, we can take increasing
>    advantage of an extensive template format, and handle Flow Records in
>    accordance with our preference.  This document describes some
>    solutions using IPFIX Mediators that solve these problems and
>    components that are needed in the internal process.
> 
>    The IPFIX Mediator, which is located between one or more Exporting
>    Processes and one or more Collecting Processes, has a main function
>    for handling Flow Records.  That function stores original Flow
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 3]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    Records and mediates them.  In addition, renewed Flow Records are

It's worth defining what mediation is.

Also, what are "renewed Flow Records"?

>    generated and distributed to an appropriate Collector or traffic
>    analyzer in accordance with flow content.

Must the mediator understand the content? eg, what about Enterprise 
Specific elements?

>    The internal model of a Mediator is composed of Collecting Processes,
>    Metering Processes, and Exporting Processes.  IPFIX Mediator acts as
>    a Collector by receiving Flow Records, and it acts as an Exporter by
>    sending Flow Records.  This dual-role architecture enables cascading
>    Mediators and building a combination of several solutions.
> 
>    This document describes a model of a solution scenario by using IPFIX
>    Mediator and its key component.
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in [RFC2119].
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 4]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 2.  Terminology
> 
>    The definitions of basic IPFIX and PSAMP terms are identical with
>    those in [I-D.ietf-psamp-framework], [RFC3917],
>    [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info], and
>    [I-D.ietf-ipfix-architecture].  Other than the above terminology, the
>    following terminology related to IPFIX Mediator is used in this
>    document.  Therefore, the terms defined in the IPFIX terminology are
>    capitalized in this document.
> 
>    IPFIX Mediator
> 
>       An IPFIX Mediator hosts at least one pair of Exporting Process and
>       Collecting Process.  An IPFIX Mediator may have the Metering

"at least one Exporting Process and one Collecting Process".

>       Process and Storing Process as optional.  An IPFIX Proxy, an IPFIX

"may optionally have Metering Processes and Storing Processes".

>       Firewall and an IPFIX concentrator are one node of IPFIX
>       Mediators.

This last line is unclear.

> 
>    Original Exporter
> 
>       An Original Exporter hosts Observation Points where IP packets can
>       be observed.
> 
>    IPFIX Proxy
> 
>       An IPFIX Proxy acts as a proxy for Original Exporter, which hosts

"Exporters"

>       Observation Points.  An IPFIX Proxy may receive Flow Records from
>       one or multiple Exporting Processes, and send them to one or
>       multiple Collecting Processes.  An IPFIX Proxy does not send the
>       information about an Original Exporter to the Collector to act as
>       an Original Exporter.

This last line is unclear.

> 
>    IPFIX Firewall
> 
>       An IPFIX Firewall exports the Flow Records to a different network
>       domain at the edge of the self-network domain.  From the
>       Collector's point of view, an IPFIX Firewall acts as an Original
>       Exporter, just like an IPFIX Proxy.  In addition, an IPFIX
>       Firewall reviews whether received Flow Records are passed forward
>       to the Collector to hide the network topology or privacy
>       information.

Does it block records, or modify them? eg, does it anonymise them?

> 
>    Metering Process
> 
>       The Metering Process in IPFIX Mediators can be considered the
>       partial Metering Process separated from the Metering Process in
>       the Original Exporter.  The Metering Process in IPFIX Mediators
>       consists of a set of subprocesses that includes the Selection
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 5]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       Process, the Aggregation Process and the Modification Process.
>       The Metering Process generates the final Flow Records that should
>       be exported.
> 
>    Selection Process
> 
>       The Selection Process in an IPFIX Mediator is similar to that of
>       PSAMP Devices, which is described in [I-D.ietf-psamp-framework].
>       However, the Selection Process in an IPFIX Mediator differs from
>       the following functions.  The Selection Process in PSAMP Devices
>       has two types of selection functions: Filtering and Sampling.  In
>       addition, the filtering function has two types of filtering
>       methods: field-match filtering and hash-based selection.  The
>       Selection Process in an IPFIX Mediator has only the field-match
>       filtering functions.  This filtering function selects Flow Records
>       based on Flow Record content.  The Selection Process is one of the
>       subprocesses in the Metering Process.
> 
>    Aggregation Process
> 
>       The Aggregation Process creates aggregated Flow Records from
>       inputted Flow Records, in accordance with aggregation rules that
>       are described in [I-D.dressler-ipfix-aggregation].  The
>       Aggregation Process is one of the subprocesses in the Metering
>       Process.
> 
>    Modification Process
> 
>       The Modification Process carries out the addition, deletion, and
>       modification of the Information Elements included in inputted Flow
>       Records.  The Modification Process adds Information Elements like
>       derived packet properties that canot be extracted in the Original
>       Exporter.  Information Elements related to derived packet
>       properties are described in [I-D.ietf-ipfix-info].  In addition,
>       the Modification Process modifies the values of the specific
>       Information Element.  For example, the modification of values is

"the values of specific Information Elements"

>       like anonymizing some Information Elements to avoid violating
>       privacy.  The Modification Process deletes some Information
>       Elements included in inputted Flow Records.  The Modification
>       Process is one of the subprocesses in the Metering Process.

- and presumably this is a key part of a firewall?

> 
>    Storing Process
> 
>       The Storing Process selects specified Information Elements
>       according to the storing rules, and then stores inputted Flow
>       Records in a storage system such as a database or flat-file
>       system.  Information Elements are specified in storing rules.  In
>       addition, the Observation Domain ID and Export Time in the header
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 6]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       of IPFIX messages are specified in the storing rules.

How does information get *out* of the Storing Process?

> 
>    Distribute Function
> 
>       The Distribute Function distributes final Flow Records based on
>       the Flow content.  The final Flow Records are handled by the
>       Exporting Process to export them to Collector.  Each classified
>       Flow Record is exported to each Collector.

To all collectors, or to a subset?

> 
>    Observation Domain ID
> 
>       An IPFIX Mediator doesn't host the Observation Point and
>       Observation Domain.  Though, the Observation Domain ID in IPFIX
>       header sent by IPFIX Mediator also indicates the largest set of
>       Observation Points in the Original Exporter, but this value does
>       not indicate the physical entity of the Original Exporter.  If
>       inputted Flow Records are aggregated in the Metering Process, the
>       Observation Domain ID value in IPFIX header SHOULD be 0.

I think only if the mediator is spoofing the original source exorter. 
Arguably a whole new set of Observation Domain values applies on the 
mediation device.

>    Transport Session Information
> 
>       In SCTP, the Transport Session Information is the SCTP
>       association.  In TCP and UDP, the Transport Session Information
>       corresponds to a 5 tuple {exporter IP address, collector IP
>       address, exporter transport port, collector transport port,
>       transport protocol}.  In IPFIX Mediator, the Collecting Process
>       manages this information.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 7]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 3.  Internal Components Model
> 
>    The following figure indicates four components (Collecting Process,
>    Metering Process, Exporting Process, and Storing Process) within the
>    IPFIX Mediator that are referred to in [RFC3917].  The Metering
>    Process can have one or multiple subprocesses.  These subprocesses
>    are the Selection Process, Aggregation Process, and Modification
>    Process that can be connected to each other in any sequence defined
>    by the user.  The Metering Process and Storing Process are options.
> 
> 
>      +--------------------------------------------------------------+
>      |                        IPFIX Mediator                        |
>      | .----------.                                     .---------. |
>      | |          |  .-------------------------------.  |         | |
>      | |Collecting|  |        Metering Process       |  |Exporting| |
>      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
>      | |          |-->|sub    |->|sub    |->|sub    |-->|         | |
>    IPFIX          |  ||process|  |process|  |process||  |         |IPFIX
>    --> |          |  ||#1     |  |#2     |  |#3     ||  |         |-->
>      | |          |  |'-------'  '-------'  '-------'|  |         | |
>      | |          |  '-------------------------------'  |         | |
>      | |          |------------------------------------>|         | |
>      | |          |  .-------.                          |         | |
>      | |          |->|Storing|                          |         | |
>      | |          |  |Process|                          |         | |
>      | |          |  '-------'                          |         | |
>      | '----------'                                     '---------' |
>      +--------------------------------------------------------------+

I think any of the metering sub-processes should be able to send data to 
the storing process. Also, the Exporting process may send data there too 
(consider Brian's file draft). Finally, there should be a route *out* of 
the storing process - either to the outside, and/or to the Metering 
Process, and/or to the Exporting Process.


>    Figure A: Key components within IPFIX Mediator.
> 
>    Each process is associated with a common identifier in the IPFIX
>    Mediator.  This method is similar to PSAMP associations in
>    [I-D.ietf-psamp-sample-tech].
> 
> 3.1.  Collecting Process
> 
>    This process receives Flow Records from the previous Exporter.  The
>    instance of this process is created according to the IPFIX session.
>    This process has functions that are described in
>    [I-D.ietf-ipfix-protocol].  The Collecting Process also forwards
>    received Flow Records with IPFIX header information and Transport
>    Session Information to multiple Metering Processes or Storing
>    Processes.  In other words, Flow Records can be duplicated by
>    forwarding several Metering Processes.  In addition, the Collecting

Or Exporting Processes.

>    Process can directly forward Flow Records to Exporting Process.
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 8]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 3.2.  Metering Process
> 
>    This process generates the renewed Flow Records from inputted Flow
>    Records with received IPFIX header information, such as "Export Time"
>    and "Observation Domain ID".  This process hosts the several
>    subprocesses.  The processing order of these functions, which could
>    be located by user definitions, would lead to different renewed Flow
>    Records.
> 
> 3.2.1.  Selection Process
> 
>    This process decides whether each Flow Record passes through to the
>    next process.  Theprocess has a filtering function and selects Flow

Typo, "Theprocess".

>    Records that are matched under given conditions.  Prior to receiving
>    Flow Records, this process has instruction pattern data that are
>    defined by the user, which specifies how the Flow Records are treated
>    by this process.  If the value of some Information Elements in the
>    Flow Record match the instruction pattern, this process selects Flow
>    Records with all fields and forwards these Flow Records to the next
>    process.  For example, this process selects the Flow Records that are
>    included in the specified destination IP address.
> 
> 3.2.2.  Aggregation Process

As a general question, is it valid to aggregate fields which were not 
originally key fields?

> 
>    This process gathers Flow Records within a given time interval and
>    then distinguishes Flow Records that have common properties.  If
>    values of a given key field are the same, that means these Flow
>    Records have common properties.  This process merges Flow Records
>    that have a common property and creates an aggregated Flow Record.
>    Therefore, for example, aggregated Flow Records have an aggregation
>    counter that indicates the number of packets.  These functions are
>    defined in accordance with the IPFIX aggregation rule in
>    [I-D.dressler-ipfix-aggregation].
> 
>    The process has instructions that are user defined prior to receiving
>    Flow Records.  The process indicates the Information Elements that
>    should become aggregated flow keys and other Information Elements
>    that should be kept or discarded.  In addition, these instruction
>    rules include Information Elements that should be added to aggregated
>    Flow Records.  The aggregated Flow Records may need to complement
>    information that is discarded during the aggregation process.  They
>    help the Collector to analyze aggregated Flow Records.  For example,
>    these Information Elements correspond to "averageActiveTime",
>    "synCount", and "flowCount" elements, as follows.
> 
>    o  averageActiveTime
> 
>       This Information Element indicates average time in milliseconds of
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007               [Page 9]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       difference between flow start time and end time of each flow
>       included in the aggregated flow.  This Information Element is
>       created from the flow time stamp Information Elements.  There are
>       "flowStartSeconds", "flowEndSeconds", "flowStartMilliSeconds",
>       "flowEndMilliSeconds", "flowStartSysUpTime", and
>       "flowEndSysUpTime".  Moreover, "minimumActiveTime" and
>       "maxmumActiveTime" might be considered in addition to the element.
> 
>    o  synCount
> 
>       This Information Elements the number of Flow Records that have
>       "tcpControlBits" which the SYN bit sets to 1 in an aggregated
>       flow.  Using this element, we can determine the number of SYN
>       packets throughout the network.  Moreover, "ackCount", "finCount",
>       "pshCount", "urgCount", and "rstCount" might be considered in
>       addition to this element.
> 
>    o  flowCount
> 
>       This Information Element is the number of Flow Records included in
>       the aggregated flow.
> 
> 3.2.3.  Modification Process
> 
>    This process modifies the received Flow Records.  This process can
>    add the new Information Elements, delete included Information
>    Elements, or modify the value of included Information Elements, as
>    follows.  If this process modify the original template, it SHOULD
>    revise the received "flowKeyIndicator".
> 
>    Addition of new Information Element
> 
>       This function adds specified Information Elements into the
>       inputted Flow Records.  The values of Information Elements are
>       extracted by searching some database based on the inputted content
>       of Flow Records.  The added Information Elements and used
>       Information Elements are configured according to instructions by
>       the user to obtain the value.  The method to obtain the value from
>       some Information Elements is outside the scope of this document.
> 
>       The IPFIX Mediator instead of the Original Exporter adds a derived
>       packet property parameter, which is useful for the traffic
>       monitoring technique.  Doing that can compensate for the inability
>       of some Exporters to add a derived packet property parameter.
>       Hereby, the Collector does not need to recognize the difference
>       between implementations of routers from several vendors.  For
>       example, the addition of "bgpNextHop{IPv4|IPv6}Address" and
>       "bgpCommunity" Information Elements is useful for making a traffic
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 10]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       matrix that covers the whole network domain. "bgpNextHop{IPv4|
>       IPv6}Address" can indicate the egress router of some network
>       domain.  In addition, "bgpCommunity" can indicate the same group
>       of destination or source IP addresses.  This value can be given by
>       looking for the BGP route database based on the destination or
>       source IP address.  In addition, "mplsVpnRouteDistinguisher",
>       which can not be extracted from the core router in MPLS networks,
>       indicates the customer's identification.  We can monitor the
>       traffic behavior per customer by adding
>       "mplsVpnRouteDistinguisher" to the Flow Records.  This value can
>       be given by looking for the BGP route database based on the
>       "mplsTopLabelStackSection" and "mplsTopLabel{IPv4|IPv6}Address".
> 
>    Deletion of Information Element
> 
>       This function deletes specified Information Elements according to
>       the instructions that are configured by the user, which indicate
>       whether an Information Element should be removed.  Hiding network
>       topology information and private information by using this
>       function is possible.
> 
>       In the case of exchanging Flow Records with different network
>       domains or customers, this function can avoid making a
>       vulnerability by deleting unnecessary Information Elements.  By
>       deleting unnecessary Information Elements, this function can hide
>       the network topology and another customer's information.  In
>       particular, "ipNextHopIP{v4|v6}Address", "bgpNextHopIP{v4|
>       v6}Address", and "bgp{Next|Prev}AdjacentAsNumber" correspond to
>       network topology information.  In addition, MPLS-related
>       Information Elements, such as "mplsLabelStackSection", that are
>       useless for customers might be removed in the case of feeding the
>       Flow Records to VPN customers.
> 
>    Modification of the value of Information Element
> 
>       This function modifies the value of specified Information Elements
>       according to instructions configured by the user.
> 
>       For example, this function enables us to overwrite private
>       information with zeros or the maximum value.  In particular, IP
>       address and port number is sensitive private information.  In the
>       case of monitoring traffic trends and traffic engineering, these
>       Information Elements are not essential factors for those purposes.
>       In that case, modification anonymizes the relevant Information
>       Elements to prevent a violation of privacy.  If modification can
>       anonymize some Information Elements, it might need to report which
>       Information Elements are anonymized.  For example,
>       "anonymizationIndicator" indicates which Information Elements have
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 11]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>       The anonymization method is outside the scope of this document.

Why would we not just modify the template and remove these Information 
Elements?

> 
> 3.3.  Exporting Process
> 
>    This process forwards Flow Records to the next Collector.  These
>    processes manage the reporting template and make an IPFIX datagram.
> 
>    In addition, this process has the Distribution Function as an option.
>    If this function is enabled, this process distributes Flow Records
>    based on Flow content and then exports each classified Flow Record to
>    each Collector.
> 
>    The Exporting Process distributes Flow Records on the basis of the
>    peering AS, as shown in the following figure.  Each classified Flow

Peer AS in the incoming data, or on the Exporting side? Is BGP required?

Surely this would/should be user configurable?

>    Record is exported to a dedicated Collector on the basis of the
>    Peering AS.
> 
>      +-------------------------------------------+
>      | IPFIX Mediator               .----------. |
>      |                              |Exporting | |
>      |                              |Process   | |
>      |   .----------.  .---------.  |          | | PeerAS#100
>  Flow -->|Collecting|->|Metering |----->/------------> Collector#A
>  Records |Process   |  |Process  |  |   |      | | PeerAS#200
>      |   '----------'  '---------'  |   /------------> Collector#B
>      |                              |   |      | | PeerAS#300
>      |                              |   /------------> Collector#C
>      |                              |   |      | | PeerAS#400
>      |                              |   /------------> Collector#D
>      |                              |          | |
>      |                              '----------' |
>      +-------------------------------------------+
> 
>  Figure B: Exporting each classified Flow Record to dedicated Collector.
> 
> 3.4.  Storing Process
> 
>    This process selects specified Information Elements using the storing
>    instruction from the inputted Flow Records.  Prior to receiving Flow

What is the "storing instruction" ?

>    Records, this process has instructions that are configured by the
>    user, which indicate whether each field should be stored or
>    discarded.  The field modifier indicates "keep" or "discard", which
>    is similar to the instruction of the aggregation process.  The field
>    modifier specifies how these Information Elements are treated by the
>    process.  This field modifier is applied to Information Elements
>    within Flow Record and IPFIX header, such as "Observation Domain ID"
>    and "Export time".  This header information MAY be used when IPFIX
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 12]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    datagrams are made of past Flow Records.
> 
>    When another node retrieves past Flow Records, we can consider

How does it retrieve them?

>    several specifications.  One solution is that another node gets a
>    specified flat file from a Mediator and decodes that flat file by
>    itself.  Other solutions are that another node sends out the query
>    command to the IPFIX Mediator through XML-RPC, SNMP, or NETCONF, and
>    then the IPFIX Mediator exports the specified past Flow Records.
>    This function is outside the scope of this document.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 13]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 4.  IPFIX Protocol Considerations
> 
>    This section describes IPFIX protocol considerations with regard to
>    IPFIX Mediator.
> 
> 4.1.  Export Time Issue
> 
>    If the Exporting Process writes the "Export Time" of the IPFIX
>    message when an IPFIX message leaves, an IPFIX Mediator needs to
>    compensate for the delta time Information Elements contained in each

"the" -> "any"

>    Flow Record.  An IPFIX Proxy SHOULD reuse the "Export Time" of

"SHOULD" -> "MUST"

>    received IPFIX messages from the Original Exporter.
> 
> 4.2.  Observation Domain ID Management
> 
>    To comply with the IPFIX protocol the Observation Domain ID value is
>    RECOMMENDED to be assigned uniquely per IPFIX Mediator.  In addition,
>    Observation Domain ID SHOULD be 0 when IPFIX Mediator exports
>    aggregated Flow Records and cannot manage the specific Observation
>    Domain ID of the Original Exporter.  If an IPFIX Proxy relays an
>    IPFIX datagram from a transport session to a transport session, IPFIX
>    Proxy does not need to overwrite the Observation Domain ID with
>    another value.  If an IPFIX Proxy relays an IPFIX datagram from
>    multiple transport sessions to a single ransport session, IPFIX Proxy
>    needs to overwrite the Observation Domain ID.  In that case, IPFIX
>    Proxy assigns the Observation Domain ID based on received Transport
>    Session Information and the original Observation Domain ID.  The
>    renewed Observation Domain ID SHOULD be managed using the received
>    Transport Session Information and original Observation Domain ID.
>    This linkage information is available for overwriting the scope field
>    of the option template.
> 
> 4.3.  Template Management
> 
>    The template ID of a generated template SHOULD be unique on the basis

"Template". Please be sure to capitalise IPFIX terminology!

>    of the Observation Domain ID assigned by an IPFIX Mediator.  The
>    template ID needs to be unique on the basis of IPFIX Mediator when
>    the Observation Domain ID is 0.  If the IPFIX Mediator overwrites the
>    received template ID to relay a received template or modified
>    template, the renewed template ID SHOULD be managed using received
>    Transport Session Information and received Observation Domain ID.
>    This linkage information is available for overwriting scope field of
>    an option template and template handling.  If IPFIX Mediator receives
>    a "template withdraw message", it SHOULD modify this message to
>    indicate relevant templates, and send "template withdraw message".
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 14]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 4.4.  Transport Session Management
> 
>    Each session of the Collecting Process and Exporting Process should
>    operate independently.  Even if one session is reset, the status of
>    the other session is kept current.  However, templates for resetting
>    collecting session SHOULD be withdrawn for the exporting session.
> 
> 4.5.  Option Template Management
> 
>    IPFIX Mediator MUST check whether the scope field is applicable, if
>    received Data Records associated Options templates are exported.  If
>    an IPFIX Mediator rewrites the Observation Domain ID or template ID,
>    these values included in scope fields SHOULD be rewritten before
>    exporting.  Instead of exporting the Options Template Records and
>    associated Data Records, Information Elements exported using the
>    Options template Record from the Original Exporter, such as sampling
>    rate or sampling method, could be merged in a Flow Record in an IPFIX
>    Mediator.  In that case, IPFIX Mediator MUST modify the relevant
>    Template Record.  Several sorts of received statistics Options
>    Template Records and associated Data Records could be exported in
>    different ways as other templates.  In IPFIX Proxy, the Data Record
>    associated by statistics Options Template Records can be exported
>    after merging its counter.  In addition, statistics Options Template
>    Records and associated Data Records can be exported by indicating the
>    source of the statistics data as a scope field instead of merging the
>    counter.  This method is described in Section 6.  The user policy
>    determines whether IPFIX Mediator and the above methods should export
>    Option Templates Records and associated Data Records.
> 
> 4.6.  Reporting of Exporter Information
> 
>    Reporting of Exporter Information, such as Exporter IP address, is

Surely that's a loss of privacy?

>    useful to identify the Original Exporter.  There are various methods
>    as follows.  An IPFIX Mediator can directly merge Exporter
>    Information into Flow Records or use Options Templates described in
>    Section 6.  If an IPFIX Mediator received fields related to the
>    Exporter information, IPFIX Mediator SHOULD NOT rewrite its own
>    previous Exporter information.  The IPFIX Mediator can append its own
>    previous Exporter Information instead of rewriting.  In the
>    Collecting Process, the order of the Exporter information means the
>    Original Exporter and the route of IPFIX Mediator.  These methods
>    defined by user policy determine whether IPFIX Mediator should report
>    that information has been exported

Some text seems to be missing here?

> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 15]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 5.  Solution Scenarios with IPFIX Mediators
> 
> 5.1.  Flexible Aggregation
> 
>    An IPFIX Mediator can aggregate Flow Records in the same manner as
>    that of IPFIX concentrator and reduce the number of Flow Records
>    received by a traffic collector.
> 
>    The following figure indicates a cascade connection of IPFIX
>    Mediators.  If a Collector measures a traffic matrix to obtain
>    traffic demand, the Collector needs Flow Records of the whole network
>    domain, but does not need detailed Flow Records.  In the first step,
>    a Mediator receives Flow Records from IPFIX Devices and then creates

"a first level Mediator"

>    aggregated low-level Flow Records.  For example, this step is prefix
>    mask aggregation.  Next, the Mediator receives aggregated Flow

"Next, a second level Mediator"

>    Records and aggregates them further.  For example, the second step is
>    the aggregation of the BGP next-hop address and exporter address.
>    After this, the collector receives high-level aggregated Flow Records
>    and then stores them.  This method enables step-by-step aggregation
>    of Flow Records without overloading a single node.
> 
>    .--------.     .--------.
>    |IPFIX   |     |IPFIX   |
>    |router#1|---->|Mediator|---.
>    |        |     |*1      |   |
>    '--------'     '--------'   |    .--------.     .---------.
>                                '--->|IPFIX   |     |Traffic  |
>    .--------.     .--------.   .--->|Mediator|---->|Collector|
>    |IPFIX   |     |IPFIX   |   |    |*2      |     |         |
>    |router#2|---->|Mediator|---'    '--------'     '---------'
>    |        |     |*1      |
>    '--------'     '--------'
> 
>    Figure C: Flexible Aggregation with cascading IPFIX Mediators.
> 
> 5.2.  Distributed Aggregation
> 
>    When the network is used globally, the distances between PoPs become
>    longer, and the maintenance of a dedicated management network is very
>    expensive.  Therefore, the huge number of Flow Records has burdened
>    the management networks of global ISPs.  If we place Mediators at
>    each PoP, the number of Flow Records exported from each PoP can be
>    reduced.  Mediators can minimize the number of Flow Records exported
>    to the Collector.  If the Collector needs detailed information, it
>    can retrieve Flow Records from Mediators that store original Flow
>    Records.
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 16]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    A management network of a global ISP is shown in the following
>    figure.  The Mediators are located at each PoP of the network, and
>    they collect Flow Records from routers in each PoP domain.  The
>    Mediator reduces the number of Flow Records by aggregating or
>    filtering, so this system reduces the load of a management network.
> 
>                 POP#Asia
>         .--------.
>       .--------. |      .---------.
>     .--------. | |----->|IPFIX    |
>     |IPFIX   | |------->|Mediator |----.
>     |router  |---'----->|#1       |    |
>     |#1      |-'        '---------'    |
>     '--------'                         |
>                                        |
>                 POP#America            |
>         .--------.                     |
>       .--------. |      .---------.    |     .---------.
>     .--------. | |----->|IPFIX    |    '---->|Traffic  |
>     |IPFIX   | |------->|Mediator |--------->|Collector|
>     |router  |---'----->|#2       |    .---->|         |
>     |#4      |-'        '---------'    |     '---------'
>     '--------'                         |
>                                        |
>                 POP#Europe             |
>         .--------.                     |
>       .--------. |      .---------.    |
>     .--------. | |----->|IPFIX    |    |
>     |IPFIX   | |------->|Mediator |----'
>     |router  |---'----->|#3       |
>     |#7      |-'        '---------'
>     '--------'
> 
>    Figure D: Traffic monitoring architecture in global network.
> 
> 5.3.  Duplication of Flow Records
> 
>    An IPFIX Mediator duplicates Flow Records to achieve redundant
>    storage or utilizes them for several purposes.  The pair of
>    Collecting Process and Metering Processes is similar to the pair of
>    the Observation Point and Metering Process.  The Collecting Process
>    duplicates Flow records by forwarding them to the multi-Metering
>    Process.
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 17]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    Several departments in an ISP want to use the same traffic
>    information for each intended purpose.  For example, the network
>    design department measures the traffic matrix to obtain traffic
>    demand, and the customer service division uses traffic information
>    for performing accounting services for each customer while the
>    network operation center uses traffic information for trouble
>    shooting analysis.  That case is shown in the following figure.  An
>    IPFIX Mediator distributes Flow Records to several Collectors that
>    have the appropriate aggregated granularity.  In addition, when a NOC
>    conducts troubleshooting, past Flow Records from Mediators can be
>    retrieved.
> 
>                                          Measurement traffic matrix.
>    .--------.                               .---------.
>    |IPFIX   |                               |Traffic  |
>    |router#1|----.                    .---->|Collector|
>    |        |    |                    |     |#1       |
>    '--------'    |                    |     '---------'
>                  |                    |  Using Accounting info.
>    .--------.    |     .---------.    |     .---------.
>    |IPFIX   |    '---->|IPFIX    |----'     |Traffic  |
>    |router#2|--------->|Mediator |--------->|Collector|
>    |        |    .---->|         |----.     |#2       |
>    '--------'    |     '---------'    |     '---------'
>                  |                    |  Using Trouble shooting.
>    .--------.    |                    |     .---------.
>    |IPFIX   |    |                    |     |Traffic  |
>    |router#1|----'                    '---->|Collector|
>    |        |                               |#3       |
>    '--------'                               '---------'

The bottom left router should be "router#3"

> 
>    Figure E: Duplication of Flow Records for several purposes.
> 
> 5.4.  Distribution of Flow Records
> 
>    An IPFIX Mediator distributes Flow Records based on Flow Record

"MAY distribute"

>    content.  This function enables load balancing of Collector and
>    sorting Flow Records without extra Collector functions.  If the Flow
>    Records are used as accounting information, this solution is useful.

It's unclear to me what this means.

> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 18]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    When we disclose traffic information to each customer, security or

"we"? -> The mediator, perhaps?

>    the privacy policy should be considered.  In that case, IPFIX
>    Mediator hides private information about each customer.  For example,
>    Mediator distributes traffic information based on RD (Route
>    Distinguisher), egress IF, peering AS number, or BGP next hop, which
>    identify the customer.  In the following figure, the IPFIX Mediator
>    distributes Flow Records based on RD.  The system securely allows
>    each customer to access only their own records.
> 
>    .--------.                               .---------.
>    |IPFIX   |                               |Traffic  |
>    |router#1|----.                    .---->|Collector|<===> Customer#A
>    |        |    |                    |     |#1       |
>    '--------'    |                    |     '---------'
>                  |                 RD=100:1
>                  |     .---------.    |
>    .--------.    '---->|IPFIX    |----'     .---------.
>    |IPFIX   |          |Mediator | RD=100:2 |Traffic  |
>    |router#2|--------->|         |--------->|Collector|<===> Customer#B
>    |        |          |         |          |#2       |
>    '--------'    .---->|         |----.     '---------'
>                  |     '---------'    |
>                  |                 RD=100:3
>    .--------.    |                    |     .---------.
>    |IPFIX   |    |                    |     |Traffic  |
>    |router#1|----'                    '---->|Collector|<===> Customer#C
>    |        |                               |#3       |
>    '--------'                               '---------'
> 
>    Figure F: Distribution of Flow Records for each customer.
> 
> 5.5.  Extraction of Suspicious Flow
> 
>    An IPFIX Mediator performs filtering based on Flow Record content.
>    If the filter conditions are set depending on the suspicious flow as
>    follows, the Collector receives the specified suspicious flow and
>    detects an anomalous flow by simply monitoring the traffic volume of
>    each suspicious flow.
> 
>    o  TCP Flow Records whose "tcpControlBits" value is set to "null"
> 
>    o  TCP Flow Records whose "tcpControlBits" value is set to the SYN
>       bit only and the packet counter is only 1.

This will always happen for TCP flows of 1 or more packets. It might be 
suspicious if the count was still 1 after some time.

> 
>    o  ICMP Flow Records whose length is too long.
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 19]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 6.  Mediator Option Template Presentation
> 
>    This section describes Option Templates that are used by IPFIX
>    Mediators.
> 
> 6.1.  Exporter Information Option Template
> 
>    Each IPFIX Mediator and final destination Collector needs to know the
>    Original Exporter and route of IPFIX Mediators.  Therefore, each
>    IPFIX Mediator informs the next Collector about previous Exporter
>    information, which is the Exporter Information Option Template that
>    specified the Original Exporter and the route of the IPFIX Mediator.
>    The final destination Collector can recognize them by receiving this
>    template.  This template is composed of the following Information
>    Elements.
> 
>    o  exporter{IPv4|IPv6}Address
> 
>    o  collector{IPv4|IPv6}Address
> 
>    o  exporterTransportPort
> 
>    o  collectorTransportPort
> 
>    o  collectorTransportProtocol
> 
>    o  observationDomainId
> 
>    The Observation Domain ID of the Original Exporter or IPFIX Mediator
>    is identified by specifying exporter/collector Information Elements,
>    such as "collector{IPv4|IPv6}Address", "collectorTransportPort",
>    "collectorTransportProtocol", ,"exporter{IPv4|IPv6}Address",
>    "exporterTransportPort", and "observationDomainId".  The set of
>    "observationDomainId" and "templateId" or "observationDomainId" might
>    be used as a scope field.  Not all Information Elements are
>    necessary.  For example, the exporter{IPv4|IPv6}Address is necessary
>    to inform the next Collector the Original Exporter which created Flow
>    Records.  If the IPFIX Mediator receives this template, it SHOULD not
>    overwrite each field.  The IPFIX Mediator appends its own previous
>    Exporter information onto received Data Records specified by the
>    Exporter Option Template and sends that information to the Collector.
>    In this manner, the route is maintained until the final destination
>    Collector.
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 20]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>    The following example describes the cascade connection of IPFIX
>    Mediators.  Each Mediator informs the next Collector about previous
>    Exporter information.
> 
>           Session#a            Session#b            Session#c
>    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
>    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
>    SrcPort:10       DstPort:20           DstPort:40
>    ODID:10          SrcPort:30           SrcPort:50
>                     ODID:0               ODID:0
> 
>    Figure G: Cascade connection of IPFIX Mediators.
> 
>    Mediator#1 or Mediator#2 sends a Data Record specified by the
>    Exporter Option Template.  The Data records are shown in Session#b or
>    Session#c, as follows.
> 
>    Session#b Data Record:
>       Field Count = 7
>       Scope Count = 1
>       templateId = XXX
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10

Could you use real-world values in the examples here and below?

P.

> 
>    Session#c Data Record:
>       Field Count = 13
>       Scope Count = 1
>       templateId = XXX
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10
>       exporterIPv4Address = 2.2.2.2
>       collectorIPv4Address = 3.3.3.3
>       collectorTransportProtocol = 16
>       exporterTransportPort = 30
>       collectorTransportPort = 40
>       observationDomainId = 0
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 21]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 6.2.  Usage of Scope Field
> 
>    An IPFIX Mediator needs to send forward a Options Template Records
>    and associated Data Records from the Original Exporter.  However,
>    IPFIX Mediator can not export an original Option Template Records and
>    associated Data Records without modification because changing a
>    session from an Exporting Process to a Collecting Process causes the
>    scope fields to become a useless value.  When an IPFIX Mediator
>    relays the Options Template Records that included Observation Domain
>    ID as a scope field and associated Data Records, an IPFIX Mediator
>    uses the Exporter Information Option Template.  The Options Template
>    Records that were created from an Original Exporter can use the
>    entire fields of the Exporter Information Option template as multiple
>    scope fields.  The Options Template Records that were created from
>    anIPFIX Mediator can uses the some fields of the Exporter Information
>    Option template as multiple scope fields.  An IPFIX Mediator needs to
>    modify the associated Data Records according to the modified Options
>    Template Record.  However, if each node uses another field except for
>    the Observation Domain ID as the scope, the scope field should be
>    considered on a case-by-case basis.
> 
>    The following example describes the cascade connection of IPFIX
>    Mediators.  Router#1 and Mediator#1 export the Metering Process
>    Statistics Option Template.
> 
> 
>           Session#a            Session#b            Session#c
>    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
>    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
>    SrcPort:10       DstPort:20           DstPort:40
>    ODID:10          SrcPort:30           SrcPort:50
>                     ODID:0               ODID:0
> 
>    Figure H: Cascade connection of IPFIX Mediators.
> 
>    Mediator#2 exports each Option Template and its Data Record with a
>    suitable scope.
> 
>    Session#c Metering Process Statistics Data Records from the Original
>    Exporter:
>       Field Count = 15
>       Scope Count = 12
>       exporterIPv4Address = 1.1.1.1
>       collectorIPv4Address = 2.2.2.2
>       collectorTransportProtocol = 16
>       exporterTransportPort = 10
>       collectorTransportPort = 20
>       observationDomainId = 10
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 22]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
>       exporterIPv4Address = 2.2.2.2
>       collectorIPv4Address = 3.3.3.3
>       collectorTransportProtocol = 16
>       exporterTransportPort = 30
>       collectorTransportPort = 40
>       observationDomainId = 0
>       exportedMessageTotalCount
>       exportedFlowTotalCount
>       exportedOctetTotalCount
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 23]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 7.  Security Considerations
> 
>    The IPFIX concentrator uses the IPFIX protocol.  Security
>    considerations about flow information are described in
>    [I-D.ietf-ipfix-protocol].
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 24]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 8.  IANA Considerations
> 
>    This document has no actions for IANA.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 25]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> 9.  References
> 
> 9.1.  Normative References
> 
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
> 
> 9.2.  Informative References
> 
>    [I-D.dressler-ipfix-aggregation]
>               Dressler, F., Sommer, C., and G. Munz, "IPFIX
>               Aggregation", draft-dressler-ipfix-aggregation-03.txt
>               (work in progress) , June 2006.
> 
>    [I-D.ietf-ipfix-architecture]
>               Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
>               "Architecture for IP Flow Information Export",
>               draft-ietf-ipfix-architecture-12.txt(work in progress) ,
>               September 2006.
> 
>    [I-D.ietf-ipfix-info]
>               Quittek, J., Bryant, S., Claise, B., and J. Meyer,
>               "Information Model for IP Flow Information Export",
>               draft-ietf-ipfix-info-13.txt(work in progress) ,
>               June 2006.
> 
>    [I-D.ietf-ipfix-protocol]
>               Claise, B., "IPFIX Protocol Specification",
>               draft-ietf-ipfix-protocol-23 (work in progress) ,
>               October 2006.
> 
>    [I-D.ietf-psamp-framework]
>               Duffield, N., "A Framework for Packet Selection and
>               Reporting", draft-ietf-psamp-framework-10.txt ,
>               January 2005.
> 
>    [I-D.ietf-psamp-sample-tech]
>               Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
>               Raspall, "Sampling and Filtering Techniques for IP Packet
>               Selection", draft-ietf-psamp-sample-tech-07.txt ,
>               July 2005.
> 
>    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
>               "Requirements for IP Flow Information Export(IPFIX)",
>               October 2004.
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 26]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Authors' Addresses
> 
>    Atsushi Kobayashi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-3978
>    Email: akoba@nttv6.net
> 
> 
>    Keisuke Ishibashi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-3407
>    Email: ishibashi.keisuke@lab.ntt.co.jp
> 
> 
>    Kondoh Tsuyoshi
>    NTT Information Sharing Platform Laboratories
>    3-9-11 Midori-cho
>    Musashino-shi, Tokyo  180-8585
>    Japan
> 
>    Phone: +81-422-59-2419
>    Email: kondoh.tsuyoshi@lab.ntt.co.jp
> 
> 
>    Daisuke Matsubara
>    Hitachi, Ltd., Central Reseach Laboratory
>    1-280 Higashi-koigakubo
>    Kokubunji-shi, Tokyo  185-8601
>    Japan
> 
>    Phone: +81-42-323-1111
>    Email: d-matuba@crl.hitachi.co.jp
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 27]
> 
> Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> 
> 
> Full Copyright Statement
> 
>    Copyright (C) The IETF Trust (2007).
> 
>    This document is subject to the rights, licenses and restrictions
>    contained in BCP 78, and except as set forth therein, the authors
>    retain all their rights.
> 
>    This document and the information contained herein are provided on an
>    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Intellectual Property
> 
>    The IETF takes no position regarding the validity or scope of any
>    Intellectual Property Rights or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; nor does it represent that it has
>    made any independent effort to identify any such rights.  Information
>    on the procedures with respect to rights in RFC documents can be
>    found in BCP 78 and BCP 79.
> 
>    Copies of IPR disclosures made to the IETF Secretariat and any
>    assurances of licenses to be made available, or the result of an
>    attempt made to obtain a general license or permission for the use of
>    such proprietary rights by implementers or users of this
>    specification can be obtained from the IETF on-line IPR repository at
>    http://www.ietf.org/ipr.
> 
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights that may cover technology that may be required to implement
>    this standard.  Please address the information to the IETF at
>    ietf-ipr@ietf.org.
> 
> 
> Acknowledgment
> 
>    Funding for the RFC Editor function is provided by the IETF
>    Administrative Support Activity (IASA).
> 
> 
> 
> 
> 
> Kobayashi, et al.       Expires December 25, 2007              [Page 28]
> 

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 19:26:42 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDqFU-00046J-27; Wed, 25 Jul 2007 19:26:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDqFS-00046C-6f
	for ipfix@ietf.org; Wed, 25 Jul 2007 19:26:30 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDqFR-0003vI-Ej
	for ipfix@ietf.org; Wed, 25 Jul 2007 19:26:30 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 01:26:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items, take two
Date: Thu, 26 Jul 2007 01:26:06 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B74DF5@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items, take two
Thread-Index: AcfPCFJDudCDJPOSTsGRFBwWFGfZqgACJuZw
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Nevil Brownlee" <nevil@auckland.ac.nz>,
	<ipfix@ietf.org>
X-OriginalArrivalTime: 25 Jul 2007 23:26:09.0078 (UTC)
	FILETIME=[2E426560:01C7CF13]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Nevil,

Your choice might consider that items 3 and 4 don't received support any =
operators and that item 5 did.

Items 3, 4 and 5 provide good examples of mediator functions. So, in my =
opinion, the first step consists in writing a doc giving the =
requirements and the arch of a mediator.

Regards
Emile  =20

> -----Message d'origine-----
> De=A0: Nevil Brownlee [mailto:nevil@auckland.ac.nz]
> Envoy=E9=A0: jeudi 26 juillet 2007 00:08
> =C0=A0: ipfix@ietf.org
> Objet=A0: [IPFIX] *Proposed* new work items, take two
>=20
>=20
> Hi again all:
>=20
> Here's a slightly improved, slightly clearer, version of my earlier
> posting.
>=20
> Cheers, Nevil
>=20
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>=20
> IPFIX: Proposal for new work
>        Based on discussion at IETF 69, Chicago
>=20
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
>=20
> 0. Remove SCTP stream restrictions in Protocol Document.
>    Agreed: WG needs to do this, as soon as possible.
>    Procedure:
>     - Call the protocol draft out of the RFC EDitor Queue
>     - Make changes (only those needed for SCTP Stream use),
>       issue a revised draft
>     - Run a short (1 week) WG last Call
>     - Run a short (2 weeks, it's a Standards Track draft) IETF Last =
Call
>     - Send draft back to RFC for evalkuatio
>     - IESG sends it back to the RFC Editor Queue
>    Assuming that all goes well, we estimate all that will take
>    6~8 weeks.  By then we expect the PSAMP Info draft to have
>    progressed so that it will be in the RFC Editor Queue too!
>     - Corresponding changes to Implementation Guidelines and
>       Testing drafts will also be needed, they will be made
>       in the next revisions of both these drafts
>=20
> 1. Configuration Data Model (Gerhard Muenz)
>    Agreed: Important to WG, not clear what protocol would be needed.
>    Proposal: (a) Develop Configuration Info Model as a WG item,
>        in English (and also an XML version) - Standards Track RFC.
>        (b) Consider what protocol would be best for IPFIX =
Configuration.
>            Requirements RFC?      Milestones: WG LC before IETF 71
>=20
> 2. SCTP Per-Stream Draft (Benoit Claise)
>    Agreed: Needs to be explored, as a possible protocol option.
>    Procedure: Make this a WG item, as Experimental RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> 3. File Format (Brian Trammel)
>    Agreed: WG item, as soon as possible.
>    Procedure: Make this a WG item, as an Informational RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> For items 0 to 4 above, we'd like to make a list of several committed
> reviewers for each. Please help me with this by filling in and
> returning the form below
>=20
> IPFIX work item Reviewers
> -------------------------
>=20
> Name: _____________________________
>=20
> I will review documents for the following items:
> (put a 'y' in the boxes on the next line)
>=20
> 0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]
>=20
> Email this form to nevil@auckland.ac.nz -- thankyou !
>=20
> =
-----------------------------------------------------------------------
>=20
> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX =
Aggregation.
>    Possible future WG item, continue discussion on mailing list.
>=20
> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?
>=20
> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> =
-----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>=20
> =
-----------------------------------------------------------------------
> This mail sent through University of Auckland =
http://www.auckland.ac.nz
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 19:26:42 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDqFU-00046J-27; Wed, 25 Jul 2007 19:26:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDqFS-00046C-6f
	for ipfix@ietf.org; Wed, 25 Jul 2007 19:26:30 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDqFR-0003vI-Ej
	for ipfix@ietf.org; Wed, 25 Jul 2007 19:26:30 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 01:26:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items, take two
Date: Thu, 26 Jul 2007 01:26:06 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B74DF5@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items, take two
Thread-Index: AcfPCFJDudCDJPOSTsGRFBwWFGfZqgACJuZw
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Nevil Brownlee" <nevil@auckland.ac.nz>,
	<ipfix@ietf.org>
X-OriginalArrivalTime: 25 Jul 2007 23:26:09.0078 (UTC)
	FILETIME=[2E426560:01C7CF13]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Nevil,

Your choice might consider that items 3 and 4 don't received support any =
operators and that item 5 did.

Items 3, 4 and 5 provide good examples of mediator functions. So, in my =
opinion, the first step consists in writing a doc giving the =
requirements and the arch of a mediator.

Regards
Emile  =20

> -----Message d'origine-----
> De=A0: Nevil Brownlee [mailto:nevil@auckland.ac.nz]
> Envoy=E9=A0: jeudi 26 juillet 2007 00:08
> =C0=A0: ipfix@ietf.org
> Objet=A0: [IPFIX] *Proposed* new work items, take two
>=20
>=20
> Hi again all:
>=20
> Here's a slightly improved, slightly clearer, version of my earlier
> posting.
>=20
> Cheers, Nevil
>=20
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>=20
> IPFIX: Proposal for new work
>        Based on discussion at IETF 69, Chicago
>=20
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
>=20
> 0. Remove SCTP stream restrictions in Protocol Document.
>    Agreed: WG needs to do this, as soon as possible.
>    Procedure:
>     - Call the protocol draft out of the RFC EDitor Queue
>     - Make changes (only those needed for SCTP Stream use),
>       issue a revised draft
>     - Run a short (1 week) WG last Call
>     - Run a short (2 weeks, it's a Standards Track draft) IETF Last =
Call
>     - Send draft back to RFC for evalkuatio
>     - IESG sends it back to the RFC Editor Queue
>    Assuming that all goes well, we estimate all that will take
>    6~8 weeks.  By then we expect the PSAMP Info draft to have
>    progressed so that it will be in the RFC Editor Queue too!
>     - Corresponding changes to Implementation Guidelines and
>       Testing drafts will also be needed, they will be made
>       in the next revisions of both these drafts
>=20
> 1. Configuration Data Model (Gerhard Muenz)
>    Agreed: Important to WG, not clear what protocol would be needed.
>    Proposal: (a) Develop Configuration Info Model as a WG item,
>        in English (and also an XML version) - Standards Track RFC.
>        (b) Consider what protocol would be best for IPFIX =
Configuration.
>            Requirements RFC?      Milestones: WG LC before IETF 71
>=20
> 2. SCTP Per-Stream Draft (Benoit Claise)
>    Agreed: Needs to be explored, as a possible protocol option.
>    Procedure: Make this a WG item, as Experimental RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> 3. File Format (Brian Trammel)
>    Agreed: WG item, as soon as possible.
>    Procedure: Make this a WG item, as an Informational RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> For items 0 to 4 above, we'd like to make a list of several committed
> reviewers for each. Please help me with this by filling in and
> returning the form below
>=20
> IPFIX work item Reviewers
> -------------------------
>=20
> Name: _____________________________
>=20
> I will review documents for the following items:
> (put a 'y' in the boxes on the next line)
>=20
> 0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]
>=20
> Email this form to nevil@auckland.ac.nz -- thankyou !
>=20
> =
-----------------------------------------------------------------------
>=20
> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX =
Aggregation.
>    Possible future WG item, continue discussion on mailing list.
>=20
> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?
>=20
> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> =
-----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>=20
> =
-----------------------------------------------------------------------
> This mail sent through University of Auckland =
http://www.auckland.ac.nz
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 20:04:04 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDqpk-0000gZ-31; Wed, 25 Jul 2007 20:04:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDqpi-0000gU-Ve
	for ipfix@ietf.org; Wed, 25 Jul 2007 20:03:59 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDqpi-0004dZ-HG
	for ipfix@ietf.org; Wed, 25 Jul 2007 20:03:58 -0400
Received: from 12.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.12])
	by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jul 2007 20:03:57 -0400
X-IronPort-AV: i="4.16,582,1175486400"; d="scan'208"; a="42928921:sNHT8296878"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items
Date: Thu, 26 Jul 2007 02:03:55 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0428F28B@307622ANEX5.global.avaya.com>
In-Reply-To: <20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items
Thread-Index: AcfPBV0O5NVW6EyPREqhBnW2clEc2QAEqgRQ
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz><46A79705.5000106@cisco.com>
	<20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Nevil Brownlee" <nevil@auckland.ac.nz>,
	<stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

To add to what Nevil said. Stewart's concern is certainly justified and
probably based on some experience :-) In full truth there is no
guarantee that the risks that he is mentioning could be 100% avoided.
However, it would help to include in the revised I-D a short log changes
section that makes clear that removing SCTP stream restrictions in
Protocol Document is the sole goal of this version. Also, the Last Call
texts should mention that it I sonly this specific set of changes that
is being last called. I will personally take care that this is included
in the IETF LC.=20

Dan

=20
=20

> -----Original Message-----
> From: Nevil Brownlee [mailto:nevil@auckland.ac.nz]=20
> Sent: Thursday, July 26, 2007 12:46 AM
> To: stbryant@cisco.com
> Cc: ipfix@ietf.org
> Subject: Re: [IPFIX] *Proposed* new work items
>=20
>=20
> Hi Stewart:
>=20
> >>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
> >>
> > That's a big deal that may result in all kinds of changes - new LC=20
> > comments, new discusses etc.  When you start this process=20
> you cannot=20
> > be sure what you will get out.
> >
> > Why not continue with draft as it is and produce a second=20
> draft that=20
> > explains how to run the ipfix protocol in this new transport mode.
>=20
> We considered doing that, it's certainly not an approach to=20
> be taken lightly.
> Consensus at the meeting was that we're blocked waiting for=20
> the PSAMP Info draft, which will probably take a fair while yet.
>=20
> The plan is to limit changes to *only* those addressed in=20
> Brian Trammell's "SCTP change" draft, which we expect to=20
> minimise the chance of new blocks appearing.  And last, since=20
> the Protocol documents is sitting in the RFC Editor queue -=20
> i.e. it hasn't been published yet - we have that (rare)=20
> chance to fix it in the original RFC, rather than forcing=20
> everyone to refer to a 'changes' RFC as well as a Protocol RFC.
>=20
> Cheers, Nevil
>=20
> --------------------------------------------------------------
> ---------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>=20
> --------------------------------------------------------------
> ---------
> This mail sent through University of Auckland=20
> http://www.auckland.ac.nz
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
>=20

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Wed Jul 25 20:04:04 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDqpk-0000gZ-31; Wed, 25 Jul 2007 20:04:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDqpi-0000gU-Ve
	for ipfix@ietf.org; Wed, 25 Jul 2007 20:03:59 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDqpi-0004dZ-HG
	for ipfix@ietf.org; Wed, 25 Jul 2007 20:03:58 -0400
Received: from 12.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.12])
	by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jul 2007 20:03:57 -0400
X-IronPort-AV: i="4.16,582,1175486400"; d="scan'208"; a="42928921:sNHT8296878"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [IPFIX] *Proposed* new work items
Date: Thu, 26 Jul 2007 02:03:55 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0428F28B@307622ANEX5.global.avaya.com>
In-Reply-To: <20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items
Thread-Index: AcfPBV0O5NVW6EyPREqhBnW2clEc2QAEqgRQ
References: <20070726024800.ek1t57ckowowow0g@webmail.auckland.ac.nz><46A79705.5000106@cisco.com>
	<20070726094628.y2fkpmxxcw00oc0g@webmail.auckland.ac.nz>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Nevil Brownlee" <nevil@auckland.ac.nz>,
	<stbryant@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

To add to what Nevil said. Stewart's concern is certainly justified and
probably based on some experience :-) In full truth there is no
guarantee that the risks that he is mentioning could be 100% avoided.
However, it would help to include in the revised I-D a short log changes
section that makes clear that removing SCTP stream restrictions in
Protocol Document is the sole goal of this version. Also, the Last Call
texts should mention that it I sonly this specific set of changes that
is being last called. I will personally take care that this is included
in the IETF LC.=20

Dan

=20
=20

> -----Original Message-----
> From: Nevil Brownlee [mailto:nevil@auckland.ac.nz]=20
> Sent: Thursday, July 26, 2007 12:46 AM
> To: stbryant@cisco.com
> Cc: ipfix@ietf.org
> Subject: Re: [IPFIX] *Proposed* new work items
>=20
>=20
> Hi Stewart:
>=20
> >>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
> >>
> > That's a big deal that may result in all kinds of changes - new LC=20
> > comments, new discusses etc.  When you start this process=20
> you cannot=20
> > be sure what you will get out.
> >
> > Why not continue with draft as it is and produce a second=20
> draft that=20
> > explains how to run the ipfix protocol in this new transport mode.
>=20
> We considered doing that, it's certainly not an approach to=20
> be taken lightly.
> Consensus at the meeting was that we're blocked waiting for=20
> the PSAMP Info draft, which will probably take a fair while yet.
>=20
> The plan is to limit changes to *only* those addressed in=20
> Brian Trammell's "SCTP change" draft, which we expect to=20
> minimise the chance of new blocks appearing.  And last, since=20
> the Protocol documents is sitting in the RFC Editor queue -=20
> i.e. it hasn't been published yet - we have that (rare)=20
> chance to fix it in the original RFC, rather than forcing=20
> everyone to refer to a 'changes' RFC as well as a Protocol RFC.
>=20
> Cheers, Nevil
>=20
> --------------------------------------------------------------
> ---------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>=20
> --------------------------------------------------------------
> ---------
> This mail sent through University of Auckland=20
> http://www.auckland.ac.nz
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
>=20

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 01:56:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwKf-0007NJ-S8; Thu, 26 Jul 2007 01:56:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwKf-0007NB-3v
	for ipfix@ietf.org; Thu, 26 Jul 2007 01:56:17 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwKe-0002PS-5N
	for ipfix@ietf.org; Thu, 26 Jul 2007 01:56:16 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 1BD4828014C8C;
	Thu, 26 Jul 2007 07:56:17 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id T+nwcuDkxVAv; Thu, 26 Jul 2007 07:56:17 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id F190A28014C80;
	Thu, 26 Jul 2007 07:56:06 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 05:56:05 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 07:56:01 +0200
Subject: Re: [IPFIX] *Proposed* new work items, take two
From: Juergen Quittek <Quittek@netlab.nec.de>
To: Nevil Brownlee <nevil@auckland.ac.nz>,
	<ipfix@ietf.org>
Message-ID: <C2CE0411.1021B%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] *Proposed* new work items, take two
Thread-Index: AcfPSaTu48Yuezs8EdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

I got questions from several WG members on the status of this list
of candidate work items for an updated IPFIX charter.

According to the discussion we had in our session on Tuesday,
the list of work items below is not final, but a suggestion that
should be discussed on this mailing list.

For item
0. Remove SCTP stream restrictions in Protocol Document
we agreed to approve the consensus we had in the session on the
mailing list.

For items
1. Configuration Data Model (Gerhard Muenz)
2. SCTP Per-Stream Draft (Benoit Claise)
3. File Format (Brian Trammel)
there was no doubt expressed that these would be
very good work items for IPFIX.

For items
4. Extended Types (Elisa Boschi)
5. IPFIX Mediation (Atayushi Kobayashi)
6. Order of Information Elements (Irino)
discussions were controversial and time was limited
So, we agreed to discuss them further on the mailing list.
I will send an individual mail for triggering discussion on
each of them in separate emails.

For any of these items: Please have a look at the related drafts
and tell us what you think about them.

Thanks,

    Juergen


On 26.07.2007 0:08 "Nevil Brownlee" <nevil@auckland.ac.nz> wrote:

> 
> Hi again all:
> 
> Here's a slightly improved, slightly clearer, version of my earlier posting.
> 
> Cheers, Nevil
> 
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> 
> IPFIX: Proposal for new work
>        Based on discussion at IETF 69, Chicago
> 
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
> 
> 0. Remove SCTP stream restrictions in Protocol Document.
>    Agreed: WG needs to do this, as soon as possible.
>    Procedure:
>     - Call the protocol draft out of the RFC EDitor Queue
>     - Make changes (only those needed for SCTP Stream use),
>       issue a revised draft
>     - Run a short (1 week) WG last Call
>     - Run a short (2 weeks, it's a Standards Track draft) IETF Last Call
>     - Send draft back to RFC for evalkuatio
>     - IESG sends it back to the RFC Editor Queue
>    Assuming that all goes well, we estimate all that will take
>    6~8 weeks.  By then we expect the PSAMP Info draft to have
>    progressed so that it will be in the RFC Editor Queue too!
>     - Corresponding changes to Implementation Guidelines and
>       Testing drafts will also be needed, they will be made
>       in the next revisions of both these drafts
> 
> 1. Configuration Data Model (Gerhard Muenz)
>    Agreed: Important to WG, not clear what protocol would be needed.
>    Proposal: (a) Develop Configuration Info Model as a WG item,
>        in English (and also an XML version) - Standards Track RFC.
>        (b) Consider what protocol would be best for IPFIX Configuration.
>            Requirements RFC?      Milestones: WG LC before IETF 71
> 
> 2. SCTP Per-Stream Draft (Benoit Claise)
>    Agreed: Needs to be explored, as a possible protocol option.
>    Procedure: Make this a WG item, as Experimental RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> 3. File Format (Brian Trammel)
>    Agreed: WG item, as soon as possible.
>    Procedure: Make this a WG item, as an Informational RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> For items 0 to 4 above, we'd like to make a list of several committed
> reviewers for each. Please help me with this by filling in and
> returning the form below
> 
> IPFIX work item Reviewers
> -------------------------
> 
> Name: _____________________________
> 
> I will review documents for the following items:
> (put a 'y' in the boxes on the next line)
> 
> 0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]
> 
> Email this form to nevil@auckland.ac.nz -- thankyou !
> 
> -----------------------------------------------------------------------
> 
> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.
> 
> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?
> 
> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.
> 
> =======================================================================
> 
> -----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> 
> -----------------------------------------------------------------------
> This mail sent through University of Auckland http://www.auckland.ac.nz
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 01:56:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwKf-0007NJ-S8; Thu, 26 Jul 2007 01:56:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwKf-0007NB-3v
	for ipfix@ietf.org; Thu, 26 Jul 2007 01:56:17 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwKe-0002PS-5N
	for ipfix@ietf.org; Thu, 26 Jul 2007 01:56:16 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 1BD4828014C8C;
	Thu, 26 Jul 2007 07:56:17 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id T+nwcuDkxVAv; Thu, 26 Jul 2007 07:56:17 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id F190A28014C80;
	Thu, 26 Jul 2007 07:56:06 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 05:56:05 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 07:56:01 +0200
Subject: Re: [IPFIX] *Proposed* new work items, take two
From: Juergen Quittek <Quittek@netlab.nec.de>
To: Nevil Brownlee <nevil@auckland.ac.nz>,
	<ipfix@ietf.org>
Message-ID: <C2CE0411.1021B%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] *Proposed* new work items, take two
Thread-Index: AcfPSaTu48Yuezs8EdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

I got questions from several WG members on the status of this list
of candidate work items for an updated IPFIX charter.

According to the discussion we had in our session on Tuesday,
the list of work items below is not final, but a suggestion that
should be discussed on this mailing list.

For item
0. Remove SCTP stream restrictions in Protocol Document
we agreed to approve the consensus we had in the session on the
mailing list.

For items
1. Configuration Data Model (Gerhard Muenz)
2. SCTP Per-Stream Draft (Benoit Claise)
3. File Format (Brian Trammel)
there was no doubt expressed that these would be
very good work items for IPFIX.

For items
4. Extended Types (Elisa Boschi)
5. IPFIX Mediation (Atayushi Kobayashi)
6. Order of Information Elements (Irino)
discussions were controversial and time was limited
So, we agreed to discuss them further on the mailing list.
I will send an individual mail for triggering discussion on
each of them in separate emails.

For any of these items: Please have a look at the related drafts
and tell us what you think about them.

Thanks,

    Juergen


On 26.07.2007 0:08 "Nevil Brownlee" <nevil@auckland.ac.nz> wrote:

> 
> Hi again all:
> 
> Here's a slightly improved, slightly clearer, version of my earlier posting.
> 
> Cheers, Nevil
> 
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> 
> IPFIX: Proposal for new work
>        Based on discussion at IETF 69, Chicago
> 
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
> 
> 0. Remove SCTP stream restrictions in Protocol Document.
>    Agreed: WG needs to do this, as soon as possible.
>    Procedure:
>     - Call the protocol draft out of the RFC EDitor Queue
>     - Make changes (only those needed for SCTP Stream use),
>       issue a revised draft
>     - Run a short (1 week) WG last Call
>     - Run a short (2 weeks, it's a Standards Track draft) IETF Last Call
>     - Send draft back to RFC for evalkuatio
>     - IESG sends it back to the RFC Editor Queue
>    Assuming that all goes well, we estimate all that will take
>    6~8 weeks.  By then we expect the PSAMP Info draft to have
>    progressed so that it will be in the RFC Editor Queue too!
>     - Corresponding changes to Implementation Guidelines and
>       Testing drafts will also be needed, they will be made
>       in the next revisions of both these drafts
> 
> 1. Configuration Data Model (Gerhard Muenz)
>    Agreed: Important to WG, not clear what protocol would be needed.
>    Proposal: (a) Develop Configuration Info Model as a WG item,
>        in English (and also an XML version) - Standards Track RFC.
>        (b) Consider what protocol would be best for IPFIX Configuration.
>            Requirements RFC?      Milestones: WG LC before IETF 71
> 
> 2. SCTP Per-Stream Draft (Benoit Claise)
>    Agreed: Needs to be explored, as a possible protocol option.
>    Procedure: Make this a WG item, as Experimental RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> 3. File Format (Brian Trammel)
>    Agreed: WG item, as soon as possible.
>    Procedure: Make this a WG item, as an Informational RFC.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
> 
> For items 0 to 4 above, we'd like to make a list of several committed
> reviewers for each. Please help me with this by filling in and
> returning the form below
> 
> IPFIX work item Reviewers
> -------------------------
> 
> Name: _____________________________
> 
> I will review documents for the following items:
> (put a 'y' in the boxes on the next line)
> 
> 0 [ ],  1 [ ],  2 [ ],  3 [ ],  4 [ ]
> 
> Email this form to nevil@auckland.ac.nz -- thankyou !
> 
> -----------------------------------------------------------------------
> 
> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.
> 
> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?
> 
> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.
> 
> =======================================================================
> 
> -----------------------------------------------------------------------
>   Nevil Brownlee                    Computer Science Department | ITS
>   Phone: +64 9 373 7599 x88941             The University of Auckland
>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
> 
> -----------------------------------------------------------------------
> This mail sent through University of Auckland http://www.auckland.ac.nz
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:09:47 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwXi-0000vr-3J; Thu, 26 Jul 2007 02:09:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwXd-0000jq-HL
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:09:41 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwXc-0002a6-Ga
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:09:41 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 832E928014C8C;
	Thu, 26 Jul 2007 08:09:41 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id za86YGlSUJEm; Thu, 26 Jul 2007 08:09:41 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 5A33528014C80;
	Thu, 26 Jul 2007 08:09:21 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:09:19 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:09:17 +0200
Subject: Re: [IPFIX] *Proposed* new work items
From: Juergen Quittek <Quittek@netlab.nec.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
	Nevil Brownlee <nevil@auckland.ac.nz>, <stbryant@cisco.com>
Message-ID: <C2CE072D.10233%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] *Proposed* new work items
Thread-Index: AcfPBV0O5NVW6EyPREqhBnW2clEc2QAEqgRQAAzekdQ=
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0428F28B@307622ANEX5.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Just for clarification: this issue is not concerning the discussion
of re-chartering IPFIX. It is the action of calling the current draft
of the IPFIX protocol back from the RFC editor queue before it gets
published and modifying it as described in draft-trammell-ipfix-sctp-change.
This implies also changes required in the implementation guidelines.
For both documents it will be required to run WGLC and IETF LC again.

If you see any problem with this (as Stewart did), please send us
your concerns until the end of next week.

Thanks,

    Juergen


Am 26.07.2007 2:03 Uhr schrieb "Romascanu, Dan (Dan)" unter
<dromasca@avaya.com>:

> To add to what Nevil said. Stewart's concern is certainly justified and
> probably based on some experience :-) In full truth there is no
> guarantee that the risks that he is mentioning could be 100% avoided.
> However, it would help to include in the revised I-D a short log changes
> section that makes clear that removing SCTP stream restrictions in
> Protocol Document is the sole goal of this version. Also, the Last Call
> texts should mention that it I sonly this specific set of changes that
> is being last called. I will personally take care that this is included
> in the IETF LC. 
> 
> Dan
> 
>  
>  
> 
>> -----Original Message-----
>> From: Nevil Brownlee [mailto:nevil@auckland.ac.nz]
>> Sent: Thursday, July 26, 2007 12:46 AM
>> To: stbryant@cisco.com
>> Cc: ipfix@ietf.org
>> Subject: Re: [IPFIX] *Proposed* new work items
>> 
>> 
>> Hi Stewart:
>> 
>>>>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>>>> 
>>> That's a big deal that may result in all kinds of changes - new LC
>>> comments, new discusses etc.  When you start this process
>> you cannot 
>>> be sure what you will get out.
>>> 
>>> Why not continue with draft as it is and produce a second
>> draft that 
>>> explains how to run the ipfix protocol in this new transport mode.
>> 
>> We considered doing that, it's certainly not an approach to
>> be taken lightly.
>> Consensus at the meeting was that we're blocked waiting for
>> the PSAMP Info draft, which will probably take a fair while yet.
>> 
>> The plan is to limit changes to *only* those addressed in
>> Brian Trammell's "SCTP change" draft, which we expect to
>> minimise the chance of new blocks appearing.  And last, since
>> the Protocol documents is sitting in the RFC Editor queue -
>> i.e. it hasn't been published yet - we have that (rare)
>> chance to fix it in the original RFC, rather than forcing
>> everyone to refer to a 'changes' RFC as well as a Protocol RFC.
>> 
>> Cheers, Nevil
>> 
>> --------------------------------------------------------------
>> ---------
>>   Nevil Brownlee                    Computer Science Department | ITS
>>   Phone: +64 9 373 7599 x88941             The University of Auckland
>>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>> 
>> --------------------------------------------------------------
>> ---------
>> This mail sent through University of Auckland
>> http://www.auckland.ac.nz
>> 
>> 
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:09:48 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwXi-0000vr-3J; Thu, 26 Jul 2007 02:09:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwXd-0000jq-HL
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:09:41 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwXc-0002a6-Ga
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:09:41 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 832E928014C8C;
	Thu, 26 Jul 2007 08:09:41 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id za86YGlSUJEm; Thu, 26 Jul 2007 08:09:41 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 5A33528014C80;
	Thu, 26 Jul 2007 08:09:21 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:09:19 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:09:17 +0200
Subject: Re: [IPFIX] *Proposed* new work items
From: Juergen Quittek <Quittek@netlab.nec.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
	Nevil Brownlee <nevil@auckland.ac.nz>, <stbryant@cisco.com>
Message-ID: <C2CE072D.10233%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] *Proposed* new work items
Thread-Index: AcfPBV0O5NVW6EyPREqhBnW2clEc2QAEqgRQAAzekdQ=
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0428F28B@307622ANEX5.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Just for clarification: this issue is not concerning the discussion
of re-chartering IPFIX. It is the action of calling the current draft
of the IPFIX protocol back from the RFC editor queue before it gets
published and modifying it as described in draft-trammell-ipfix-sctp-change.
This implies also changes required in the implementation guidelines.
For both documents it will be required to run WGLC and IETF LC again.

If you see any problem with this (as Stewart did), please send us
your concerns until the end of next week.

Thanks,

    Juergen


Am 26.07.2007 2:03 Uhr schrieb "Romascanu, Dan (Dan)" unter
<dromasca@avaya.com>:

> To add to what Nevil said. Stewart's concern is certainly justified and
> probably based on some experience :-) In full truth there is no
> guarantee that the risks that he is mentioning could be 100% avoided.
> However, it would help to include in the revised I-D a short log changes
> section that makes clear that removing SCTP stream restrictions in
> Protocol Document is the sole goal of this version. Also, the Last Call
> texts should mention that it I sonly this specific set of changes that
> is being last called. I will personally take care that this is included
> in the IETF LC. 
> 
> Dan
> 
>  
>  
> 
>> -----Original Message-----
>> From: Nevil Brownlee [mailto:nevil@auckland.ac.nz]
>> Sent: Thursday, July 26, 2007 12:46 AM
>> To: stbryant@cisco.com
>> Cc: ipfix@ietf.org
>> Subject: Re: [IPFIX] *Proposed* new work items
>> 
>> 
>> Hi Stewart:
>> 
>>>>      re-run WG Last Call and IETF Last Call, resubmit to IESG.
>>>> 
>>> That's a big deal that may result in all kinds of changes - new LC
>>> comments, new discusses etc.  When you start this process
>> you cannot 
>>> be sure what you will get out.
>>> 
>>> Why not continue with draft as it is and produce a second
>> draft that 
>>> explains how to run the ipfix protocol in this new transport mode.
>> 
>> We considered doing that, it's certainly not an approach to
>> be taken lightly.
>> Consensus at the meeting was that we're blocked waiting for
>> the PSAMP Info draft, which will probably take a fair while yet.
>> 
>> The plan is to limit changes to *only* those addressed in
>> Brian Trammell's "SCTP change" draft, which we expect to
>> minimise the chance of new blocks appearing.  And last, since
>> the Protocol documents is sitting in the RFC Editor queue -
>> i.e. it hasn't been published yet - we have that (rare)
>> chance to fix it in the original RFC, rather than forcing
>> everyone to refer to a 'changes' RFC as well as a Protocol RFC.
>> 
>> Cheers, Nevil
>> 
>> --------------------------------------------------------------
>> ---------
>>   Nevil Brownlee                    Computer Science Department | ITS
>>   Phone: +64 9 373 7599 x88941             The University of Auckland
>>   FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>> 
>> --------------------------------------------------------------
>> ---------
>> This mail sent through University of Auckland
>> http://www.auckland.ac.nz
>> 
>> 
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:28:01 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwpK-00051f-Pd; Thu, 26 Jul 2007 02:27:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwpH-0004qj-QE
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:27:56 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwpH-0002ql-Bw
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:27:55 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 636C428014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:27:56 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3qznCdzbLcV4 for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:27:56 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 52E0D28014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:27:51 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:27:49 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:27:47 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE0B83.10238%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #4: extended types
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [IPFIX] new work item candidate #4: extended types
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidates #4 to become a new IPFIX work item is described by
draft draft-boschi-ipfix-extended-type-00.txt.

> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.

It is a method for assigning data types to unknown IPFIX information
elements by using option records that map data types to element identifiers.

It can be applied in cases where an IPFIX collector does not know the
data type of received information elements. This may in particular happen
if enterprise specific elements are used. Without this information the
collector would treat these elements as if they were of type octet array.
With this information it may be able to treat them more appropriately.

The current version of the IPFIX file format draft recommends using this
method when IPFIX records are stored.

Do you think this is a useful extension of the IPFIX protocol?
Do you think we should accept this as an IPFIX work item?
Please have a look at the draft and send your comments.

Thanks,

    Juergen



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:28:01 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwpK-00051f-Pd; Thu, 26 Jul 2007 02:27:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwpH-0004qj-QE
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:27:56 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDwpH-0002ql-Bw
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:27:55 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 636C428014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:27:56 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3qznCdzbLcV4 for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:27:56 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 52E0D28014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:27:51 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:27:49 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:27:47 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE0B83.10238%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #4: extended types
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [IPFIX] new work item candidate #4: extended types
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidates #4 to become a new IPFIX work item is described by
draft draft-boschi-ipfix-extended-type-00.txt.

> 4. Extended Types (Elisa Boschi)
>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>    specify what operations make sense for an IE.
>    Support shown for this as a WG item, as for File Format.
>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.

It is a method for assigning data types to unknown IPFIX information
elements by using option records that map data types to element identifiers.

It can be applied in cases where an IPFIX collector does not know the
data type of received information elements. This may in particular happen
if enterprise specific elements are used. Without this information the
collector would treat these elements as if they were of type octet array.
With this information it may be able to treat them more appropriately.

The current version of the IPFIX file format draft recommends using this
method when IPFIX records are stored.

Do you think this is a useful extension of the IPFIX protocol?
Do you think we should accept this as an IPFIX work item?
Please have a look at the draft and send your comments.

Thanks,

    Juergen



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:38:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwzo-0004q4-D5; Thu, 26 Jul 2007 02:38:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwzn-0004pz-96
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:38:47 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDwzl-0005Hl-Uk
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:38:47 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0806C28014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:38:45 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UTGfTsCDqrQH for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:38:44 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id E8FD928014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:38:39 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:38:38 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:38:36 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #6: order of information elements
Thread-Index: AcfPT5fU1kEdaTtCEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [IPFIX] new work item candidate #6: order of information elements
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidates #6 to become a new IPFIX work item is described by
draft draft-irino-ipfix-ie-order-02.txt.

> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?

This draft suggests a special ordering of information elements in a
flow record.  At the very brief presentation at our session, the author
explained that he can improve the performance of IPFIX exporter and
collector significantly. To prove this, he compared a random order
of information elements with an order according to his proposal
and achieved significant performance improvements.

Speaking as technical contributor, I think that if these results would
be the same also for other implementations of IPFIX, then this looks like
a very good IPFIX work item.

Speaking as co-chair, I would like to ask everybody who has an IPFIX
implementation to conduct a short experiment in order to find out if
the improvement is the same for his/her implementations.

Would any implementor be willing to do so?
If yes, until when would you have results?

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:38:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDwzo-0004q4-D5; Thu, 26 Jul 2007 02:38:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDwzn-0004pz-96
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:38:47 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDwzl-0005Hl-Uk
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:38:47 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0806C28014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:38:45 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UTGfTsCDqrQH for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:38:44 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id E8FD928014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:38:39 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:38:38 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:38:36 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #6: order of information elements
Thread-Index: AcfPT5fU1kEdaTtCEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [IPFIX] new work item candidate #6: order of information elements
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidates #6 to become a new IPFIX work item is described by
draft draft-irino-ipfix-ie-order-02.txt.

> 6. Order of Information Elements (Irino)
>    Interesting, need more people to measure possible efficiency gain.
>    Would this be better as an individual draft?

This draft suggests a special ordering of information elements in a
flow record.  At the very brief presentation at our session, the author
explained that he can improve the performance of IPFIX exporter and
collector significantly. To prove this, he compared a random order
of information elements with an order according to his proposal
and achieved significant performance improvements.

Speaking as technical contributor, I think that if these results would
be the same also for other implementations of IPFIX, then this looks like
a very good IPFIX work item.

Speaking as co-chair, I would like to ask everybody who has an IPFIX
implementation to conduct a short experiment in order to find out if
the improvement is the same for his/her implementations.

Would any implementor be willing to do so?
If yes, until when would you have results?

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:53:24 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDxDu-0007FB-4m; Thu, 26 Jul 2007 02:53:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDxDt-0007CK-3Q
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:53:21 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDxDr-0005WP-Rk
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:53:21 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id EC08228014C90
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:53:20 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fZx8lMO0l1ym for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:53:20 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id DB9A828014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:53:15 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:53:14 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:53:05 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE1171.10242%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #5: aggregation/mediation
Thread-Index: AcfPUZ3L3BjRUztEEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [IPFIX] new work item candidate #5: aggregation/mediation
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidate #5 to become a new IPFIX work item is described by
draft-kobayashi-ipfix-mediator-model-00.txt.

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.

This draft describes how IPFIX flow records from a large number of exporters
can be aggregated by one or more a mediator devices. This is a contribution
from an operator and during the discussion Emile coming from another
operator confirmed that this is a highly relevant use case.

At the IETF we are usually short of feedback from operators. If now two
operators tell us that the WG should work on this issue, we should
consider the item seriously.

Please have a look at the draft and tell us what you think about the idea
and if this should or should not become and IPFIX work item.

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 02:53:24 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDxDu-0007FB-4m; Thu, 26 Jul 2007 02:53:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDxDt-0007CK-3Q
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:53:21 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDxDr-0005WP-Rk
	for ipfix@ietf.org; Thu, 26 Jul 2007 02:53:21 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id EC08228014C90
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:53:20 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fZx8lMO0l1ym for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 08:53:20 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id DB9A828014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 08:53:15 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 06:53:14 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 08:53:05 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE1171.10242%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #5: aggregation/mediation
Thread-Index: AcfPUZ3L3BjRUztEEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [IPFIX] new work item candidate #5: aggregation/mediation
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidate #5 to become a new IPFIX work item is described by
draft-kobayashi-ipfix-mediator-model-00.txt.

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.

This draft describes how IPFIX flow records from a large number of exporters
can be aggregated by one or more a mediator devices. This is a contribution
from an operator and during the discussion Emile coming from another
operator confirmed that this is a highly relevant use case.

At the IETF we are usually short of feedback from operators. If now two
operators tell us that the WG should work on this issue, we should
consider the item seriously.

Please have a look at the draft and tell us what you think about the idea
and if this should or should not become and IPFIX work item.

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 03:01:41 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDxLs-0004mL-2P; Thu, 26 Jul 2007 03:01:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDxLq-0004m9-C7
	for ipfix@ietf.org; Thu, 26 Jul 2007 03:01:34 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDxLq-0005fu-2A
	for ipfix@ietf.org; Thu, 26 Jul 2007 03:01:34 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 23DBC28014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 09:01:35 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3WIq-CPDwBUD for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 09:01:35 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 1363828014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 09:01:30 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 07:01:28 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 09:01:26 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE1366.10247%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #7: flow sampling
Thread-Index: AcfPUshpBwhbcjtGEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [IPFIX] new work item candidate #7: flow sampling
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidate #7 to become a new IPFIX work item is described by
draft-peluso-flowselection-tech-00.txt.

> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.

This draft discusses an issue, we have been discussing already two or three
years ago: the sampling of flows by a metering/exporting process. Still,
this issue is rather new to the IPFIX WG and has not yet been discussed a
lot. Research work might be needed to fully understand the issue.

Speaking as technical contributor, I think that this work needs to become
better understood and more mature before becoming a WG work item.

Please have a look at the draft and tell us your opinion.

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 03:01:41 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDxLs-0004mL-2P; Thu, 26 Jul 2007 03:01:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDxLq-0004m9-C7
	for ipfix@ietf.org; Thu, 26 Jul 2007 03:01:34 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDxLq-0005fu-2A
	for ipfix@ietf.org; Thu, 26 Jul 2007 03:01:34 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 23DBC28014C8C
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 09:01:35 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3WIq-CPDwBUD for <ipfix@ietf.org>;
	Thu, 26 Jul 2007 09:01:35 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 1363828014C80
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 09:01:30 +0200 (CEST)
Received: from 67.97.210.2 ([67.97.210.2]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jul 2007 07:01:28 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 09:01:26 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: <ipfix@ietf.org>
Message-ID: <C2CE1366.10247%Quittek@netlab.nec.de>
Thread-Topic: new work item candidate #7: flow sampling
Thread-Index: AcfPUshpBwhbcjtGEdytZQAWy4a5Gw==
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [IPFIX] new work item candidate #7: flow sampling
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

Candidate #7 to become a new IPFIX work item is described by
draft-peluso-flowselection-tech-00.txt.

> 7. Flow Sampling (Tanja Zseby)
>    Early stage so far, comments/participation encouraged.

This draft discusses an issue, we have been discussing already two or three
years ago: the sampling of flows by a metering/exporting process. Still,
this issue is rather new to the IPFIX WG and has not yet been discussed a
lot. Research work might be needed to fully understand the issue.

Speaking as technical contributor, I think that this work needs to become
better understood and more mature before becoming a WG work item.

Please have a look at the draft and tell us your opinion.

Thanks,

    Juergen


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From nicombatted@alneta.lt Thu Jul 26 04:30:14 2007
Return-path: <nicombatted@alneta.lt>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDyje-0003TR-Iu
	for ipfix-archive@lists.ietf.org; Thu, 26 Jul 2007 04:30:14 -0400
Received: from pool-138-89-74-82.mad.east.verizon.net ([138.89.74.82])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IDyjd-0005jU-FR
	for ipfix-archive@lists.ietf.org; Thu, 26 Jul 2007 04:30:14 -0400
Message-ID: <000e01c7cf3d$a8fb61b0$05ff270c@DAVE>
From: "Lucille Hare" <nicombatted@alneta.lt>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject:   Thank you, we are ready to lend money regardless of Credit
Date: Thu, 26 Jul 2007 04:29:09 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_000B_01C7CF3D.A8FB61B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2963
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

------=_NextPart_000_000B_01C7CF3D.A8FB61B0
Content-Type: text/plain;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable


Your credit does not matter to us!
 
If you have your own business and need IMMEDIATE ready money to spend =
ANY way you like or need Extra money to give the business a boost or  =
want A low interest loan - NO STRINGS ATTACHED, here is best deal we can =
offer you THIS EVENING (hurry, this deal will expire TONIGHT):
 
$54,000+ loan
 
Hurry, when the deal is gone, it is gone. Simply Call Us... 
 
Don't worry about approval, your credit history will not disqualify you!
 
Call Us Free on 877-542-1880
------=_NextPart_000_000B_01C7CF3D.A8FB61B0
Content-Type: text/html;
        charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
windows-1250">
<META content=3D"MSHTML 6.00.2900.1158" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit does not =
matter to us!</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you have your own =
business and wish IMMEDIATE money to spend ANY way you like or require =
Extra money to give your company a boost or  want A low interest loan - =
NO STRINGS ATTACHED, here is best deal we can offer you THIS EVENING =
(hurry, this offer will expire TODAY):</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$25,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when best deal =
is gone, it is gone. Simply Call Us... </B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Do not worry about =
approval, your credit will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Call Us Free on =
877-542-1880</B></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_000B_01C7CF3D.A8FB61B0--



From oehchair@3sheep.com Thu Jul 26 05:34:45 2007
Return-path: <oehchair@3sheep.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDzk5-0000qn-9f
	for ipfix-archive@lists.ietf.org; Thu, 26 Jul 2007 05:34:45 -0400
Received: from dynamic-acs-24-239-32-188.zoominternet.net ([24.239.32.188])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IDzk3-0000r4-V3
	for ipfix-archive@lists.ietf.org; Thu, 26 Jul 2007 05:34:45 -0400
Message-ID: <001601c7cf46$99b64c70$017fed34@MARK>
From: "Nadine Campos" <oehchair@3sheep.com>
To: "ipfix-archive" <ipfix-archive@lists.ietf.org>
Subject: Re: Thanks, we are ready to lend some cash regardless of Credit
Date: Thu, 26 Jul 2007 05:30:19 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0013_01C7CF46.99B64C70"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.1106
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

------=_NextPart_000_0013_01C7CF46.99B64C70
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Your credit score does not matter to us!
 
If you have your own business and require IMMEDIATE money to spend ANY =
way you like or require Extra money to give your business a boost or  =
need A low interest loan - NO STRINGS ATTACHED, here is our deal we can =
offer you THIS NIGHT (hurry, this offer will expire NOW):
 
$33,000+ loan
 
Hurry, when our best deal is gone, it is gone. Simply Call Us... 
 
Don't worry about approval, your credit will not disqualify you!
 
Call Us Free on 877-542-1880
------=_NextPart_000_0013_01C7CF46.99B64C70
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3D=
iso-8859-1">
<META content=3D"MSHTML 6.00.2600.1081" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Your credit doesn't =
matter to us!</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>If you have your own =
business and want IMMEDIATE ready money to spend ANY way you like or =
wish Extra money to give your company a boost or  want A low interest =
loan - NO STRINGS ATTACHED, here is the deal we can offer you TONIGHT =
(hurry, this offer will expire THIS EVENING):</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>$39,000+ =
loan</B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Hurry, when our deal is =
gone, it is gone. Simply Call Us... </B></FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Do not worry about =
approval, your credit score will not disqualify you!</FONT></DIV>
<DIV align=3Dcenter> &nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>Call Us Free on =
877-542-1880</B></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_0013_01C7CF46.99B64C70--



From ipfix-bounces@ietf.org Thu Jul 26 05:41:06 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDzq4-0004jq-UI; Thu, 26 Jul 2007 05:40:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDzq4-0004jk-36
	for ipfix@ietf.org; Thu, 26 Jul 2007 05:40:56 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDzq2-00012A-HU
	for ipfix@ietf.org; Thu, 26 Jul 2007 05:40:56 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6Q9eohB017954; 
	Thu, 26 Jul 2007 11:40:50 +0200
Message-ID: <46A86C0B.90209@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 11:40:27 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
In-Reply-To: <46A7D10F.3050509@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6Q9eohB017954
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul,

Just a small comment:

Paul Aitken wrote:
>>    Modification of the value of Information Element
>>
>>       This function modifies the value of specified Information Elemen=
ts
>>       according to instructions configured by the user.
>>
>>       For example, this function enables us to overwrite private
>>       information with zeros or the maximum value.  In particular, IP
>>       address and port number is sensitive private information.  In th=
e
>>       case of monitoring traffic trends and traffic engineering, these
>>       Information Elements are not essential factors for those purpose=
s.
>>       In that case, modification anonymizes the relevant Information
>>       Elements to prevent a violation of privacy.  If modification can
>>       anonymize some Information Elements, it might need to report whi=
ch
>>       Information Elements are anonymized.  For example,
>>       "anonymizationIndicator" indicates which Information Elements ha=
ve
>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>>       The anonymization method is outside the scope of this document.
>=20
> Why would we not just modify the template and remove these Information
> Elements?

Instead of removing IP addresses you might want to apply anonymization
techniques which preserve prefix information while still preventing
inference of the original addresses. E.g. see CryptoPAN already deployed
by many Netflow tools like "flow-tools":
http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 05:41:06 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDzq4-0004jq-UI; Thu, 26 Jul 2007 05:40:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDzq4-0004jk-36
	for ipfix@ietf.org; Thu, 26 Jul 2007 05:40:56 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDzq2-00012A-HU
	for ipfix@ietf.org; Thu, 26 Jul 2007 05:40:56 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6Q9eohB017954; 
	Thu, 26 Jul 2007 11:40:50 +0200
Message-ID: <46A86C0B.90209@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 11:40:27 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
In-Reply-To: <46A7D10F.3050509@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6Q9eohB017954
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul,

Just a small comment:

Paul Aitken wrote:
>>    Modification of the value of Information Element
>>
>>       This function modifies the value of specified Information Elemen=
ts
>>       according to instructions configured by the user.
>>
>>       For example, this function enables us to overwrite private
>>       information with zeros or the maximum value.  In particular, IP
>>       address and port number is sensitive private information.  In th=
e
>>       case of monitoring traffic trends and traffic engineering, these
>>       Information Elements are not essential factors for those purpose=
s.
>>       In that case, modification anonymizes the relevant Information
>>       Elements to prevent a violation of privacy.  If modification can
>>       anonymize some Information Elements, it might need to report whi=
ch
>>       Information Elements are anonymized.  For example,
>>       "anonymizationIndicator" indicates which Information Elements ha=
ve
>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>>       The anonymization method is outside the scope of this document.
>=20
> Why would we not just modify the template and remove these Information
> Elements?

Instead of removing IP addresses you might want to apply anonymization
techniques which preserve prefix information while still preventing
inference of the original addresses. E.g. see CryptoPAN already deployed
by many Netflow tools like "flow-tools":
http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 07:18:12 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE1M5-0002dv-H3; Thu, 26 Jul 2007 07:18:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE1M3-0002dp-3x
	for ipfix@ietf.org; Thu, 26 Jul 2007 07:18:03 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE1M1-0002dc-3x
	for ipfix@ietf.org; Thu, 26 Jul 2007 07:18:02 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6QBI0Zx028452; 
	Thu, 26 Jul 2007 13:18:00 +0200
Message-ID: <46A882D0.4050700@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 13:17:36 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Juergen Quittek <Quittek@netlab.nec.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
In-Reply-To: <C2CE0B83.10238%Quittek@netlab.nec.de>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6QBI0Zx028452
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

I'm undecided about this draft.

On the one hand, it's a nice idea to have some IEs which allow
describing the type and semantic of other IEs. On the other hand, my
impression is that the usefulness is very restricted and not as broad as
claimed in the introduction of the draft:

   ... Having to do some sort of tool-specific
   configuration (or code modification) on every tool just to tell which
   type each used Information Element has is a huge amount of work for
   users and implementors of enterprise-specific Information Elements.
   Many tools in fact only need to know the field's data type to work on
   them. ...

In my opinion, any deeper analysis and processing of metering data
requires knowledge about the semantic. Just knowing the data type may be
enough to display values correctly. Considering
informationElementSemanticType, you might also know if the calculation
of statistical properties (max, min, mean, variance etc.) makes sense or
not. But any further analysis would probably require more semantical
knowledge. That's why I assume that, in practice, analyzing and
processing enterprise-specific data will mostly be performed with
specialized analysis tools that have been implemented for this specific
purpose. And for these tools, there is no need to export the IE informati=
on.

By the way: Have you considered an additional IE like
informationElementDescription holding an octet string describing the
semantic of the IE "in human-readable English"?

Regards,
Gerhard


Juergen Quittek wrote:
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
>> 4. Extended Types (Elisa Boschi)
>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>    specify what operations make sense for an IE.
>>    Support shown for this as a WG item, as for File Format.
>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element identif=
iers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular happ=
en
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet arra=
y.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using thi=
s
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 07:18:12 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE1M5-0002dv-H3; Thu, 26 Jul 2007 07:18:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE1M3-0002dp-3x
	for ipfix@ietf.org; Thu, 26 Jul 2007 07:18:03 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE1M1-0002dc-3x
	for ipfix@ietf.org; Thu, 26 Jul 2007 07:18:02 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6QBI0Zx028452; 
	Thu, 26 Jul 2007 13:18:00 +0200
Message-ID: <46A882D0.4050700@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 13:17:36 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Juergen Quittek <Quittek@netlab.nec.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
In-Reply-To: <C2CE0B83.10238%Quittek@netlab.nec.de>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6QBI0Zx028452
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear all,

I'm undecided about this draft.

On the one hand, it's a nice idea to have some IEs which allow
describing the type and semantic of other IEs. On the other hand, my
impression is that the usefulness is very restricted and not as broad as
claimed in the introduction of the draft:

   ... Having to do some sort of tool-specific
   configuration (or code modification) on every tool just to tell which
   type each used Information Element has is a huge amount of work for
   users and implementors of enterprise-specific Information Elements.
   Many tools in fact only need to know the field's data type to work on
   them. ...

In my opinion, any deeper analysis and processing of metering data
requires knowledge about the semantic. Just knowing the data type may be
enough to display values correctly. Considering
informationElementSemanticType, you might also know if the calculation
of statistical properties (max, min, mean, variance etc.) makes sense or
not. But any further analysis would probably require more semantical
knowledge. That's why I assume that, in practice, analyzing and
processing enterprise-specific data will mostly be performed with
specialized analysis tools that have been implemented for this specific
purpose. And for these tools, there is no need to export the IE informati=
on.

By the way: Have you considered an additional IE like
informationElementDescription holding an octet string describing the
semantic of the IE "in human-readable English"?

Regards,
Gerhard


Juergen Quittek wrote:
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
>> 4. Extended Types (Elisa Boschi)
>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>    specify what operations make sense for an IE.
>>    Support shown for this as a WG item, as for File Format.
>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element identif=
iers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular happ=
en
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet arra=
y.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using thi=
s
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From weakishness@decoration-bijoux-artisanat-inde.com Thu Jul 26 08:19:30 2007
Return-path: <weakishness@decoration-bijoux-artisanat-inde.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE2JV-0006TQ-Ox; Thu, 26 Jul 2007 08:19:29 -0400
Received: from relay.pilot-tv.com.ua ([212.9.242.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IE2JU-0003mi-38; Thu, 26 Jul 2007 08:19:29 -0400
Received: from [212.9.242.14] by mail.decoration-bijoux-artisanat-inde.com; Thu, 26 Jul 2007 12:23:13 -0200
Message-ID: <01c7cf7f$bc7a5b00$0ef209d4@weakishness>
From: "Houston Ames" <weakishness@decoration-bijoux-artisanat-inde.com>
To: <ipfix-archive@lists.ietf.org>
Subject: THANKS TO THIS SITE I CAN DOWNLOAD PHOTOSHOP CS3 ONLY $89 $269 Retail Price - US $ 1799.00 you save $1529
Date: Thu, 26 Jul 2007 12:23:13 -0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

You save: $529.05 adobe photoshop cs2 v9.0
http://weboemlinksoft.com




From ipfix-bounces@ietf.org Thu Jul 26 10:13:10 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE45R-0000Xx-Bp; Thu, 26 Jul 2007 10:13:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE45Q-0000Xs-K7
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:13:04 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE45Q-0004yX-34
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:13:04 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:13:02 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFRIqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149084141:sNHT28674508"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QED1wx032482; 
	Thu, 26 Jul 2007 16:13:01 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QECtkt007876; 
	Thu, 26 Jul 2007 14:12:55 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA05019;
	Thu, 26 Jul 2007 15:12:49 +0100 (BST)
Message-ID: <46A8ABE3.4000806@cisco.com>
Date: Thu, 26 Jul 2007 15:12:51 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
In-Reply-To: <46A86C0B.90209@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2555; t=1185459181;
	x=1186323181; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20Review=3A=20draft-kobayashi-ipfix-mediator-
	model-00 |Sender:=20;
	bh=8nKt0yfGUSQc7evlyGNf2xCX8iGCHgzj7vnXMHagkrY=;
	b=Q+iEd8e6SEXIc5y6qxL9LOSEdCMPZfwqGC7r3XE0v2wz7LfPgGFwE807RbiGym1gd71mCVrn
	5l6Hx/yZ0aYFoRkRZlBBjOSEccQ9TMRkm3dMfw0YHJzlC6+y7vc0DmHJ;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

> Just a small comment:
> 
> Paul Aitken wrote:
>>>    Modification of the value of Information Element
>>>
>>>       This function modifies the value of specified Information Elements
>>>       according to instructions configured by the user.
>>>
>>>       For example, this function enables us to overwrite private
>>>       information with zeros or the maximum value.  In particular, IP
>>>       address and port number is sensitive private information.  In the
>>>       case of monitoring traffic trends and traffic engineering, these
>>>       Information Elements are not essential factors for those purposes.
>>>       In that case, modification anonymizes the relevant Information
>>>       Elements to prevent a violation of privacy.  If modification can
>>>       anonymize some Information Elements, it might need to report which
>>>       Information Elements are anonymized.  For example,
>>>       "anonymizationIndicator" indicates which Information Elements have
>>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>>>       The anonymization method is outside the scope of this document.
>> Why would we not just modify the template and remove these Information
>> Elements?
> 
> Instead of removing IP addresses you might want to apply anonymization
> techniques which preserve prefix information while still preventing
> inference of the original addresses. E.g. see CryptoPAN already deployed
> by many Netflow tools like "flow-tools":
> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/

Indeed, anonymization is mentioned in section 6.7 of the IPFIX 
requirements, RFC 3917.

However, as far as I can see it's not something that anyone in the WG 
seems to have worked on until now. But since now it appears both in 
Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's 
time we began to consider what the best method might be?

So my question is: what is the value of storing or forwarding anonymised 
information? Since the original data can not be determined from the 
anoymised data, it only serves to indicate that there was some data 
there which was anonymised (ie, the anonymised data is of no value 
itself) - and I can think of a better way to do that, eg send a reduced 
size version of the field with zero-length.

And if it's not necessary to indicate that the field was there then 
surely the best way to anoymise it is to remove it entirely?

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:13:10 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE45R-0000Xx-Bp; Thu, 26 Jul 2007 10:13:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE45Q-0000Xs-K7
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:13:04 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE45Q-0004yX-34
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:13:04 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:13:02 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFRIqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149084141:sNHT28674508"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QED1wx032482; 
	Thu, 26 Jul 2007 16:13:01 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QECtkt007876; 
	Thu, 26 Jul 2007 14:12:55 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA05019;
	Thu, 26 Jul 2007 15:12:49 +0100 (BST)
Message-ID: <46A8ABE3.4000806@cisco.com>
Date: Thu, 26 Jul 2007 15:12:51 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
In-Reply-To: <46A86C0B.90209@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2555; t=1185459181;
	x=1186323181; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20Review=3A=20draft-kobayashi-ipfix-mediator-
	model-00 |Sender:=20;
	bh=8nKt0yfGUSQc7evlyGNf2xCX8iGCHgzj7vnXMHagkrY=;
	b=Q+iEd8e6SEXIc5y6qxL9LOSEdCMPZfwqGC7r3XE0v2wz7LfPgGFwE807RbiGym1gd71mCVrn
	5l6Hx/yZ0aYFoRkRZlBBjOSEccQ9TMRkm3dMfw0YHJzlC6+y7vc0DmHJ;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

> Just a small comment:
> 
> Paul Aitken wrote:
>>>    Modification of the value of Information Element
>>>
>>>       This function modifies the value of specified Information Elements
>>>       according to instructions configured by the user.
>>>
>>>       For example, this function enables us to overwrite private
>>>       information with zeros or the maximum value.  In particular, IP
>>>       address and port number is sensitive private information.  In the
>>>       case of monitoring traffic trends and traffic engineering, these
>>>       Information Elements are not essential factors for those purposes.
>>>       In that case, modification anonymizes the relevant Information
>>>       Elements to prevent a violation of privacy.  If modification can
>>>       anonymize some Information Elements, it might need to report which
>>>       Information Elements are anonymized.  For example,
>>>       "anonymizationIndicator" indicates which Information Elements have
>>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
>>>       The anonymization method is outside the scope of this document.
>> Why would we not just modify the template and remove these Information
>> Elements?
> 
> Instead of removing IP addresses you might want to apply anonymization
> techniques which preserve prefix information while still preventing
> inference of the original addresses. E.g. see CryptoPAN already deployed
> by many Netflow tools like "flow-tools":
> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/

Indeed, anonymization is mentioned in section 6.7 of the IPFIX 
requirements, RFC 3917.

However, as far as I can see it's not something that anyone in the WG 
seems to have worked on until now. But since now it appears both in 
Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's 
time we began to consider what the best method might be?

So my question is: what is the value of storing or forwarding anonymised 
information? Since the original data can not be determined from the 
anoymised data, it only serves to indicate that there was some data 
there which was anonymised (ie, the anonymised data is of no value 
itself) - and I can think of a better way to do that, eg send a reduced 
size version of the field with zero-length.

And if it's not necessary to indicate that the field was there then 
surely the best way to anoymise it is to remove it entirely?

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:15:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE47I-0002tx-8H; Thu, 26 Jul 2007 10:15:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE47H-0002tr-HC
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:14:59 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE47G-0006MZ-9F
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:14:59 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:14:58 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAExJqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149084341:sNHT194078512"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QEEvPV018665; 
	Thu, 26 Jul 2007 16:14:57 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QEEukt008566; 
	Thu, 26 Jul 2007 14:14:56 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA05194;
	Thu, 26 Jul 2007 15:14:54 +0100 (BST)
Message-ID: <46A8AC61.803@cisco.com>
Date: Thu, 26 Jul 2007 15:14:57 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
	<46A882D0.4050700@informatik.uni-tuebingen.de>
In-Reply-To: <46A882D0.4050700@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=359; t=1185459297;
	x=1186323297; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20new=20work=20item=20candidate=20#4=3A=20ext
	ended=20types |Sender:=20;
	bh=xDrwWmy+z3WFehKGfXowYL8yAfs6t2eqgyxwKMSU7Ow=;
	b=ma5vveJPndpJOV/2ztBRNl2ljcfxAh6YaXRa/Pj82AeynxlSLTK+CBwuzZnSmGVyRZpfWmp8
	7UcICfk0RpSmarl2O0pZ6MgYqgk1fFJ0B4S+UIKx7Ey8WSnGqZY4CSAF;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

> By the way: Have you considered an additional IE like
> informationElementDescription holding an octet string describing the
> semantic of the IE "in human-readable English"?

Perhaps we should just export an XML definition with all the fields 
which we find in IPFIX-INFO? :-)

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:15:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE47I-0002tx-8H; Thu, 26 Jul 2007 10:15:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE47H-0002tr-HC
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:14:59 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE47G-0006MZ-9F
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:14:59 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:14:58 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAExJqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149084341:sNHT194078512"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QEEvPV018665; 
	Thu, 26 Jul 2007 16:14:57 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QEEukt008566; 
	Thu, 26 Jul 2007 14:14:56 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA05194;
	Thu, 26 Jul 2007 15:14:54 +0100 (BST)
Message-ID: <46A8AC61.803@cisco.com>
Date: Thu, 26 Jul 2007 15:14:57 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
	<46A882D0.4050700@informatik.uni-tuebingen.de>
In-Reply-To: <46A882D0.4050700@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=359; t=1185459297;
	x=1186323297; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20new=20work=20item=20candidate=20#4=3A=20ext
	ended=20types |Sender:=20;
	bh=xDrwWmy+z3WFehKGfXowYL8yAfs6t2eqgyxwKMSU7Ow=;
	b=ma5vveJPndpJOV/2ztBRNl2ljcfxAh6YaXRa/Pj82AeynxlSLTK+CBwuzZnSmGVyRZpfWmp8
	7UcICfk0RpSmarl2O0pZ6MgYqgk1fFJ0B4S+UIKx7Ey8WSnGqZY4CSAF;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

> By the way: Have you considered an additional IE like
> informationElementDescription holding an octet string describing the
> semantic of the IE "in human-readable English"?

Perhaps we should just export an XML definition with all the fields 
which we find in IPFIX-INFO? :-)

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:36:33 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4S8-0004QM-NS; Thu, 26 Jul 2007 10:36:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4S7-0004QH-M3
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:36:31 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4S6-0006DR-Sw
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:36:31 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6QEaQHx028583; 
	Thu, 26 Jul 2007 16:36:26 +0200
Message-ID: <46A8B154.2050806@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 16:36:04 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
In-Reply-To: <46A8ABE3.4000806@cisco.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1489396408=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1489396408==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050505030004010509060304"

This is a cryptographically signed message in MIME format.

--------------ms050505030004010509060304
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Paul,

Paul Aitken wrote:
>> Paul Aitken wrote:
>>> Why would we not just modify the template and remove these Information
>>> Elements?
>>
>> Instead of removing IP addresses you might want to apply anonymization
>> techniques which preserve prefix information while still preventing
>> inference of the original addresses. E.g. see CryptoPAN already deployed
>> by many Netflow tools like "flow-tools":
>> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
> 
> Indeed, anonymization is mentioned in section 6.7 of the IPFIX
> requirements, RFC 3917.
> 
> However, as far as I can see it's not something that anyone in the WG
> seems to have worked on until now. But since now it appears both in
> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's
> time we began to consider what the best method might be?

Just because this issue has not been on the mailing list, this does not
mean that nobody in the community has been working on it. For example,
we have worked on it in the scope of the HISTORY project focusing on
different anonymization techniques and legal issues in Germany.
http://www.history-project.net/index.php?show=anonym
http://www.history-project.net/anonym/index_e.html
http://www7.informatik.uni-erlangen.de/~dressler/publications/pik-2006.pdf

> So my question is: what is the value of storing or forwarding anonymised
> information? Since the original data can not be determined from the
> anoymised data, it only serves to indicate that there was some data
> there which was anonymised (ie, the anonymised data is of no value
> itself) - and I can think of a better way to do that, eg send a reduced
> size version of the field with zero-length.

There is a difference in anonymized data and non-existing data, e.g. if
two anonymized IP addresses are different, you know that the original
ones were different as well, and that they belonged to the same subnet
(if prefix-preserving techniques are deployed). But if you remove the
information, you lose this information.

> And if it's not necessary to indicate that the field was there then
> surely the best way to anoymise it is to remove it entirely?

Anonymization is very important for academics who always try to convince
network operators to give them some real measurement data for their
research.

Regards,
Gerhard

-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms050505030004010509060304
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDcyNjE0MzYwNFowIwYJKoZIhvcNAQkEMRYEFMPjXAERlqXz
p968WphXU/moPQhNMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQCvoeXnBrx/oOmkCWI2yxyANgkdYPXr1YF4rDAZfkZXsrhQaTlbBfxXeXab
pkivxExtRJ4IXJlBcih0lD1IjGbRk53PXa6iuuPpCPDAHnz7XJPvYBRwdjOo6vQ7hD0GB8hC
zcPlHxXH8nq3IHPvVZ1gobRN3nPDQeOPhK/tnPCFC82VkoafVmG+y1lF2kCOBLVA6tMi5sxO
75ChhPcPYJBF1/G921wi85c9xuX2rDRoPlJ/soSEyV6mn2jmGQ38vmz5d+seGKRidtZxJKVK
usZfYyvqJSxUFzXd70hmnbMU8jyBQqic+0moPBapT0chdVsnEUG7iX5uY8DnGjMPU3LjAAAA
AAAA
--------------ms050505030004010509060304--


--===============1489396408==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1489396408==--




From ipfix-bounces@ietf.org Thu Jul 26 10:36:33 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4S8-0004QM-NS; Thu, 26 Jul 2007 10:36:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4S7-0004QH-M3
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:36:31 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4S6-0006DR-Sw
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:36:31 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6QEaQHx028583; 
	Thu, 26 Jul 2007 16:36:26 +0200
Message-ID: <46A8B154.2050806@informatik.uni-tuebingen.de>
Date: Thu, 26 Jul 2007 16:36:04 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
In-Reply-To: <46A8ABE3.4000806@cisco.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.187; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1489396408=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1489396408==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050505030004010509060304"

This is a cryptographically signed message in MIME format.

--------------ms050505030004010509060304
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Paul,

Paul Aitken wrote:
>> Paul Aitken wrote:
>>> Why would we not just modify the template and remove these Information
>>> Elements?
>>
>> Instead of removing IP addresses you might want to apply anonymization
>> techniques which preserve prefix information while still preventing
>> inference of the original addresses. E.g. see CryptoPAN already deployed
>> by many Netflow tools like "flow-tools":
>> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
> 
> Indeed, anonymization is mentioned in section 6.7 of the IPFIX
> requirements, RFC 3917.
> 
> However, as far as I can see it's not something that anyone in the WG
> seems to have worked on until now. But since now it appears both in
> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's
> time we began to consider what the best method might be?

Just because this issue has not been on the mailing list, this does not
mean that nobody in the community has been working on it. For example,
we have worked on it in the scope of the HISTORY project focusing on
different anonymization techniques and legal issues in Germany.
http://www.history-project.net/index.php?show=anonym
http://www.history-project.net/anonym/index_e.html
http://www7.informatik.uni-erlangen.de/~dressler/publications/pik-2006.pdf

> So my question is: what is the value of storing or forwarding anonymised
> information? Since the original data can not be determined from the
> anoymised data, it only serves to indicate that there was some data
> there which was anonymised (ie, the anonymised data is of no value
> itself) - and I can think of a better way to do that, eg send a reduced
> size version of the field with zero-length.

There is a difference in anonymized data and non-existing data, e.g. if
two anonymized IP addresses are different, you know that the original
ones were different as well, and that they belonged to the same subnet
(if prefix-preserving techniques are deployed). But if you remove the
information, you lose this information.

> And if it's not necessary to indicate that the field was there then
> surely the best way to anoymise it is to remove it entirely?

Anonymization is very important for academics who always try to convince
network operators to give them some real measurement data for their
research.

Regards,
Gerhard

-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms050505030004010509060304
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDcyNjE0MzYwNFowIwYJKoZIhvcNAQkEMRYEFMPjXAERlqXz
p968WphXU/moPQhNMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQCvoeXnBrx/oOmkCWI2yxyANgkdYPXr1YF4rDAZfkZXsrhQaTlbBfxXeXab
pkivxExtRJ4IXJlBcih0lD1IjGbRk53PXa6iuuPpCPDAHnz7XJPvYBRwdjOo6vQ7hD0GB8hC
zcPlHxXH8nq3IHPvVZ1gobRN3nPDQeOPhK/tnPCFC82VkoafVmG+y1lF2kCOBLVA6tMi5sxO
75ChhPcPYJBF1/G921wi85c9xuX2rDRoPlJ/soSEyV6mn2jmGQ38vmz5d+seGKRidtZxJKVK
usZfYyvqJSxUFzXd70hmnbMU8jyBQqic+0moPBapT0chdVsnEUG7iX5uY8DnGjMPU3LjAAAA
AAAA
--------------ms050505030004010509060304--


--===============1489396408==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1489396408==--




From ipfix-bounces@ietf.org Thu Jul 26 10:42:15 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4Xf-00018Q-E9; Thu, 26 Jul 2007 10:42:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4Xe-000172-DZ
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:42:14 -0400
Received: from tama55.ecl.ntt.co.jp ([129.60.39.103])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4Xd-0006Lu-Ds
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:42:14 -0400
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by tama55.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEgBZO000852;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id ACECD20AE2B;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 7D82320AE29;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEgAqi007268; 
	Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6QEgAYO010199; Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from imm.m.ecl.ntt.co.jp (imm0.m.ecl.ntt.co.jp [129.60.5.151])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6QEgAxx010196; Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.56])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEg794020795;
	Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Message-ID: <46A8B2EB.6090800@lab.ntt.co.jp>
Date: Thu, 26 Jul 2007 23:42:51 +0900
From: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Organization: NTT
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Juergen Quittek <Quittek@netlab.nec.de>, ipfix@ietf.org
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
In-Reply-To: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

(2007/07/26 15:38), Juergen Quittek wrote:
> Dear all,
> 
> Candidates #6 to become a new IPFIX work item is described by
> draft draft-irino-ipfix-ie-order-02.txt.
> 
>> 6. Order of Information Elements (Irino)
>>    Interesting, need more people to measure possible efficiency gain.
>>    Would this be better as an individual draft?
> 
> This draft suggests a special ordering of information elements in a
> flow record.  At the very brief presentation at our session, the author
> explained that he can improve the performance of IPFIX exporter and
> collector significantly. To prove this, he compared a random order
> of information elements with an order according to his proposal
> and achieved significant performance improvements.
> 
> Speaking as technical contributor, I think that if these results would
> be the same also for other implementations of IPFIX, then this looks like
> a very good IPFIX work item.
> 
> Speaking as co-chair, I would like to ask everybody who has an IPFIX
> implementation to conduct a short experiment in order to find out if
> the improvement is the same for his/her implementations.
> 
> Would any implementor be willing to do so?
> If yes, until when would you have results?
> 
> Thanks,
> 
>     Juergen

A day before yesterday, I had a presentation about a performance result
when exporters and collectors use same order, however I didn't have any 
time to talk about the reason of difference of performance.

In the slide,
( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
I use very primitive collector which I implemented. This collector
receive data records and write the data to file.
This collector has internal proprietary format to store to data to file.
The format consists of some Information Elements whose size are full
size. (For example, bgpSourceAsNumber is 4 octets.)

This collector process following steps:
  1) read the data record.
  2) convert received data records to the collector's format on memory.
  3) write to file from memory.

I tested each combination of 3 kind of orders for template of exporter
and format of collector.
  1) An order same as NetFlow version 5
  2) Suggested Order in my draft (separating constant fixed length IEs
and reduced size encoding applicable IEs)
  3) Random order
In this test, exporter's template includes set of Information Elements
same as NetFlow version 5 fields.
These templates and formats are shown in page 9 in the slide.

I measured 10 times this test.
The matrix table in page 4 is the result of this test. Upper one shows
total time, lower one shows ratio.

My collector program can process bulk of sequential Information
Elements. For example in the case reading from date records ordered by
suggested order to writing format formed by suggested order, my
collector program copies first 20 octets (from sourceIPv4Address to
ipClassOfService) at once.

I described counts for processing in from page 10 to 12 in the slide.
For example, in the best case that a exporter uses suggested order and a
collector uses suggested order, the counts for processing (processing
means coping data in this case) is 8 (on middle table in page 11). In
the worst case a exporter uses random order and collector uses random
order, the counts is 17 (on right table in page 11). Difference of the
counts for processing effects their performance.
my presentation shows one of the best case.

Therefore, there are effective case and ineffective case by ordering.

Example of effective case
  writing to files
  real time flow filtering (comparing bulk data)

Example of ineffective case
  when process each Information Element

By the way, if all exporter supports draft-muenz-ipfix-configuration and
operators can set configuration about template completely freely, my
draft is not important, because operator can adjust configuration for
collector.
However currently NetFlow v9 implementations of some router makers are
not configurable at all. Operators can choice preset template on these 
implementations. If this state continues in future, reference order is 
valuable for these exporters' implementations and collectors' 
implementations. Therefore I've thought a reference order should be
defined as Informational. I suggested an order adjusted for collector's
performance, however perhaps it is not suitable for exporter. So I hope
to discuss on WG.

thanks,
Hitoshi Irino

-- 
Hitoshi Irino
NTT Network Service Systems Laboratories
9-11 Midori-cho 3-Chome, Musashino-shi, Tokyo 180-8585 Japan
Tel: +81-422-59-4403  Fax: +81-422-59-4549

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:42:16 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4Xf-00018Q-E9; Thu, 26 Jul 2007 10:42:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4Xe-000172-DZ
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:42:14 -0400
Received: from tama55.ecl.ntt.co.jp ([129.60.39.103])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4Xd-0006Lu-Ds
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:42:14 -0400
Received: from mfs34.rdh.ecl.ntt.co.jp (mfs34.rdh.ecl.ntt.co.jp
	[129.60.39.114])
	by tama55.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEgBZO000852;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from mfs34.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id ACECD20AE2B;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (nttmail3.ecl.ntt.co.jp [129.60.39.100])
	by mfs34.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 7D82320AE29;
	Thu, 26 Jul 2007 23:42:11 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by nttmail3.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEgAqi007268; 
	Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6QEgAYO010199; Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from imm.m.ecl.ntt.co.jp (imm0.m.ecl.ntt.co.jp [129.60.5.151])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	l6QEgAxx010196; Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Received: from [127.0.0.1] ([129.60.80.56])
	by imm.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id l6QEg794020795;
	Thu, 26 Jul 2007 23:42:10 +0900 (JST)
Message-ID: <46A8B2EB.6090800@lab.ntt.co.jp>
Date: Thu, 26 Jul 2007 23:42:51 +0900
From: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Organization: NTT
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Juergen Quittek <Quittek@netlab.nec.de>, ipfix@ietf.org
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
In-Reply-To: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: 
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

(2007/07/26 15:38), Juergen Quittek wrote:
> Dear all,
> 
> Candidates #6 to become a new IPFIX work item is described by
> draft draft-irino-ipfix-ie-order-02.txt.
> 
>> 6. Order of Information Elements (Irino)
>>    Interesting, need more people to measure possible efficiency gain.
>>    Would this be better as an individual draft?
> 
> This draft suggests a special ordering of information elements in a
> flow record.  At the very brief presentation at our session, the author
> explained that he can improve the performance of IPFIX exporter and
> collector significantly. To prove this, he compared a random order
> of information elements with an order according to his proposal
> and achieved significant performance improvements.
> 
> Speaking as technical contributor, I think that if these results would
> be the same also for other implementations of IPFIX, then this looks like
> a very good IPFIX work item.
> 
> Speaking as co-chair, I would like to ask everybody who has an IPFIX
> implementation to conduct a short experiment in order to find out if
> the improvement is the same for his/her implementations.
> 
> Would any implementor be willing to do so?
> If yes, until when would you have results?
> 
> Thanks,
> 
>     Juergen

A day before yesterday, I had a presentation about a performance result
when exporters and collectors use same order, however I didn't have any 
time to talk about the reason of difference of performance.

In the slide,
( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
I use very primitive collector which I implemented. This collector
receive data records and write the data to file.
This collector has internal proprietary format to store to data to file.
The format consists of some Information Elements whose size are full
size. (For example, bgpSourceAsNumber is 4 octets.)

This collector process following steps:
  1) read the data record.
  2) convert received data records to the collector's format on memory.
  3) write to file from memory.

I tested each combination of 3 kind of orders for template of exporter
and format of collector.
  1) An order same as NetFlow version 5
  2) Suggested Order in my draft (separating constant fixed length IEs
and reduced size encoding applicable IEs)
  3) Random order
In this test, exporter's template includes set of Information Elements
same as NetFlow version 5 fields.
These templates and formats are shown in page 9 in the slide.

I measured 10 times this test.
The matrix table in page 4 is the result of this test. Upper one shows
total time, lower one shows ratio.

My collector program can process bulk of sequential Information
Elements. For example in the case reading from date records ordered by
suggested order to writing format formed by suggested order, my
collector program copies first 20 octets (from sourceIPv4Address to
ipClassOfService) at once.

I described counts for processing in from page 10 to 12 in the slide.
For example, in the best case that a exporter uses suggested order and a
collector uses suggested order, the counts for processing (processing
means coping data in this case) is 8 (on middle table in page 11). In
the worst case a exporter uses random order and collector uses random
order, the counts is 17 (on right table in page 11). Difference of the
counts for processing effects their performance.
my presentation shows one of the best case.

Therefore, there are effective case and ineffective case by ordering.

Example of effective case
  writing to files
  real time flow filtering (comparing bulk data)

Example of ineffective case
  when process each Information Element

By the way, if all exporter supports draft-muenz-ipfix-configuration and
operators can set configuration about template completely freely, my
draft is not important, because operator can adjust configuration for
collector.
However currently NetFlow v9 implementations of some router makers are
not configurable at all. Operators can choice preset template on these 
implementations. If this state continues in future, reference order is 
valuable for these exporters' implementations and collectors' 
implementations. Therefore I've thought a reference order should be
defined as Informational. I suggested an order adjusted for collector's
performance, however perhaps it is not suitable for exporter. So I hope
to discuss on WG.

thanks,
Hitoshi Irino

-- 
Hitoshi Irino
NTT Network Service Systems Laboratories
9-11 Midori-cho 3-Chome, Musashino-shi, Tokyo 180-8585 Japan
Tel: +81-422-59-4403  Fax: +81-422-59-4549

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:45:52 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4bA-0002wA-9A; Thu, 26 Jul 2007 10:45:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4b9-0002w1-Kh
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:45:51 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE4b8-0007ko-Aw
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:45:51 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:45:49 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIlQqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149088993:sNHT29877264"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QEjnJ2011848; 
	Thu, 26 Jul 2007 16:45:49 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QEjnkt023485; 
	Thu, 26 Jul 2007 14:45:49 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA07981;
	Thu, 26 Jul 2007 15:45:47 +0100 (BST)
Message-ID: <46A8B39D.8040208@cisco.com>
Date: Thu, 26 Jul 2007 15:45:49 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
	<46A8B154.2050806@informatik.uni-tuebingen.de>
In-Reply-To: <46A8B154.2050806@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2636; t=1185461149;
	x=1186325149; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20Review=3A=20draft-kobayashi-ipfix-mediator-
	model-00 |Sender:=20;
	bh=RKja3qI9UFzgLiOrv3ci5jXL8RBLyB0DCbHaihAtX+M=;
	b=Oiw8fJ7QPfQo7Qgf7+Dn1awONAMSZlXuvHkt/JN1MQCBuZ9D9eke6EMbviUXtoGzrTNB9s2d
	JcM/HA9P68AQmCETxMdU17OQG+A4R+RBc5c/UARKf7JUE5EeHFFjXQfG;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

These are all very points. Thank you for sharing them here. Perhaps you 
should write an IPFIX anonymisation draft? :-)


> Paul Aitken wrote:
>>> Paul Aitken wrote:
>>>> Why would we not just modify the template and remove these Information
>>>> Elements?
>>> Instead of removing IP addresses you might want to apply anonymization
>>> techniques which preserve prefix information while still preventing
>>> inference of the original addresses. E.g. see CryptoPAN already deployed
>>> by many Netflow tools like "flow-tools":
>>> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
>> Indeed, anonymization is mentioned in section 6.7 of the IPFIX
>> requirements, RFC 3917.
>>
>> However, as far as I can see it's not something that anyone in the WG
>> seems to have worked on until now. But since now it appears both in
>> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's
>> time we began to consider what the best method might be?
> 
> Just because this issue has not been on the mailing list, this does not
> mean that nobody in the community has been working on it. For example,
> we have worked on it in the scope of the HISTORY project focusing on
> different anonymization techniques and legal issues in Germany.
> http://www.history-project.net/index.php?show=anonym
> http://www.history-project.net/anonym/index_e.html
> http://www7.informatik.uni-erlangen.de/~dressler/publications/pik-2006.pdf
> 
>> So my question is: what is the value of storing or forwarding anonymised
>> information? Since the original data can not be determined from the
>> anoymised data, it only serves to indicate that there was some data
>> there which was anonymised (ie, the anonymised data is of no value
>> itself) - and I can think of a better way to do that, eg send a reduced
>> size version of the field with zero-length.
> 
> There is a difference in anonymized data and non-existing data, e.g. if
> two anonymized IP addresses are different, you know that the original
> ones were different as well, and that they belonged to the same subnet
> (if prefix-preserving techniques are deployed). But if you remove the
> information, you lose this information.
> 
>> And if it's not necessary to indicate that the field was there then
>> surely the best way to anoymise it is to remove it entirely?
> 
> Anonymization is very important for academics who always try to convince
> network operators to give them some real measurement data for their
> research.
> 
> Regards,
> Gerhard

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 10:45:52 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4bA-0002wA-9A; Thu, 26 Jul 2007 10:45:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4b9-0002w1-Kh
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:45:51 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE4b8-0007ko-Aw
	for ipfix@ietf.org; Thu, 26 Jul 2007 10:45:51 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 16:45:49 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIlQqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149088993:sNHT29877264"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QEjnJ2011848; 
	Thu, 26 Jul 2007 16:45:49 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QEjnkt023485; 
	Thu, 26 Jul 2007 14:45:49 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA07981;
	Thu, 26 Jul 2007 15:45:47 +0100 (BST)
Message-ID: <46A8B39D.8040208@cisco.com>
Date: Thu, 26 Jul 2007 15:45:49 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
References: <46A7D10F.3050509@cisco.com>
	<46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
	<46A8B154.2050806@informatik.uni-tuebingen.de>
In-Reply-To: <46A8B154.2050806@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2636; t=1185461149;
	x=1186325149; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20Review=3A=20draft-kobayashi-ipfix-mediator-
	model-00 |Sender:=20;
	bh=RKja3qI9UFzgLiOrv3ci5jXL8RBLyB0DCbHaihAtX+M=;
	b=Oiw8fJ7QPfQo7Qgf7+Dn1awONAMSZlXuvHkt/JN1MQCBuZ9D9eke6EMbviUXtoGzrTNB9s2d
	JcM/HA9P68AQmCETxMdU17OQG+A4R+RBc5c/UARKf7JUE5EeHFFjXQfG;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Gerhard,

These are all very points. Thank you for sharing them here. Perhaps you 
should write an IPFIX anonymisation draft? :-)


> Paul Aitken wrote:
>>> Paul Aitken wrote:
>>>> Why would we not just modify the template and remove these Information
>>>> Elements?
>>> Instead of removing IP addresses you might want to apply anonymization
>>> techniques which preserve prefix information while still preventing
>>> inference of the original addresses. E.g. see CryptoPAN already deployed
>>> by many Netflow tools like "flow-tools":
>>> http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
>> Indeed, anonymization is mentioned in section 6.7 of the IPFIX
>> requirements, RFC 3917.
>>
>> However, as far as I can see it's not something that anyone in the WG
>> seems to have worked on until now. But since now it appears both in
>> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's
>> time we began to consider what the best method might be?
> 
> Just because this issue has not been on the mailing list, this does not
> mean that nobody in the community has been working on it. For example,
> we have worked on it in the scope of the HISTORY project focusing on
> different anonymization techniques and legal issues in Germany.
> http://www.history-project.net/index.php?show=anonym
> http://www.history-project.net/anonym/index_e.html
> http://www7.informatik.uni-erlangen.de/~dressler/publications/pik-2006.pdf
> 
>> So my question is: what is the value of storing or forwarding anonymised
>> information? Since the original data can not be determined from the
>> anoymised data, it only serves to indicate that there was some data
>> there which was anonymised (ie, the anonymised data is of no value
>> itself) - and I can think of a better way to do that, eg send a reduced
>> size version of the field with zero-length.
> 
> There is a difference in anonymized data and non-existing data, e.g. if
> two anonymized IP addresses are different, you know that the original
> ones were different as well, and that they belonged to the same subnet
> (if prefix-preserving techniques are deployed). But if you remove the
> information, you lose this information.
> 
>> And if it's not necessary to indicate that the field was there then
>> surely the best way to anoymise it is to remove it entirely?
> 
> Anonymization is very important for academics who always try to convince
> network operators to give them some real measurement data for their
> research.
> 
> Regards,
> Gerhard

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 11:02:20 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4r1-0005BO-Kg; Thu, 26 Jul 2007 11:02:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4r0-0005B4-BR
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:02:14 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4qz-0006z0-Qx
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:02:14 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 17:01:57 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAAtUqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149091360:sNHT7737832650"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QF1vv6017554; 
	Thu, 26 Jul 2007 17:01:57 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QF1ukt000966; 
	Thu, 26 Jul 2007 15:01:56 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA09319;
	Thu, 26 Jul 2007 16:01:54 +0100 (BST)
Message-ID: <46A8B761.5060107@cisco.com>
Date: Thu, 26 Jul 2007 16:01:53 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1959; t=1185462117;
	x=1186326117; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20new=20work=20item=20candidate=20#6=3A=20ord
	er=20of=20information=20elements |Sender:=20;
	bh=t8DbpjlIT2Xh3O+ap7yJh/EpTNpMkTw0/H0PyCPFGgo=;
	b=DD0yKcrj2CLdsobSFCqh+AVqjFaTufoEyq0kmp6TTD/yc7eT/B1pJDmLk/peAeEspL5BXtXX
	5uOe3yXUH1TVga5oRbfGEhngZhMZ+LRwnAzEQt6gtQAMt+LAIcFkgyof;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hitoshi-san,

> By the way, if all exporter supports draft-muenz-ipfix-configuration and
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
>
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these 
> implementations. If this state continues in future, reference order is 
> valuable for these exporters' implementations and collectors' 
> implementations.

Cisco's new Flexible NetFlow (http://cisco.com/go/fnf) allows users to 
configure which fields are monitored for each individual cache.

Obviously this affects the export templates - but since the user 
configures which fields are in the cache (and not the export templates), 
the router is able to store and export the fields in the most optimal way.

Actually, I think that changing what is monitored by (re)configuring the 
export template(s) is exactly the wrong way to go.

Rather, the user should configure what they want to monitor and the 
export template(s) should be changed by the Exporting Process to support 
the fields that are being monitored.

If your research proves a way to optimise the export, then this model 
also allows the Exporting Process to optimise the exported data 
independently of the user's configuration. So it's definitely a big win.


> Therefore I've thought a reference order should be defined as Informational.

If other groups are able to show similar improvements, then I think we 
will all want to adopt your ideas.

So I hope that everyone will follow Jeurgen's request:

     I would like to ask everybody who has an IPFIX implementation to
     conduct a short experiment in order to find out if the improvement
     is the same for his/her implementations.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 11:02:20 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4r1-0005BO-Kg; Thu, 26 Jul 2007 11:02:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4r0-0005B4-BR
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:02:14 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE4qz-0006z0-Qx
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:02:14 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 17:01:57 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAAtUqEaQ/uCLZmdsb2JhbACPaAsKJA
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149091360:sNHT7737832650"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6QF1vv6017554; 
	Thu, 26 Jul 2007 17:01:57 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QF1ukt000966; 
	Thu, 26 Jul 2007 15:01:56 GMT
Received: from [10.89.21.61] (rcdn-vpn-cluster-2-316.cisco.com [10.89.21.61])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA09319;
	Thu, 26 Jul 2007 16:01:54 +0100 (BST)
Message-ID: <46A8B761.5060107@cisco.com>
Date: Thu, 26 Jul 2007 16:01:53 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1959; t=1185462117;
	x=1186326117; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20new=20work=20item=20candidate=20#6=3A=20ord
	er=20of=20information=20elements |Sender:=20;
	bh=t8DbpjlIT2Xh3O+ap7yJh/EpTNpMkTw0/H0PyCPFGgo=;
	b=DD0yKcrj2CLdsobSFCqh+AVqjFaTufoEyq0kmp6TTD/yc7eT/B1pJDmLk/peAeEspL5BXtXX
	5uOe3yXUH1TVga5oRbfGEhngZhMZ+LRwnAzEQt6gtQAMt+LAIcFkgyof;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hitoshi-san,

> By the way, if all exporter supports draft-muenz-ipfix-configuration and
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
>
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these 
> implementations. If this state continues in future, reference order is 
> valuable for these exporters' implementations and collectors' 
> implementations.

Cisco's new Flexible NetFlow (http://cisco.com/go/fnf) allows users to 
configure which fields are monitored for each individual cache.

Obviously this affects the export templates - but since the user 
configures which fields are in the cache (and not the export templates), 
the router is able to store and export the fields in the most optimal way.

Actually, I think that changing what is monitored by (re)configuring the 
export template(s) is exactly the wrong way to go.

Rather, the user should configure what they want to monitor and the 
export template(s) should be changed by the Exporting Process to support 
the fields that are being monitored.

If your research proves a way to optimise the export, then this model 
also allows the Exporting Process to optimise the exported data 
independently of the user's configuration. So it's definitely a big win.


> Therefore I've thought a reference order should be defined as Informational.

If other groups are able to show similar improvements, then I think we 
will all want to adopt your ideas.

So I hope that everyone will follow Jeurgen's request:

     I would like to ask everybody who has an IPFIX implementation to
     conduct a short experiment in order to find out if the improvement
     is the same for his/her implementations.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 11:04:33 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4tE-0000tV-SZ; Thu, 26 Jul 2007 11:04:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4tD-0000r9-1E
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:04:31 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE4tB-0008Nu-J2
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:04:31 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QF4QY13467; Thu, 26 Jul 2007 17:04:26 +0200 (CEST)
Received: from [10.82.241.128] (rtp-vpn2-384.cisco.com [10.82.241.128])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QF4OQ13402; Thu, 26 Jul 2007 17:04:24 +0200 (CEST)
Message-ID: <46A8B7F7.9050008@cisco.com>
Date: Thu, 26 Jul 2007 10:04:23 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
	<46A882D0.4050700@informatik.uni-tuebingen.de>
In-Reply-To: <46A882D0.4050700@informatik.uni-tuebingen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1988918953=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1988918953==
Content-Type: multipart/alternative;
	boundary="------------080802010407020004090407"

This is a multi-part message in MIME format.
--------------080802010407020004090407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

I have exactly the same concern.

Regards, Benoit.
> Dear all,
>
> I'm undecided about this draft.
>
> On the one hand, it's a nice idea to have some IEs which allow
> describing the type and semantic of other IEs. On the other hand, my
> impression is that the usefulness is very restricted and not as broad as
> claimed in the introduction of the draft:
>
>    ... Having to do some sort of tool-specific
>    configuration (or code modification) on every tool just to tell which
>    type each used Information Element has is a huge amount of work for
>    users and implementors of enterprise-specific Information Elements.
>    Many tools in fact only need to know the field's data type to work on
>    them. ...
>
> In my opinion, any deeper analysis and processing of metering data
> requires knowledge about the semantic. Just knowing the data type may be
> enough to display values correctly. Considering
> informationElementSemanticType, you might also know if the calculation
> of statistical properties (max, min, mean, variance etc.) makes sense or
> not. But any further analysis would probably require more semantical
> knowledge. That's why I assume that, in practice, analyzing and
> processing enterprise-specific data will mostly be performed with
> specialized analysis tools that have been implemented for this specific
> purpose. And for these tools, there is no need to export the IE information.
>
> By the way: Have you considered an additional IE like
> informationElementDescription holding an octet string describing the
> semantic of the IE "in human-readable English"?
>
> Regards,
> Gerhard
>
>
> Juergen Quittek wrote:
>   
>> Dear all,
>>
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>
>>     
>>> 4. Extended Types (Elisa Boschi)
>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>    specify what operations make sense for an IE.
>>>    Support shown for this as a WG item, as for File Format.
>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>>       
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element identifiers.
>>
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular happen
>> if enterprise specific elements are used. Without this information the
>> collector would treat these elements as if they were of type octet array.
>> With this information it may be able to treat them more appropriately.
>>
>> The current version of the IPFIX file format draft recommends using this
>> method when IPFIX records are stored.
>>
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>
>> Thanks,
>>
>>     Juergen
>>
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>>     
>
>   


--------------080802010407020004090407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all,<br>
<br>
I have exactly the same concern.<br>
<br>
Regards, Benoit.<br>
<blockquote cite="mid46A882D0.4050700@informatik.uni-tuebingen.de"
 type="cite">
  <pre wrap="">Dear all,

I'm undecided about this draft.

On the one hand, it's a nice idea to have some IEs which allow
describing the type and semantic of other IEs. On the other hand, my
impression is that the usefulness is very restricted and not as broad as
claimed in the introduction of the draft:

   ... Having to do some sort of tool-specific
   configuration (or code modification) on every tool just to tell which
   type each used Information Element has is a huge amount of work for
   users and implementors of enterprise-specific Information Elements.
   Many tools in fact only need to know the field's data type to work on
   them. ...

In my opinion, any deeper analysis and processing of metering data
requires knowledge about the semantic. Just knowing the data type may be
enough to display values correctly. Considering
informationElementSemanticType, you might also know if the calculation
of statistical properties (max, min, mean, variance etc.) makes sense or
not. But any further analysis would probably require more semantical
knowledge. That's why I assume that, in practice, analyzing and
processing enterprise-specific data will mostly be performed with
specialized analysis tools that have been implemented for this specific
purpose. And for these tools, there is no need to export the IE information.

By the way: Have you considered an additional IE like
informationElementDescription holding an octet string describing the
semantic of the IE "in human-readable English"?

Regards,
Gerhard


Juergen Quittek wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Dear all,

Candidates #4 to become a new IPFIX work item is described by
draft draft-boschi-ipfix-extended-type-00.txt.

    </pre>
    <blockquote type="cite">
      <pre wrap="">4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
      </pre>
    </blockquote>
    <pre wrap="">It is a method for assigning data types to unknown IPFIX information
elements by using option records that map data types to element identifiers.

It can be applied in cases where an IPFIX collector does not know the
data type of received information elements. This may in particular happen
if enterprise specific elements are used. Without this information the
collector would treat these elements as if they were of type octet array.
With this information it may be able to treat them more appropriately.

The current version of the IPFIX file format draft recommends using this
method when IPFIX records are stored.

Do you think this is a useful extension of the IPFIX protocol?
Do you think we should accept this as an IPFIX work item?
Please have a look at the draft and send your comments.

Thanks,

    Juergen



_______________________________________________
IPFIX mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
</body>
</html>

--------------080802010407020004090407--


--===============1988918953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1988918953==--




From ipfix-bounces@ietf.org Thu Jul 26 11:04:33 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE4tE-0000tV-SZ; Thu, 26 Jul 2007 11:04:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE4tD-0000r9-1E
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:04:31 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE4tB-0008Nu-J2
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:04:31 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QF4QY13467; Thu, 26 Jul 2007 17:04:26 +0200 (CEST)
Received: from [10.82.241.128] (rtp-vpn2-384.cisco.com [10.82.241.128])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QF4OQ13402; Thu, 26 Jul 2007 17:04:24 +0200 (CEST)
Message-ID: <46A8B7F7.9050008@cisco.com>
Date: Thu, 26 Jul 2007 10:04:23 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <C2CE0B83.10238%Quittek@netlab.nec.de>
	<46A882D0.4050700@informatik.uni-tuebingen.de>
In-Reply-To: <46A882D0.4050700@informatik.uni-tuebingen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1988918953=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1988918953==
Content-Type: multipart/alternative;
	boundary="------------080802010407020004090407"

This is a multi-part message in MIME format.
--------------080802010407020004090407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

I have exactly the same concern.

Regards, Benoit.
> Dear all,
>
> I'm undecided about this draft.
>
> On the one hand, it's a nice idea to have some IEs which allow
> describing the type and semantic of other IEs. On the other hand, my
> impression is that the usefulness is very restricted and not as broad as
> claimed in the introduction of the draft:
>
>    ... Having to do some sort of tool-specific
>    configuration (or code modification) on every tool just to tell which
>    type each used Information Element has is a huge amount of work for
>    users and implementors of enterprise-specific Information Elements.
>    Many tools in fact only need to know the field's data type to work on
>    them. ...
>
> In my opinion, any deeper analysis and processing of metering data
> requires knowledge about the semantic. Just knowing the data type may be
> enough to display values correctly. Considering
> informationElementSemanticType, you might also know if the calculation
> of statistical properties (max, min, mean, variance etc.) makes sense or
> not. But any further analysis would probably require more semantical
> knowledge. That's why I assume that, in practice, analyzing and
> processing enterprise-specific data will mostly be performed with
> specialized analysis tools that have been implemented for this specific
> purpose. And for these tools, there is no need to export the IE information.
>
> By the way: Have you considered an additional IE like
> informationElementDescription holding an octet string describing the
> semantic of the IE "in human-readable English"?
>
> Regards,
> Gerhard
>
>
> Juergen Quittek wrote:
>   
>> Dear all,
>>
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>
>>     
>>> 4. Extended Types (Elisa Boschi)
>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>    specify what operations make sense for an IE.
>>>    Support shown for this as a WG item, as for File Format.
>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>>       
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element identifiers.
>>
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular happen
>> if enterprise specific elements are used. Without this information the
>> collector would treat these elements as if they were of type octet array.
>> With this information it may be able to treat them more appropriately.
>>
>> The current version of the IPFIX file format draft recommends using this
>> method when IPFIX records are stored.
>>
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>
>> Thanks,
>>
>>     Juergen
>>
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>>     
>
>   


--------------080802010407020004090407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all,<br>
<br>
I have exactly the same concern.<br>
<br>
Regards, Benoit.<br>
<blockquote cite="mid46A882D0.4050700@informatik.uni-tuebingen.de"
 type="cite">
  <pre wrap="">Dear all,

I'm undecided about this draft.

On the one hand, it's a nice idea to have some IEs which allow
describing the type and semantic of other IEs. On the other hand, my
impression is that the usefulness is very restricted and not as broad as
claimed in the introduction of the draft:

   ... Having to do some sort of tool-specific
   configuration (or code modification) on every tool just to tell which
   type each used Information Element has is a huge amount of work for
   users and implementors of enterprise-specific Information Elements.
   Many tools in fact only need to know the field's data type to work on
   them. ...

In my opinion, any deeper analysis and processing of metering data
requires knowledge about the semantic. Just knowing the data type may be
enough to display values correctly. Considering
informationElementSemanticType, you might also know if the calculation
of statistical properties (max, min, mean, variance etc.) makes sense or
not. But any further analysis would probably require more semantical
knowledge. That's why I assume that, in practice, analyzing and
processing enterprise-specific data will mostly be performed with
specialized analysis tools that have been implemented for this specific
purpose. And for these tools, there is no need to export the IE information.

By the way: Have you considered an additional IE like
informationElementDescription holding an octet string describing the
semantic of the IE "in human-readable English"?

Regards,
Gerhard


Juergen Quittek wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Dear all,

Candidates #4 to become a new IPFIX work item is described by
draft draft-boschi-ipfix-extended-type-00.txt.

    </pre>
    <blockquote type="cite">
      <pre wrap="">4. Extended Types (Elisa Boschi)
   Needed for IPFIX files, most useful for Enterprise IEs; need to
   specify what operations make sense for an IE.
   Support shown for this as a WG item, as for File Format.
   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
      </pre>
    </blockquote>
    <pre wrap="">It is a method for assigning data types to unknown IPFIX information
elements by using option records that map data types to element identifiers.

It can be applied in cases where an IPFIX collector does not know the
data type of received information elements. This may in particular happen
if enterprise specific elements are used. Without this information the
collector would treat these elements as if they were of type octet array.
With this information it may be able to treat them more appropriately.

The current version of the IPFIX file format draft recommends using this
method when IPFIX records are stored.

Do you think this is a useful extension of the IPFIX protocol?
Do you think we should accept this as an IPFIX work item?
Please have a look at the draft and send your comments.

Thanks,

    Juergen



_______________________________________________
IPFIX mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
</body>
</html>

--------------080802010407020004090407--


--===============1988918953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1988918953==--




From ipfix-bounces@ietf.org Thu Jul 26 11:18:04 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE56A-0003JW-71; Thu, 26 Jul 2007 11:17:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE568-0003HG-M2
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:17:52 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE567-0007SC-AT
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:17:52 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QFHoC11900; Thu, 26 Jul 2007 17:17:50 +0200 (CEST)
Received: from [10.82.241.128] (rtp-vpn2-384.cisco.com [10.82.241.128])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QFHlQ11831; Thu, 26 Jul 2007 17:17:48 +0200 (CEST)
Message-ID: <46A8BB1B.1000101@cisco.com>
Date: Thu, 26 Jul 2007 10:17:47 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1425890092=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1425890092==
Content-Type: multipart/alternative;
	boundary="------------010200030500060207060503"

This is a multi-part message in MIME format.
--------------010200030500060207060503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

During the last IETF, the draft was presented and my initial thought 
was: it makes sense to put the variable length I.E. at the end of 
record. So we could add a few sentences in the implementation guideline 
about it.
Now, when I look at the slide 4 of 
http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf, I see a gain 
in time that varies from 22 to 86%. Pretty impressive.
So if this gain is confirmed, then this is a very interesting draft for 
the working group, which could be experimental to start with...

I'm also happy that Irino-san clarifies the scope the draft below

     Example of effective case
     writing to files
     real time flow filtering (comparing bulk data)

    Example of ineffective case
     when process each Information Element

So the big gain is when writing into a file, while the gain is lower 
(actually no sure if there is one) when writing into a DB

Regards, Benoit.
> Dear all,
>
> (2007/07/26 15:38), Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #6 to become a new IPFIX work item is described by
>> draft draft-irino-ipfix-ie-order-02.txt.
>>
>>> 6. Order of Information Elements (Irino)
>>>    Interesting, need more people to measure possible efficiency gain.
>>>    Would this be better as an individual draft?
>>
>> This draft suggests a special ordering of information elements in a
>> flow record.  At the very brief presentation at our session, the author
>> explained that he can improve the performance of IPFIX exporter and
>> collector significantly. To prove this, he compared a random order
>> of information elements with an order according to his proposal
>> and achieved significant performance improvements.
>>
>> Speaking as technical contributor, I think that if these results would
>> be the same also for other implementations of IPFIX, then this looks 
>> like
>> a very good IPFIX work item.
>>
>> Speaking as co-chair, I would like to ask everybody who has an IPFIX
>> implementation to conduct a short experiment in order to find out if
>> the improvement is the same for his/her implementations.
>>
>> Would any implementor be willing to do so?
>> If yes, until when would you have results?
>>
>> Thanks,
>>
>>     Juergen
>
> A day before yesterday, I had a presentation about a performance result
> when exporters and collectors use same order, however I didn't have 
> any time to talk about the reason of difference of performance.
>
> In the slide,
> ( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
> I use very primitive collector which I implemented. This collector
> receive data records and write the data to file.
> This collector has internal proprietary format to store to data to file.
> The format consists of some Information Elements whose size are full
> size. (For example, bgpSourceAsNumber is 4 octets.)
>
> This collector process following steps:
>  1) read the data record.
>  2) convert received data records to the collector's format on memory.
>  3) write to file from memory.
>
> I tested each combination of 3 kind of orders for template of exporter
> and format of collector.
>  1) An order same as NetFlow version 5
>  2) Suggested Order in my draft (separating constant fixed length IEs
> and reduced size encoding applicable IEs)
>  3) Random order
> In this test, exporter's template includes set of Information Elements
> same as NetFlow version 5 fields.
> These templates and formats are shown in page 9 in the slide.
>
> I measured 10 times this test.
> The matrix table in page 4 is the result of this test. Upper one shows
> total time, lower one shows ratio.
>
> My collector program can process bulk of sequential Information
> Elements. For example in the case reading from date records ordered by
> suggested order to writing format formed by suggested order, my
> collector program copies first 20 octets (from sourceIPv4Address to
> ipClassOfService) at once.
>
> I described counts for processing in from page 10 to 12 in the slide.
> For example, in the best case that a exporter uses suggested order and a
> collector uses suggested order, the counts for processing (processing
> means coping data in this case) is 8 (on middle table in page 11). In
> the worst case a exporter uses random order and collector uses random
> order, the counts is 17 (on right table in page 11). Difference of the
> counts for processing effects their performance.
> my presentation shows one of the best case.
>
> Therefore, there are effective case and ineffective case by ordering.
>
> Example of effective case
>  writing to files
>  real time flow filtering (comparing bulk data)
>
> Example of ineffective case
>  when process each Information Element
>
> By the way, if all exporter supports draft-muenz-ipfix-configuration and
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these 
> implementations. If this state continues in future, reference order is 
> valuable for these exporters' implementations and collectors' 
> implementations. Therefore I've thought a reference order should be
> defined as Informational. I suggested an order adjusted for collector's
> performance, however perhaps it is not suitable for exporter. So I hope
> to discuss on WG.
>
> thanks,
> Hitoshi Irino
>


--------------010200030500060207060503
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all,<br>
<br>
During the last IETF, the draft was presented and my initial thought
was: it makes sense to put the variable length I.E. at the end of
record. So we could add a few sentences in the implementation guideline
about it.<br>
Now, when I look at the slide 4 of
<a class="moz-txt-link-freetext" href="http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf">http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf</a>, I see a
gain in time that varies from 22 to 86%. Pretty impressive.<br>
So if this gain is confirmed, then this is a very interesting draft for
the working group, which could be experimental to start with...<br>
<br>
I'm also happy that Irino-san clarifies the scope the draft below<br>
<blockquote>&nbsp;Example of effective case
  <br>
&nbsp;writing to files
  <br>
&nbsp;real time flow filtering (comparing bulk data)
  <br>
  <br>
Example of ineffective case
  <br>
&nbsp;when process each Information Element
  <br>
</blockquote>
So the big gain is when writing into a file, while the gain is lower
(actually no sure if there is one) when writing into a DB<br>
<br>
Regards, Benoit.<br>
<blockquote cite="mid46A8B2EB.6090800@lab.ntt.co.jp" type="cite">Dear
all,
  <br>
  <br>
(2007/07/26 15:38), Juergen Quittek wrote:
  <br>
  <blockquote type="cite">Dear all,
    <br>
    <br>
Candidates #6 to become a new IPFIX work item is described by
    <br>
draft draft-irino-ipfix-ie-order-02.txt.
    <br>
    <br>
    <blockquote type="cite">6. Order of Information Elements (Irino)
      <br>
&nbsp;&nbsp; Interesting, need more people to measure possible efficiency gain.
      <br>
&nbsp;&nbsp; Would this be better as an individual draft?
      <br>
    </blockquote>
    <br>
This draft suggests a special ordering of information elements in a
    <br>
flow record.&nbsp; At the very brief presentation at our session, the author
    <br>
explained that he can improve the performance of IPFIX exporter and
    <br>
collector significantly. To prove this, he compared a random order
    <br>
of information elements with an order according to his proposal
    <br>
and achieved significant performance improvements.
    <br>
    <br>
Speaking as technical contributor, I think that if these results would
    <br>
be the same also for other implementations of IPFIX, then this looks
like
    <br>
a very good IPFIX work item.
    <br>
    <br>
Speaking as co-chair, I would like to ask everybody who has an IPFIX
    <br>
implementation to conduct a short experiment in order to find out if
    <br>
the improvement is the same for his/her implementations.
    <br>
    <br>
Would any implementor be willing to do so?
    <br>
If yes, until when would you have results?
    <br>
    <br>
Thanks,
    <br>
    <br>
&nbsp;&nbsp;&nbsp; Juergen
    <br>
  </blockquote>
  <br>
A day before yesterday, I had a presentation about a performance result
  <br>
when exporters and collectors use same order, however I didn't have any
time to talk about the reason of difference of performance.
  <br>
  <br>
In the slide,
  <br>
( <a class="moz-txt-link-freetext" href="http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf">http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf</a> )
  <br>
I use very primitive collector which I implemented. This collector
  <br>
receive data records and write the data to file.
  <br>
This collector has internal proprietary format to store to data to
file.
  <br>
The format consists of some Information Elements whose size are full
  <br>
size. (For example, bgpSourceAsNumber is 4 octets.)
  <br>
  <br>
This collector process following steps:
  <br>
&nbsp;1) read the data record.
  <br>
&nbsp;2) convert received data records to the collector's format on memory.
  <br>
&nbsp;3) write to file from memory.
  <br>
  <br>
I tested each combination of 3 kind of orders for template of exporter
  <br>
and format of collector.
  <br>
&nbsp;1) An order same as NetFlow version 5
  <br>
&nbsp;2) Suggested Order in my draft (separating constant fixed length IEs
  <br>
and reduced size encoding applicable IEs)
  <br>
&nbsp;3) Random order
  <br>
In this test, exporter's template includes set of Information Elements
  <br>
same as NetFlow version 5 fields.
  <br>
These templates and formats are shown in page 9 in the slide.
  <br>
  <br>
I measured 10 times this test.
  <br>
The matrix table in page 4 is the result of this test. Upper one shows
  <br>
total time, lower one shows ratio.
  <br>
  <br>
My collector program can process bulk of sequential Information
  <br>
Elements. For example in the case reading from date records ordered by
  <br>
suggested order to writing format formed by suggested order, my
  <br>
collector program copies first 20 octets (from sourceIPv4Address to
  <br>
ipClassOfService) at once.
  <br>
  <br>
I described counts for processing in from page 10 to 12 in the slide.
  <br>
For example, in the best case that a exporter uses suggested order and
a
  <br>
collector uses suggested order, the counts for processing (processing
  <br>
means coping data in this case) is 8 (on middle table in page 11). In
  <br>
the worst case a exporter uses random order and collector uses random
  <br>
order, the counts is 17 (on right table in page 11). Difference of the
  <br>
counts for processing effects their performance.
  <br>
my presentation shows one of the best case.
  <br>
  <br>
Therefore, there are effective case and ineffective case by ordering.
  <br>
  <br>
Example of effective case
  <br>
&nbsp;writing to files
  <br>
&nbsp;real time flow filtering (comparing bulk data)
  <br>
  <br>
Example of ineffective case
  <br>
&nbsp;when process each Information Element
  <br>
  <br>
By the way, if all exporter supports draft-muenz-ipfix-configuration
and
  <br>
operators can set configuration about template completely freely, my
  <br>
draft is not important, because operator can adjust configuration for
  <br>
collector.
  <br>
However currently NetFlow v9 implementations of some router makers are
  <br>
not configurable at all. Operators can choice preset template on these
implementations. If this state continues in future, reference order is
valuable for these exporters' implementations and collectors'
implementations. Therefore I've thought a reference order should be
  <br>
defined as Informational. I suggested an order adjusted for collector's
  <br>
performance, however perhaps it is not suitable for exporter. So I hope
  <br>
to discuss on WG.
  <br>
  <br>
thanks,
  <br>
Hitoshi Irino
  <br>
  <br>
</blockquote>
<br>
</body>
</html>

--------------010200030500060207060503--


--===============1425890092==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1425890092==--




From ipfix-bounces@ietf.org Thu Jul 26 11:18:04 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE56A-0003JW-71; Thu, 26 Jul 2007 11:17:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE568-0003HG-M2
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:17:52 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE567-0007SC-AT
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:17:52 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QFHoC11900; Thu, 26 Jul 2007 17:17:50 +0200 (CEST)
Received: from [10.82.241.128] (rtp-vpn2-384.cisco.com [10.82.241.128])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QFHlQ11831; Thu, 26 Jul 2007 17:17:48 +0200 (CEST)
Message-ID: <46A8BB1B.1000101@cisco.com>
Date: Thu, 26 Jul 2007 10:17:47 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1425890092=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1425890092==
Content-Type: multipart/alternative;
	boundary="------------010200030500060207060503"

This is a multi-part message in MIME format.
--------------010200030500060207060503
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

During the last IETF, the draft was presented and my initial thought 
was: it makes sense to put the variable length I.E. at the end of 
record. So we could add a few sentences in the implementation guideline 
about it.
Now, when I look at the slide 4 of 
http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf, I see a gain 
in time that varies from 22 to 86%. Pretty impressive.
So if this gain is confirmed, then this is a very interesting draft for 
the working group, which could be experimental to start with...

I'm also happy that Irino-san clarifies the scope the draft below

     Example of effective case
     writing to files
     real time flow filtering (comparing bulk data)

    Example of ineffective case
     when process each Information Element

So the big gain is when writing into a file, while the gain is lower 
(actually no sure if there is one) when writing into a DB

Regards, Benoit.
> Dear all,
>
> (2007/07/26 15:38), Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #6 to become a new IPFIX work item is described by
>> draft draft-irino-ipfix-ie-order-02.txt.
>>
>>> 6. Order of Information Elements (Irino)
>>>    Interesting, need more people to measure possible efficiency gain.
>>>    Would this be better as an individual draft?
>>
>> This draft suggests a special ordering of information elements in a
>> flow record.  At the very brief presentation at our session, the author
>> explained that he can improve the performance of IPFIX exporter and
>> collector significantly. To prove this, he compared a random order
>> of information elements with an order according to his proposal
>> and achieved significant performance improvements.
>>
>> Speaking as technical contributor, I think that if these results would
>> be the same also for other implementations of IPFIX, then this looks 
>> like
>> a very good IPFIX work item.
>>
>> Speaking as co-chair, I would like to ask everybody who has an IPFIX
>> implementation to conduct a short experiment in order to find out if
>> the improvement is the same for his/her implementations.
>>
>> Would any implementor be willing to do so?
>> If yes, until when would you have results?
>>
>> Thanks,
>>
>>     Juergen
>
> A day before yesterday, I had a presentation about a performance result
> when exporters and collectors use same order, however I didn't have 
> any time to talk about the reason of difference of performance.
>
> In the slide,
> ( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
> I use very primitive collector which I implemented. This collector
> receive data records and write the data to file.
> This collector has internal proprietary format to store to data to file.
> The format consists of some Information Elements whose size are full
> size. (For example, bgpSourceAsNumber is 4 octets.)
>
> This collector process following steps:
>  1) read the data record.
>  2) convert received data records to the collector's format on memory.
>  3) write to file from memory.
>
> I tested each combination of 3 kind of orders for template of exporter
> and format of collector.
>  1) An order same as NetFlow version 5
>  2) Suggested Order in my draft (separating constant fixed length IEs
> and reduced size encoding applicable IEs)
>  3) Random order
> In this test, exporter's template includes set of Information Elements
> same as NetFlow version 5 fields.
> These templates and formats are shown in page 9 in the slide.
>
> I measured 10 times this test.
> The matrix table in page 4 is the result of this test. Upper one shows
> total time, lower one shows ratio.
>
> My collector program can process bulk of sequential Information
> Elements. For example in the case reading from date records ordered by
> suggested order to writing format formed by suggested order, my
> collector program copies first 20 octets (from sourceIPv4Address to
> ipClassOfService) at once.
>
> I described counts for processing in from page 10 to 12 in the slide.
> For example, in the best case that a exporter uses suggested order and a
> collector uses suggested order, the counts for processing (processing
> means coping data in this case) is 8 (on middle table in page 11). In
> the worst case a exporter uses random order and collector uses random
> order, the counts is 17 (on right table in page 11). Difference of the
> counts for processing effects their performance.
> my presentation shows one of the best case.
>
> Therefore, there are effective case and ineffective case by ordering.
>
> Example of effective case
>  writing to files
>  real time flow filtering (comparing bulk data)
>
> Example of ineffective case
>  when process each Information Element
>
> By the way, if all exporter supports draft-muenz-ipfix-configuration and
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these 
> implementations. If this state continues in future, reference order is 
> valuable for these exporters' implementations and collectors' 
> implementations. Therefore I've thought a reference order should be
> defined as Informational. I suggested an order adjusted for collector's
> performance, however perhaps it is not suitable for exporter. So I hope
> to discuss on WG.
>
> thanks,
> Hitoshi Irino
>


--------------010200030500060207060503
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear all,<br>
<br>
During the last IETF, the draft was presented and my initial thought
was: it makes sense to put the variable length I.E. at the end of
record. So we could add a few sentences in the implementation guideline
about it.<br>
Now, when I look at the slide 4 of
<a class="moz-txt-link-freetext" href="http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf">http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf</a>, I see a
gain in time that varies from 22 to 86%. Pretty impressive.<br>
So if this gain is confirmed, then this is a very interesting draft for
the working group, which could be experimental to start with...<br>
<br>
I'm also happy that Irino-san clarifies the scope the draft below<br>
<blockquote>&nbsp;Example of effective case
  <br>
&nbsp;writing to files
  <br>
&nbsp;real time flow filtering (comparing bulk data)
  <br>
  <br>
Example of ineffective case
  <br>
&nbsp;when process each Information Element
  <br>
</blockquote>
So the big gain is when writing into a file, while the gain is lower
(actually no sure if there is one) when writing into a DB<br>
<br>
Regards, Benoit.<br>
<blockquote cite="mid46A8B2EB.6090800@lab.ntt.co.jp" type="cite">Dear
all,
  <br>
  <br>
(2007/07/26 15:38), Juergen Quittek wrote:
  <br>
  <blockquote type="cite">Dear all,
    <br>
    <br>
Candidates #6 to become a new IPFIX work item is described by
    <br>
draft draft-irino-ipfix-ie-order-02.txt.
    <br>
    <br>
    <blockquote type="cite">6. Order of Information Elements (Irino)
      <br>
&nbsp;&nbsp; Interesting, need more people to measure possible efficiency gain.
      <br>
&nbsp;&nbsp; Would this be better as an individual draft?
      <br>
    </blockquote>
    <br>
This draft suggests a special ordering of information elements in a
    <br>
flow record.&nbsp; At the very brief presentation at our session, the author
    <br>
explained that he can improve the performance of IPFIX exporter and
    <br>
collector significantly. To prove this, he compared a random order
    <br>
of information elements with an order according to his proposal
    <br>
and achieved significant performance improvements.
    <br>
    <br>
Speaking as technical contributor, I think that if these results would
    <br>
be the same also for other implementations of IPFIX, then this looks
like
    <br>
a very good IPFIX work item.
    <br>
    <br>
Speaking as co-chair, I would like to ask everybody who has an IPFIX
    <br>
implementation to conduct a short experiment in order to find out if
    <br>
the improvement is the same for his/her implementations.
    <br>
    <br>
Would any implementor be willing to do so?
    <br>
If yes, until when would you have results?
    <br>
    <br>
Thanks,
    <br>
    <br>
&nbsp;&nbsp;&nbsp; Juergen
    <br>
  </blockquote>
  <br>
A day before yesterday, I had a presentation about a performance result
  <br>
when exporters and collectors use same order, however I didn't have any
time to talk about the reason of difference of performance.
  <br>
  <br>
In the slide,
  <br>
( <a class="moz-txt-link-freetext" href="http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf">http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf</a> )
  <br>
I use very primitive collector which I implemented. This collector
  <br>
receive data records and write the data to file.
  <br>
This collector has internal proprietary format to store to data to
file.
  <br>
The format consists of some Information Elements whose size are full
  <br>
size. (For example, bgpSourceAsNumber is 4 octets.)
  <br>
  <br>
This collector process following steps:
  <br>
&nbsp;1) read the data record.
  <br>
&nbsp;2) convert received data records to the collector's format on memory.
  <br>
&nbsp;3) write to file from memory.
  <br>
  <br>
I tested each combination of 3 kind of orders for template of exporter
  <br>
and format of collector.
  <br>
&nbsp;1) An order same as NetFlow version 5
  <br>
&nbsp;2) Suggested Order in my draft (separating constant fixed length IEs
  <br>
and reduced size encoding applicable IEs)
  <br>
&nbsp;3) Random order
  <br>
In this test, exporter's template includes set of Information Elements
  <br>
same as NetFlow version 5 fields.
  <br>
These templates and formats are shown in page 9 in the slide.
  <br>
  <br>
I measured 10 times this test.
  <br>
The matrix table in page 4 is the result of this test. Upper one shows
  <br>
total time, lower one shows ratio.
  <br>
  <br>
My collector program can process bulk of sequential Information
  <br>
Elements. For example in the case reading from date records ordered by
  <br>
suggested order to writing format formed by suggested order, my
  <br>
collector program copies first 20 octets (from sourceIPv4Address to
  <br>
ipClassOfService) at once.
  <br>
  <br>
I described counts for processing in from page 10 to 12 in the slide.
  <br>
For example, in the best case that a exporter uses suggested order and
a
  <br>
collector uses suggested order, the counts for processing (processing
  <br>
means coping data in this case) is 8 (on middle table in page 11). In
  <br>
the worst case a exporter uses random order and collector uses random
  <br>
order, the counts is 17 (on right table in page 11). Difference of the
  <br>
counts for processing effects their performance.
  <br>
my presentation shows one of the best case.
  <br>
  <br>
Therefore, there are effective case and ineffective case by ordering.
  <br>
  <br>
Example of effective case
  <br>
&nbsp;writing to files
  <br>
&nbsp;real time flow filtering (comparing bulk data)
  <br>
  <br>
Example of ineffective case
  <br>
&nbsp;when process each Information Element
  <br>
  <br>
By the way, if all exporter supports draft-muenz-ipfix-configuration
and
  <br>
operators can set configuration about template completely freely, my
  <br>
draft is not important, because operator can adjust configuration for
  <br>
collector.
  <br>
However currently NetFlow v9 implementations of some router makers are
  <br>
not configurable at all. Operators can choice preset template on these
implementations. If this state continues in future, reference order is
valuable for these exporters' implementations and collectors'
implementations. Therefore I've thought a reference order should be
  <br>
defined as Informational. I suggested an order adjusted for collector's
  <br>
performance, however perhaps it is not suitable for exporter. So I hope
  <br>
to discuss on WG.
  <br>
  <br>
thanks,
  <br>
Hitoshi Irino
  <br>
  <br>
</blockquote>
<br>
</body>
</html>

--------------010200030500060207060503--


--===============1425890092==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1425890092==--




From ipfix-bounces@ietf.org Thu Jul 26 11:27:08 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5Ez-00045y-7Z; Thu, 26 Jul 2007 11:27:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5Ex-00045q-HT
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:26:59 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE5Ew-0007lb-DN
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:26:59 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6QFQgVe068161;
	Fri, 27 Jul 2007 00:26:43 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 27 Jul 2007 00:26:44 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
In-Reply-To: <46A8ABE3.4000806@cisco.com>
References: <46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
Message-Id: <20070726234801.4975.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 27 Jul 2007 00:26:44 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul-san and Gerhard-san,

Paul-san, thank you for big comments about mediator draft.
I will reply your comment one step at a time.

Gerhard-san, thank you for your notification about reference.

I think that anonymisation is good solution to prevent to violate privacy
information. Even if the original data can not be determined from the
anonymised data, we can monitor the traffic trend, as follows.

For example,
- How long does each flow continue the session?
- How many packets does each flow send? 
- Proportion of heavy flow or heavy customer. 
- Proportion of short flow or one packet flow.  
- How many flows does each network prefix included?
To do it, anonymization technique needs to preserve prefix, just like
Gerhard reference.

And furthermore, this data becomes useful data by comparing between past
data and simulating future data.

And, pairs of comparison are considered several type.

- each peering points
- mobile network and broadband network
- tariff system: fixed amount rate and metered rate
:

Above data can not be measured, if associated field becomes zero or
removal.

Best Regards,
Atsushi KOBAYASHI

On Thu, 26 Jul 2007 15:12:51 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Gerhard,
> 
> > Just a small comment:
> > 
> > Paul Aitken wrote:
> >>>    Modification of the value of Information Element
> >>>
> >>>       This function modifies the value of specified Information Elements
> >>>       according to instructions configured by the user.
> >>>
> >>>       For example, this function enables us to overwrite private
> >>>       information with zeros or the maximum value.  In particular, IP
> >>>       address and port number is sensitive private information.  In the
> >>>       case of monitoring traffic trends and traffic engineering, these
> >>>       Information Elements are not essential factors for those purposes.
> >>>       In that case, modification anonymizes the relevant Information
> >>>       Elements to prevent a violation of privacy.  If modification can
> >>>       anonymize some Information Elements, it might need to report which
> >>>       Information Elements are anonymized.  For example,
> >>>       "anonymizationIndicator" indicates which Information Elements have
> >>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
> >>>       The anonymization method is outside the scope of this document.
> >> Why would we not just modify the template and remove these Information
> >> Elements?
> > 
> > Instead of removing IP addresses you might want to apply anonymization
> > techniques which preserve prefix information while still preventing
> > inference of the original addresses. E.g. see CryptoPAN already deployed
> > by many Netflow tools like "flow-tools":
> > http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
> 
> Indeed, anonymization is mentioned in section 6.7 of the IPFIX 
> requirements, RFC 3917.
> 
> However, as far as I can see it's not something that anyone in the WG 
> seems to have worked on until now. But since now it appears both in 
> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's 
> time we began to consider what the best method might be?
> 
> So my question is: what is the value of storing or forwarding anonymised 
> information? Since the original data can not be determined from the 
> anoymised data, it only serves to indicate that there was some data 
> there which was anonymised (ie, the anonymised data is of no value 
> itself) - and I can think of a better way to do that, eg send a reduced 
> size version of the field with zero-length.
> 
> And if it's not necessary to indicate that the field was there then 
> surely the best way to anoymise it is to remove it entirely?
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 11:27:08 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE5Ez-00045y-7Z; Thu, 26 Jul 2007 11:27:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE5Ex-00045q-HT
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:26:59 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE5Ew-0007lb-DN
	for ipfix@ietf.org; Thu, 26 Jul 2007 11:26:59 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6QFQgVe068161;
	Fri, 27 Jul 2007 00:26:43 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 27 Jul 2007 00:26:44 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] Review: draft-kobayashi-ipfix-mediator-model-00
In-Reply-To: <46A8ABE3.4000806@cisco.com>
References: <46A86C0B.90209@informatik.uni-tuebingen.de>
	<46A8ABE3.4000806@cisco.com>
Message-Id: <20070726234801.4975.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 27 Jul 2007 00:26:44 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Paul-san and Gerhard-san,

Paul-san, thank you for big comments about mediator draft.
I will reply your comment one step at a time.

Gerhard-san, thank you for your notification about reference.

I think that anonymisation is good solution to prevent to violate privacy
information. Even if the original data can not be determined from the
anonymised data, we can monitor the traffic trend, as follows.

For example,
- How long does each flow continue the session?
- How many packets does each flow send? 
- Proportion of heavy flow or heavy customer. 
- Proportion of short flow or one packet flow.  
- How many flows does each network prefix included?
To do it, anonymization technique needs to preserve prefix, just like
Gerhard reference.

And furthermore, this data becomes useful data by comparing between past
data and simulating future data.

And, pairs of comparison are considered several type.

- each peering points
- mobile network and broadband network
- tariff system: fixed amount rate and metered rate
:

Above data can not be measured, if associated field becomes zero or
removal.

Best Regards,
Atsushi KOBAYASHI

On Thu, 26 Jul 2007 15:12:51 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Gerhard,
> 
> > Just a small comment:
> > 
> > Paul Aitken wrote:
> >>>    Modification of the value of Information Element
> >>>
> >>>       This function modifies the value of specified Information Elements
> >>>       according to instructions configured by the user.
> >>>
> >>>       For example, this function enables us to overwrite private
> >>>       information with zeros or the maximum value.  In particular, IP
> >>>       address and port number is sensitive private information.  In the
> >>>       case of monitoring traffic trends and traffic engineering, these
> >>>       Information Elements are not essential factors for those purposes.
> >>>       In that case, modification anonymizes the relevant Information
> >>>       Elements to prevent a violation of privacy.  If modification can
> >>>       anonymize some Information Elements, it might need to report which
> >>>       Information Elements are anonymized.  For example,
> >>>       "anonymizationIndicator" indicates which Information Elements have
> >>>       been anonymized as a bitmap, just like the "flowKeyIndicator".
> >>>       The anonymization method is outside the scope of this document.
> >> Why would we not just modify the template and remove these Information
> >> Elements?
> > 
> > Instead of removing IP addresses you might want to apply anonymization
> > techniques which preserve prefix information while still preventing
> > inference of the original addresses. E.g. see CryptoPAN already deployed
> > by many Netflow tools like "flow-tools":
> > http://www.cc.gatech.edu/computing/Networking/projects/cryptopan/
> 
> Indeed, anonymization is mentioned in section 6.7 of the IPFIX 
> requirements, RFC 3917.
> 
> However, as far as I can see it's not something that anyone in the WG 
> seems to have worked on until now. But since now it appears both in 
> Brian's file draft and in Kobayshi-san's mediator draft, perhaps it's 
> time we began to consider what the best method might be?
> 
> So my question is: what is the value of storing or forwarding anonymised 
> information? Since the original data can not be determined from the 
> anoymised data, it only serves to indicate that there was some data 
> there which was anonymised (ie, the anonymised data is of no value 
> itself) - and I can think of a better way to do that, eg send a reduced 
> size version of the field with zero-length.
> 
> And if it's not necessary to indicate that the field was there then 
> surely the best way to anoymise it is to remove it entirely?
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 12:37:43 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE6LL-0007hQ-01; Thu, 26 Jul 2007 12:37:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE6LK-0007hK-6k
	for ipfix@ietf.org; Thu, 26 Jul 2007 12:37:38 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE6LJ-0002B4-0D
	for ipfix@ietf.org; Thu, 26 Jul 2007 12:37:38 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:37:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Jul 2007 18:37:13 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <C2CE0B83.10238%Quittek@netlab.nec.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8Q
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<C2CE0B83.10238%Quittek@netlab.nec.de>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Juergen Quittek" <Quittek@netlab.nec.de>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>, <ipfix@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 16:37:15.0970 (UTC)
	FILETIME=[39CCF220:01C7CFA3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4da339c42fe5be09fa120bb0fcc4a575
Cc: 
Subject: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0194419872=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0194419872==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFA3.42576263"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFA3.42576263
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

HI Juergen and Nevil,
=20
Work item #3
Storing IPFIX records in files requires interoperability only when =
exchanging these files with some one else or some other application. So =
it's a function of mediation.
=20
Work item #4 points indirectly to a major point concern for telcos: how =
to map a private IE on a standard one?=20
=20
Work item #5 defines mediator arch & functions. Then it gives many use =
cases and requirements.
=20
Work items #3, #4 and #5 give many functions a mediator may implement.
At this step, the functions required for interoperability between =
mediators are not identified. So please consider the necessity to define =
the interoperability requirements prior to re charter.
=20
Regards
Emile
=20
=20
> -----Message d'origine-----
> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9 : jeudi 26 juillet 2007 08:28
> =C0 : ipfix@ietf.org
> Objet : [IPFIX] new work item candidate #4: extended types
>=20
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
> > 4. Extended Types (Elisa Boschi)
> >    Needed for IPFIX files, most useful for Enterprise IEs; need to
> >    specify what operations make sense for an IE.
> >    Support shown for this as a WG item, as for File Format.
> >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element
> identifiers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular =
happen
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet =
array.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using =
this
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

------_=_NextPart_001_01C7CFA3.42576263
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C7CFB3.FBE653A0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>HI <span =
class=3DSpellE>Juergen</span> and Nevil,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item =
#3<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Storing IPFIX records in files =
requires interoperability
only when exchanging these files with some one else or some other =
application. So
it's a function of mediation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #4 points indirectly =
to a major
point concern for <span class=3DSpellE>telcos</span>: how to map a =
private IE on a
standard one? <o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #5 defines mediator =
arch &amp;
functions. Then it gives many use cases and =
requirements.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work items #3, #4 and #5 give =
many
functions a mediator may implement.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>At this step, the functions =
required for interoperability
between mediators are not identified. So please consider the necessity =
to
define the interoperability requirements prior to re =
charter.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Emile<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; -----Message =
d'origine-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; De&nbsp;: Juergen <span =
class=3DSpellE>Quittek</span>
[mailto:Quittek@netlab.nec.de]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; Envoy=E9&nbsp;: jeudi 26 juillet 2007 =
08:28<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; =C0&nbsp;: =
ipfix@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DSpellE><span =
class=3DGramE>Objet</span></span><span
class=3DGramE>&nbsp;:</span> [IPFIX] new work item candidate #4: =
extended types<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Dear all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Candidates #4 to become a new IPFIX work =
item is
described by<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; draft
draft-boschi-ipfix-extended-type-00.txt.</span></font></span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt; =
4.</span></font></span><span
lang=3DEN-US> Extended Types (Elisa <span =
class=3DSpellE>Boschi</span>)<o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Needed for IPFIX files, most useful for Enterprise <span =
class=3DSpellE>IEs</span>;
need to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>specify what operations make sense for an =
IE.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Support shown for this as a WG item, as for File =
Format.</span></font></span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Milestones:<span style=3D'mso-spacerun:yes'>=A0 </span>WG LC =
after IETF 70,
to IESG before <span class=3DGramE>IETF<span =
style=3D'mso-spacerun:yes'>=A0 =
</span>71</span>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; It is a method for assigning data types =
to
unknown IPFIX information<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>elements</span> by =
using option
records that map data types to element<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span =
class=3DGramE>identifiers</span>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; It can be applied in cases where an =
IPFIX
collector does not know the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>data</span> type of =
received
information elements. This may in particular =
happen<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>if</span> enterprise =
specific
elements are used. Without this information =
the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>collector</span> =
would treat
these elements as if they were of type octet =
array.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; With this information it may be able to =
treat
them more appropriately.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; The current version of the IPFIX file =
format
draft recommends using this<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>method</span> when =
IPFIX
records are stored.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Do you think this is a useful extension =
of the
IPFIX protocol?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Do you think we should accept this as an =
IPFIX
work item?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Please have a look at the draft and send =
your
comments.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0=A0 </span><span
class=3DSpellE>Juergen</span><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
_______________________________________________<o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; IPFIX mailing =
list<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
IPFIX@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
https://www1.ietf.org/mailman/listinfo/ipfix<o:p></o:p></span></font></p>=


</div>

</body>

</html>

------_=_NextPart_001_01C7CFA3.42576263--


--===============0194419872==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0194419872==--




From ipfix-bounces@ietf.org Thu Jul 26 12:37:43 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE6LL-0007hQ-01; Thu, 26 Jul 2007 12:37:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE6LK-0007hK-6k
	for ipfix@ietf.org; Thu, 26 Jul 2007 12:37:38 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE6LJ-0002B4-0D
	for ipfix@ietf.org; Thu, 26 Jul 2007 12:37:38 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 18:37:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Jul 2007 18:37:13 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <C2CE0B83.10238%Quittek@netlab.nec.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8Q
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<C2CE0B83.10238%Quittek@netlab.nec.de>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Juergen Quittek" <Quittek@netlab.nec.de>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>, <ipfix@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 16:37:15.0970 (UTC)
	FILETIME=[39CCF220:01C7CFA3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4da339c42fe5be09fa120bb0fcc4a575
Cc: 
Subject: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0194419872=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0194419872==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFA3.42576263"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFA3.42576263
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

HI Juergen and Nevil,
=20
Work item #3
Storing IPFIX records in files requires interoperability only when =
exchanging these files with some one else or some other application. So =
it's a function of mediation.
=20
Work item #4 points indirectly to a major point concern for telcos: how =
to map a private IE on a standard one?=20
=20
Work item #5 defines mediator arch & functions. Then it gives many use =
cases and requirements.
=20
Work items #3, #4 and #5 give many functions a mediator may implement.
At this step, the functions required for interoperability between =
mediators are not identified. So please consider the necessity to define =
the interoperability requirements prior to re charter.
=20
Regards
Emile
=20
=20
> -----Message d'origine-----
> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9 : jeudi 26 juillet 2007 08:28
> =C0 : ipfix@ietf.org
> Objet : [IPFIX] new work item candidate #4: extended types
>=20
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
> > 4. Extended Types (Elisa Boschi)
> >    Needed for IPFIX files, most useful for Enterprise IEs; need to
> >    specify what operations make sense for an IE.
> >    Support shown for this as a WG item, as for File Format.
> >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element
> identifiers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular =
happen
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet =
array.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using =
this
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

------_=_NextPart_001_01C7CFA3.42576263
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C7CFB3.FBE653A0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>HI <span =
class=3DSpellE>Juergen</span> and Nevil,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item =
#3<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Storing IPFIX records in files =
requires interoperability
only when exchanging these files with some one else or some other =
application. So
it's a function of mediation.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #4 points indirectly =
to a major
point concern for <span class=3DSpellE>telcos</span>: how to map a =
private IE on a
standard one? <o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #5 defines mediator =
arch &amp;
functions. Then it gives many use cases and =
requirements.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work items #3, #4 and #5 give =
many
functions a mediator may implement.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>At this step, the functions =
required for interoperability
between mediators are not identified. So please consider the necessity =
to
define the interoperability requirements prior to re =
charter.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'tab-stops:7.0cm'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Emile<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; -----Message =
d'origine-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; De&nbsp;: Juergen <span =
class=3DSpellE>Quittek</span>
[mailto:Quittek@netlab.nec.de]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; Envoy=E9&nbsp;: jeudi 26 juillet 2007 =
08:28<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;mso-ansi-language:FR'>&gt; =C0&nbsp;: =
ipfix@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DSpellE><span =
class=3DGramE>Objet</span></span><span
class=3DGramE>&nbsp;:</span> [IPFIX] new work item candidate #4: =
extended types<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Dear all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Candidates #4 to become a new IPFIX work =
item is
described by<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; draft
draft-boschi-ipfix-extended-type-00.txt.</span></font></span><span =
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt; =
4.</span></font></span><span
lang=3DEN-US> Extended Types (Elisa <span =
class=3DSpellE>Boschi</span>)<o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Needed for IPFIX files, most useful for Enterprise <span =
class=3DSpellE>IEs</span>;
need to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>specify what operations make sense for an =
IE.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><span class=3DGramE><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Support shown for this as a WG item, as for File =
Format.</span></font></span><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; &gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0
</span>Milestones:<span style=3D'mso-spacerun:yes'>=A0 </span>WG LC =
after IETF 70,
to IESG before <span class=3DGramE>IETF<span =
style=3D'mso-spacerun:yes'>=A0 =
</span>71</span>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; It is a method for assigning data types =
to
unknown IPFIX information<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>elements</span> by =
using option
records that map data types to element<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span =
class=3DGramE>identifiers</span>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; It can be applied in cases where an =
IPFIX
collector does not know the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>data</span> type of =
received
information elements. This may in particular =
happen<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>if</span> enterprise =
specific
elements are used. Without this information =
the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>collector</span> =
would treat
these elements as if they were of type octet =
array.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; With this information it may be able to =
treat
them more appropriately.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; The current version of the IPFIX file =
format
draft recommends using this<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <span class=3DGramE>method</span> when =
IPFIX
records are stored.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Do you think this is a useful extension =
of the
IPFIX protocol?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Do you think we should accept this as an =
IPFIX
work item?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Please have a look at the draft and send =
your
comments.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt;<span =
style=3D'mso-spacerun:yes'>=A0=A0=A0=A0 </span><span
class=3DSpellE>Juergen</span><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
_______________________________________________<o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; IPFIX mailing =
list<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
IPFIX@ietf.org<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>&gt; =
https://www1.ietf.org/mailman/listinfo/ipfix<o:p></o:p></span></font></p>=


</div>

</body>

</html>

------_=_NextPart_001_01C7CFA3.42576263--


--===============0194419872==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0194419872==--




From ipfix-bounces@ietf.org Thu Jul 26 13:42:08 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE7Le-0003kt-KZ; Thu, 26 Jul 2007 13:42:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7Lc-0003kn-CS
	for ipfix@ietf.org; Thu, 26 Jul 2007 13:42:00 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE7La-00052a-MI
	for ipfix@ietf.org; Thu, 26 Jul 2007 13:42:00 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QHfv524426; Thu, 26 Jul 2007 19:41:57 +0200 (CEST)
Received: from [10.82.224.112] (rtp-vpn1-112.cisco.com [10.82.224.112])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QHftQ24348; Thu, 26 Jul 2007 19:41:55 +0200 (CEST)
Message-ID: <46A8DCE2.5010508@cisco.com>
Date: Thu, 26 Jul 2007 12:41:54 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43ca87c8fcef5d9f6e966e1c3917103e
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0542245692=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0542245692==
Content-Type: multipart/alternative;
	boundary="------------050301020608020707050905"

This is a multi-part message in MIME format.
--------------050301020608020707050905
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by av-tac-bru.cisco.com id
	l6QHfv524426

Hi Emile,
>
> HI Juergen and Nevil,
>
> =20
>
> Work item #3
>
> Storing IPFIX records in files requires interoperability only when=20
> exchanging these files with some one else or some other application.=20
> So it's a function of mediation.
>
> =20
>
> Work item #4 points indirectly to a major point concern for telcos:=20
> how to map a private IE on a standard one?
>
I'm not sure this draft answers this question.

Regards, Benoit.
>
> =20
>
> Work item #5 defines mediator arch & functions. Then it gives many use=20
> cases and requirements.
>
> =20
>
> Work items #3, #4 and #5 give many functions a mediator may implement.
>
> At this step, the functions required for interoperability between=20
> mediators are not identified. So please consider the necessity to=20
> define the interoperability requirements prior to re charter.
>
> =20
>
> Regards
>
> Emile
>
> =20
>
> =20
>
> > -----Message d'origine-----
>
> > De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>
> > Envoy=E9 : jeudi 26 juillet 2007 08:28
>
> > =C0 : ipfix@ietf.org
>
> > Objet : [IPFIX] new work item candidate #4: extended types
>
> >
>
> > Dear all,
>
> >
>
> > Candidates #4 to become a new IPFIX work item is described by
>
> > draft draft-boschi-ipfix-extended-type-00.txt.
>
> >
>
> > > 4. Extended Types (Elisa Boschi)
>
> > >    Needed for IPFIX files, most useful for Enterprise IEs; need to
>
> > >    specify what operations make sense for an IE.
>
> > >    Support shown for this as a WG item, as for File Format.
>
> > >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>
> >
>
> > It is a method for assigning data types to unknown IPFIX information
>
> > elements by using option records that map data types to element
>
> > identifiers.
>
> >
>
> > It can be applied in cases where an IPFIX collector does not know the
>
> > data type of received information elements. This may in particular ha=
ppen
>
> > if enterprise specific elements are used. Without this information th=
e
>
> > collector would treat these elements as if they were of type octet ar=
ray.
>
> > With this information it may be able to treat them more appropriately.
>
> >
>
> > The current version of the IPFIX file format draft recommends using t=
his
>
> > method when IPFIX records are stored.
>
> >
>
> > Do you think this is a useful extension of the IPFIX protocol?
>
> > Do you think we should accept this as an IPFIX work item?
>
> > Please have a look at the draft and send your comments.
>
> >
>
> > Thanks,
>
> >
>
> >     Juergen
>
> >
>
> >
>
> >
>
> > _______________________________________________
>
> > IPFIX mailing list
>
> > IPFIX@ietf.org
>
> > https://www1.ietf.org/mailman/listinfo/ipfix
>
> -----------------------------------------------------------------------=
-
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
>  =20


--------------050301020608020707050905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Emile,<br>
<blockquote
 cite="midDD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="ProgId" content="Word.Document">
  <meta name="Generator" content="Microsoft Word 11">
  <meta name="Originator" content="Microsoft Word 11">
  <link rel="File-List" href="cid:filelist.xml@01C7CFB3.FBE653A0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
 </w:LatentStyles>
</xml><![endif]-->
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
  </style><!--[if gte mso 10]>
<style>
 /* Style Definitions */ 
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
  <div class="Section1">
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">HI <span class="SpellE">Juergen</span>
and Nevil,<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #3<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Storing IPFIX records in files
requires interoperability
only when exchanging these files with some one else or some other
application. So
it's a function of mediation.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #4 points indirectly
to a major
point concern for <span class="SpellE">telcos</span>: how to map a
private IE on a
standard one?</span></font></p>
  </div>
</blockquote>
I'm not sure this draft answers this question.<br>
<br>
Regards, Benoit.<br>
<blockquote
 cite="midDD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr"
 type="cite">
  <div class="Section1">
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"> <o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #5 defines mediator
arch &amp;
functions. Then it gives many use cases and requirements.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work items #3, #4 and #5 give
many
functions a mediator may implement.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">At this step, the functions
required for interoperability
between mediators are not identified. So please consider the necessity
to
define the interoperability requirements prior to re charter.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Regards<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Emile<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; -----Message d'origine-----<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; De&nbsp;: Juergen <span class="SpellE">Quittek</span>
[<a class="moz-txt-link-freetext" href="mailto:Quittek@netlab.nec.de">mailto:Quittek@netlab.nec.de</a>]<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; Envoy&eacute;&nbsp;: jeudi 26 juillet 2007 08:28<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; &Agrave;&nbsp;: <a class="moz-txt-link-abbreviated" href="mailto:ipfix@ietf.org">ipfix@ietf.org</a><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="SpellE"><span
 class="GramE">Objet</span></span><span class="GramE">&nbsp;:</span> [IPFIX]
new work item candidate #4: extended types<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Dear all,<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Candidates #4 to become a
new IPFIX work item is
described by<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; draft
draft-boschi-ipfix-extended-type-00.txt.</span></font></span><span
 lang="EN-US"><o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; &gt; 4.</span></font></span><span
 lang="EN-US"> Extended Types (Elisa <span class="SpellE">Boschi</span>)<o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>Needed for IPFIX files, most useful for Enterprise <span
 class="SpellE">IEs</span>;
need to<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>specify what operations make sense for an IE.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span
 style="">&nbsp;&nbsp;&nbsp;
  </span>Support shown for this as a WG item, as for File Format.</span></font></span><span
 lang="EN-US"><o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>Milestones:<span style="">&nbsp; </span>WG LC after IETF 70,
to IESG before <span class="GramE">IETF<span style="">&nbsp; </span>71</span>.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; It is a method for
assigning data types to
unknown IPFIX information<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">elements</span>
by using option
records that map data types to element<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">identifiers</span>.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; It can be applied in cases
where an IPFIX
collector does not know the<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">data</span>
type of received
information elements. This may in particular happen<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">if</span>
enterprise specific
elements are used. Without this information the<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">collector</span>
would treat
these elements as if they were of type octet array.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; With this information it
may be able to treat
them more appropriately.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; The current version of the
IPFIX file format
draft recommends using this<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">method</span>
when IPFIX
records are stored.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Do you think this is a
useful extension of the
IPFIX protocol?<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Do you think we should
accept this as an IPFIX
work item?<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Please have a look at the
draft and send your
comments.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Thanks,<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;<span style="">&nbsp;&nbsp;&nbsp;&nbsp; </span><span
 class="SpellE">Juergen</span><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;
_______________________________________________<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; IPFIX mailing list<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a><o:p></o:p></span></font></p>
  </div>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
IPFIX mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------050301020608020707050905--


--===============0542245692==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0542245692==--




From ipfix-bounces@ietf.org Thu Jul 26 13:42:08 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE7Le-0003kt-KZ; Thu, 26 Jul 2007 13:42:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7Lc-0003kn-CS
	for ipfix@ietf.org; Thu, 26 Jul 2007 13:42:00 -0400
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE7La-00052a-MI
	for ipfix@ietf.org; Thu, 26 Jul 2007 13:42:00 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QHfv524426; Thu, 26 Jul 2007 19:41:57 +0200 (CEST)
Received: from [10.82.224.112] (rtp-vpn1-112.cisco.com [10.82.224.112])
	by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id
	l6QHftQ24348; Thu, 26 Jul 2007 19:41:55 +0200 (CEST)
Message-ID: <46A8DCE2.5010508@cisco.com>
Date: Thu, 26 Jul 2007 12:41:54 -0500
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43ca87c8fcef5d9f6e966e1c3917103e
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0542245692=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0542245692==
Content-Type: multipart/alternative;
	boundary="------------050301020608020707050905"

This is a multi-part message in MIME format.
--------------050301020608020707050905
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by av-tac-bru.cisco.com id
	l6QHfv524426

Hi Emile,
>
> HI Juergen and Nevil,
>
> =20
>
> Work item #3
>
> Storing IPFIX records in files requires interoperability only when=20
> exchanging these files with some one else or some other application.=20
> So it's a function of mediation.
>
> =20
>
> Work item #4 points indirectly to a major point concern for telcos:=20
> how to map a private IE on a standard one?
>
I'm not sure this draft answers this question.

Regards, Benoit.
>
> =20
>
> Work item #5 defines mediator arch & functions. Then it gives many use=20
> cases and requirements.
>
> =20
>
> Work items #3, #4 and #5 give many functions a mediator may implement.
>
> At this step, the functions required for interoperability between=20
> mediators are not identified. So please consider the necessity to=20
> define the interoperability requirements prior to re charter.
>
> =20
>
> Regards
>
> Emile
>
> =20
>
> =20
>
> > -----Message d'origine-----
>
> > De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>
> > Envoy=E9 : jeudi 26 juillet 2007 08:28
>
> > =C0 : ipfix@ietf.org
>
> > Objet : [IPFIX] new work item candidate #4: extended types
>
> >
>
> > Dear all,
>
> >
>
> > Candidates #4 to become a new IPFIX work item is described by
>
> > draft draft-boschi-ipfix-extended-type-00.txt.
>
> >
>
> > > 4. Extended Types (Elisa Boschi)
>
> > >    Needed for IPFIX files, most useful for Enterprise IEs; need to
>
> > >    specify what operations make sense for an IE.
>
> > >    Support shown for this as a WG item, as for File Format.
>
> > >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>
> >
>
> > It is a method for assigning data types to unknown IPFIX information
>
> > elements by using option records that map data types to element
>
> > identifiers.
>
> >
>
> > It can be applied in cases where an IPFIX collector does not know the
>
> > data type of received information elements. This may in particular ha=
ppen
>
> > if enterprise specific elements are used. Without this information th=
e
>
> > collector would treat these elements as if they were of type octet ar=
ray.
>
> > With this information it may be able to treat them more appropriately.
>
> >
>
> > The current version of the IPFIX file format draft recommends using t=
his
>
> > method when IPFIX records are stored.
>
> >
>
> > Do you think this is a useful extension of the IPFIX protocol?
>
> > Do you think we should accept this as an IPFIX work item?
>
> > Please have a look at the draft and send your comments.
>
> >
>
> > Thanks,
>
> >
>
> >     Juergen
>
> >
>
> >
>
> >
>
> > _______________________________________________
>
> > IPFIX mailing list
>
> > IPFIX@ietf.org
>
> > https://www1.ietf.org/mailman/listinfo/ipfix
>
> -----------------------------------------------------------------------=
-
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
>  =20


--------------050301020608020707050905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Emile,<br>
<blockquote
 cite="midDD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="ProgId" content="Word.Document">
  <meta name="Generator" content="Microsoft Word 11">
  <meta name="Originator" content="Microsoft Word 11">
  <link rel="File-List" href="cid:filelist.xml@01C7CFB3.FBE653A0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
 </w:LatentStyles>
</xml><![endif]-->
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
  </style><!--[if gte mso 10]>
<style>
 /* Style Definitions */ 
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
  <div class="Section1">
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">HI <span class="SpellE">Juergen</span>
and Nevil,<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #3<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Storing IPFIX records in files
requires interoperability
only when exchanging these files with some one else or some other
application. So
it's a function of mediation.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #4 points indirectly
to a major
point concern for <span class="SpellE">telcos</span>: how to map a
private IE on a
standard one?</span></font></p>
  </div>
</blockquote>
I'm not sure this draft answers this question.<br>
<br>
Regards, Benoit.<br>
<blockquote
 cite="midDD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr"
 type="cite">
  <div class="Section1">
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"> <o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work item #5 defines mediator
arch &amp;
functions. Then it gives many use cases and requirements.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Work items #3, #4 and #5 give
many
functions a mediator may implement.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">At this step, the functions
required for interoperability
between mediators are not identified. So please consider the necessity
to
define the interoperability requirements prior to re charter.<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Regards<o:p></o:p></span></font></p>
  <p class="MsoPlainText" style=""><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">Emile<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; -----Message d'origine-----<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; De&nbsp;: Juergen <span class="SpellE">Quittek</span>
[<a class="moz-txt-link-freetext" href="mailto:Quittek@netlab.nec.de">mailto:Quittek@netlab.nec.de</a>]<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; Envoy&eacute;&nbsp;: jeudi 26 juillet 2007 08:28<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;">&gt; &Agrave;&nbsp;: <a class="moz-txt-link-abbreviated" href="mailto:ipfix@ietf.org">ipfix@ietf.org</a><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="SpellE"><span
 class="GramE">Objet</span></span><span class="GramE">&nbsp;:</span> [IPFIX]
new work item candidate #4: extended types<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Dear all,<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Candidates #4 to become a
new IPFIX work item is
described by<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; draft
draft-boschi-ipfix-extended-type-00.txt.</span></font></span><span
 lang="EN-US"><o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; &gt; 4.</span></font></span><span
 lang="EN-US"> Extended Types (Elisa <span class="SpellE">Boschi</span>)<o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>Needed for IPFIX files, most useful for Enterprise <span
 class="SpellE">IEs</span>;
need to<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>specify what operations make sense for an IE.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><span class="GramE"><font face="Courier New"
 size="2"><span style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span
 style="">&nbsp;&nbsp;&nbsp;
  </span>Support shown for this as a WG item, as for File Format.</span></font></span><span
 lang="EN-US"><o:p></o:p></span></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; &gt;<span style="">&nbsp;&nbsp;&nbsp;
  </span>Milestones:<span style="">&nbsp; </span>WG LC after IETF 70,
to IESG before <span class="GramE">IETF<span style="">&nbsp; </span>71</span>.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; It is a method for
assigning data types to
unknown IPFIX information<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">elements</span>
by using option
records that map data types to element<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">identifiers</span>.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; It can be applied in cases
where an IPFIX
collector does not know the<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">data</span>
type of received
information elements. This may in particular happen<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">if</span>
enterprise specific
elements are used. Without this information the<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">collector</span>
would treat
these elements as if they were of type octet array.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; With this information it
may be able to treat
them more appropriately.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; The current version of the
IPFIX file format
draft recommends using this<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <span class="GramE">method</span>
when IPFIX
records are stored.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Do you think this is a
useful extension of the
IPFIX protocol?<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Do you think we should
accept this as an IPFIX
work item?<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Please have a look at the
draft and send your
comments.<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; Thanks,<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;<span style="">&nbsp;&nbsp;&nbsp;&nbsp; </span><span
 class="SpellE">Juergen</span><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;
_______________________________________________<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; IPFIX mailing list<o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt; <a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><o:p></o:p></span></font></p>
  <p class="MsoPlainText"><font face="Courier New" size="2"><span
 style="font-size: 10pt;" lang="EN-US">&gt;
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a><o:p></o:p></span></font></p>
  </div>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
IPFIX mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPFIX@ietf.org">IPFIX@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.org/mailman/listinfo/ipfix</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------050301020608020707050905--


--===============0542245692==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0542245692==--




From ipfix-bounces@ietf.org Thu Jul 26 14:19:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE7wC-0005ni-LQ; Thu, 26 Jul 2007 14:19:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7wB-0005mM-35
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:19:47 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE7w9-0005l7-O5
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:19:47 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 20:19:46 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAPuCqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149107205:sNHT30247078"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QIJjQc016872; 
	Thu, 26 Jul 2007 20:19:45 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QIJgkt005970; 
	Thu, 26 Jul 2007 18:19:42 GMT
Received: from [10.82.240.227] (rtp-vpn2-227.cisco.com [10.82.240.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id TAA25831;
	Thu, 26 Jul 2007 19:19:40 +0100 (BST)
Message-ID: <46A8E5BF.7040108@cisco.com>
Date: Thu, 26 Jul 2007 19:19:43 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=738; t=1185473985;
	x=1186337985; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20requirements=3A=20=20Extraction,
	=20Distribu
	tion, =20Duplication, =0A=20=09Aggregation=20, =20Storage,
	=20Self=20Descripti
	on,=20Anonymization,=20=09Obfuscation=20=20... |Sender:=20;
	bh=tR04+PMeRy3ST61Sx5bHxB+CYO5cWfGjtD7rijqHvdI=;
	b=wJpIC+W6+yW6ZY5E2dT8Elxjs8qLBLJemR31aTdbnx79gOUil5M5nyhhxi6kmKztYA8fG6YH
	Vy9ACL9Euh8lNE14WlWJ8hJBWiClzmLp4pGUu7jZLcma5G/93UzvhniZ;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Emile,


> Work item #3
> 
> Storing IPFIX records in files requires interoperability only when 
> exchanging these files with some one else or some other application. So 
> it's a function of mediation.

If I consider a slight change of focus and name to "IP Flow Information 
Exchange", then I think an interoperable file format is crucial.

It's possible that simple collectors will want to use the file format to 
store received flows, and such files may be exchanged by researchers for 
analysing data or testing purposes.

So while the file format MAY be a function of mediation, I certainly 
don't think it's exclusively a mediation function.

Cheers.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 14:19:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE7wC-0005ni-LQ; Thu, 26 Jul 2007 14:19:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7wB-0005mM-35
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:19:47 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE7w9-0005l7-O5
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:19:47 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 20:19:46 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAPuCqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149107205:sNHT30247078"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QIJjQc016872; 
	Thu, 26 Jul 2007 20:19:45 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QIJgkt005970; 
	Thu, 26 Jul 2007 18:19:42 GMT
Received: from [10.82.240.227] (rtp-vpn2-227.cisco.com [10.82.240.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id TAA25831;
	Thu, 26 Jul 2007 19:19:40 +0100 (BST)
Message-ID: <46A8E5BF.7040108@cisco.com>
Date: Thu, 26 Jul 2007 19:19:43 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=738; t=1185473985;
	x=1186337985; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20requirements=3A=20=20Extraction,
	=20Distribu
	tion, =20Duplication, =0A=20=09Aggregation=20, =20Storage,
	=20Self=20Descripti
	on,=20Anonymization,=20=09Obfuscation=20=20... |Sender:=20;
	bh=tR04+PMeRy3ST61Sx5bHxB+CYO5cWfGjtD7rijqHvdI=;
	b=wJpIC+W6+yW6ZY5E2dT8Elxjs8qLBLJemR31aTdbnx79gOUil5M5nyhhxi6kmKztYA8fG6YH
	Vy9ACL9Euh8lNE14WlWJ8hJBWiClzmLp4pGUu7jZLcma5G/93UzvhniZ;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Emile,


> Work item #3
> 
> Storing IPFIX records in files requires interoperability only when 
> exchanging these files with some one else or some other application. So 
> it's a function of mediation.

If I consider a slight change of focus and name to "IP Flow Information 
Exchange", then I think an interoperable file format is crucial.

It's possible that simple collectors will want to use the file format to 
store received flows, and such files may be exchanged by researchers for 
analysing data or testing purposes.

So while the file format MAY be a function of mediation, I certainly 
don't think it's exclusively a mediation function.

Cheers.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From rdghlu@lsc.net.tw Thu Jul 26 14:29:22 2007
Return-path: <rdghlu@lsc.net.tw>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE85S-0004WP-0Z; Thu, 26 Jul 2007 14:29:22 -0400
Received: from [89.242.44.143] (helo=lsc.net.tw)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IE85J-0005wO-As; Thu, 26 Jul 2007 14:29:21 -0400
Message-ID: <229501c7cff1$1610dba0$2f1abb5b@rdghlu>
From: "Oscar" <rdghlu@lsc.net.tw>
To: "Jamey" <ipfix-archive@lists.ietf.org>
Cc: "Shayne Hudson" <idmr-archive@lists.ietf.org>,
	"Jeannetta Little" <ipsec-archive@lists.ietf.org>,
	"Clinton Gordon" <6lowpan@lists.ietf.org>,
	"Haley Gilbert" <kitten@lists.ietf.org>,
	"Reena" <iporpr-archive@lists.ietf.org>
Subject: Yes or no
Date: Fri, 27 Jul 2007 01:54:36 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

Finally prices you can appreciate about.

DiscountPharmacy a Best Canadian Intl. Medicine Service Supplier. Ever
since opening in Y2k of March, Discount-Pharmacy  has merit many
pharmaceutics official approvals and turn out to be one of the largely
reliable pharmacies on the Internet. With over  regular staff, and over 4500
prescribed by doctor filled every day and shipped cautiously to patients
globally, you can count on us with your medical prescription medicine
purchase.

For more Information, Try this Link: www.viberx.org


Places of honour reading had been kept for the Miss Lammeters near the town
head gladly of the slope principal tea-table in th snake pass hour wail Here
and there a sallow, begrimed face looked out from a gloomy doorway at the
strangers, and increa DIVERS WOMEN axillary map mark set OF THE CHORUS. 
With that, line Dunstan slammed dream the door behind him, and left Godfrey
to that asinine bitter send rumination on his pe One band was round flying,
down good by place empty rocks and trees





From ipfix-bounces@ietf.org Thu Jul 26 14:35:46 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Bd-00018b-B9; Thu, 26 Jul 2007 14:35:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Bc-00018W-HP
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:35:44 -0400
Received: from franclinus.red.cert.org ([192.88.209.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE8Ba-00063r-LP
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:35:44 -0400
Received: from franclinus.red.cert.org (localhost [127.0.0.1])
	by franclinus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6QIZVsH008042 for <ipfix@ietf.org>; Thu, 26 Jul 2007 14:35:38 -0400
Received: (from defang@localhost)
	by franclinus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6QIYHHd007955
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 14:34:17 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by franclinus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6QIYFks007952;
	Thu, 26 Jul 2007 14:34:17 -0400 (EDT)
Received: from [130.129.18.248] (vpn-10-25-4-9.remote.cert.org [10.25.4.9])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6QIYFfH023964; Thu, 26 Jul 2007 14:34:15 -0400
In-Reply-To: <46A8DCE2.5010508@cisco.com>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8DCE2.5010508@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <71DCBA8E-C0FB-4B60-9EA8-43EA87C31217@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
Date: Thu, 26 Jul 2007 13:34:12 -0500
To: Benoit Claise <bclaise@cisco.com>,
	STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Benoit, Emile,

>> Work item #4 points indirectly to a major point concern for  
>> telcos: how to map a private IE on a standard one?
>>
> I'm not sure this draft answers this question

Speaking as a co-author of the draft in question, indeed, it does  
not. It aims to provide a generalized method for representing the  
properties of Information Elements as defined in the IPFIX  
Information Model inline within an IPFIX Message. We have a bit more  
work to do on a -01 revision which will address those Information  
Element properties (e.g., units, names) not presently in the draft;  
such a revision is forthcoming.

Information Element equivalence, while potentially interesting, is  
out of scope and would be a subject for future work in another draft.  
I'm not sure how useful it would be beyond two particular cases (1. a  
private IE which is submitted to IANA and becomes an IANA IE; 2. two  
vendors exporting _exactly_ the same data with different IEs within  
their own respective PEN number spaces), but I'll admit I've not  
thought that deeply about it...
>> Work items #3, #4 and #5 give many functions a mediator may  
>> implement.
While the file draft and extended type draft define functions that  
may be implemented within a mediator, they are not specifically  
scoped to the mediator case. So I don't think it's necessary to  
define a mediator architecture in order to specify a file format and  
extended type mechanism.

(i.e., what Paul just said).

Regards,

Brian

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 14:35:46 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Bd-00018b-B9; Thu, 26 Jul 2007 14:35:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Bc-00018W-HP
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:35:44 -0400
Received: from franclinus.red.cert.org ([192.88.209.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE8Ba-00063r-LP
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:35:44 -0400
Received: from franclinus.red.cert.org (localhost [127.0.0.1])
	by franclinus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6QIZVsH008042 for <ipfix@ietf.org>; Thu, 26 Jul 2007 14:35:38 -0400
Received: (from defang@localhost)
	by franclinus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6QIYHHd007955
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 14:34:17 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by franclinus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6QIYFks007952;
	Thu, 26 Jul 2007 14:34:17 -0400 (EDT)
Received: from [130.129.18.248] (vpn-10-25-4-9.remote.cert.org [10.25.4.9])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6QIYFfH023964; Thu, 26 Jul 2007 14:34:15 -0400
In-Reply-To: <46A8DCE2.5010508@cisco.com>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8DCE2.5010508@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <71DCBA8E-C0FB-4B60-9EA8-43EA87C31217@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization,
	Obfuscation  ...
Date: Thu, 26 Jul 2007 13:34:12 -0500
To: Benoit Claise <bclaise@cisco.com>,
	STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Benoit, Emile,

>> Work item #4 points indirectly to a major point concern for  
>> telcos: how to map a private IE on a standard one?
>>
> I'm not sure this draft answers this question

Speaking as a co-author of the draft in question, indeed, it does  
not. It aims to provide a generalized method for representing the  
properties of Information Elements as defined in the IPFIX  
Information Model inline within an IPFIX Message. We have a bit more  
work to do on a -01 revision which will address those Information  
Element properties (e.g., units, names) not presently in the draft;  
such a revision is forthcoming.

Information Element equivalence, while potentially interesting, is  
out of scope and would be a subject for future work in another draft.  
I'm not sure how useful it would be beyond two particular cases (1. a  
private IE which is submitted to IANA and becomes an IANA IE; 2. two  
vendors exporting _exactly_ the same data with different IEs within  
their own respective PEN number spaces), but I'll admit I've not  
thought that deeply about it...
>> Work items #3, #4 and #5 give many functions a mediator may  
>> implement.
While the file draft and extended type draft define functions that  
may be implemented within a mediator, they are not specifically  
scoped to the mediator case. So I don't think it's necessary to  
define a mediator architecture in order to specify a file format and  
extended type mechanism.

(i.e., what Paul just said).

Regards,

Brian

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 14:48:34 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Nw-00047w-Cx; Thu, 26 Jul 2007 14:48:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Nv-00047r-MG
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:48:27 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8Nu-00056f-5A
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:48:27 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 20:48:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Jul 2007 20:47:57 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75066@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A8DCE2.5010508@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: mapping private IE
Thread-Index: AcfPrEpH4q8EFfYaRb+HVQgQEE9zVAABTOeg
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8DCE2.5010508@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Benoit Claise" <bclaise@cisco.com>
X-OriginalArrivalTime: 26 Jul 2007 18:48:17.0240 (UTC)
	FILETIME=[877B8D80:01C7CFB5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f8267f77ca4545e62c57802503816d5
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] mapping private IE
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1349655586=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1349655586==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFB5.8708EE2B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFB5.8708EE2B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Benoit,
=20
The aim of this draft is to standardize the transcoding of private IE to =
standard datatype. It is a subset of one telco need: mapping private IE =
to a standard IE.=20
=20
The approach I propose is really open because new datatypes IE may be =
added in the future in the IANA IPFIX info model registry.=20
=20
Regards
Emile
=20
________________________________

De : Benoit Claise [mailto:bclaise@cisco.com]=20
Envoy=E9 : jeudi 26 juillet 2007 19:42
=C0 : STEPHAN Emile RD-CORE-LAN
Cc : Juergen Quittek; Nevil Brownlee; ipfix@ietf.org
Objet : Re: [IPFIX] requirements: Extraction, Distribution, =
Duplication,Aggregation , Storage, Self Description, Anonymization, =
Obfuscation ...
=20
Hi Emile,


HI Juergen and Nevil,
=20
Work item #3
Storing IPFIX records in files requires interoperability only when =
exchanging these files with some one else or some other application. So =
it's a function of mediation.
=20
Work item #4 points indirectly to a major point concern for telcos: how =
to map a private IE on a standard one?
I'm not sure this draft answers this question.

Regards, Benoit.


=20
Work item #5 defines mediator arch & functions. Then it gives many use =
cases and requirements.
=20
Work items #3, #4 and #5 give many functions a mediator may implement.
At this step, the functions required for interoperability between =
mediators are not identified. So please consider the necessity to define =
the interoperability requirements prior to re charter.
=20
Regards
Emile
=20
=20
> -----Message d'origine-----
> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9 : jeudi 26 juillet 2007 08:28
> =C0 : ipfix@ietf.org
> Objet : [IPFIX] new work item candidate #4: extended types
>=20
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
> > 4. Extended Types (Elisa Boschi)
> >    Needed for IPFIX files, most useful for Enterprise IEs; need to
> >    specify what operations make sense for an IE.
> >    Support shown for this as a WG item, as for File Format.
> >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element
> identifiers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular =
happen
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet =
array.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using =
this
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
=20



________________________________



=20
_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix
 =20
=20

------_=_NextPart_001_01C7CFB5.8708EE2B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C7CFC6.3F550840">
<link rel=3DEdit-Time-Data href=3D"cid:editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	color:black;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	color:black;
	mso-ansi-language:EN-US;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Hi =
Benoit,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The aim of this =
draft is
to standardize the <span class=3DSpellE>transcoding</span> of private IE =
to standard
<span class=3DSpellE>datatype</span>. It is a subset of one <span =
class=3DSpellE>telco</span>
need: mapping private IE to a standard IE. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The approach I =
propose is
really open because new <span class=3DSpellE>datatypes</span> IE may be =
added in
the future in the IANA IPFIX info model registry. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Regards<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Emile<o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext;
mso-ansi-language:FR'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;mso-ansi-la=
nguage:
FR;font-weight:bold'>De&nbsp;:</span></font></b><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;
mso-ansi-language:FR'> Benoit Claise [mailto:bclaise@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> jeudi 26 =
juillet
2007 19:42<br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> STEPHAN Emile =
RD-CORE-LAN<br>
<b><span style=3D'font-weight:bold'>Cc&nbsp;:</span></b> Juergen =
Quittek; Nevil
Brownlee; ipfix@ietf.org<br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> Re: [IPFIX]
requirements: Extraction, Distribution, Duplication,Aggregation , =
Storage, Self
Description, Anonymization, Obfuscation ...</span></font><font =
color=3Dblack><span
style=3D'color:windowtext;mso-ansi-language:FR'><o:p></o:p></span></font>=
</p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
lang=3DEN-US style=3D'font-size:12.0pt'>Hi Emile,<br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'><!--[if gte mso 9]><xml>
 <u1:OfficeDocumentSettings>
  <u1:RelyOnVML/>
  <u1:DoNotRelyOnCSS/>
 </u1:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>90</u2:Zoom>
  <u2:SpellingState>Clean</u2:SpellingState>
  <u2:GrammarState>Clean</u2:GrammarState>
  <u2:DocumentKind>DocumentEmail</u2:DocumentKind>
  <u2:HyphenationZone>21</u2:HyphenationZone>
  <u2:EnvelopeVis/>
  <u2:PunctuationKerning/>
  <u2:ValidateAgainstSchemas/>
  <u2:SaveIfXMLInvalid>false</u2:SaveIfXMLInvalid>
  <u2:IgnoreMixedContent>false</u2:IgnoreMixedContent>
  <u2:AlwaysShowPlaceholderText>false</u2:AlwaysShowPlaceholderText>
  <u2:Compatibility>
   <u2:BreakWrappedTables/>
   <u2:SnapToGridInCell/>
   <u2:WrapTextWithPunct/>
   <u2:UseAsianBreakRules/>
   <u2:DontGrowAutofit/>
   <u2:UseFELayout/>
  </u2:Compatibility>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">  =
</u3:LatentStyles>
</xml><![endif]-->HI Juergen and =
Nevil,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item =
#3<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Storing IPFIX records in files =
requires
interoperability only when exchanging these files with some one else or =
some
other application. So it's a function of =
mediation.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #4 points indirectly =
to a major
point concern for telcos: how to map a private IE on a standard =
one?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-ansi-language:FR'>I'm not sure this draft =
answers
this question.<br>
<br>
Regards, Benoit.<br style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p></u4:p><u4:p>&nbsp;</u4:p><o:p></o:p></s=
pan></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #5 defines mediator =
arch &amp;
functions. Then it gives many use cases and =
requirements.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work items #3, #4 and #5 give =
many
functions a mediator may =
implement.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>At this step, the functions =
required for
interoperability between mediators are not identified. So please =
consider the
necessity to define the interoperability requirements prior to re =
charter.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Regards<u4:p></u4:p><o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Emile<u4:p></u4:p><o:p></o:p></span></font></p=
>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; -----Message =
d'origine-----<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; De&nbsp;: Juergen Quittek =
[<a
href=3D"mailto:Quittek@netlab.nec.de">mailto:Quittek@netlab.nec.de</a>]<u=
4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Envoy=E9&nbsp;: jeudi 26 =
juillet 2007
08:28<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =C0&nbsp;: <a
href=3D"mailto:ipfix@ietf.org">ipfix@ietf.org</a><u4:p></u4:p><o:p></o:p>=
</span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Objet&nbsp;: [IPFIX] new =
work item
candidate #4: extended types<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Dear =
all,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Candidates #4 to become a =
new IPFIX
work item is described by<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; draft
draft-boschi-ipfix-extended-type-00.txt.<o:p></o:p></span></font></p>

<u4:p></u4:p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt; 4. Extended Types =
(Elisa Boschi)<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
Needed for
IPFIX files, most useful for Enterprise IEs; need =
to<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
specify what
operations make sense for an =
IE.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
Support shown
for this as a WG item, as for File Format.<o:p></o:p></span></font></p>

<u4:p></u4:p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp;
Milestones:&nbsp; WG LC after IETF 70, to IESG before IETF&nbsp; =
71.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; It is a method for =
assigning data
types to unknown IPFIX =
information<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; elements by using option =
records that
map data types to element<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
identifiers.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; It can be applied in cases =
where an
IPFIX collector does not know =
the<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; data type of received =
information
elements. This may in particular =
happen<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; if enterprise specific =
elements are
used. Without this information =
the<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; collector would treat these =
elements
as if they were of type octet =
array.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; With this information it =
may be able
to treat them more =
appropriately.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; The current version of the =
IPFIX file
format draft recommends using =
this<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; method when IPFIX records =
are stored.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Do you think this is a =
useful
extension of the IPFIX =
protocol?<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Do you think we should =
accept this as
an IPFIX work item?<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Please have a look at the =
draft and
send your comments.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
Thanks,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
Juergen<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt;
_______________________________________________<u4:p></u4:p><o:p></o:p></=
span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; IPFIX mailing =
list<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; <a =
href=3D"mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><u4:p></u4:p><o:p></o:p>=
</span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; <a
href=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.o=
rg/mailman/listinfo/ipfix</a><u4:p></u4:p><o:p></o:p></span></font></p>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre
style=3D'text-align:center'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>

<hr size=3D4 width=3D"90%" align=3Dcenter>

</span></font></pre><pre><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
_<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>IPFIX mailing =
list<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><o:p></o:p></span></font=
></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.o=
rg/mailman/listinfo/ipfix</a><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><span style=3D'mso-spacerun:yes'>=A0 =
</span><o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-ansi-language:FR'><o:p>&nbsp;</o:p></span><=
/font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7CFB5.8708EE2B--


--===============1349655586==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1349655586==--




From ipfix-bounces@ietf.org Thu Jul 26 14:48:35 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Nw-00047w-Cx; Thu, 26 Jul 2007 14:48:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Nv-00047r-MG
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:48:27 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8Nu-00056f-5A
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:48:27 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 20:48:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 26 Jul 2007 20:47:57 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75066@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A8DCE2.5010508@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: mapping private IE
Thread-Index: AcfPrEpH4q8EFfYaRb+HVQgQEE9zVAABTOeg
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8DCE2.5010508@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Benoit Claise" <bclaise@cisco.com>
X-OriginalArrivalTime: 26 Jul 2007 18:48:17.0240 (UTC)
	FILETIME=[877B8D80:01C7CFB5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f8267f77ca4545e62c57802503816d5
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] mapping private IE
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1349655586=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1349655586==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFB5.8708EE2B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFB5.8708EE2B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Benoit,
=20
The aim of this draft is to standardize the transcoding of private IE to =
standard datatype. It is a subset of one telco need: mapping private IE =
to a standard IE.=20
=20
The approach I propose is really open because new datatypes IE may be =
added in the future in the IANA IPFIX info model registry.=20
=20
Regards
Emile
=20
________________________________

De : Benoit Claise [mailto:bclaise@cisco.com]=20
Envoy=E9 : jeudi 26 juillet 2007 19:42
=C0 : STEPHAN Emile RD-CORE-LAN
Cc : Juergen Quittek; Nevil Brownlee; ipfix@ietf.org
Objet : Re: [IPFIX] requirements: Extraction, Distribution, =
Duplication,Aggregation , Storage, Self Description, Anonymization, =
Obfuscation ...
=20
Hi Emile,


HI Juergen and Nevil,
=20
Work item #3
Storing IPFIX records in files requires interoperability only when =
exchanging these files with some one else or some other application. So =
it's a function of mediation.
=20
Work item #4 points indirectly to a major point concern for telcos: how =
to map a private IE on a standard one?
I'm not sure this draft answers this question.

Regards, Benoit.


=20
Work item #5 defines mediator arch & functions. Then it gives many use =
cases and requirements.
=20
Work items #3, #4 and #5 give many functions a mediator may implement.
At this step, the functions required for interoperability between =
mediators are not identified. So please consider the necessity to define =
the interoperability requirements prior to re charter.
=20
Regards
Emile
=20
=20
> -----Message d'origine-----
> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9 : jeudi 26 juillet 2007 08:28
> =C0 : ipfix@ietf.org
> Objet : [IPFIX] new work item candidate #4: extended types
>=20
> Dear all,
>=20
> Candidates #4 to become a new IPFIX work item is described by
> draft draft-boschi-ipfix-extended-type-00.txt.
>=20
> > 4. Extended Types (Elisa Boschi)
> >    Needed for IPFIX files, most useful for Enterprise IEs; need to
> >    specify what operations make sense for an IE.
> >    Support shown for this as a WG item, as for File Format.
> >    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It is a method for assigning data types to unknown IPFIX information
> elements by using option records that map data types to element
> identifiers.
>=20
> It can be applied in cases where an IPFIX collector does not know the
> data type of received information elements. This may in particular =
happen
> if enterprise specific elements are used. Without this information the
> collector would treat these elements as if they were of type octet =
array.
> With this information it may be able to treat them more appropriately.
>=20
> The current version of the IPFIX file format draft recommends using =
this
> method when IPFIX records are stored.
>=20
> Do you think this is a useful extension of the IPFIX protocol?
> Do you think we should accept this as an IPFIX work item?
> Please have a look at the draft and send your comments.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix
=20



________________________________



=20
_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix
 =20
=20

------_=_NextPart_001_01C7CFB5.8708EE2B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C7CFC6.3F550840">
<link rel=3DEdit-Time-Data href=3D"cid:editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>90</w:Zoom>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	color:black;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	color:black;
	mso-ansi-language:EN-US;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]--><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Hi =
Benoit,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The aim of this =
draft is
to standardize the <span class=3DSpellE>transcoding</span> of private IE =
to standard
<span class=3DSpellE>datatype</span>. It is a subset of one <span =
class=3DSpellE>telco</span>
need: mapping private IE to a standard IE. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The approach I =
propose is
really open because new <span class=3DSpellE>datatypes</span> IE may be =
added in
the future in the IANA IPFIX info model registry. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Regards<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Emile<o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext;
mso-ansi-language:FR'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;mso-ansi-la=
nguage:
FR;font-weight:bold'>De&nbsp;:</span></font></b><font size=3D2 =
color=3Dblack
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;
mso-ansi-language:FR'> Benoit Claise [mailto:bclaise@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> jeudi 26 =
juillet
2007 19:42<br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> STEPHAN Emile =
RD-CORE-LAN<br>
<b><span style=3D'font-weight:bold'>Cc&nbsp;:</span></b> Juergen =
Quittek; Nevil
Brownlee; ipfix@ietf.org<br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> Re: [IPFIX]
requirements: Extraction, Distribution, Duplication,Aggregation , =
Storage, Self
Description, Anonymization, Obfuscation ...</span></font><font =
color=3Dblack><span
style=3D'color:windowtext;mso-ansi-language:FR'><o:p></o:p></span></font>=
</p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
lang=3DEN-US =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
lang=3DEN-US style=3D'font-size:12.0pt'>Hi Emile,<br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'><!--[if gte mso 9]><xml>
 <u1:OfficeDocumentSettings>
  <u1:RelyOnVML/>
  <u1:DoNotRelyOnCSS/>
 </u1:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>90</u2:Zoom>
  <u2:SpellingState>Clean</u2:SpellingState>
  <u2:GrammarState>Clean</u2:GrammarState>
  <u2:DocumentKind>DocumentEmail</u2:DocumentKind>
  <u2:HyphenationZone>21</u2:HyphenationZone>
  <u2:EnvelopeVis/>
  <u2:PunctuationKerning/>
  <u2:ValidateAgainstSchemas/>
  <u2:SaveIfXMLInvalid>false</u2:SaveIfXMLInvalid>
  <u2:IgnoreMixedContent>false</u2:IgnoreMixedContent>
  <u2:AlwaysShowPlaceholderText>false</u2:AlwaysShowPlaceholderText>
  <u2:Compatibility>
   <u2:BreakWrappedTables/>
   <u2:SnapToGridInCell/>
   <u2:WrapTextWithPunct/>
   <u2:UseAsianBreakRules/>
   <u2:DontGrowAutofit/>
   <u2:UseFELayout/>
  </u2:Compatibility>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">  =
</u3:LatentStyles>
</xml><![endif]-->HI Juergen and =
Nevil,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item =
#3<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Storing IPFIX records in files =
requires
interoperability only when exchanging these files with some one else or =
some
other application. So it's a function of =
mediation.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #4 points indirectly =
to a major
point concern for telcos: how to map a private IE on a standard =
one?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-ansi-language:FR'>I'm not sure this draft =
answers
this question.<br>
<br>
Regards, Benoit.<br style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p></u4:p><u4:p>&nbsp;</u4:p><o:p></o:p></s=
pan></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work item #5 defines mediator =
arch &amp;
functions. Then it gives many use cases and =
requirements.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Work items #3, #4 and #5 give =
many
functions a mediator may =
implement.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>At this step, the functions =
required for
interoperability between mediators are not identified. So please =
consider the
necessity to define the interoperability requirements prior to re =
charter.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Regards<u4:p></u4:p><o:p></o:p></span></font><=
/p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'>Emile<u4:p></u4:p><o:p></o:p></span></font></p=
>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><u4:p>&nbsp;</u4:p><o:p></o:p></span></font></=
p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; -----Message =
d'origine-----<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; De&nbsp;: Juergen Quittek =
[<a
href=3D"mailto:Quittek@netlab.nec.de">mailto:Quittek@netlab.nec.de</a>]<u=
4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Envoy=E9&nbsp;: jeudi 26 =
juillet 2007
08:28<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =C0&nbsp;: <a
href=3D"mailto:ipfix@ietf.org">ipfix@ietf.org</a><u4:p></u4:p><o:p></o:p>=
</span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Objet&nbsp;: [IPFIX] new =
work item
candidate #4: extended types<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Dear =
all,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Candidates #4 to become a =
new IPFIX
work item is described by<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; draft
draft-boschi-ipfix-extended-type-00.txt.<o:p></o:p></span></font></p>

<u4:p></u4:p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt; 4. Extended Types =
(Elisa Boschi)<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
Needed for
IPFIX files, most useful for Enterprise IEs; need =
to<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
specify what
operations make sense for an =
IE.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp; =
Support shown
for this as a WG item, as for File Format.<o:p></o:p></span></font></p>

<u4:p></u4:p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; &gt;&nbsp;&nbsp;&nbsp;
Milestones:&nbsp; WG LC after IETF 70, to IESG before IETF&nbsp; =
71.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; It is a method for =
assigning data
types to unknown IPFIX =
information<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; elements by using option =
records that
map data types to element<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
identifiers.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; It can be applied in cases =
where an
IPFIX collector does not know =
the<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; data type of received =
information
elements. This may in particular =
happen<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; if enterprise specific =
elements are
used. Without this information =
the<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; collector would treat these =
elements
as if they were of type octet =
array.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; With this information it =
may be able
to treat them more =
appropriately.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; The current version of the =
IPFIX file
format draft recommends using =
this<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; method when IPFIX records =
are stored.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Do you think this is a =
useful
extension of the IPFIX =
protocol?<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Do you think we should =
accept this as
an IPFIX work item?<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; Please have a look at the =
draft and
send your comments.<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
Thanks,<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
Juergen<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; =
<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt;
_______________________________________________<u4:p></u4:p><o:p></o:p></=
span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; IPFIX mailing =
list<u4:p></u4:p><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; <a =
href=3D"mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><u4:p></u4:p><o:p></o:p>=
</span></font></p>

<p class=3DMsoPlainText><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&gt; <a
href=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.o=
rg/mailman/listinfo/ipfix</a><u4:p></u4:p><o:p></o:p></span></font></p>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre
style=3D'text-align:center'><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>

<hr size=3D4 width=3D"90%" align=3Dcenter>

</span></font></pre><pre><font size=3D2 color=3Dblack face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
_<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>IPFIX mailing =
list<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:IPFIX@ietf.org">IPFIX@ietf.org</a><o:p></o:p></span></font=
></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https://www1.ietf.o=
rg/mailman/listinfo/ipfix</a><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><span style=3D'mso-spacerun:yes'>=A0 =
</span><o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-ansi-language:FR'><o:p>&nbsp;</o:p></span><=
/font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7CFB5.8708EE2B--


--===============1349655586==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1349655586==--




From ipfix-bounces@ietf.org Thu Jul 26 14:54:28 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Tj-000273-Kt; Thu, 26 Jul 2007 14:54:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Ti-00026y-Nm
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:54:26 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8Ti-0005CT-1q
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:54:26 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0A5A928016A80;
	Thu, 26 Jul 2007 20:54:27 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dnRletM05lXz; Thu, 26 Jul 2007 20:54:26 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id DB94128014C90;
	Thu, 26 Jul 2007 20:54:06 +0200 (CEST)
Received: from 130.129.82.248 ([130.129.82.248]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 26 Jul 2007 18:54:05 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 20:54:03 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>,
	Nevil Brownlee <nevil@auckland.ac.nz>, <ipfix@ietf.org>
Message-ID: <C2CEBA6B.10314%Quittek@netlab.nec.de>
Thread-Topic: requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8QAAefNig=
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: 
Subject: [IPFIX] Re: requirements:  Extraction, Distribution, Duplication,
 Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Emile,


Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
<emile.stephan@orange-ftgroup.com>:

> HI Juergen and Nevil,
> =20
> Work item #3
> Storing IPFIX records in files requires interoperability only when exchan=
ging
> these files with some one else or some other application. So it's a funct=
ion
> of mediation.

I agree that one may see it this way and it is a very good point to conside=
r
when working on a file format.  However, for the discussions we are having
I would prefer to separate the discussion on the file format work item from
the discussion on the mediator work item.

> Work item #4 points indirectly to a major point concern for telcos: how t=
o map
> a private IE on a standard one?

Now I understand your requirement.
However, as it is currently written, the proposed work does not suggest to
map enterprise-specific IEs to standard ones, but to just assign data types
to unknown (enterprise-specific) IEs. This is a use case different to yours=
.

> Work item #5 defines mediator arch & functions. Then it gives many use ca=
ses
> and requirements.

I fully agree.
=20
> Work items #3, #4 and #5 give many functions a mediator may implement.
> At this step, the functions required for interoperability between mediato=
rs
> are not identified. So please consider the necessity to define the
> interoperability requirements prior to re charter.

Thank you  for this hint.
We will consider it if we charter a work item on mediation.

Thanks,

    Juergen

> Regards
> Emile
> =20
> =20
>> -----Message d'origine-----
>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>> Envoy=E9 : jeudi 26 juillet 2007 08:28
>> =C0 : ipfix@ietf.org
>> Objet : [IPFIX] new work item candidate #4: extended types
>>=20
>> Dear all,
>>=20
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>=20
>>> 4. Extended Types (Elisa Boschi)
>>> =A0=A0=A0 Needed for IPFIX files, most useful for Enterprise IEs; need to
>>> =A0=A0=A0 specify what operations make sense for an IE.
>>> =A0=A0=A0 Support shown for this as a WG item, as for File Format.
>>> =A0=A0=A0 Milestones:=A0 WG LC after IETF 70, to IESG before IETF=A0 71.
>>=20
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element
>> identifiers.
>>=20
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular happe=
n
>> if enterprise specific elements are used. Without this information the
>> collector would treat these elements as if they were of type octet array=
.
>> With this information it may be able to treat them more appropriately.
>>=20
>> The current version of the IPFIX file format draft recommends using this
>> method when IPFIX records are stored.
>>=20
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>=20
>> Thanks,
>>=20
>> =A0=A0=A0=A0 Juergen
>>=20
>>=20
>>=20
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 14:54:28 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE8Tj-000273-Kt; Thu, 26 Jul 2007 14:54:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8Ti-00026y-Nm
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:54:26 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8Ti-0005CT-1q
	for ipfix@ietf.org; Thu, 26 Jul 2007 14:54:26 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0A5A928016A80;
	Thu, 26 Jul 2007 20:54:27 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dnRletM05lXz; Thu, 26 Jul 2007 20:54:26 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id DB94128014C90;
	Thu, 26 Jul 2007 20:54:06 +0200 (CEST)
Received: from 130.129.82.248 ([130.129.82.248]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 26 Jul 2007 18:54:05 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 26 Jul 2007 20:54:03 +0200
From: Juergen Quittek <Quittek@netlab.nec.de>
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>,
	Nevil Brownlee <nevil@auckland.ac.nz>, <ipfix@ietf.org>
Message-ID: <C2CEBA6B.10314%Quittek@netlab.nec.de>
Thread-Topic: requirements:  Extraction, Distribution, Duplication,
	Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8QAAefNig=
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: 
Subject: [IPFIX] Re: requirements:  Extraction, Distribution, Duplication,
 Aggregation , Storage, Self Description, Anonymization, Obfuscation  ...
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Emile,


Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
<emile.stephan@orange-ftgroup.com>:

> HI Juergen and Nevil,
> =20
> Work item #3
> Storing IPFIX records in files requires interoperability only when exchan=
ging
> these files with some one else or some other application. So it's a funct=
ion
> of mediation.

I agree that one may see it this way and it is a very good point to conside=
r
when working on a file format.  However, for the discussions we are having
I would prefer to separate the discussion on the file format work item from
the discussion on the mediator work item.

> Work item #4 points indirectly to a major point concern for telcos: how t=
o map
> a private IE on a standard one?

Now I understand your requirement.
However, as it is currently written, the proposed work does not suggest to
map enterprise-specific IEs to standard ones, but to just assign data types
to unknown (enterprise-specific) IEs. This is a use case different to yours=
.

> Work item #5 defines mediator arch & functions. Then it gives many use ca=
ses
> and requirements.

I fully agree.
=20
> Work items #3, #4 and #5 give many functions a mediator may implement.
> At this step, the functions required for interoperability between mediato=
rs
> are not identified. So please consider the necessity to define the
> interoperability requirements prior to re charter.

Thank you  for this hint.
We will consider it if we charter a work item on mediation.

Thanks,

    Juergen

> Regards
> Emile
> =20
> =20
>> -----Message d'origine-----
>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>> Envoy=E9 : jeudi 26 juillet 2007 08:28
>> =C0 : ipfix@ietf.org
>> Objet : [IPFIX] new work item candidate #4: extended types
>>=20
>> Dear all,
>>=20
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>=20
>>> 4. Extended Types (Elisa Boschi)
>>> =A0=A0=A0 Needed for IPFIX files, most useful for Enterprise IEs; need to
>>> =A0=A0=A0 specify what operations make sense for an IE.
>>> =A0=A0=A0 Support shown for this as a WG item, as for File Format.
>>> =A0=A0=A0 Milestones:=A0 WG LC after IETF 70, to IESG before IETF=A0 71.
>>=20
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element
>> identifiers.
>>=20
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular happe=
n
>> if enterprise specific elements are used. Without this information the
>> collector would treat these elements as if they were of type octet array=
.
>> With this information it may be able to treat them more appropriately.
>>=20
>> The current version of the IPFIX file format draft recommends using this
>> method when IPFIX records are stored.
>>=20
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>=20
>> Thanks,
>>=20
>> =A0=A0=A0=A0 Juergen
>>=20
>>=20
>>=20
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 15:48:21 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9Jr-0002Ks-AA; Thu, 26 Jul 2007 15:48:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9Jq-0002Kn-4z
	for ipfix@ietf.org; Thu, 26 Jul 2007 15:48:18 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9Jo-0007bQ-A7
	for ipfix@ietf.org; Thu, 26 Jul 2007 15:48:18 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 21:48:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jul 2007 21:47:45 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506D@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A8E5BF.7040108@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Telco needs of standard IPFIX middleware I/O
Thread-Index: AcfPsY2hDapUqeiATiecQsNV+1PcNgABSfmg
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8E5BF.7040108@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Paul Aitken" <paitken@cisco.com>
X-OriginalArrivalTime: 26 Jul 2007 19:48:05.0785 (UTC)
	FILETIME=[E26C1090:01C7CFBD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] Telco needs of standard IPFIX middleware I/O
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Paul,

I focus on telco current needs.

There are multiple ways to carry a 'file'. You can pipe it through some =
filtering or aggregation process. In this context Brian draft has great =
value because it is defining I/O for IPFIX middlewares.=20

Regards
Emile


> -----Message d'origine-----
> De=A0: Paul Aitken [mailto:paitken@cisco.com]
> Envoy=E9=A0: jeudi 26 juillet 2007 20:20
> =C0=A0: STEPHAN Emile RD-CORE-LAN
> Cc=A0: Juergen Quittek; Nevil Brownlee; ipfix@ietf.org
> Objet=A0: Re: [IPFIX] requirements: Extraction, Distribution, =
Duplication,
> Aggregation , Storage, Self Description, Anonymization, Obfuscation =
...
>=20
> Emile,
>=20
>=20
> > Work item #3
> >
> > Storing IPFIX records in files requires interoperability only when
> > exchanging these files with some one else or some other application. =
So
> > it's a function of mediation.
>=20
> If I consider a slight change of focus and name to "IP Flow =
Information
> Exchange", then I think an interoperable file format is crucial.
>=20
> It's possible that simple collectors will want to use the file format =
to
> store received flows, and such files may be exchanged by researchers =
for
> analysing data or testing purposes.
>=20
> So while the file format MAY be a function of mediation, I certainly
> don't think it's exclusively a mediation function.
>=20
> Cheers.
> --
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 15:48:21 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9Jr-0002Ks-AA; Thu, 26 Jul 2007 15:48:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9Jq-0002Kn-4z
	for ipfix@ietf.org; Thu, 26 Jul 2007 15:48:18 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9Jo-0007bQ-A7
	for ipfix@ietf.org; Thu, 26 Jul 2007 15:48:18 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 21:48:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jul 2007 21:47:45 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506D@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <46A8E5BF.7040108@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Telco needs of standard IPFIX middleware I/O
Thread-Index: AcfPsY2hDapUqeiATiecQsNV+1PcNgABSfmg
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<C2CE0B83.10238%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<46A8E5BF.7040108@cisco.com>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Paul Aitken" <paitken@cisco.com>
X-OriginalArrivalTime: 26 Jul 2007 19:48:05.0785 (UTC)
	FILETIME=[E26C1090:01C7CFBD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
Subject: [IPFIX] Telco needs of standard IPFIX middleware I/O
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Paul,

I focus on telco current needs.

There are multiple ways to carry a 'file'. You can pipe it through some =
filtering or aggregation process. In this context Brian draft has great =
value because it is defining I/O for IPFIX middlewares.=20

Regards
Emile


> -----Message d'origine-----
> De=A0: Paul Aitken [mailto:paitken@cisco.com]
> Envoy=E9=A0: jeudi 26 juillet 2007 20:20
> =C0=A0: STEPHAN Emile RD-CORE-LAN
> Cc=A0: Juergen Quittek; Nevil Brownlee; ipfix@ietf.org
> Objet=A0: Re: [IPFIX] requirements: Extraction, Distribution, =
Duplication,
> Aggregation , Storage, Self Description, Anonymization, Obfuscation =
...
>=20
> Emile,
>=20
>=20
> > Work item #3
> >
> > Storing IPFIX records in files requires interoperability only when
> > exchanging these files with some one else or some other application. =
So
> > it's a function of mediation.
>=20
> If I consider a slight change of focus and name to "IP Flow =
Information
> Exchange", then I think an interoperable file format is crucial.
>=20
> It's possible that simple collectors will want to use the file format =
to
> store received flows, and such files may be exchanged by researchers =
for
> analysing data or testing purposes.
>=20
> So while the file format MAY be a function of mediation, I certainly
> don't think it's exclusively a mediation function.
>=20
> Cheers.
> --
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 16:28:23 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9wW-00086j-SN; Thu, 26 Jul 2007 16:28:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9wR-00082h-Af
	for ipfix@ietf.org; Thu, 26 Jul 2007 16:28:11 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9wP-0008Nz-R3
	for ipfix@ietf.org; Thu, 26 Jul 2007 16:28:11 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 22:27:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jul 2007 22:27:52 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <C2CEBA6B.10314%Quittek@netlab.nec.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: discussion on telco requirement prior to  re chartering
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8QAAefNigAAe0A8A==
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<C2CEBA6B.10314%Quittek@netlab.nec.de>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Juergen Quittek" <Quittek@netlab.nec.de>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>, <ipfix@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 20:27:47.0816 (UTC)
	FILETIME=[6E392680:01C7CFC3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: 
Subject: [IPFIX] discussion on telco requirement prior to  re chartering
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Juergen and Nevil,

It does not make sense to separate item 3 and 5 because they compliment =
together regarding telco needs of standard I/O for IPFIX middlewares.=20

I don't support item 4 because it introduces a second level of =
datamodeling and because the datatype lists are not extensible.=20


Regards
Emile


> -----Message d'origine-----
> De=A0: Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9=A0: jeudi 26 juillet 2007 20:54
> =C0=A0: STEPHAN Emile RD-CORE-LAN; Nevil Brownlee; ipfix@ietf.org
> Cc=A0: Romascanu, Dan (Dan)
> Objet=A0: Re: requirements: Extraction, Distribution,
> Duplication,Aggregation , Storage, Self Description, Anonymization,
> Obfuscation ...
>=20
> Hi Emile,
>=20
>=20
> Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
> <emile.stephan@orange-ftgroup.com>:
>=20
> > HI Juergen and Nevil,
> >
> > Work item #3
> > Storing IPFIX records in files requires interoperability only when
> exchanging
> > these files with some one else or some other application. So it's a
> function
> > of mediation.
>=20
> I agree that one may see it this way and it is a very good point to
> consider
> when working on a file format.  However, for the discussions we are =
having
> I would prefer to separate the discussion on the file format work item
> from
> the discussion on the mediator work item.
>=20
> > Work item #4 points indirectly to a major point concern for telcos: =
how
> to map
> > a private IE on a standard one?
>=20
> Now I understand your requirement.
> However, as it is currently written, the proposed work does not =
suggest to
> map enterprise-specific IEs to standard ones, but to just assign data
> types
> to unknown (enterprise-specific) IEs. This is a use case different to
> yours.
>=20
> > Work item #5 defines mediator arch & functions. Then it gives many =
use
> cases
> > and requirements.
>=20
> I fully agree.
>=20
> > Work items #3, #4 and #5 give many functions a mediator may =
implement.
> > At this step, the functions required for interoperability between
> mediators
> > are not identified. So please consider the necessity to define the
> > interoperability requirements prior to re charter.
>=20
> Thank you  for this hint.
> We will consider it if we charter a work item on mediation.
>=20
> Thanks,
>=20
>     Juergen
>=20
> > Regards
> > Emile
> >
> >
> >> -----Message d'origine-----
> >> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> >> Envoy=E9 : jeudi 26 juillet 2007 08:28
> >> =C0 : ipfix@ietf.org
> >> Objet : [IPFIX] new work item candidate #4: extended types
> >>
> >> Dear all,
> >>
> >> Candidates #4 to become a new IPFIX work item is described by
> >> draft draft-boschi-ipfix-extended-type-00.txt.
> >>
> >>> 4. Extended Types (Elisa Boschi)
> >>> =A0=A0=A0 Needed for IPFIX files, most useful for Enterprise IEs; =
need to
> >>> =A0=A0=A0 specify what operations make sense for an IE.
> >>> =A0=A0=A0 Support shown for this as a WG item, as for File Format.
> >>> =A0=A0=A0 Milestones:=A0 WG LC after IETF 70, to IESG before =
IETF=A0 71.
> >>
> >> It is a method for assigning data types to unknown IPFIX =
information
> >> elements by using option records that map data types to element
> >> identifiers.
> >>
> >> It can be applied in cases where an IPFIX collector does not know =
the
> >> data type of received information elements. This may in particular
> happen
> >> if enterprise specific elements are used. Without this information =
the
> >> collector would treat these elements as if they were of type octet
> array.
> >> With this information it may be able to treat them more =
appropriately.
> >>
> >> The current version of the IPFIX file format draft recommends using
> this
> >> method when IPFIX records are stored.
> >>
> >> Do you think this is a useful extension of the IPFIX protocol?
> >> Do you think we should accept this as an IPFIX work item?
> >> Please have a look at the draft and send your comments.
> >>
> >> Thanks,
> >>
> >> =A0=A0=A0=A0 Juergen
> >>
> >>
> >>
> >> _______________________________________________
> >> IPFIX mailing list
> >> IPFIX@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ipfix
> >
>=20


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 16:28:23 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IE9wW-00086j-SN; Thu, 26 Jul 2007 16:28:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9wR-00082h-Af
	for ipfix@ietf.org; Thu, 26 Jul 2007 16:28:11 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9wP-0008Nz-R3
	for ipfix@ietf.org; Thu, 26 Jul 2007 16:28:11 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 22:27:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jul 2007 22:27:52 +0200
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <C2CEBA6B.10314%Quittek@netlab.nec.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: discussion on telco requirement prior to  re chartering
Thread-Index: AcfPThT+U45yJDtBEdytZQAWy4a5GwAScO8QAAefNigAAe0A8A==
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>
	<C2CEBA6B.10314%Quittek@netlab.nec.de>
From: "STEPHAN Emile RD-CORE-LAN" <emile.stephan@orange-ftgroup.com>
To: "Juergen Quittek" <Quittek@netlab.nec.de>,
	"Nevil Brownlee" <nevil@auckland.ac.nz>, <ipfix@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 20:27:47.0816 (UTC)
	FILETIME=[6E392680:01C7CFC3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: 
Subject: [IPFIX] discussion on telco requirement prior to  re chartering
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Juergen and Nevil,

It does not make sense to separate item 3 and 5 because they compliment =
together regarding telco needs of standard I/O for IPFIX middlewares.=20

I don't support item 4 because it introduces a second level of =
datamodeling and because the datatype lists are not extensible.=20


Regards
Emile


> -----Message d'origine-----
> De=A0: Juergen Quittek [mailto:Quittek@netlab.nec.de]
> Envoy=E9=A0: jeudi 26 juillet 2007 20:54
> =C0=A0: STEPHAN Emile RD-CORE-LAN; Nevil Brownlee; ipfix@ietf.org
> Cc=A0: Romascanu, Dan (Dan)
> Objet=A0: Re: requirements: Extraction, Distribution,
> Duplication,Aggregation , Storage, Self Description, Anonymization,
> Obfuscation ...
>=20
> Hi Emile,
>=20
>=20
> Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
> <emile.stephan@orange-ftgroup.com>:
>=20
> > HI Juergen and Nevil,
> >
> > Work item #3
> > Storing IPFIX records in files requires interoperability only when
> exchanging
> > these files with some one else or some other application. So it's a
> function
> > of mediation.
>=20
> I agree that one may see it this way and it is a very good point to
> consider
> when working on a file format.  However, for the discussions we are =
having
> I would prefer to separate the discussion on the file format work item
> from
> the discussion on the mediator work item.
>=20
> > Work item #4 points indirectly to a major point concern for telcos: =
how
> to map
> > a private IE on a standard one?
>=20
> Now I understand your requirement.
> However, as it is currently written, the proposed work does not =
suggest to
> map enterprise-specific IEs to standard ones, but to just assign data
> types
> to unknown (enterprise-specific) IEs. This is a use case different to
> yours.
>=20
> > Work item #5 defines mediator arch & functions. Then it gives many =
use
> cases
> > and requirements.
>=20
> I fully agree.
>=20
> > Work items #3, #4 and #5 give many functions a mediator may =
implement.
> > At this step, the functions required for interoperability between
> mediators
> > are not identified. So please consider the necessity to define the
> > interoperability requirements prior to re charter.
>=20
> Thank you  for this hint.
> We will consider it if we charter a work item on mediation.
>=20
> Thanks,
>=20
>     Juergen
>=20
> > Regards
> > Emile
> >
> >
> >> -----Message d'origine-----
> >> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
> >> Envoy=E9 : jeudi 26 juillet 2007 08:28
> >> =C0 : ipfix@ietf.org
> >> Objet : [IPFIX] new work item candidate #4: extended types
> >>
> >> Dear all,
> >>
> >> Candidates #4 to become a new IPFIX work item is described by
> >> draft draft-boschi-ipfix-extended-type-00.txt.
> >>
> >>> 4. Extended Types (Elisa Boschi)
> >>> =A0=A0=A0 Needed for IPFIX files, most useful for Enterprise IEs; =
need to
> >>> =A0=A0=A0 specify what operations make sense for an IE.
> >>> =A0=A0=A0 Support shown for this as a WG item, as for File Format.
> >>> =A0=A0=A0 Milestones:=A0 WG LC after IETF 70, to IESG before =
IETF=A0 71.
> >>
> >> It is a method for assigning data types to unknown IPFIX =
information
> >> elements by using option records that map data types to element
> >> identifiers.
> >>
> >> It can be applied in cases where an IPFIX collector does not know =
the
> >> data type of received information elements. This may in particular
> happen
> >> if enterprise specific elements are used. Without this information =
the
> >> collector would treat these elements as if they were of type octet
> array.
> >> With this information it may be able to treat them more =
appropriately.
> >>
> >> The current version of the IPFIX file format draft recommends using
> this
> >> method when IPFIX records are stored.
> >>
> >> Do you think this is a useful extension of the IPFIX protocol?
> >> Do you think we should accept this as an IPFIX work item?
> >> Please have a look at the draft and send your comments.
> >>
> >> Thanks,
> >>
> >> =A0=A0=A0=A0 Juergen
> >>
> >>
> >>
> >> _______________________________________________
> >> IPFIX mailing list
> >> IPFIX@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ipfix
> >
>=20


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From gejarrcvek@arrc.net Thu Jul 26 17:34:32 2007
Return-path: <gejarrcvek@arrc.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEAye-0004C6-03; Thu, 26 Jul 2007 17:34:32 -0400
Received: from [88.227.93.83] (helo=[88.227.93.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IEAyd-0000Bl-7Z; Thu, 26 Jul 2007 17:34:31 -0400
Received: from [88.227.93.83] by mail.usave.net; Thu, 26 Jul 2007 21:34:31 -0200
Date:	Thu, 26 Jul 2007 21:34:31 -0200
From:	"Curt Bloom" <gejarrcvek@arrc.net>
X-Mailer: The Bat! (v3.71.01) Professional
Reply-To: gejarrcvek@arrc.net
X-Priority: 3 (Normal)
Message-ID: <819568330.26135762014117@arrc.net>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------3D3DA21A0C5136"
X-Spam-Score: 0.6 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------3D3DA21A0C5136
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

Our Warmest Greetings!!! 
Particular offer for you Our Dear Clients!!!
Only these 5 days for our byers unimaginable offer!!! 
On all medicines you need!!!   
Fill your life with colors of delight!!!  
http://gohour.cn/ 

Truly Yours, 
On-line association of pharmacists
------------3D3DA21A0C5136
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Our Warmest Greetings!!! </em></font><br>
Particular offer for you <font color="#FF0000"><em>Our Dear Clients!!!</em></font><br>
Only these <font color="#FF0000"><em>5 days</em></font> for our byers unimaginable offer!!! <br>
On all medicines you need!!! </strong> <strong><br><br> 
<a href="http://gohour.cn/" target="_blank"><em>Fill your life with colors of delight!!! </em></a></strong> 
<font color="#D9EDFF">http://gohour.cn/</font><br><br> 

<strong>Truly Yours,<br> 
<em>On-line association of pharmacists</em></strong></p>

</BODY></HTML>
------------3D3DA21A0C5136--




From ipfix-bounces@ietf.org Thu Jul 26 17:42:18 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEB62-0002wK-5L; Thu, 26 Jul 2007 17:42:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEB60-0002nR-JU
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:42:08 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEB5z-0000Kn-SS
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:42:08 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 23:42:05 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAOixqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149115846:sNHT28837402"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QLg5Nx016767
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 23:42:05 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QLg4kt027617
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 21:42:04 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id WAA10065
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 22:42:03 +0100 (BST)
Message-ID: <46A9152E.9010807@cisco.com>
Date: Thu, 26 Jul 2007 22:42:06 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4049; t=1185486125;
	x=1186350125; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20IPFIX-PROTO=3A=20template=20reuse |Sender:=20;
	bh=QI985jLX9AdHWshYbq90YYxIgoBfqe7B/fSDdNRXvz8=;
	b=JxZlXN8WJnkmAJzkuFjUzihGcWh0AiR2FtVJf0MhqAjTG/9A6IxBYEM1tFAxoujsjPoAzvMT
	oPM+Qup75NpdZpLnm/kHY/zIFSNhM0sFeErj5Wa6KUh6oYYLuqc3ZCeL;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Subject: [IPFIX] IPFIX-PROTO: template reuse
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

While working on the IPFIX-TESTING draft, I realised that IPFIX-PROTO
doesn't specify very clearly what to do if a Template ID is reused
inside the template expiry time (ie, same Template ID, different
template definition) while TCP transport is being used.


With SCTP and TCP transports, we expect Templates only to be sent once.
Section 8 (Template Management / SCTP) and 10.4.2.2 (Templates
Management / TCP) of IPFIX-PROTO say:

    Before
    reusing a Template ID, the Template MUST be deleted.  In order to
    delete an allocated Template, the Template is withdrawn through the
    use of a Template Withdraw Message.


And in section 9 (The Collecting Process's Side):

    Template Sets and Option Template Sets are only sent once.  The
    Collecting Process MUST store the Template Record information for
    the duration of the association so that it can interpret the
    corresponding Data Records that are received in subsequent Data
    Sets.


Which is followed by a clear statement of what to do for SCTP:

    Template IDs are unique per SCTP association and per Observation
    Domain.  If the Collecting Process receives a Template which has
    already been received but which has not previously been withdrawn
    (i.e. a Template Record from the same Exporter Observation Domain
    with the same Template ID received on the SCTP association), then
    the Collecting Process MUST shutdown the association.


With UDP transport, we can expect a Template to be refreshed many times.
eg, it's possible that the Template changes because the Exporting
Process restarted. So we have to allow this.

And with TCP... well, we don't say at all.

We can't even suppose to follow the malformed message rule:

    If the Collecting Process receives a malformed IPFIX Message, it
    MUST reset the TCP connection, discard the IPFIX Message, and SHOULD
    log the error.

- because a Template reuse won't be a malformed Message itself; it'll be
a valid Message. It's only because the Collector has previously received
a different definition for the same Template ID that there's any problem
(ie, the problem is due to Collector state).


Looking at section 10 and comparing the SCTP, UDP and TCP sub-sections, 
it's clear that the TCP "Collecting Process" section is missing.

The SCTP Collecting Process section (10.2.5) simply says:

    When the transport protocol is SCTP, the default Collector
    processing described in Section 9 is used.


I would like to see a new TCP / Collecting Process section (probably 
just at the end of the existing TCP section, ie new section 10.4.3).

Without wanting to reproduce section 9 entirely, it might say:

    When the transport protocol is TCP the default Collector processing
    described in Section 9 is used, with "SCTP association" being
    substituted by "TCP connection".


When I read section 9 with that substitution, it makes sense - except 
for a couple of places where it mentions SCTP stream zero, which I hope 
will soon be fixed too.


This should be followed by a TCP / Failover section similar to the SCTP 
and UDP sections (10.2.6 and 10.3.8).

eg, it may read:

    If the Collecting Process does not acknowledge the attempt by the
    Exporting Process to establish an association the Exporting Process
    should retry using an exponential backoff.  The
    Exporter MAY log an alarm if the time to establish the association
    exceeds a specified threshold, configurable on the Exporter.

    If Collecting Process failover is supported by the Exporting Process
    a second TCP connection MAY be opened in advance.


- though we may not want to limit to "a second" (neither here, nor in 
the SCTP Failover section, 10.2.6). We may wish to say "additional..." 
instead.


Finally, a very minor correction: 10.4.2.2 "Templates Management" should 
be singular, just like 10.2.4.4 and 10.3.6.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 17:42:18 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEB62-0002wK-5L; Thu, 26 Jul 2007 17:42:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEB60-0002nR-JU
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:42:08 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEB5z-0000Kn-SS
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:42:08 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 26 Jul 2007 23:42:05 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAOixqEaQ/uCKh2dsb2JhbACPaAEBAQgKJw
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149115846:sNHT28837402"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QLg5Nx016767
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 23:42:05 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QLg4kt027617
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 21:42:04 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id WAA10065
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 22:42:03 +0100 (BST)
Message-ID: <46A9152E.9010807@cisco.com>
Date: Thu, 26 Jul 2007 22:42:06 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: ipfix@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4049; t=1185486125;
	x=1186350125; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20IPFIX-PROTO=3A=20template=20reuse |Sender:=20;
	bh=QI985jLX9AdHWshYbq90YYxIgoBfqe7B/fSDdNRXvz8=;
	b=JxZlXN8WJnkmAJzkuFjUzihGcWh0AiR2FtVJf0MhqAjTG/9A6IxBYEM1tFAxoujsjPoAzvMT
	oPM+Qup75NpdZpLnm/kHY/zIFSNhM0sFeErj5Wa6KUh6oYYLuqc3ZCeL;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Subject: [IPFIX] IPFIX-PROTO: template reuse
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Dear all,

While working on the IPFIX-TESTING draft, I realised that IPFIX-PROTO
doesn't specify very clearly what to do if a Template ID is reused
inside the template expiry time (ie, same Template ID, different
template definition) while TCP transport is being used.


With SCTP and TCP transports, we expect Templates only to be sent once.
Section 8 (Template Management / SCTP) and 10.4.2.2 (Templates
Management / TCP) of IPFIX-PROTO say:

    Before
    reusing a Template ID, the Template MUST be deleted.  In order to
    delete an allocated Template, the Template is withdrawn through the
    use of a Template Withdraw Message.


And in section 9 (The Collecting Process's Side):

    Template Sets and Option Template Sets are only sent once.  The
    Collecting Process MUST store the Template Record information for
    the duration of the association so that it can interpret the
    corresponding Data Records that are received in subsequent Data
    Sets.


Which is followed by a clear statement of what to do for SCTP:

    Template IDs are unique per SCTP association and per Observation
    Domain.  If the Collecting Process receives a Template which has
    already been received but which has not previously been withdrawn
    (i.e. a Template Record from the same Exporter Observation Domain
    with the same Template ID received on the SCTP association), then
    the Collecting Process MUST shutdown the association.


With UDP transport, we can expect a Template to be refreshed many times.
eg, it's possible that the Template changes because the Exporting
Process restarted. So we have to allow this.

And with TCP... well, we don't say at all.

We can't even suppose to follow the malformed message rule:

    If the Collecting Process receives a malformed IPFIX Message, it
    MUST reset the TCP connection, discard the IPFIX Message, and SHOULD
    log the error.

- because a Template reuse won't be a malformed Message itself; it'll be
a valid Message. It's only because the Collector has previously received
a different definition for the same Template ID that there's any problem
(ie, the problem is due to Collector state).


Looking at section 10 and comparing the SCTP, UDP and TCP sub-sections, 
it's clear that the TCP "Collecting Process" section is missing.

The SCTP Collecting Process section (10.2.5) simply says:

    When the transport protocol is SCTP, the default Collector
    processing described in Section 9 is used.


I would like to see a new TCP / Collecting Process section (probably 
just at the end of the existing TCP section, ie new section 10.4.3).

Without wanting to reproduce section 9 entirely, it might say:

    When the transport protocol is TCP the default Collector processing
    described in Section 9 is used, with "SCTP association" being
    substituted by "TCP connection".


When I read section 9 with that substitution, it makes sense - except 
for a couple of places where it mentions SCTP stream zero, which I hope 
will soon be fixed too.


This should be followed by a TCP / Failover section similar to the SCTP 
and UDP sections (10.2.6 and 10.3.8).

eg, it may read:

    If the Collecting Process does not acknowledge the attempt by the
    Exporting Process to establish an association the Exporting Process
    should retry using an exponential backoff.  The
    Exporter MAY log an alarm if the time to establish the association
    exceeds a specified threshold, configurable on the Exporter.

    If Collecting Process failover is supported by the Exporting Process
    a second TCP connection MAY be opened in advance.


- though we may not want to limit to "a second" (neither here, nor in 
the SCTP Failover section, 10.2.6). We may wish to say "additional..." 
instead.


Finally, a very minor correction: 10.4.2.2 "Templates Management" should 
be singular, just like 10.2.4.4 and 10.3.6.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 17:51:10 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBEj-0001Hf-00; Thu, 26 Jul 2007 17:51:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBEh-0001Ha-G2
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:07 -0400
Received: from beniaminus.red.cert.org ([192.88.209.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBEg-0001Rd-Tc
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:07 -0400
Received: from beniaminus.red.cert.org (localhost [127.0.0.1])
	by beniaminus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6QLowEh008118 for <ipfix@ietf.org>; Thu, 26 Jul 2007 17:51:03 -0400
Received: (from defang@localhost)
	by beniaminus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6QLn14i007955
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 17:49:01 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by beniaminus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6QLmvTS007947;
	Thu, 26 Jul 2007 17:49:01 -0400 (EDT)
Received: from [130.129.18.248] (vpn-10-25-4-9.remote.cert.org [10.25.4.9])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6QLmvS3015571; Thu, 26 Jul 2007 17:48:57 -0400
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] *Proposed* new work items, take two
Date: Thu, 26 Jul 2007 16:48:55 -0500
To: Nevil Brownlee <nevil@auckland.ac.nz>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Nevil and all,

Comments inline on the proposed work items below...

Cheers,

Brian

On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:

>
> Hi again all:
>
> Here's a slightly improved, slightly clearer, version of my earlier  
> posting.
>
> Cheers, Nevil
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>
> IPFIX: Proposal for new work
>       Based on discussion at IETF 69, Chicago
>
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
>
> 0. Remove SCTP stream restrictions in Protocol Document.
>   Agreed: WG needs to do this, as soon as possible.
>   Procedure:
>    - Call the protocol draft out of the RFC EDitor Queue
>    - Make changes (only those needed for SCTP Stream use),
>      issue a revised draft
>    - Run a short (1 week) WG last Call
>    - Run a short (2 weeks, it's a Standards Track draft) IETF Last  
> Call
>    - Send draft back to RFC for evalkuatio
>    - IESG sends it back to the RFC Editor Queue
>   Assuming that all goes well, we estimate all that will take
>   6~8 weeks.  By then we expect the PSAMP Info draft to have
>   progressed so that it will be in the RFC Editor Queue too!
>    - Corresponding changes to Implementation Guidelines and
>      Testing drafts will also be needed, they will be made
>      in the next revisions of both these drafts
>
> 1. Configuration Data Model (Gerhard Muenz)
>   Agreed: Important to WG, not clear what protocol would be needed.
>   Proposal: (a) Develop Configuration Info Model as a WG item,
>       in English (and also an XML version) - Standards Track RFC.
>       (b) Consider what protocol would be best for IPFIX  
> Configuration.
>           Requirements RFC?      Milestones: WG LC before IETF 71
>
> 2. SCTP Per-Stream Draft (Benoit Claise)
>   Agreed: Needs to be explored, as a possible protocol option.
>   Procedure: Make this a WG item, as Experimental RFC.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

It's unclear to me that, after the stream restriction change in point  
0. above, this should be Experimental as opposed to Informational...  
Per 2026, Experimental RFCs are intended as an archival record of a  
research work. Unless the primary intention is to change this draft  
to be a description and evaluation of the performance benefits of  
this (and potentially other) stream selection methods, it appears  
very much to be the description of an export method (which will be in  
line with the protocol after the stream restriction change in point  
0. above) that has potential performance and other benefits within a  
defined set of use cases, very much like the recently-approved  
(Informational) Reducing Redundancy draft.

> 3. File Format (Brian Trammel)
>   Agreed: WG item, as soon as possible.
>   Procedure: Make this a WG item, as an Informational RFC.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

As per Dan Romascanu's comments on the File Format during the IPFIX  
meeting in Dallas or Montreal (I do not recall which at the moment),  
and, indeed, per the Intended Status on the present revision of the  
document, I believe the File Format draft should be considered as a  
Standards Track RFC. The primary motivation of the draft is to  
promote the interoperability of files used in flow measurement  
infrastructures, to provide in a way a "fourth transport  
protocol" (filesystems and anything that can access filesystems) for  
IPFIX Messages.

> 4. Extended Types (Elisa Boschi)
>   Needed for IPFIX files, most useful for Enterprise IEs; need to
>   specify what operations make sense for an IE.
>   Support shown for this as a WG item, as for File Format.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

Another point to reiterate here - the File Format draft includes a  
normative reference to this draft, as it uses the Options Template  
defined there to meet the self-description requirement when a file  
contains Enterprise-Specific Information Elements. The two should be  
considered for adoption together. The primary reason the extended  
type draft was created (from text originally in the file draft) was  
that we (the file draft authors) thought that the method might be  
useful on the wire, and we received feedback during and after the  
meeting in Prague that we were not the only ones who thought so.

Regards,

Brian


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 17:51:10 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBEj-0001Hf-00; Thu, 26 Jul 2007 17:51:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBEh-0001Ha-G2
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:07 -0400
Received: from beniaminus.red.cert.org ([192.88.209.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBEg-0001Rd-Tc
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:07 -0400
Received: from beniaminus.red.cert.org (localhost [127.0.0.1])
	by beniaminus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6QLowEh008118 for <ipfix@ietf.org>; Thu, 26 Jul 2007 17:51:03 -0400
Received: (from defang@localhost)
	by beniaminus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6QLn14i007955
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 17:49:01 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by beniaminus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6QLmvTS007947;
	Thu, 26 Jul 2007 17:49:01 -0400 (EDT)
Received: from [130.129.18.248] (vpn-10-25-4-9.remote.cert.org [10.25.4.9])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6QLmvS3015571; Thu, 26 Jul 2007 17:48:57 -0400
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] *Proposed* new work items, take two
Date: Thu, 26 Jul 2007 16:48:55 -0500
To: Nevil Brownlee <nevil@auckland.ac.nz>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Nevil and all,

Comments inline on the proposed work items below...

Cheers,

Brian

On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:

>
> Hi again all:
>
> Here's a slightly improved, slightly clearer, version of my earlier  
> posting.
>
> Cheers, Nevil
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>
> IPFIX: Proposal for new work
>       Based on discussion at IETF 69, Chicago
>
> For IPFIX mailing list, we suggest that items 1-6
> (above the --- line) be adopted as new WG work items.
> Please comment by 6 Aug 07 <<<<
> Also, we need reviewers; please fill in and email back the
> questionnaire form below!!
>
> 0. Remove SCTP stream restrictions in Protocol Document.
>   Agreed: WG needs to do this, as soon as possible.
>   Procedure:
>    - Call the protocol draft out of the RFC EDitor Queue
>    - Make changes (only those needed for SCTP Stream use),
>      issue a revised draft
>    - Run a short (1 week) WG last Call
>    - Run a short (2 weeks, it's a Standards Track draft) IETF Last  
> Call
>    - Send draft back to RFC for evalkuatio
>    - IESG sends it back to the RFC Editor Queue
>   Assuming that all goes well, we estimate all that will take
>   6~8 weeks.  By then we expect the PSAMP Info draft to have
>   progressed so that it will be in the RFC Editor Queue too!
>    - Corresponding changes to Implementation Guidelines and
>      Testing drafts will also be needed, they will be made
>      in the next revisions of both these drafts
>
> 1. Configuration Data Model (Gerhard Muenz)
>   Agreed: Important to WG, not clear what protocol would be needed.
>   Proposal: (a) Develop Configuration Info Model as a WG item,
>       in English (and also an XML version) - Standards Track RFC.
>       (b) Consider what protocol would be best for IPFIX  
> Configuration.
>           Requirements RFC?      Milestones: WG LC before IETF 71
>
> 2. SCTP Per-Stream Draft (Benoit Claise)
>   Agreed: Needs to be explored, as a possible protocol option.
>   Procedure: Make this a WG item, as Experimental RFC.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

It's unclear to me that, after the stream restriction change in point  
0. above, this should be Experimental as opposed to Informational...  
Per 2026, Experimental RFCs are intended as an archival record of a  
research work. Unless the primary intention is to change this draft  
to be a description and evaluation of the performance benefits of  
this (and potentially other) stream selection methods, it appears  
very much to be the description of an export method (which will be in  
line with the protocol after the stream restriction change in point  
0. above) that has potential performance and other benefits within a  
defined set of use cases, very much like the recently-approved  
(Informational) Reducing Redundancy draft.

> 3. File Format (Brian Trammel)
>   Agreed: WG item, as soon as possible.
>   Procedure: Make this a WG item, as an Informational RFC.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

As per Dan Romascanu's comments on the File Format during the IPFIX  
meeting in Dallas or Montreal (I do not recall which at the moment),  
and, indeed, per the Intended Status on the present revision of the  
document, I believe the File Format draft should be considered as a  
Standards Track RFC. The primary motivation of the draft is to  
promote the interoperability of files used in flow measurement  
infrastructures, to provide in a way a "fourth transport  
protocol" (filesystems and anything that can access filesystems) for  
IPFIX Messages.

> 4. Extended Types (Elisa Boschi)
>   Needed for IPFIX files, most useful for Enterprise IEs; need to
>   specify what operations make sense for an IE.
>   Support shown for this as a WG item, as for File Format.
>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.

Another point to reiterate here - the File Format draft includes a  
normative reference to this draft, as it uses the Options Template  
defined there to meet the self-description requirement when a file  
contains Enterprise-Specific Information Elements. The two should be  
considered for adoption together. The primary reason the extended  
type draft was created (from text originally in the file draft) was  
that we (the file draft authors) thought that the method might be  
useful on the wire, and we received feedback during and after the  
meeting in Prague that we were not the only ones who thought so.

Regards,

Brian


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 17:51:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBEz-0001XP-BZ; Thu, 26 Jul 2007 17:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBEy-0001XK-Ib
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:24 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBEw-0001Rl-OG
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:24 -0400
X-ASG-Debug-ID: 1185486681-3c1f00320000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1185486681
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 7EFE38CAE1
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 22:51:21 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B46a9175d0000>; Thu, 26 Jul 2007 21:51:25 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 22:51:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: Re: [IPFIX] new work item candidate #4: extended types
Subject: Re: [IPFIX] new work item candidate #4: extended types
Date: Thu, 26 Jul 2007 22:51:21 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] new work item candidate #4: extended types
Thread-Index: AcfPzxo95ZI1Uv8xRJ++1i8BMypyEw==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <muenz@informatik.uni-tuebingen.de>
X-OriginalArrivalTime: 26 Jul 2007 21:51:20.0911 (UTC)
	FILETIME=[1A42BDF0:01C7CFCF]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1437712723=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1437712723==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFCF.1A50B147"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFCF.1A50B147
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Gerhard,

>=20
> On the one hand, it's a nice idea to have some IEs which allow
> describing the type and semantic of other IEs. On the other hand, my
> impression is that the usefulness is very restricted and not as broad a=
s
> claimed in the introduction of the draft:
>=20
>    ... Having to do some sort of tool-specific
>    configuration (or code modification) on every tool just to tell whic=
h
>    type each used Information Element has is a huge amount of work for
>    users and implementors of enterprise-specific Information Elements.
>    Many tools in fact only need to know the field's data type to work o=
n
>    them. ...
>

One of the use cases we have in mind here would be a collaborative measur=
ement infrastructure where each exporter is implemented by a different ve=
ndor and exports slightly different enterprise IEs. In that case, having =
type information in the message stream allows ad-hoc preliminary analysis=
=20of the enterprise specific data.=20

Our claim that many tools only need to know the field's data types to wor=
k on them applies...so the usefulness of the draft is not too "restricted=
"=20
=20
> In my opinion, any deeper analysis and processing of metering data
> requires knowledge about the semantic. Just knowing the data type may b=
e
> enough to display values correctly. Considering
> informationElementSemanticType, you might also know if the calculation
> of statistical properties (max, min, mean, variance etc.) makes sense o=
r
> not. But any further analysis would probably require more semantical
> knowledge. That's why I assume that, in practice, analyzing and
> processing enterprise-specific data will mostly be performed with
> specialized analysis tools that have been implemented for this specific=

> purpose. And for these tools, there is no need to export the IE informa=
tion.
>=20

...but those ad hoc tools won't be reusable, unless tool specific configu=
ration or code modification are done for any used Enterprise Specific IE.=
=20And what about if the tools are not updated?=20

A real life example that this draft would solve is mentioned in:
http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html

...which also contains the motivation for this draft.

Regards,
Elisa


>=20
> Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>
>>> 4. Extended Types (Elisa Boschi)
>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>    specify what operations make sense for an IE.
>>>    Support shown for this as a WG item, as for File Format.
>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element identi=
fiers.
>>
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular hap=
pen
>> if enterprise specific elements are used. Without this information the=

>> collector would treat these elements as if they were of type octet arr=
ay.
>> With this information it may be able to treat them more appropriately.=

>>
>> The current version of the IPFIX file format draft recommends using th=
is
>> method when IPFIX records are stored.
>>
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>
>> Thanks,
>>
>>     Juergen
>>
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20

*************************************************************************=
*************************=20
E-mail Confidentiality Notice and Disclaimer.=20

This email and any files transmitted with it are confidential and are int=
ended solely for the use=20
of the individual or entity to which they are addressed. Access to this e=
-mail by anyone else is=20
unauthorised. If you are not the intended recipient, any disclosure, copy=
ing, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-m=
ail messages are not=20
necessarily secure. Hitachi does not accept responsibility for any change=
s made to this message=20
after it was sent.=20

Please note that Hitachi checks outgoing e-mail messages for the presence=
=20of computer viruses.=20
*************************************************************************=
*************************

------_=_NextPart_001_01C7CFCF.1A50B147
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7235.2=
">
<TITLE>Re: [IPFIX] new work item candidate #4: extended types</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Gerhard,<BR>
<BR>
&gt;<BR>
&gt; On the one hand, it's a nice idea to have some IEs which allow<BR>
&gt; describing the type and semantic of other IEs. On the other hand, my=
<BR>
&gt; impression is that the usefulness is very restricted and not as broa=
d as<BR>
&gt; claimed in the introduction of the draft:<BR>
&gt;<BR>
&gt;&nbsp;&nbsp;&nbsp; ... Having to do some sort of tool-specific<BR>
&gt;&nbsp;&nbsp;&nbsp; configuration (or code modification) on every tool=
=20just to tell which<BR>
&gt;&nbsp;&nbsp;&nbsp; type each used Information Element has is a huge a=
mount of work for<BR>
&gt;&nbsp;&nbsp;&nbsp; users and implementors of enterprise-specific Info=
rmation Elements.<BR>
&gt;&nbsp;&nbsp;&nbsp; Many tools in fact only need to know the field's d=
ata type to work on<BR>
&gt;&nbsp;&nbsp;&nbsp; them. ...<BR>
&gt;<BR>
<BR>
One of the use cases we have in mind here would be a collaborative measur=
ement infrastructure where each exporter is implemented by a different ve=
ndor and exports slightly different enterprise IEs. In that case, having =
type information in the message stream allows ad-hoc preliminary analysis=
=20of the enterprise specific data.<BR>
<BR>
Our claim that many tools only need to know the field's data types to wor=
k on them applies...so the usefulness of the draft is not too &quot;restr=
icted&quot;<BR>
<BR>
&gt; In my opinion, any deeper analysis and processing of metering data<B=
R>
&gt; requires knowledge about the semantic. Just knowing the data type ma=
y be<BR>
&gt; enough to display values correctly. Considering<BR>
&gt; informationElementSemanticType, you might also know if the calculati=
on<BR>
&gt; of statistical properties (max, min, mean, variance etc.) makes sens=
e or<BR>
&gt; not. But any further analysis would probably require more semantical=
<BR>
&gt; knowledge. That's why I assume that, in practice, analyzing and<BR>
&gt; processing enterprise-specific data will mostly be performed with<BR=
>
&gt; specialized analysis tools that have been implemented for this speci=
fic<BR>
&gt; purpose. And for these tools, there is no need to export the IE info=
rmation.<BR>
&gt;<BR>
<BR>
...but those ad hoc tools won't be reusable, unless tool specific configu=
ration or code modification are done for any used Enterprise Specific IE.=
=20And what about if the tools are not updated?<BR>
<BR>
A real life example that this draft would solve is mentioned in:<BR>
<A HREF=3D"http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.h=
tml">http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html</A=
><BR>
<BR>
...which also contains the motivation for this draft.<BR>
<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
&gt;<BR>
&gt; Juergen Quittek wrote:<BR>
&gt;&gt; Dear all,<BR>
&gt;&gt;<BR>
&gt;&gt; Candidates #4 to become a new IPFIX work item is described by<BR=
>
&gt;&gt; draft draft-boschi-ipfix-extended-type-00.txt.<BR>
&gt;&gt;<BR>
&gt;&gt;&gt; 4. Extended Types (Elisa Boschi)<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Needed for IPFIX files, most useful for En=
terprise IEs; need to<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; specify what operations make sense for an =
IE.<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Support shown for this as a WG item, as fo=
r File Format.<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Milestones:&nbsp; WG LC after IETF 70, to =
IESG before IETF&nbsp; 71.<BR>
&gt;&gt; It is a method for assigning data types to unknown IPFIX informa=
tion<BR>
&gt;&gt; elements by using option records that map data types to element =
identifiers.<BR>
&gt;&gt;<BR>
&gt;&gt; It can be applied in cases where an IPFIX collector does not kno=
w the<BR>
&gt;&gt; data type of received information elements. This may in particul=
ar happen<BR>
&gt;&gt; if enterprise specific elements are used. Without this informati=
on the<BR>
&gt;&gt; collector would treat these elements as if they were of type oct=
et array.<BR>
&gt;&gt; With this information it may be able to treat them more appropri=
ately.<BR>
&gt;&gt;<BR>
&gt;&gt; The current version of the IPFIX file format draft recommends us=
ing this<BR>
&gt;&gt; method when IPFIX records are stored.<BR>
&gt;&gt;<BR>
&gt;&gt; Do you think this is a useful extension of the IPFIX protocol?<B=
R>
&gt;&gt; Do you think we should accept this as an IPFIX work item?<BR>
&gt;&gt; Please have a look at the draft and send your comments.<BR>
&gt;&gt;<BR>
&gt;&gt; Thanks,<BR>
&gt;&gt;<BR>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Juergen<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt; _______________________________________________<BR>
&gt;&gt; IPFIX mailing list<BR>
&gt;&gt; IPFIX@ietf.org<BR>
&gt;&gt; <A HREF=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https:/=
/www1.ietf.org/mailman/listinfo/ipfix</A><BR>
&gt;<BR>
</FONT>
</P>


<P><FONT face=3D"Courier New"=20
size=3D2>****************************************************************=
**********************************<BR></FONT><FONT=20
face=3D"Courier New" size=3D2>E-mail Confidentiality Notice and Disclaime=
r.=20
</FONT></P>
<P><FONT face=3D"Courier New" size=3D2>This email and any files transmitt=
ed with it=20
are confidential and are intended solely for the use of the individual or=
=20entity=20
to which they are addressed. Access to this e-mail by anyone else is=20
unauthorised. If you are not the intended recipient,any disclosure, copyi=
ng,=20
distribution or any action taken or omitted to be taken in reliance on it=
, is=20
prohibited. <BR>E-mail messages are not necessarily secure.Hitachi does n=
ot=20
accept responsibility for any changes made to this message after it was=20
sent.<BR><BR>Please note that Hitachi checks outgoing e-mail&nbsp;message=
s for=20
the presence of computer viruses.=20
<BR>*********************************************************************=
*****************************</FONT></P>
</BODY>
</HTML>

------_=_NextPart_001_01C7CFCF.1A50B147--


--===============1437712723==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1437712723==--




From ipfix-bounces@ietf.org Thu Jul 26 17:51:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBEz-0001XP-BZ; Thu, 26 Jul 2007 17:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBEy-0001XK-Ib
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:24 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBEw-0001Rl-OG
	for ipfix@ietf.org; Thu, 26 Jul 2007 17:51:24 -0400
X-ASG-Debug-ID: 1185486681-3c1f00320000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1185486681
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 7EFE38CAE1
	for <ipfix@ietf.org>; Thu, 26 Jul 2007 22:51:21 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B46a9175d0000>; Thu, 26 Jul 2007 21:51:25 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 22:51:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: Re: [IPFIX] new work item candidate #4: extended types
Subject: Re: [IPFIX] new work item candidate #4: extended types
Date: Thu, 26 Jul 2007 22:51:21 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] new work item candidate #4: extended types
Thread-Index: AcfPzxo95ZI1Uv8xRJ++1i8BMypyEw==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <muenz@informatik.uni-tuebingen.de>
X-OriginalArrivalTime: 26 Jul 2007 21:51:20.0911 (UTC)
	FILETIME=[1A42BDF0:01C7CFCF]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1437712723=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1437712723==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CFCF.1A50B147"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CFCF.1A50B147
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Gerhard,

>=20
> On the one hand, it's a nice idea to have some IEs which allow
> describing the type and semantic of other IEs. On the other hand, my
> impression is that the usefulness is very restricted and not as broad a=
s
> claimed in the introduction of the draft:
>=20
>    ... Having to do some sort of tool-specific
>    configuration (or code modification) on every tool just to tell whic=
h
>    type each used Information Element has is a huge amount of work for
>    users and implementors of enterprise-specific Information Elements.
>    Many tools in fact only need to know the field's data type to work o=
n
>    them. ...
>

One of the use cases we have in mind here would be a collaborative measur=
ement infrastructure where each exporter is implemented by a different ve=
ndor and exports slightly different enterprise IEs. In that case, having =
type information in the message stream allows ad-hoc preliminary analysis=
=20of the enterprise specific data.=20

Our claim that many tools only need to know the field's data types to wor=
k on them applies...so the usefulness of the draft is not too "restricted=
"=20
=20
> In my opinion, any deeper analysis and processing of metering data
> requires knowledge about the semantic. Just knowing the data type may b=
e
> enough to display values correctly. Considering
> informationElementSemanticType, you might also know if the calculation
> of statistical properties (max, min, mean, variance etc.) makes sense o=
r
> not. But any further analysis would probably require more semantical
> knowledge. That's why I assume that, in practice, analyzing and
> processing enterprise-specific data will mostly be performed with
> specialized analysis tools that have been implemented for this specific=

> purpose. And for these tools, there is no need to export the IE informa=
tion.
>=20

...but those ad hoc tools won't be reusable, unless tool specific configu=
ration or code modification are done for any used Enterprise Specific IE.=
=20And what about if the tools are not updated?=20

A real life example that this draft would solve is mentioned in:
http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html

...which also contains the motivation for this draft.

Regards,
Elisa


>=20
> Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #4 to become a new IPFIX work item is described by
>> draft draft-boschi-ipfix-extended-type-00.txt.
>>
>>> 4. Extended Types (Elisa Boschi)
>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>    specify what operations make sense for an IE.
>>>    Support shown for this as a WG item, as for File Format.
>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>> It is a method for assigning data types to unknown IPFIX information
>> elements by using option records that map data types to element identi=
fiers.
>>
>> It can be applied in cases where an IPFIX collector does not know the
>> data type of received information elements. This may in particular hap=
pen
>> if enterprise specific elements are used. Without this information the=

>> collector would treat these elements as if they were of type octet arr=
ay.
>> With this information it may be able to treat them more appropriately.=

>>
>> The current version of the IPFIX file format draft recommends using th=
is
>> method when IPFIX records are stored.
>>
>> Do you think this is a useful extension of the IPFIX protocol?
>> Do you think we should accept this as an IPFIX work item?
>> Please have a look at the draft and send your comments.
>>
>> Thanks,
>>
>>     Juergen
>>
>>
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20

*************************************************************************=
*************************=20
E-mail Confidentiality Notice and Disclaimer.=20

This email and any files transmitted with it are confidential and are int=
ended solely for the use=20
of the individual or entity to which they are addressed. Access to this e=
-mail by anyone else is=20
unauthorised. If you are not the intended recipient, any disclosure, copy=
ing, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-m=
ail messages are not=20
necessarily secure. Hitachi does not accept responsibility for any change=
s made to this message=20
after it was sent.=20

Please note that Hitachi checks outgoing e-mail messages for the presence=
=20of computer viruses.=20
*************************************************************************=
*************************

------_=_NextPart_001_01C7CFCF.1A50B147
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7235.2=
">
<TITLE>Re: [IPFIX] new work item candidate #4: extended types</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Gerhard,<BR>
<BR>
&gt;<BR>
&gt; On the one hand, it's a nice idea to have some IEs which allow<BR>
&gt; describing the type and semantic of other IEs. On the other hand, my=
<BR>
&gt; impression is that the usefulness is very restricted and not as broa=
d as<BR>
&gt; claimed in the introduction of the draft:<BR>
&gt;<BR>
&gt;&nbsp;&nbsp;&nbsp; ... Having to do some sort of tool-specific<BR>
&gt;&nbsp;&nbsp;&nbsp; configuration (or code modification) on every tool=
=20just to tell which<BR>
&gt;&nbsp;&nbsp;&nbsp; type each used Information Element has is a huge a=
mount of work for<BR>
&gt;&nbsp;&nbsp;&nbsp; users and implementors of enterprise-specific Info=
rmation Elements.<BR>
&gt;&nbsp;&nbsp;&nbsp; Many tools in fact only need to know the field's d=
ata type to work on<BR>
&gt;&nbsp;&nbsp;&nbsp; them. ...<BR>
&gt;<BR>
<BR>
One of the use cases we have in mind here would be a collaborative measur=
ement infrastructure where each exporter is implemented by a different ve=
ndor and exports slightly different enterprise IEs. In that case, having =
type information in the message stream allows ad-hoc preliminary analysis=
=20of the enterprise specific data.<BR>
<BR>
Our claim that many tools only need to know the field's data types to wor=
k on them applies...so the usefulness of the draft is not too &quot;restr=
icted&quot;<BR>
<BR>
&gt; In my opinion, any deeper analysis and processing of metering data<B=
R>
&gt; requires knowledge about the semantic. Just knowing the data type ma=
y be<BR>
&gt; enough to display values correctly. Considering<BR>
&gt; informationElementSemanticType, you might also know if the calculati=
on<BR>
&gt; of statistical properties (max, min, mean, variance etc.) makes sens=
e or<BR>
&gt; not. But any further analysis would probably require more semantical=
<BR>
&gt; knowledge. That's why I assume that, in practice, analyzing and<BR>
&gt; processing enterprise-specific data will mostly be performed with<BR=
>
&gt; specialized analysis tools that have been implemented for this speci=
fic<BR>
&gt; purpose. And for these tools, there is no need to export the IE info=
rmation.<BR>
&gt;<BR>
<BR>
...but those ad hoc tools won't be reusable, unless tool specific configu=
ration or code modification are done for any used Enterprise Specific IE.=
=20And what about if the tools are not updated?<BR>
<BR>
A real life example that this draft would solve is mentioned in:<BR>
<A HREF=3D"http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.h=
tml">http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html</A=
><BR>
<BR>
...which also contains the motivation for this draft.<BR>
<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
&gt;<BR>
&gt; Juergen Quittek wrote:<BR>
&gt;&gt; Dear all,<BR>
&gt;&gt;<BR>
&gt;&gt; Candidates #4 to become a new IPFIX work item is described by<BR=
>
&gt;&gt; draft draft-boschi-ipfix-extended-type-00.txt.<BR>
&gt;&gt;<BR>
&gt;&gt;&gt; 4. Extended Types (Elisa Boschi)<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Needed for IPFIX files, most useful for En=
terprise IEs; need to<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; specify what operations make sense for an =
IE.<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Support shown for this as a WG item, as fo=
r File Format.<BR>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; Milestones:&nbsp; WG LC after IETF 70, to =
IESG before IETF&nbsp; 71.<BR>
&gt;&gt; It is a method for assigning data types to unknown IPFIX informa=
tion<BR>
&gt;&gt; elements by using option records that map data types to element =
identifiers.<BR>
&gt;&gt;<BR>
&gt;&gt; It can be applied in cases where an IPFIX collector does not kno=
w the<BR>
&gt;&gt; data type of received information elements. This may in particul=
ar happen<BR>
&gt;&gt; if enterprise specific elements are used. Without this informati=
on the<BR>
&gt;&gt; collector would treat these elements as if they were of type oct=
et array.<BR>
&gt;&gt; With this information it may be able to treat them more appropri=
ately.<BR>
&gt;&gt;<BR>
&gt;&gt; The current version of the IPFIX file format draft recommends us=
ing this<BR>
&gt;&gt; method when IPFIX records are stored.<BR>
&gt;&gt;<BR>
&gt;&gt; Do you think this is a useful extension of the IPFIX protocol?<B=
R>
&gt;&gt; Do you think we should accept this as an IPFIX work item?<BR>
&gt;&gt; Please have a look at the draft and send your comments.<BR>
&gt;&gt;<BR>
&gt;&gt; Thanks,<BR>
&gt;&gt;<BR>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; Juergen<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt;<BR>
&gt;&gt; _______________________________________________<BR>
&gt;&gt; IPFIX mailing list<BR>
&gt;&gt; IPFIX@ietf.org<BR>
&gt;&gt; <A HREF=3D"https://www1.ietf.org/mailman/listinfo/ipfix">https:/=
/www1.ietf.org/mailman/listinfo/ipfix</A><BR>
&gt;<BR>
</FONT>
</P>


<P><FONT face=3D"Courier New"=20
size=3D2>****************************************************************=
**********************************<BR></FONT><FONT=20
face=3D"Courier New" size=3D2>E-mail Confidentiality Notice and Disclaime=
r.=20
</FONT></P>
<P><FONT face=3D"Courier New" size=3D2>This email and any files transmitt=
ed with it=20
are confidential and are intended solely for the use of the individual or=
=20entity=20
to which they are addressed. Access to this e-mail by anyone else is=20
unauthorised. If you are not the intended recipient,any disclosure, copyi=
ng,=20
distribution or any action taken or omitted to be taken in reliance on it=
, is=20
prohibited. <BR>E-mail messages are not necessarily secure.Hitachi does n=
ot=20
accept responsibility for any changes made to this message after it was=20
sent.<BR><BR>Please note that Hitachi checks outgoing e-mail&nbsp;message=
s for=20
the presence of computer viruses.=20
<BR>*********************************************************************=
*****************************</FONT></P>
</BODY>
</HTML>

------_=_NextPart_001_01C7CFCF.1A50B147--


--===============1437712723==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1437712723==--




From ipfix-bounces@ietf.org Thu Jul 26 18:08:31 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBVX-0000ZT-3B; Thu, 26 Jul 2007 18:08:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBVV-0000ZI-7x
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:08:29 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBVS-0001i3-5u
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:08:29 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 27 Jul 2007 00:08:26 +0200
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149116859:sNHT195053562"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QM8OMp020718; 
	Fri, 27 Jul 2007 00:08:24 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QM8Okt003660; 
	Thu, 26 Jul 2007 22:08:24 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id XAA12077;
	Thu, 26 Jul 2007 23:08:20 +0100 (BST)
Message-ID: <46A91B58.40909@cisco.com>
Date: Thu, 26 Jul 2007 23:08:24 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Brian Trammell <bht@cert.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=93109; t=1185487704;
	x=1186351704; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Review=3A=20draft-trammell-ipfix-file-04
	|Sender:=20; bh=tGlfspVCDUfUKZ9xbha+MW1US9hPYWJrjQ/cJ3VOrkA=;
	b=MjNr9vPrALcS3lLe3QYtbAmCGYAkrGisHOKxzaviaysSVtvWqwJvaU4TKv0t7qNKS7y+I30C
	WQvnGpzPSWqcTTJ8ue9WUtBTId5ZhoaJIr3kHOKonueqy6tc/bB4FsKM;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 56e89b758a38944229c8153fc72e2933
Cc: ipfix@ietf.org
Subject: [IPFIX] Review: draft-trammell-ipfix-file-04
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Brian.

Please see my comments inline.

> 
> IPFIX Working Group                                          B. Trammell
> Internet-Draft                                                CERT/NetSA
> Intended status: Standards Track                               E. Boschi
> Expires: January 10, 2008                                 Hitachi Europe
>                                                                  L. Mark
>                                                                 T. Zseby
>                                                         Fraunhofer FOKUS
>                                                                A. Wagner
>                                                               ETH Zurich
>                                                             July 9, 2007
> 
> 
>                        An IPFIX-Based File Format
>                     draft-trammell-ipfix-file-04.txt
> 
> Status of this Memo
> 
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
> 
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
> 
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
> 
>    This Internet-Draft will expire on January 10, 2008.
> 
> Copyright Notice
> 
>    Copyright (C) The IETF Trust (2007).
> 
> Abstract
> 
>    This document describes a file format for the storage of flow data
>    based upon the IPFIX message format.  It proposes a set of
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 1]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    requirements for flat-file, binary flow data file formats, evaluates
>    flow storage systems presently in use for their conformance to these
>    requirements, then applies the IPFIX message format to these
>    requirements to build a new file format.  This IPFIX-based file
>    format is designed to facilitate interoperability and reusability
>    among a wide variety of flow storage, processing, and analysis tools.
> 
> 
> Table of Contents
> 
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
>    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
>    3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  5
>    4.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  7
>      4.1.  Record Format Flexibility  . . . . . . . . . . . . . . . .  7
>      4.2.  Self Description . . . . . . . . . . . . . . . . . . . . .  7
>      4.3.  Data Compression . . . . . . . . . . . . . . . . . . . . .  8
>      4.4.  Indexing and Searching . . . . . . . . . . . . . . . . . .  8
>      4.5.  Data Integrity . . . . . . . . . . . . . . . . . . . . . .  9
>      4.6.  Creator Authentication and Confidentiality . . . . . . . .  9
>      4.7.  Anonymization and Obfuscation  . . . . . . . . . . . . . . 10
>      4.8.  Performance Characteristics  . . . . . . . . . . . . . . . 10
>    5.  Survey of Existing Flow and Trace File Formats . . . . . . . . 11
>      5.1.  NetFlow V5/V7  . . . . . . . . . . . . . . . . . . . . . . 11
>      5.2.  Argus 2  . . . . . . . . . . . . . . . . . . . . . . . . . 11
>      5.3.  SiLK . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
>      5.4.  libpcap dumpfile . . . . . . . . . . . . . . . . . . . . . 12
>    6.  IPFIX File Format Description  . . . . . . . . . . . . . . . . 13
>      6.1.  Recommended Information Elements for IPFIX Files . . . . . 15
>        6.1.1.  collectionTimeMilliseconds . . . . . . . . . . . . . . 16
>        6.1.2.  informationElementAnonymizationType  . . . . . . . . . 16
>        6.1.3.  maxExportSeconds . . . . . . . . . . . . . . . . . . . 16
>        6.1.4.  maxFlowEndSeconds  . . . . . . . . . . . . . . . . . . 17
>        6.1.5.  messageMD5Checksum . . . . . . . . . . . . . . . . . . 17
>        6.1.6.  messageScope . . . . . . . . . . . . . . . . . . . . . 17
>        6.1.7.  minExportSeconds . . . . . . . . . . . . . . . . . . . 18
>        6.1.8.  minFlowStartSeconds  . . . . . . . . . . . . . . . . . 18
>        6.1.9.  sessionScope . . . . . . . . . . . . . . . . . . . . . 19
>      6.2.  Recommended Options Templates for IPFIX Files  . . . . . . 19
>        6.2.1.  Message Checksum Options Template  . . . . . . . . . . 19
>        6.2.2.  Template Anonymization Options Template  . . . . . . . 20
>        6.2.3.  File Time Window Options Template  . . . . . . . . . . 21
>        6.2.4.  Export Session Details Options Template  . . . . . . . 22
>        6.2.5.  Message Details Options Template . . . . . . . . . . . 23
>      6.3.  Recommended Compression Error Resilience Strategy  . . . . 25
>      6.4.  Recommended Encryption Error Resilience Strategy . . . . . 27
>    7.  Applicability of IPFIX Files . . . . . . . . . . . . . . . . . 27
>      7.1.  Testing IPFIX Collecting Processes . . . . . . . . . . . . 27
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 2]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>      7.2.  Storage of IPFIX-collected Flow Data . . . . . . . . . . . 28
>    8.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
>    9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 29
>    10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 29
>    11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
>    12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
>      12.1. Normative References . . . . . . . . . . . . . . . . . . . 30
>      12.2. Informative References . . . . . . . . . . . . . . . . . . 31
>    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
>    Intellectual Property and Copyright Statements . . . . . . . . . . 34
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 3]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 1.  Introduction
> 
>    This document proposes a file format based upon IPFIX.  It begins by
>    exploring the motivation for proposing a standardized flow file
>    format, and using IPFIX as the basis for this new file format.  It
>    then proposes a set of requirements for this file format, evaluates
>    existing flow storage file formats for their conformance to these
>    requirements, and describes either how the IPFIX message format meets
>    each requirement, or how a file format based upon it could meet the
>    requirement.  It closes by proposing an initial specification of the

"the" -> "a"


>    new file format and providing examples of IPFIX Files meeting this

"Files" -> in the past we were avoiding capitalising terminology until 
after the terminology section, though I'm not sure whether this is a 
MUST or a SHOULD :-)  Same for "Options" below BTW.


>    specification.  This format makes use of the IPFIX Options mechanism
>    for additional file metadata, in order to avoid requiring any
>    protocol or message format extensions.
> 
> 
> 2.  Terminology
> 
>    Terms used in this document that are defined in the Terminology
>    section of the IPFIX Protocol [I-D.ietf-ipfix-protocol] document are
>    to be interpreted as defined there.
> 
>    IPFIX File:   An IPFIX File is a serialized stream of IPFIX Messages
>       stored on a filesystem.  Any IPFIX Message stream that would be
>       considered valid when transported one or more of the specified

"transported *on* one"

>       IPFIX transports (SCTP, TCP, or UDP) as defined in the IPFIX
>       Protocol draft [I-D.ietf-ipfix-protocol] is considered an IPFIX
>       File for purposes of this draft; however, this draft further
>       restricts that definition with recommendations on the construction
>       of IPFIX Files that meet the requirements identified herein.
> 
>    IPFIX File Reader:   An IPFIX File Reader is a Process which reads
>       IPFIX Files from a filesystem, and is analogous to an IPFIX
>       Collecting Process.  An IPFIX File Reader MUST behave as an IPFIX
>       Collecting Process as outlined in the IPFIX Protocol draft
>       [I-D.ietf-ipfix-protocol], except as modified by this document.
> 
>    IPFIX File Writer:   An IPFIX File Writer is a process which writes
>       IPFIX Files to a filesystem, and is analogous to an IPFIX
>       Exporting Process.  An IPFIX File Writer MUST behave as an IPFIX
>       Exporting Process as outlined in the IPFIX Protocol draft
>       [I-D.ietf-ipfix-protocol], except as modified by this document.
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in RFC 2119 [RFC2119].
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 4]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 3.  Motivation

For this section, please cite references for every assertion.

> 
>    There are a wide variety of applications for the file-based storage
>    of IP flow data, across a continuum of time scales.  Tools used in
>    the analysis of flow data and creation of analysis products often use
>    files as a convenient unit of work, with an ephemeral lifetime.  A
>    set of flows relevant to a security investigation may be stored in a
>    file for the duration of that investigation, and futher exchanged
>    among incident handlers via email or within an external incident
>    handling workflow application.  Sets of flow data relevant to
>    Internet measurement research may be published as files, much as
>    libpcap packet trace files are, to provide common data sets for the
>    repeatability of research efforts; these files would have lifetimes
>    measured in months or years.  Operational flow measurement systems
>    also have a need for long-term, archival storage of flow data, either
>    as a primary flow data repository, or as a backing tier for online
>    storage in a relational database management system (RDBMS).
> 
>    The variety of applications of flow data, and the variety of
>    presently deployed storage approaches, would seem to indicate the
>    need for a standard approach to flow storage with applicability
>    across the continuum of time scales over which flow data is stored.
>    A storage format based around flat files would best address the
>    variety of storage requirements.  While much work has been done on

Can you justify this?

>    structured storage via RDBMS, relational database systems are not a
>    good basis for format standardization owing to the fact that their
>    internal data structures are generally private to a single
>    implementation and subject to change for internal reasons.  Also,
>    there are a wide variety of operations available on flat files, and
>    external tools and standards can be leveraged to meet file-based flow
>    storage requiremenets.  Further, flow data is often not very

Typo, "requiremenets."

Can you justify "often"? Perhaps cite refs.

>    semantically complicated, is managed in very high volume, and
>    therefore an RDBMS-based flow storage system would not benefit much
>    from the advantages of relational database technology.
> 
>    The simplest way to create a new file format is simply to serialize
>    some internal data model to disk, with either textual or binary
>    representation of data elements, and some framing strategy for
>    delimiting fields and records.  "Ad-hoc" file formats such as this
>    have several important disadvantages.  One, they impose the semantics
>    of the data model from which they are derived on the file format; as
>    such, they are difficult to extend, describe, and standardize.
> 
>    Over the past decade XML markup has emerged as a new "universal"
>    representation format for structured data.  It is intended to be
>    human-readable; indeed, that is one reason for its rapid adoption.
>    However XML has limited usefulness for representing network flow
>    data.  Network flow data has a simple, repetitive, non-hierarchical
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 5]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    structure that does not benefit much from XML.  An XML representation
>    of flow data would be an essentially flat list of the attributes and
>    their values for each flow record.  At the same time network flow
>    data has well-defined semantics, required to do any meaningful
>    processing; these semantics are not known to typical XML tools.

Give examples of processing? eg, "such as ..."

> 
>    The XML approach to data encoding is very heavyweight when compared
>    to binary flow encoding.  While binary flow encodings use a small
>    number of (or even just one) flat data structures that are entirely

"use a small number of flat data structures (or even just one)"

>    sufficient to encode flow data, XML uses start- and end-tags, and
>    plain-text encoding of the actual values.  This leads to significant
>    inefficiency in encoding size.  Typical network flow datasets can
>    contain millions or billions of flows per hour of traffic
>    represented.  Any increase in storage size per record can have
>    dramatic impact on flow data storage and transfer sizes.  While data
>    compression algorithms can partially remove the redundancy introduced
>    by XML encoding, they introduce additional overhead of their own.
> 
>    A further problem is that XML processing tools require a full XML
>    parser.  XML parsers are fully general and therefore complex,
>    resource-intensive and relatively slow.  Since network flow datasets
>    can be very large, XML parsing introduces significant processing time
>    overhead.  At the same time, parsers for typical binary flow data
>    encoding are simply structured, since they only need to parse a very
>    small header and then have complete knowledge of all following fields
>    for the particular flow.  These can then be read in a very efficient
>    linear fashion without the need for any further decisions.  The

Do you include variable length fields in that assertion too?

>    overhead from encoding flow data with XML may well be prohibitive for
>    processing steps that are easily done with standard binary flow
>    encodings.  At the same time XML encoding offers no discernible
>    advantage to the flow storage use case.
> 
>    This leads us to propose the IPFIX message format as the basis for a

Is this a proposal or a standard?

>    new flow data file format.  The IPFIX working group, in defining the
>    IPFIX protocol, has already defined an information model and data
>    formatting rules for representation of flow data.  Especially at
>    shorter time scales, when a file is a unit of data interchange, the
>    filesystem may be viewed as simply another IPFIX message transport
>    between processes.  This format is especially well suited to
>    representing flow data, as it was designed specifically for flow data
>    export; it is easily extensible unlike ad-hoc serialization, and
>    compact unlike XML.  In addition, IPFIX is an emerging standard for
>    the export and collection of flow data; using a common format for
>    storage and analysis at the collection side allows implementors to
>    use substantially the same information model and data formatting
>    implementation for transport as well as storage.
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 6]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 4.  Requirements
> 
>    In this section, we outline a proposed set of requirements
>    [SAINT2007] for any persistent storage format for flow data.  First
>    and foremost, a flow data file format should support storage across
>    the continuum of time scales important to flow storage applications.
>    Each of the requirements enumerated in the sections below is broadly
>    applicable to flow storage applications, though each may be more
>    important at certain time scales.  For each, we first identify the
>    requirement, then explain how the IPFIX message format addresses it,
>    or briefly outline the changes that must be made in order for an
>    IPFIX-based file format to meet the requirement.
> 
> 4.1.  Record Format Flexibility
> 
>    Due to the wide variety of flow attributes collected by different
>    network flow attribute measurement systems, the ideal flow storage
>    format will not impose a single data model or a specific record type
>    on the flows it stores.  The file format must be flexible and
>    extensible; that is, it must support multiple record types definable
>    within the file itself, and must be able to support new field types
>    for data within the records in a graceful way.
> 
>    IPFIX provides extensibility through the use of Templates to describe
>    each Data Record, through the use of an IANA Registry to define its
>    Information Elements, and through the use of enterprise-specific
>    Information Elements.
> 
> 4.2.  Self Description
> 
>    Archived data may be read at a time in the future where any external
>    reference to the meaning of the data may be lost.  The ideal flow
>    storage format should be self-describing; that is, a process reading

"should be"? Ideally it *is*.

>    flow data from storage should be able to properly interpret the
>    stored flows without reference to anything other than standard
>    sources (e.g., the standards document describing the file format) and
>    the stored flow data itself.
> 
>    The IPFIX message format is partially self-describing; that is, IPFIX
>    Templates containing only IANA-assigned Information Elements can be
>    completely interpreted according to the IPFIX Information Model
>    without additional external data.
> 
>    However, Templates containing private information elements lack

"private" -> "Enterprise Specific". Also again below.

"Information Elements"

>    detailed type and semantic information; a Collecting Process
>    receiving data described by a template containing private Information
>    Elements it does not understand can only treat the data contained
>    within those Information Elements as octet arrays.  To be fully self-
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 7]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    describing, Enterprise-Specific Information Elements must be

"must be" -> this is certainly one option, though not the only possible one.

>    additionally described via IPFIX Options according to the Information
>    Element Semantics Options Template defined in "Extended Type
>    Information for IPFIX Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type].
> 
> 4.3.  Data Compression
> 
>    Regardless of the representation format, flow data describing traffic
>    on real networks tends to be highly compressible.  Compression tends

References!

>    to improve the scalability of flow collection systems, by reducing
>    the disk storage and I/O bandwidth requirement for a given workload.

- while increasing CPU requirements.

>    The ideal flow storage format should support applications which wish

Should?

>    to leverage this fact by supporting compression of stored data.
> 
>    The IPFIX message format has no support for data compression, as the
>    IPFIX protocol was designed for speed and simplicity of export.  Of
>    course, any flat file is readily compressible using a wide variety of
>    external data compression tools, formats, and algorithms; therefore,
>    this requirement can be met externally.

"external data compression tools" implies the file has already been made 
- in which case the I/O mentioned above is irrelevant.

> 
>    However, a couple of simple optimizations can be made by File Writers
>    to increase the integrity and usability of compressed IPFIX data;
>    these are outlined in the Recommended Compression Strategy section,

It's the "Recommended Compression Error Resilience Strategy" section.

>    which appears below.
> 
> 4.4.  Indexing and Searching
> 
>    Binary, record stream oriented file formats natively support only one
>    form of searching, sequential scan in file order.  By choosing the
>    order of records in a file carefully (e.g., by flow start or flow end

"By choosing to order records in"

>    time), a file can be indexed by a single key.

Multiple keys could be used, ie primary and secondary.

> 
>    Beyond this, properly addressing indexing is an application-specific
>    problem, as it inherently involves tradeoffs between storage
>    complexity and retrieval speed, and requirements vary widely based on
>    time scales and the types of queries used from site to site.
>    However, a generic standard flow storage format may provide limited

"may"? Is it a SHOULD?

>    direct support for indexing and searching.
> 
>    The ideal flow storage format will support a limited table of

"will"? Is it a MUST?

>    contents facility noting that the records in a file contain data
>    relating only to certain keys or values of keys, in order to keep
>    multi-file search implementations from having to scan a file for data
>    it does not contain.
> 
>    The IPFIX message format has no direct support for indexing.
>    However, its template mechanism and the technique described in
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 8]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    "Reducing Redundancy in IPFIX and PSAMP Reports"
>    [I-D.ietf-ipfix-reducing-redundancy] can be used to describe the
>    contents of a file in a limited way.  Additionally, as flow data is
>    often sorted and divided by time, the start and end time of the flows
>    in a file may be declared using the File Time Window Options Record
>    defined below.
> 
> 4.5.  Data Integrity
> 
>    When storing flow data over long time scales, especially for archival
>    purposes, it is important to ensure that hardware or software faults
>    do not introduce errors into the data over time.  The ideal flow
>    storage format will support the detection and correction of encoding-

"will"? Plus many times below too. Consider whether RFC 2119 language 
would be more appropriate - because what I hear is you describing a 
product you've built, rather than writing the requirements or spec for it.

>    level errors in the data.
> 
>    Note that more advanced error correction is almost certainly best

What about error detection?

>    handled at a layer below that addressed by this document.  Error
>    correction is a topic well addressed by the storage industry in
>    general (e.g. by RAID and other technolgies), and by specifying a
>    flow storage format based upon files, we can leverage these features
>    to meet this requirement.
> 
>    However, the ideal flow storage format will be resilient against
>    errors, providing an internal facility for the detection of errors
>    and the ability to isolate errors to as few data records as possible.
> 
>    Note that this requirement interacts with the choice of data
>    compression or encryption algorithm.  The use of block compression
>    algorithms can serve to isolate errors to a single compression block,
>    unlike stream compressors, which may fail to resynchronize after a
>    single bit error, invalidating the entire message stream.  Similarly,
>    the use of a stream cipher can serve to isloate errors in the
>    plaintext without amplifying them as, for example, a cipher in CBC

References please!

>    mode can.  See the "Recommended Compression Error Resilience
>    Strategy" and "Recommended Encryption Error Resilience Strategy"
>    sections below for more on this interaction.
> 
>    The IPFIX message format does not support data integrity assurance.
>    It is assumed that advanced error correction will be provided
>    externally.  For simple error detection support, checksums may be
>    attached to messages via IPFIX Options according to the Message
>    Checksum Options Template defined below.

I'd much prefer a csum IE.

> 
> 4.6.  Creator Authentication and Confidentiality
> 
>    Storage of flow data across long time scales may also require
>    assurance that no unauthorized entity can read or modify the stored
>    data.  Asymmetric-key cryptography can be applied to this problem, by
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 9]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    signing flow data with the private key of the creator, and encrypting
>    it with the public keys of those authorized to read it.  The ideal
>    flow storage format will support the encryption and signing of flow
>    data.
> 
>    As with error correction, this problem has been addressed well at a
>    layer below that addressed by this document.  Instead of specifying a

Refs?

>    particular choice of encryption technology, we can leverage the fact
>    that existing cryptographic technologies work quite well on data

"quite well"?

>    stored in files to meet this requirement.
> 
>    Beyond support for the use of TLS for transport over TCP or DTLS for
>    transport over SCTP or UDP, both of which provide transient
>    authentication and confidentiality, the IPFIX protocol does not
>    support this requirement directly.  It is assumed that this

"It is assumed"? -> "This requirement MUST"

>    requirement will be met externally.
> 
> 4.7.  Anonymization and Obfuscation
> 
>    To ensure the privacy of individuals and organizations at the
>    endpoints of communications represented by flow records, it is often
>    necessary to obfuscate or anonymize stored and exported flow data.
>    The ideal flow storage format will provide for a notation that a
>    given information element on a given record type represents
>    anonymized, rather than real, data.
> 
>    The IPFIX message format presently has no support for anonymization
>    notation.  It should be noted that anonymization is one of the
>    requirements given for IPFIX in RFC 3917 [RFC3917].  The decision to
>    qualify this requirement with 'MAY' and not 'MUST' in the
>    requirements document, and its subsequent lack of specification in
>    the current version of the IPFIX protocol, is due to the fact that
>    anonymization algorithms are still a research issue, and that there
>    currently exist no standardized methods for anonymization.
> 
>    Simple anonymization notation may be attached to templates via IPFIX
>    Options according to the Template Anonymization Options Template
>    defined below.
> 
> 4.8.  Performance Characteristics
> 
>    The ideal standard flow storage format will not have a significant
>    negative impact on the performance of the application implementing
>    it.  This is a non-functional requirement, but it is important to
>    note that a standard that implies a performance penalty is unlikely
>    to be widely implemented and adopted.
> 
>    A static analysis of the IPFIX message format would seem to suggest
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 10]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    that implementations of it are not particularly prone to slowness;
>    indeed, a template-based data representation is more easily subject
>    to optimization for common cases than representations that embed
>    structural information directly in the data stream (e.g.  XML).
>    However, a full analysis of the impact of using IPFIX messages as a
>    basis for flow data storage on read/write performance will require
>    more implementation experience and performance measurement.
> 
> 
> 5.  Survey of Existing Flow and Trace File Formats

Who selected these formats and why? How was the selection made?

> 
> 5.1.  NetFlow V5/V7

I think we use lowercase v: v5 and v7.

Do you consider that v7 is widely used?

> 
>    One de facto standard for the storage of flow data collected via
>    Cisco NetFlow V5 or V7 is to serialize a stream of "raw" NetFlow
>    datagrams into files.  These NetFlow PDU files consist of a
>    collection of header- prefixed blocks (corresponding to the datagrams
>    as received on the wire) containing fixed-length binary flow records.
>    NetFlow V5 and V7 data may be mixed within a given file, as the
>    header on each datagram defines the NetFlow version of the records
>    following; there is indeed very little difference between the two
>    record formats.
> 
>    NetFlow V5/V7 PDU files are neither extensible nor self-describing;
>    however, their status as a de facto standard means the definition of
>    the data format is well-understood.  Indexing, compression, error
>    detection and correction, authentication, and confidentiality must be
>    handled externally.
> 
> 5.2.  Argus 2
> 
>    QoSient's Argus (as of version 2.0.6) uses a file format based upon a
>    stream of type-and-length prefixed records.  There are two general
>    types of records in this stream, management records and flow records.
>    Management records export flow collection statistics, much like the
>    recommended scoped data records in the IPFIX protocol.  Flow records
>    contain information about a single flow each, and are further typed
>    based upon the protocol of the flow (e.g., IP, ICMP, ARP).  The Argus
>    file format natively spports bidirectional flow export, as each flow
>    record contains both forward and reverse counters.
> 
>    The Argus tools support a transport protocol that simply encapsulates
>    a record stream over a TCP connection.  Transport is collector-
>    initiated; that is, a collector establishes a connection to an
>    exporter in order to read a record stream.
> 
>    Argus files are not self-describing; that is, only the Argus tools
>    themselves encapsulate the definition of each of the record types.
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 11]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    The Argus file format is not extensible without changing the Argus
>    implementation.  Argus provides no indexing facility for its file
>    format, though records are roughly sorted by record generation time.
>    Compression, error correction, authentication, and confidentiality
>    are handled externally to the format, and are available as with all
>    files.  There is no special support for data obfuscation in the
>    format.
> 
> 5.3.  SiLK
> 
>    The CERT/NetSA SiLK tools use a set of fixed-length binary record
>    formats.  Each file is prefixed with a header which denotes which
>    record format the file is stored in.  These record formats are
>    differentiated by the presence or absence of certain fields; in this
>    way, each format identifier is essentially a short-hand identifier
>    for a template describing the record.  This also implies that only
>    one type of record may be stored in any given file.
> 
>    As with Argus, SiLK files are not self-describing and are not
>    extensible.  SiLK provides no indexing facility, though files are
>    generally stored in flow end time order; and when used for archival
>    storage, information about sensors and flow times appearing in each
>    file is stored in the file path name.  Compression is handled

Actually this can be done for any format here.

>    internally to the file format, and allows the storage of compressed
>    data in a file with uncompressed headers, and a guarantee of
>    compression block boundary alignment with record boundaries.  Error
>    correction, authentication, and confidentiality can be handled
>    externally.  There is no special support for data obfuscation in the

obfuscation? Which IPFIX calls anonymisation?

>    SiLK file format.
> 
> 5.4.  libpcap dumpfile
> 
>    The libpcap dumpfile format is a packet trace format rather than a
>    flow file format, so it does not address any of the requirements
>    outlined above.  However, it is used widely in a use case (data
>    storage and distribution for network measurement research) similar to
>    one addressed by the format proposed in this draft, so we include it
>    here.
> 
>    libpcap dumpfiles consist of a file header containing information
>    common to the whole file (most importantly, the datalink layer, for
>    interpretation of the datalink headers on each frame), followed by a
>    set of raw captured frame records each prefixed by a frame header
>    containing timestamp and length information.  The format is not
>    particularly flexible or self-describing, nor does it need to be:
>    undecoded frames are about as semantically simple as network traffic
>    data can get.
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 12]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    However, the simplicity and ubiquity of the libpcap dumpfile format
>    has led to its becoming a de facto standard for the distribution of
>    packet trace data for Internet measurement applications.  We propose
>    the file format described in this draft in part as an analogue to the
>    libpcap dumpfile format for flow data.
> 
>    Note that libpcap dumpfiles could be used as a storage format for any
>    unidirectional, datagram-oriented protocol such as IPFIX or NetFlow,
>    simply by storing the captured export session.  However, this has
>    several important drawbacks.  First, the additional per-packet
>    headers provided by pcap are redundant in the case of IPFIX, as
>    length and export time are already available in the IPFIX Message
>    Header.  Second, the link, network, and transport layer headers are
>    stored in a dumpfile; these are not necessary for the successful
>    interpretation of an IPFIX Message, and add additional decode
>    overhead.  Third, a file created by capturing an export session may
>    require additional processing to reassemble fragmented datagrams in
>    the message stream.
> 
> 
> 6.  IPFIX File Format Description
> 
>    An IPFIX file, as defined by this draft and elaborated below, is at
>    its core simply an IPFIX Message stream serialized to some
>    filesystem.  Any valid serialized IPFIX Message stream MUST be
>    accepted by a File Reader as a valid IPFIX file.  In this way, the
>    filesystem is simply treated as another IPFIX Transport alongside
>    SCTP, TCP, and UDP, although one with unusually high latency, as the
>    File Reader and File Writer are not necessarily synchronized in time,
>    unlike IPFIX Collecting and Exporting Processes.

The EP and CP are not synch'd at all.

> 
>    An IPFIX File Reader MUST accept as valid any IPFIX message stream
>    that would be considered valid by one or more of the other defined
>    IPFIX transport layers.  Practically, this means that the union of
>    template management features supported by SCTP, TCP, and UDP MUST be
>    supported in IPFIX Files.  The following requirements apply to IPFIX
>    File Readers:
> 
>    o  File Readers MUST accept IPFIX Messages containing Template Sets,
>       Options Template Sets, and Data Sets within the same message, as
>       with IPFIX over TCP or UDP.
> 
>    o  File Readers MUST accept Template Sets that define templates
>       already defined within the file, as may occur with template
>       retransmission when using IPFIX over UDP as described in section
>       10.3.6 of the IPFIX Protocol draft [I-D.ietf-ipfix-protocol].  In
>       the event of a conflict between a resent definition and a previous
>       definition, the File Reader MUST assume that the new template
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 13]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>       replaces the old, as consistent with UDP template expiration and
>       ID reuse.
> 
>    o  File Readers MUST accept Template Withdrawals as described in
>       section 8 of the IPFIX Protocol draft [I-D.ietf-ipfix-protocol],
>       provided that the Template to be withdrawn is defined, as is the
>       case with IPFIX over TCP and SCTP.

I'm thinking that FILE is essentially a layer below EP / CP but above 
transport, something like this:

	+------+        +------+
	|  EP  |        |  CP  |
	+------+--------+------+
	|         File         |
	+----------------------+
	|       transport      |
	+----------------------+

> 
>    However, for representation simplicity and read performance, File
>    Writers SHOULD use the following template and scope management
>    strategy:
> 
>    o  File Writers SHOULD emit Template Sets and Options Template Sets

I think this is a MUST, since data ahead of the necessary Templates 
could be discarded and is therefore of no value. Or put another way, if 
the Template is in the file somewhere, rewrite the file to put the 
Template at the start.

>       to appear at the beginning of the file, before any Data Sets, to
>       ensure all Templates are available and can be inspected before any
>       data is read.  If the set of Templates used within a File is not
>       known when the File Writer starts writing the File, the File
>       Writer MAY interleave Template Sets and Options Template Sets with
>       Data Sets within the File, but SHOULD write each Template Set or
>       Options Template Set before any Data Set described by that
>       Template.
> 
>    o  File Writers SHOULD emit special Data Records described by Options
>       Templates at the beginning of the file after Template Sets and
>       Options Template Sets as above, but before any other Data Records,
>       in the following order:
> 
>       *  Time window order records described by the File Time Window
>          Options Template as defined in section 6.2.3 below; followed by
> 
>       *  commonPropertiesId definitions as described in "Reducing
>          Redundancy in IPFIX and PSAMP Reports"
>          [I-D.ietf-ipfix-reducing-redundancy]; followed by
> 
>       *  Semantics records as described in "Extended Type Information
>          for IPFIX Enterprise-Specific Information Elements"
>          [I-D.boschi-ipfix-extended-type]; followed by
> 
>       *  Anonymization notation records described by the Template
>          Anonymization Options Template as defined in section 6.2.2
>          below.
> 
>    o  File Writers SHOULD emit Data Records described by Options

Again, MUST.

>       Templates to appear in the file before any Data Records which
>       depend on the scopes defined by those options.
> 
>    o  File Writers SHOULD use Template Withdrawals to withdraw Templates

Again, MUST.

>       if template IDs need to be reused.  In this case, the new

You'd have to generate them for UDP, because they won't exist.

> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 14]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>       Templates reusing those IDs SHOULD appear directly in the file
>       after the Template Withdrawals making the IDs available for reuse.
>       Template Withdrawals SHOULD NOT be used unless necessary to reuse
>       template IDs.

Why?

> 
>    Each IPFIX File is generally synonymous with a single Transport
>    Session.  File Writers SHOULD store the Templates and Options
>    required to decode the data within the File in the File itself, and
>    File Readers SHOULD NOT use Templates or Options defined in one file
>    to decode or interpret Data Sets in another.

What if I want to save each SCTP stream to a different file?

> 
>    However, some applications, particularly those storing large
>    collections of data over long periods of time, may benefit from the
>    ability to treat a collection of IPFIX Files as a single Transport
>    Session.  A File Reader MAY be configurable to treat a collection of
>    Files (e.g., all the files in a directory) as a single Transport
>    Session.  However, a File Reader MUST NOT treat a single IPFIX File
>    as containing multiple Transport Sessions.

So we need a new file if/when the Transport Session shuts down?

> 
>    File Writers SHOULD write IPFIX Messages within an IPFIX File in
>    ascending Export Time order.  If a File Writer is writing data

Here, ascending order. Below...

>    collected from an IPFIX Collecting Process, the Export Time SHOULD be
>    the export time as reported by the remote IPFIX Exporting Process;
>    otherwise, the Export Time should be the time at which the message
>    was written to the file.
> 
>    By default, File Writers MAY write records to an IPFIX File in any
>    order.  However, File Writers that write flow records to an IPFIX

... any order. Confusing.

>    File in flowStartTime or flowEndTime order SHOULD be consistent in
>    this ordering within each File.

Why? And which are we recommending here, if it's a standard?

> 
>    If an IPFIX File uses the technique described in "Reducing Redundancy
>    in IPFIX and PSAMP Reports" [I-D.ietf-ipfix-reducing-redundancy] AND
>    all of the non-Options Templates in the File contain the

Do you mean "contain *only* the" ?

>    commonPropertiesId Information Element, a File Reader MAY assume the
>    set of commonPropertiesId definitions provides a complete table of
>    contents for the file, for searching purposes.
> 
> 6.1.  Recommended Information Elements for IPFIX Files
> 
>    The following information elements are used by the options templates
>    below to allow IPFIX message streams to meet the requirements
>    outlined above without extension to the message format or protocol.
>    IPFIX File Readers and Writers SHOULD support these Information

MUST?

>    Elements as defined below.
> 
>    In addition, IPFIX File Readers and Writers SHOULD support the
>    Information Elements defined in "Extended Type Information for IPFIX
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 15]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type] in order to support self-description
>    of Enterprise-Specific Information Elements and anonymization
>    notation.
> 
> 6.1.1.  collectionTimeMilliseconds
> 
>    Description:   The absolute timestamp at which the data within the
>       scope containing this IE was received by a Collecting Process.

When an Exporting Process writes to a file, there's no CP time.

>       This IE SHOULD be bound to its containing IPFIX Message via an
>       options record and the messageScope IE, as defined below.

Say where, ie 6.1.6.

> 
>    Abstract Data Type:   dateTimeMilliseconds
> 
>    ElementId:   TBD1
> 
>    Status:   Proposed
> 
> 6.1.2.  informationElementAnonymizationType

It's a flag, not a type.

> 
>    Description:   A description of the anonymization status of an IPFIX
>       information element within a template.  If this field is FALSE,

"Template"

>       the corresponding IE is not anonymized; to the best ability of the
>       Exporting Process to determine, it represents a real value.  If
>       this field is TRUE, the corresponding IE is anonymized; to the
>       best ability of the Exporting Process to determine, it represents
>       a value that has been transformed to maintain privacy.  Note that
>       if no informationElementAnonymizationType is specified for an
>       information element, it is assumed to be FALSE, or not anonymized.

"Information Element"

> 
>    Abstract Data Type:   boolean
> 
>    ElementId:   TBD2
> 
>    Status:   Proposed
> 
> 6.1.3.  maxExportSeconds
> 
>    Description:   The absolute Export Time of the latest IPFIX message
>       within the scope containing this IE.  This IE SHOULD be bound to
>       its containing IPFIX Transport Session (i.e., File) via an options
>       record and the sessionScope IE, as defined below, and SHOULD

Say where, ie 6.1.9.

>       appear only once in a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 16]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    ElementId:   TBD3
> 
>    Status:   Proposed
> 
>    Units:   seconds

Does this give good granularity?

> 
> 6.1.4.  maxFlowEndSeconds
> 
>    Description:   The latest absolute timestamp of the last packet
>       within any Flow within the scope containing this IE, rounded up to
>       the second.  This IE SHOULD be bound to its containing IPFIX
>       Transport Session (i.e., File) via an options record and the
>       sessionScope IE, as defined below, and SHOULD appear only once in
>       a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD4
> 
>    Status:   Proposed
> 
>    Units:   seconds

Again, does this give good granularity?

> 
> 6.1.5.  messageMD5Checksum
> 
>    Description:   The MD5 checksum of the IPFIX Message containing this
>       record.  This IE SHOULD be bound to its containing IPFIX Message
>       via an options record and the messageScope IE, as defined below,

Eeuuwww. The message should directly contain its own csum IE.

For "below", again say where.

>       and SHOULD appear only once in a given IPFIX Message.  To

Split to a new paragraph here.

>       calculate the value of this IE, first buffer the containing IPFIX
>       Message, setting the value of this IE to all zeroes.  Then
>       caluclate the MD5 checksum of the resulting buffer as defined in
>       RFC 1321 [RFC1321], place the resulting value in this IE, and
>       export the buffered message.
> 
>    Abstract Data Type:   octetArray (16 bytes)
> 
>    ElementId:   TBD5
> 
>    Status:   Proposed
> 
>    Reference:   RFC 1321, The MD5 Message-Digest Algorithm [RFC1321]
> 
> 6.1.6.  messageScope
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 17]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Description:   The presence of this Information Element as scope in
>       an Options Template signifies that the options described by the
>       Template apply to the IPFIX Message that contains them.  It is
>       defined for general purpose message scoping of options, and
>       proposed specifically to allow the attachment a checksum to a
>       message via IPFIX Options.  The value of this Information Element
>       MUST be written as 0 by the File Writer or Exporting Process.  The
>       value of this Information Element MUST be ignored by the File
>       Reader or the Collecting Process.
> 
>    Abstract Data Type:   octet

The size should really be zero, right?

> 
>    ElementId:   TBD6
> 
>    Status:   Proposed
> 
> 6.1.7.  minExportSeconds
> 
>    Description:   The absolute Export Time of the earliest IPFIX message
>       within the scope containing this IE.  This IE SHOULD be bound to
>       its containing IPFIX Transport Session (i.e., File) via an options
>       record and the sessionScope IE, as defined below, and SHOULD
>       appear only once in a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD7
> 
>    Status:   Proposed
> 
>    Units:   seconds
> 
> 6.1.8.  minFlowStartSeconds
> 
>    Description:   The earliest absolute timestamp of the first packet
>       within any Flow within the scope containing this IE, rounded down
>       to the second.  This IE SHOULD be bound to its containing IPFIX
>       Transport Session (i.e., File) via an options record and the
>       sessionScope IE, as defined below, and SHOULD appear only once in
>       a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD8
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 18]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Status:   Proposed
> 
>    Units:   seconds
> 
> 6.1.9.  sessionScope
> 
>    Description:   The presence of this Information Element as scope in
>       an Options Template signifies that the options described by the
>       Template apply to the IPFIX Transport Session that contains them.
>       Note that as all options are implicitly scoped to Transport
>       Session and Observation Domain, this Information Element is
>       equivalent to a "null" scope.  It is defined for general purpose
>       session scoping of options, and proposed specifically to allow the
>       attachment of time window to a file via IPFIX Options.  The value

Split to a new paragraph.

>       of this Information Element MUST be written as 0 by the File
>       Writer or Exporting Process.  The value of this Information
>       Element MUST be ignored by the File Reader or the Collecting
>       Process.
> 
>    Abstract Data Type:   octet

Again, the size should really be zero, right?

> 
>    ElementId:   TBD9
> 
>    Status:   Proposed
> 
> 6.2.  Recommended Options Templates for IPFIX Files
> 
>    The following Options Templates allow IPFIX message streams to meet
>    the requirements outlined above without extension to the message
>    format or protocol.  They are defined in terms of existing
>    Information Elements defined in the IPFIX Information Model
>    [I-D.ietf-ipfix-info], the extended type Information Elements defined
>    in "Extended Type Information for IPFIX Enterprise-Specific
>    Information Elements" [I-D.boschi-ipfix-extended-type], as well as
>    Information Elements defined in the section above.  IPFIX File

Say which section above.

>    Readers and Writers SHOULD support these options templates as defined
>    below.
> 
>    In addition, IPFIX File Readers and Writers SHOULD support the
>    Options Templates defined in "Extended Type Information for IPFIX
>    Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type] in order to support self-description
>    of enterprise-specific Information Elements.
> 
> 6.2.1.  Message Checksum Options Template
> 
>    The Message Checksum Options Template specifies the structure of a
>    Data Record for attaching an MD5 message checksum to an IPFIX
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 19]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Message.  An MD5 message checksum as described MAY be used if long-
>    term data integrity is important to the application.  The described
>    Data Record MUST appear only once per IPFIX Message.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +--------------------+----------------------------------------------+
>    | IE                 | Description                                  |
>    +--------------------+----------------------------------------------+
>    | messageScope       | A marker denoting this Option applies to the |
>    |                    | whole IPFIX message; content is ignored.     |
>    |                    | This Information Element MUST be defined as  |
>    |                    | a Scope Field.                               |

Consider inserting some vertical whitespace here to make these more 
readable.

>    | messageMD5Checksum | The MD5 checksum of the containing IPFIX     |
>    |                    | Message.                                     |
>    +--------------------+----------------------------------------------+
> 
> 6.2.2.  Template Anonymization Options Template
> 
>    The Template Anonymization Options Template specifies the structure
>    of a Data Record for attaching anonymization notation information to
>    Information Elements in specified Template Records.  A Data Record
>    described by this Template SHOULD appear for each Information Element
>    within a Template known by the Exporting Process or File Writer to
>    contain anonymized data.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +-------------------------------------+-----------------------------+
>    | IE                                  | Description                 |
>    +-------------------------------------+-----------------------------+
>    | templateId                          | The Template ID of the      |
>    |                                     | template this record        |
>    |                                     | describes; it is assumed to |
>    |                                     | be valid within the         |
>    |                                     | Observation Domain ID of    |
>    |                                     | the containing IPFIX        |
>    |                                     | Message, and MUST identify  |
>    |                                     | a Template that has already |
>    |                                     | been exported.  This        |
>    |                                     | Information Element MUST be |
>    |                                     | defined as a Scope Field.   |
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 20]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | informationElementId                | The Information Element     |
>    |                                     | identifier of the           |
>    |                                     | Information Element within  |
>    |                                     | the specified Template this |
>    |                                     | record describes.  This     |
>    |                                     | Information Element MUST be |
>    |                                     | defined as a Scope Field.   |
>    | privateEnterpriseNumber             | The Private Enterprise      |
>    |                                     | number of the Information   |
>    |                                     | Element within the          |
>    |                                     | specified Template this     |
>    |                                     | record describes.  May be 0 |
>    |                                     | if this record describes a  |
>    |                                     | public Information Element. |
>    |                                     | This Information Element    |
>    |                                     | MUST be defined as a Scope  |
>    |                                     | Field.                      |

Put the PEN last so it can be omitted if zero.

>    | informationElementAnonymizationType | The anonymization type of   |
>    |                                     | the specified Information   |
>    |                                     | Element.                    |
>    +-------------------------------------+-----------------------------+
> 
> 6.2.3.  File Time Window Options Template
> 
>    The File Time Window Options Template specifies the structure of a
>    Data Record for attaching a time window to an IPFIX File; this Data
>    Record is referred to as a time window record.  A time window record
>    defines the earliest flow start time and the latest flow end time of
>    the flow records within a File.  One and only one time window record
>    MAY appear within an IPFIX File if the time window information is
>    available; a File Writer MUST NOT write more than one time window
>    record to an IPFIX File.  A File Writer that writes a time window
>    record to a File MUST NOT write any Flow with a start time before the
>    beginning of the window or an end time after the end of the window to
>    that File.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +---------------------+---------------------------------------------+
>    | IE                  | Description                                 |
>    +---------------------+---------------------------------------------+
>    | sessionScope        | A marker denoting this Option applies to    |
>    |                     | the whole IPFIX Transport Session (i.e.,    |
>    |                     | IPFIX File); content is ignored.  This      |
>    |                     | Information Element MUST be defined as a    |
>    |                     | Scope Field.                                |
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 21]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | minFlowStartSeconds | The start time of the earliest flow in the  |
>    |                     | Transport Session (i.e., File) in epoch     |
>    |                     | seconds.                                    |
>    | maxFlowEndSeconds   | The end time of the latest flow in the      |
>    |                     | Transport Session (i.e., File) in epoch     |
>    |                     | seconds.                                    |
>    +---------------------+---------------------------------------------+
> 
> 6.2.4.  Export Session Details Options Template
> 
>    The Export Session Details Options Template specifies the structure
>    of a Data Record for recording the details of an IPFIX Transport
>    Session in an IPFIX File.  It is intended for use in storing a single
>    complete IPFIX Transport Session in a single IPFIX File.  The
>    described Data Record SHOULD appear only once in a given IPFIX File.
> 
>    The template SHOULD contain the following Information Elements,
>    subject to applicability as noted on each Information Element:
> 
>    +----------------------------+--------------------------------------+
>    | IE                         | Description                          |
>    +----------------------------+--------------------------------------+
>    | sessionScope               | A marker denoting this Option        |
>    |                            | applies to the whole IPFIX Transport |
>    |                            | Session (i.e., IPFIX File); content  |
>    |                            | is ignored.  This Information        |
>    |                            | Element MUST be defined as a Scope   |
>    |                            | Field.                               |
>    | exporterIPv4Address        | IPv4 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv4     |
>    |                            | interface.  For multi-homed SCTP     |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Exporting Process.                   |
>    | exporterIPv6Address        | IPv6 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv6     |
>    |                            | interface.  For multi-homed SCTP     |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Exporting Process.                   |
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 22]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | exporterTransportPort      | The source port from which the       |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.                       |
>    | collectorIPv4Address       | IPv4 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv4 interface.  For multi-homed  |
>    |                            | SCTP associations, this SHOULD be    |
>    |                            | the primary path endpoint address of |
>    |                            | the Collecting Process.              |
>    | collectorIPv6Address       | IPv6 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv6 interface.  For multi-homed  |
>    |                            | SCTP associations, this SHOULD be    |
>    |                            | the primary path endpoint address of |
>    |                            | the Collecting Process.              |
>    | collectorTransportPort     | The destination port on which the    |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.                       |
>    | collectorTransportProtocol | The IP Protocol Identifier of the    |
>    |                            | transport protocol used to transport |
>    |                            | Messages within this Transport       |
>    |                            | Session.                             |

However, it's not specific to the Collector.

>    | collectorProtocolVersion   | The version of the IPFIX Protocol    |
>    |                            | used to transport Messages within    |
>    |                            | this Transport Session.              |

And again. Also below.

>    | minExportSeconds           | The Export Time of the first Message |
>    |                            | in the Transport Session.            |
>    | maxExportSeconds           | The Export Time of the last Message  |
>    |                            | in the Transport Session.            |
>    +----------------------------+--------------------------------------+
> 
> 6.2.5.  Message Details Options Template
> 
>    The Message Details Options Template specifies the structure of a
>    Data Record for attaching additional export details to an IPFIX
>    Message.  These details include the time at which a message was
>    received and information about the export and collection
>    infrastructure used to transport the Message.
> 
>    The template SHOULD contain the following Information Elements,
>    subject to applicability as noted for each Information Element.  Note
>    that when used in conjunction with the Export Session Details Options
>    Template, when storing a single complete IPFIX Transport Session in
>    an IPFIX File, this template SHOULD contain only the messageScope and
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 23]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    collectionTimeMilliseconds Information Elements.
> 
>    +----------------------------+--------------------------------------+
>    | IE                         | Description                          |
>    +----------------------------+--------------------------------------+
>    | messageScope               | A marker denoting this Option        |
>    |                            | applies to the whole IPFIX message;  |
>    |                            | content is ignored.  This            |
>    |                            | Information Element MUST be defined  |
>    |                            | as a Scope Field.                    |
>    | collectionTimeMilliseconds | The absolute time at which this      |
>    |                            | Message was received by the IPFIX    |
>    |                            | Collecting Process.                  |
>    | exporterIPv4Address        | IPv4 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv4     |
>    |                            | interface, and if this information   |
>    |                            | is not available via the Export      |
>    |                            | Session Details Options Template.    |
>    |                            | For multi-homed SCTP associations,   |
>    |                            | this SHOULD be the primary path      |
>    |                            | endpoint address of the Exporting    |
>    |                            | Process.                             |
>    | exporterIPv6Address        | IPv6 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv6     |
>    |                            | interface, and if this information   |
>    |                            | is not available via the Export      |
>    |                            | Session Details Options Template.    |
>    |                            | For multi-homed SCTP associations,   |
>    |                            | this SHOULD be the primary path      |
>    |                            | endpoint address of the Exporting    |
>    |                            | Process.                             |
>    | exporterTransportPort      | The source port from which the       |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.  Present only if this |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 24]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | collectorIPv4Address       | IPv4 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv4 interface, and if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.  For multi-homed SCTP      |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Collecting Process.                  |
>    | collectorIPv6Address       | IPv6 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv6 interface, and if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.  For multi-homed SCTP      |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Collecting Process.                  |
>    | collectorTransportPort     | The destination port on which the    |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.  Present only if this |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
>    | collectorTransportProtocol | The IP Protocol Identifier of the    |
>    |                            | transport protocol used to transport |
>    |                            | Messages within this Transport       |
>    |                            | Session.  Present only if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
>    | collectorProtocolVersion   | The version of the IPFIX Protocol    |
>    |                            | used to transport Messages within    |
>    |                            | this Transport Session.  Present     |
>    |                            | only if this information is not      |
>    |                            | available via the Export Session     |
>    |                            | Details Options Template.            |
>    +----------------------------+--------------------------------------+
> 
> 6.3.  Recommended Compression Error Resilience Strategy
> 
>    Note that, since any file may be compressed and decompressed with a
>    variety of widely available tools implementing a variety of
>    compression standards (both specified and de facto), compression of
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 25]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    IPFIX File data can be accomplished externally.  However, compression
>    at the file level is not particularly resilient to errors; in the
>    worst case, a single bit error in a stream-compressed file may result
>    in the loss of the entire file.
> 
>    To limit the impact of errors on the recoverability of compressed
>    data, we recommend the use of block compression where possible.
>    Ideally, the block compression algorithm should support the
>    identification and isolation of blocks containing errors; bzip2 is an
>    example of such a block compressor.
> 
>    Since the block boundary of a block-compressed IPFIX File may fall in
>    the middle of an IPFIX Message, resynchronization of an IPFIX Message
>    stream by a File Reader after a compression error requires some care.
>    The beginning of an IPFIX Message may be identified by its header
>    signature (the Version field of the Message Header, 0x00 0x0A,
>    followed by a 16-bit Message Length), but simply searching for the
>    first occurance of the Version field is insufficient, since these two
>    bytes may occur in valid IPFIX Template or Data Sets.
> 
>    Therefore, we propose the following algorithm for File Readers to
>    resynchronize an IPFIX Message Stream after skipping a compressed
>    block containing errors:
> 
>    1.  Search after the error for the first occurance of the byte string
>        0x00, 0x0A (the IPFIX Message Header Version field.)
> 
>    2.  Treat this field as the beginning of a candidate IPFIX Message.
>        Read the two bytes following the Version field as a Message
>        Length, and seek to that offset from the beginning of the
>        candidate IPFIX Message.
> 
>    3.  If the first two bytes after the candidate IPFIX Message are
>        0x00, 0x0A (i.e., the IPFIX Message Header Version field of the
>        next message in the stream), or if the end of the file is reached
>        precisely at the end of the candidate IPFIX Message, presume that
>        the candidate IPFIX Message is valid, and begin reading the IPFIX
>        File from the start of the candidate IPFIX Message.

I think this is insufficient: one should iterate over the entire message 
to the end to be sure.

> 
>    4.  If not, or if the seek reaches end-of-file or another block
>        containing errors before finding the end of the candidate
>        message, go back to step 1, starting the search two bytes from
>        the start of the candidate IPFIX Message.
> 
>    The algorithm above will improperly identify a non-message as a
>    message approximately 1 in 2^32 times, assuming random IPFIX data.
>    It may be expanded to consider multiple candidate IPFIX Messages in
>    order to increase reliability.

It should be, since the random nature of the data means it'll probably 
fail 9 times out of 10.

> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 26]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    In applications (e.g. archival storage) in which error resilience is
>    very important, File Writers SHOULD use block compression algorithms,
>    and MAY attempt to align IPFIX Messages within compression blocks to
>    ease resynchronization after errors, if such is supported by the
>    chosen block compressor.  File Readers SHOULD use the
>    resynchronization algorithm above to minimize data loss due to
>    compression errors.
> 
> 6.4.  Recommended Encryption Error Resilience Strategy
> 
>    File-level encryption has error resiliency issues similar to file-
>    level compression.  Single bit errors in the encrypted data stream
>    can result in unreadability of the entire remaining file, dependent
>    on the encryption method used.  The use of CBC (Cipher Block
>    Chaining) mode, which suffers from this low error resilience, is
>    relatively common.
> 
>    In applications (e.g. archival storage) in which error resilience is
>    very important, File Writers SHOULD use a stream cipher, for example
>    a block cipher in OFB (Output Feedback) mode (often referred to as
>    stream mode) instead of modes like CBC when encrypting, since errors
>    are not amplified by stream ciphers: A single-bit error in the
>    ciphertext results in a single bit error in the plaintext.
>    Alternatively File Writers SHOULD use any other cipher which can
>    resynchronize after bit errors.  An example is a block cipher in CBC
>    mode that is reinitialized after a specific amount of data has been
>    encrypted.  The maximum data loss per bit-error is then up to the
>    next reinitialization point.  In this case, File Writers SHOULD also
>    use the Message Checksum Options Template to attach a checksum to
>    each IPFIX Message in the IPFIX File, in order to support the
>    recognition of errors in the decrypted data.
> 
> 
> 7.  Applicability of IPFIX Files
> 
>    This section describes the specific applicability of IPFIX Files to
>    various use cases.  IPFIX Files are particularly useful in a flow
>    collection and processing infrastructure using IPFIX for flow export.
>    We explore the applicability and provide guidelines for using IPFIX
>    files during the implementation and operation of IPFIX Collecting
>    Processes.
> 
> 7.1.  Testing IPFIX Collecting Processes
> 
>    IPFIX Files can be used to store IPFIX Messages for the testing of
>    IPFIX Collecting Processes.  A variety of test cases may be stored in
>    IPFIX Files.  First, IPFIX data sets collected in real network
>    environments and stored in an IPFIX File can be used as input to
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 27]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    check the behavior of new or extended implementations of IPFIX
>    Collectors.  Furthermore, IPFIX Files could be used to validate the
>    operation of a given IPFIX Collecting Process in a new environment,
>    i.e., to test with recorded IPFIX data from the target network before
>    installing the Collecting Process in the network.
> 
>    The IPFIX File format can also be used to store artificial, non-
>    compliant reference messages for specific Collecting Process test
>    cases.  Examples for such test cases are sets of IPFIX records with
>    undefined Information Elements, Data Records described by missing
>    Templates, or incorrectly framed messages or data sets.
>    Representative error handling test cases are defined in "IPFIX
>    Testing" [I-D.ietf-ipfix-testing].
> 
>    Furthermore, fast replay of IPFIX records stored in a file can be
>    used for stress/load tests (e.g., high rate of incoming Data Records,
>    large Templates with high Information Element counts), as described
>    in "IPFIX Testing" [I-D.ietf-ipfix-testing].  The provisioning and
>    use of a set of reference files for testing simplifies the
>    performance of tests and increases the comparability of test results.
> 
>    Note that an extremely simple IPFIX Exporting Process may be crafted
>    for testing purposes by simply reading an IPFIX File and transmitting
>    it directly to a Collecting Process.  Similarly, an extremely simple
>    Collecting Process may be crafted for testing purposes by simply
>    accepting connections and/or IPFIX Messages from Exporting Processes
>    and writing the session's message stream to an IPFIX File.
> 
> 7.2.  Storage of IPFIX-collected Flow Data
> 
>    IPFIX Files can also, naturally, be used to store flow data collected
>    by an IPFIX Collecting Process; indeed, this was one of the primary
>    initial motivations behind the file format described within this
>    document.  Using IPFIX Files as such allows IPFIX implementations to
>    leverage substantially the same code for flow export and flow
>    storage.  In addition, the storage of single Transport Sessions in
>    IPFIX Files is particularly important for network measurement
>    research, allowing repeatability of experiments by providing a format
>    for the storage and exchange of IPFIX flow trace data much as the
>    libpcap format is used for experiments on packet trace data.
> 
>    As noted in the section above, the simplest way for a Collecting
>    Process to store the data collected in a single Transport Session is
>    to simply write the incoming IPFIX Messages to a file as they are
>    read.  However, while the resulting files are valid IPFIX Files, they
>    are lacking information about the IPFIX Transport Session used to
>    export them, such as the network addresses of the Exporting and
>    Collecting Processes and the protocols used to transport them.  An
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 28]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    IPFIX File Writer MAY store a single IPFIX Transport Session in an
>    IPFIX File and record information about the Transport Session using
>    the Export Session Details Options Template described above.
> 
>    Additional per-Message information MAY be recorded by the File Writer
>    using the Message Details Options Template described above.  Per-
>    message information includes the time at which each IPFIX Message was
>    received at the Collecting Process, and can be used to resend IPFIX
>    Messages while keeping the original measurement plane traffic
>    profile.  This Options Template also allows the storage of the export
>    session metainformation provided the Export Session Details Options

Isn't it "meta information" ?

>    Template, for storing information from multiple Transport Sessions in
>    the same IPFIX File.
> 
> 
> 8.  Examples
> 
>    [TODO in revision -05 or later]
> 
> 
> 9.  Security Considerations
> 
>    The IPFIX-based file format itself does not directly introduce
>    security issues.  Rather it is used to store information which may
>    for privacy or business issues be considered sensitive.  The file
>    format must therefore provide appropriate procedures to guarantee the
>    integrity and confidentiality of the stored information.

The OS or storage system could also do this.

P.

> 
>    The underlying protocol used to exchange the information that will be
>    stored using the format proposed in this document must as well apply
>    appropriate procedures to guarantee the integrity and confidentiality
>    of the exported information.  Such issues are addressed in separate
>    documents, specifically in the IPFIX Protocol
>    [I-D.ietf-ipfix-protocol].
> 
> 
> 10.  IANA Considerations
> 
>    This document specifies the creation of several new IPFIX Information
>    Elements in the IPFIX Information Element registry located at
>    http://www.iana.org/assignments/ipfix, as defined in section 6.1
>    above.  IANA has assigned the following Information Element numbers
>    for their respective Information Elements as specified below:
> 
>    o  Information Element number TBD1 for the collectionTimeMilliseconds
>       Information Element.
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 29]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    o  Information Element number TBD2 for the
>       informationElementAnonymizationType Information Element.
> 
>    o  Information Element number TBD3 for the maxExportSeconds
>       Information Element.
> 
>    o  Information Element number TBD4 for the maxFlowEndSeconds
>       Information Element.
> 
>    o  Information Element number TBD5 for the messageMD5Checksum
>       Information Element.
> 
>    o  Information Element number TBD6 for the messageScope Information
>       Element.
> 
>    o  Information Element number TBD7 for the minExportSeconds
>       Information Element.
> 
>    o  Information Element number TBD8 for the minFlowStartSeconds
>       Information Element.
> 
>    o  Information Element number TBD9 for the sessionScope Information
>       Element.
> 
>    [NOTE for IANA: The text TBD1, TBD2, TBD3, TBD4, TBD5, TBD6, TBD7,
>    TBD8, and TBD9 should be replaced with the respective assigned
>    Information Element numbers where they appear in this document.]
> 
> 
> 11.  Acknowledgements
> 
>    Thanks to Maurizio Molina, Tom Kosnar, Andreas Kind, and Andrew
>    Johnson for technical assistance with the requirements and their
>    implementation within this specification.
> 
> 
> 12.  References
> 
> 12.1.  Normative References
> 
>    [I-D.ietf-ipfix-protocol]
>               Claise, B., "Specification of the IPFIX Protocol for the
>               Exchange", draft-ietf-ipfix-protocol-24 (work in
>               progress), November 2006.
> 
>    [I-D.ietf-ipfix-info]
>               Quittek, J., "Information Model for IP Flow Information
>               Export", draft-ietf-ipfix-info-15 (work in progress),
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 30]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>               February 2007.
> 
>    [I-D.ietf-ipfix-reducing-redundancy]
>               Boschi, E., "Reducing Redundancy in IP Flow Information
>               Export (IPFIX) and Packet  Sampling (PSAMP) Reports",
>               draft-ietf-ipfix-reducing-redundancy-04 (work in
>               progress), May 2007.
> 
>    [RFC1321]  Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
>               April 1992.
> 
>    [I-D.boschi-ipfix-extended-type]
>               Boschi, E., Mark, L., Trammell, B., and T. Zseby,
>               "Extended Type Information for IPFIX Enterprise-Specific
>               Information Elements", draft-boschi-ipfix-ext-type-00
>               (work in progress), June 2007.
> 
> 12.2.  Informative References
> 
>    [I-D.ietf-ipfix-biflow]
>               Trammell, B. and E. Boschi, "Bidirectional Flow Export
>               using IPFIX", draft-ietf-ipfix-biflow-05 (work in
>               progress), June 2007.
> 
>    [I-D.ietf-ipfix-testing]
>               Schmoll, C. and P. Aitken, "IP Flow Information eXport
>               (IPFIX) Testing", draft-ietf-ipfix-testing-01 (work in
>               progress), June 2007.
> 
>    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
>               "Requirements for IP Flow Information Export (IPFIX)",
>               RFC 3917, October 2004.
> 
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
> 
>    [SAINT2007]
>               Trammell, B., Boschi, E., Mark, L., and T. Zseby,
>               "Requirements for a standardized flow storage solution",
>                in Proceedings of the SAINT 2007 workshop on Internet
>               Measurement Technology, Hiroshima, Japan, January 2007.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 31]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> Authors' Addresses
> 
>    Brian H. Trammell
>    CERT Network Situational Awareness
>    Software Engineering Institute
>    4500 Fifth Avenue
>    Pittsburgh, Pennsylvania  15213
>    United States
> 
>    Phone: +1 412 268 9748
>    Email: bht@cert.org
> 
> 
>    Elisa Boschi
>    Hitachi Europe SAS
>    Immeuble Le Theleme
>    1503 Route les Dolines
>    06560 Valbonne
>    France
> 
>    Phone: +33 4 89874100
>    Email: elisa.boschi@hitachi-eu.com
> 
> 
>    Lutz Mark
>    Fraunhofer Institute for Open Communication Systems
>    Kaiserin-Augusta-Allee 31
>    10589 Berlin
>    Germany
> 
>    Phone: +49 30 3463 7306
>    Email: lutz.mark@fokus.fraunhofer.de
> 
> 
>    Tanja Zseby
>    Fraunhofer Institute for Open Communication Systems
>    Kaiserin-Augusta-Allee 31
>    10589 Berlin
>    Germany
> 
>    Phone: +49 30 3463 7153
>    Email: tanja.zseby@fokus.fraunhofer.de
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 32]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Arno Wagner
>    Swiss Federal Institute of Technology Zurich
>    Gloriastrasse 35
>    8092 Zurich
>    Switzerland
> 
>    Phone: +41 44 632 70 04
>    Email: arno@wagner.name
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 33]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> Full Copyright Statement
> 
>    Copyright (C) The IETF Trust (2007).
> 
>    This document is subject to the rights, licenses and restrictions
>    contained in BCP 78, and except as set forth therein, the authors
>    retain all their rights.
> 
>    This document and the information contained herein are provided on an
>    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Intellectual Property
> 
>    The IETF takes no position regarding the validity or scope of any
>    Intellectual Property Rights or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; nor does it represent that it has
>    made any independent effort to identify any such rights.  Information
>    on the procedures with respect to rights in RFC documents can be
>    found in BCP 78 and BCP 79.
> 
>    Copies of IPR disclosures made to the IETF Secretariat and any
>    assurances of licenses to be made available, or the result of an
>    attempt made to obtain a general license or permission for the use of
>    such proprietary rights by implementers or users of this
>    specification can be obtained from the IETF on-line IPR repository at
>    http://www.ietf.org/ipr.
> 
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights that may cover technology that may be required to implement
>    this standard.  Please address the information to the IETF at
>    ietf-ipr@ietf.org.
> 
> 
> Acknowledgment
> 
>    Funding for the RFC Editor function is provided by the IETF
>    Administrative Support Activity (IASA).
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 34]
> 
> 

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 18:08:31 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBVX-0000ZT-3B; Thu, 26 Jul 2007 18:08:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBVV-0000ZI-7x
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:08:29 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBVS-0001i3-5u
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:08:29 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 27 Jul 2007 00:08:26 +0200
X-IronPort-AV: i="4.16,584,1175464800"; 
	d="scan'208"; a="149116859:sNHT195053562"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6QM8OMp020718; 
	Fri, 27 Jul 2007 00:08:24 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6QM8Okt003660; 
	Thu, 26 Jul 2007 22:08:24 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id XAA12077;
	Thu, 26 Jul 2007 23:08:20 +0100 (BST)
Message-ID: <46A91B58.40909@cisco.com>
Date: Thu, 26 Jul 2007 23:08:24 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Brian Trammell <bht@cert.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=93109; t=1185487704;
	x=1186351704; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Review=3A=20draft-trammell-ipfix-file-04
	|Sender:=20; bh=tGlfspVCDUfUKZ9xbha+MW1US9hPYWJrjQ/cJ3VOrkA=;
	b=MjNr9vPrALcS3lLe3QYtbAmCGYAkrGisHOKxzaviaysSVtvWqwJvaU4TKv0t7qNKS7y+I30C
	WQvnGpzPSWqcTTJ8ue9WUtBTId5ZhoaJIr3kHOKonueqy6tc/bB4FsKM;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 56e89b758a38944229c8153fc72e2933
Cc: ipfix@ietf.org
Subject: [IPFIX] Review: draft-trammell-ipfix-file-04
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Brian.

Please see my comments inline.

> 
> IPFIX Working Group                                          B. Trammell
> Internet-Draft                                                CERT/NetSA
> Intended status: Standards Track                               E. Boschi
> Expires: January 10, 2008                                 Hitachi Europe
>                                                                  L. Mark
>                                                                 T. Zseby
>                                                         Fraunhofer FOKUS
>                                                                A. Wagner
>                                                               ETH Zurich
>                                                             July 9, 2007
> 
> 
>                        An IPFIX-Based File Format
>                     draft-trammell-ipfix-file-04.txt
> 
> Status of this Memo
> 
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
> 
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
> 
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
> 
>    This Internet-Draft will expire on January 10, 2008.
> 
> Copyright Notice
> 
>    Copyright (C) The IETF Trust (2007).
> 
> Abstract
> 
>    This document describes a file format for the storage of flow data
>    based upon the IPFIX message format.  It proposes a set of
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 1]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    requirements for flat-file, binary flow data file formats, evaluates
>    flow storage systems presently in use for their conformance to these
>    requirements, then applies the IPFIX message format to these
>    requirements to build a new file format.  This IPFIX-based file
>    format is designed to facilitate interoperability and reusability
>    among a wide variety of flow storage, processing, and analysis tools.
> 
> 
> Table of Contents
> 
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
>    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
>    3.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  5
>    4.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  7
>      4.1.  Record Format Flexibility  . . . . . . . . . . . . . . . .  7
>      4.2.  Self Description . . . . . . . . . . . . . . . . . . . . .  7
>      4.3.  Data Compression . . . . . . . . . . . . . . . . . . . . .  8
>      4.4.  Indexing and Searching . . . . . . . . . . . . . . . . . .  8
>      4.5.  Data Integrity . . . . . . . . . . . . . . . . . . . . . .  9
>      4.6.  Creator Authentication and Confidentiality . . . . . . . .  9
>      4.7.  Anonymization and Obfuscation  . . . . . . . . . . . . . . 10
>      4.8.  Performance Characteristics  . . . . . . . . . . . . . . . 10
>    5.  Survey of Existing Flow and Trace File Formats . . . . . . . . 11
>      5.1.  NetFlow V5/V7  . . . . . . . . . . . . . . . . . . . . . . 11
>      5.2.  Argus 2  . . . . . . . . . . . . . . . . . . . . . . . . . 11
>      5.3.  SiLK . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
>      5.4.  libpcap dumpfile . . . . . . . . . . . . . . . . . . . . . 12
>    6.  IPFIX File Format Description  . . . . . . . . . . . . . . . . 13
>      6.1.  Recommended Information Elements for IPFIX Files . . . . . 15
>        6.1.1.  collectionTimeMilliseconds . . . . . . . . . . . . . . 16
>        6.1.2.  informationElementAnonymizationType  . . . . . . . . . 16
>        6.1.3.  maxExportSeconds . . . . . . . . . . . . . . . . . . . 16
>        6.1.4.  maxFlowEndSeconds  . . . . . . . . . . . . . . . . . . 17
>        6.1.5.  messageMD5Checksum . . . . . . . . . . . . . . . . . . 17
>        6.1.6.  messageScope . . . . . . . . . . . . . . . . . . . . . 17
>        6.1.7.  minExportSeconds . . . . . . . . . . . . . . . . . . . 18
>        6.1.8.  minFlowStartSeconds  . . . . . . . . . . . . . . . . . 18
>        6.1.9.  sessionScope . . . . . . . . . . . . . . . . . . . . . 19
>      6.2.  Recommended Options Templates for IPFIX Files  . . . . . . 19
>        6.2.1.  Message Checksum Options Template  . . . . . . . . . . 19
>        6.2.2.  Template Anonymization Options Template  . . . . . . . 20
>        6.2.3.  File Time Window Options Template  . . . . . . . . . . 21
>        6.2.4.  Export Session Details Options Template  . . . . . . . 22
>        6.2.5.  Message Details Options Template . . . . . . . . . . . 23
>      6.3.  Recommended Compression Error Resilience Strategy  . . . . 25
>      6.4.  Recommended Encryption Error Resilience Strategy . . . . . 27
>    7.  Applicability of IPFIX Files . . . . . . . . . . . . . . . . . 27
>      7.1.  Testing IPFIX Collecting Processes . . . . . . . . . . . . 27
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 2]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>      7.2.  Storage of IPFIX-collected Flow Data . . . . . . . . . . . 28
>    8.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
>    9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 29
>    10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 29
>    11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
>    12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
>      12.1. Normative References . . . . . . . . . . . . . . . . . . . 30
>      12.2. Informative References . . . . . . . . . . . . . . . . . . 31
>    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
>    Intellectual Property and Copyright Statements . . . . . . . . . . 34
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 3]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 1.  Introduction
> 
>    This document proposes a file format based upon IPFIX.  It begins by
>    exploring the motivation for proposing a standardized flow file
>    format, and using IPFIX as the basis for this new file format.  It
>    then proposes a set of requirements for this file format, evaluates
>    existing flow storage file formats for their conformance to these
>    requirements, and describes either how the IPFIX message format meets
>    each requirement, or how a file format based upon it could meet the
>    requirement.  It closes by proposing an initial specification of the

"the" -> "a"


>    new file format and providing examples of IPFIX Files meeting this

"Files" -> in the past we were avoiding capitalising terminology until 
after the terminology section, though I'm not sure whether this is a 
MUST or a SHOULD :-)  Same for "Options" below BTW.


>    specification.  This format makes use of the IPFIX Options mechanism
>    for additional file metadata, in order to avoid requiring any
>    protocol or message format extensions.
> 
> 
> 2.  Terminology
> 
>    Terms used in this document that are defined in the Terminology
>    section of the IPFIX Protocol [I-D.ietf-ipfix-protocol] document are
>    to be interpreted as defined there.
> 
>    IPFIX File:   An IPFIX File is a serialized stream of IPFIX Messages
>       stored on a filesystem.  Any IPFIX Message stream that would be
>       considered valid when transported one or more of the specified

"transported *on* one"

>       IPFIX transports (SCTP, TCP, or UDP) as defined in the IPFIX
>       Protocol draft [I-D.ietf-ipfix-protocol] is considered an IPFIX
>       File for purposes of this draft; however, this draft further
>       restricts that definition with recommendations on the construction
>       of IPFIX Files that meet the requirements identified herein.
> 
>    IPFIX File Reader:   An IPFIX File Reader is a Process which reads
>       IPFIX Files from a filesystem, and is analogous to an IPFIX
>       Collecting Process.  An IPFIX File Reader MUST behave as an IPFIX
>       Collecting Process as outlined in the IPFIX Protocol draft
>       [I-D.ietf-ipfix-protocol], except as modified by this document.
> 
>    IPFIX File Writer:   An IPFIX File Writer is a process which writes
>       IPFIX Files to a filesystem, and is analogous to an IPFIX
>       Exporting Process.  An IPFIX File Writer MUST behave as an IPFIX
>       Exporting Process as outlined in the IPFIX Protocol draft
>       [I-D.ietf-ipfix-protocol], except as modified by this document.
> 
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in RFC 2119 [RFC2119].
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 4]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 3.  Motivation

For this section, please cite references for every assertion.

> 
>    There are a wide variety of applications for the file-based storage
>    of IP flow data, across a continuum of time scales.  Tools used in
>    the analysis of flow data and creation of analysis products often use
>    files as a convenient unit of work, with an ephemeral lifetime.  A
>    set of flows relevant to a security investigation may be stored in a
>    file for the duration of that investigation, and futher exchanged
>    among incident handlers via email or within an external incident
>    handling workflow application.  Sets of flow data relevant to
>    Internet measurement research may be published as files, much as
>    libpcap packet trace files are, to provide common data sets for the
>    repeatability of research efforts; these files would have lifetimes
>    measured in months or years.  Operational flow measurement systems
>    also have a need for long-term, archival storage of flow data, either
>    as a primary flow data repository, or as a backing tier for online
>    storage in a relational database management system (RDBMS).
> 
>    The variety of applications of flow data, and the variety of
>    presently deployed storage approaches, would seem to indicate the
>    need for a standard approach to flow storage with applicability
>    across the continuum of time scales over which flow data is stored.
>    A storage format based around flat files would best address the
>    variety of storage requirements.  While much work has been done on

Can you justify this?

>    structured storage via RDBMS, relational database systems are not a
>    good basis for format standardization owing to the fact that their
>    internal data structures are generally private to a single
>    implementation and subject to change for internal reasons.  Also,
>    there are a wide variety of operations available on flat files, and
>    external tools and standards can be leveraged to meet file-based flow
>    storage requiremenets.  Further, flow data is often not very

Typo, "requiremenets."

Can you justify "often"? Perhaps cite refs.

>    semantically complicated, is managed in very high volume, and
>    therefore an RDBMS-based flow storage system would not benefit much
>    from the advantages of relational database technology.
> 
>    The simplest way to create a new file format is simply to serialize
>    some internal data model to disk, with either textual or binary
>    representation of data elements, and some framing strategy for
>    delimiting fields and records.  "Ad-hoc" file formats such as this
>    have several important disadvantages.  One, they impose the semantics
>    of the data model from which they are derived on the file format; as
>    such, they are difficult to extend, describe, and standardize.
> 
>    Over the past decade XML markup has emerged as a new "universal"
>    representation format for structured data.  It is intended to be
>    human-readable; indeed, that is one reason for its rapid adoption.
>    However XML has limited usefulness for representing network flow
>    data.  Network flow data has a simple, repetitive, non-hierarchical
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 5]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    structure that does not benefit much from XML.  An XML representation
>    of flow data would be an essentially flat list of the attributes and
>    their values for each flow record.  At the same time network flow
>    data has well-defined semantics, required to do any meaningful
>    processing; these semantics are not known to typical XML tools.

Give examples of processing? eg, "such as ..."

> 
>    The XML approach to data encoding is very heavyweight when compared
>    to binary flow encoding.  While binary flow encodings use a small
>    number of (or even just one) flat data structures that are entirely

"use a small number of flat data structures (or even just one)"

>    sufficient to encode flow data, XML uses start- and end-tags, and
>    plain-text encoding of the actual values.  This leads to significant
>    inefficiency in encoding size.  Typical network flow datasets can
>    contain millions or billions of flows per hour of traffic
>    represented.  Any increase in storage size per record can have
>    dramatic impact on flow data storage and transfer sizes.  While data
>    compression algorithms can partially remove the redundancy introduced
>    by XML encoding, they introduce additional overhead of their own.
> 
>    A further problem is that XML processing tools require a full XML
>    parser.  XML parsers are fully general and therefore complex,
>    resource-intensive and relatively slow.  Since network flow datasets
>    can be very large, XML parsing introduces significant processing time
>    overhead.  At the same time, parsers for typical binary flow data
>    encoding are simply structured, since they only need to parse a very
>    small header and then have complete knowledge of all following fields
>    for the particular flow.  These can then be read in a very efficient
>    linear fashion without the need for any further decisions.  The

Do you include variable length fields in that assertion too?

>    overhead from encoding flow data with XML may well be prohibitive for
>    processing steps that are easily done with standard binary flow
>    encodings.  At the same time XML encoding offers no discernible
>    advantage to the flow storage use case.
> 
>    This leads us to propose the IPFIX message format as the basis for a

Is this a proposal or a standard?

>    new flow data file format.  The IPFIX working group, in defining the
>    IPFIX protocol, has already defined an information model and data
>    formatting rules for representation of flow data.  Especially at
>    shorter time scales, when a file is a unit of data interchange, the
>    filesystem may be viewed as simply another IPFIX message transport
>    between processes.  This format is especially well suited to
>    representing flow data, as it was designed specifically for flow data
>    export; it is easily extensible unlike ad-hoc serialization, and
>    compact unlike XML.  In addition, IPFIX is an emerging standard for
>    the export and collection of flow data; using a common format for
>    storage and analysis at the collection side allows implementors to
>    use substantially the same information model and data formatting
>    implementation for transport as well as storage.
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 6]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> 4.  Requirements
> 
>    In this section, we outline a proposed set of requirements
>    [SAINT2007] for any persistent storage format for flow data.  First
>    and foremost, a flow data file format should support storage across
>    the continuum of time scales important to flow storage applications.
>    Each of the requirements enumerated in the sections below is broadly
>    applicable to flow storage applications, though each may be more
>    important at certain time scales.  For each, we first identify the
>    requirement, then explain how the IPFIX message format addresses it,
>    or briefly outline the changes that must be made in order for an
>    IPFIX-based file format to meet the requirement.
> 
> 4.1.  Record Format Flexibility
> 
>    Due to the wide variety of flow attributes collected by different
>    network flow attribute measurement systems, the ideal flow storage
>    format will not impose a single data model or a specific record type
>    on the flows it stores.  The file format must be flexible and
>    extensible; that is, it must support multiple record types definable
>    within the file itself, and must be able to support new field types
>    for data within the records in a graceful way.
> 
>    IPFIX provides extensibility through the use of Templates to describe
>    each Data Record, through the use of an IANA Registry to define its
>    Information Elements, and through the use of enterprise-specific
>    Information Elements.
> 
> 4.2.  Self Description
> 
>    Archived data may be read at a time in the future where any external
>    reference to the meaning of the data may be lost.  The ideal flow
>    storage format should be self-describing; that is, a process reading

"should be"? Ideally it *is*.

>    flow data from storage should be able to properly interpret the
>    stored flows without reference to anything other than standard
>    sources (e.g., the standards document describing the file format) and
>    the stored flow data itself.
> 
>    The IPFIX message format is partially self-describing; that is, IPFIX
>    Templates containing only IANA-assigned Information Elements can be
>    completely interpreted according to the IPFIX Information Model
>    without additional external data.
> 
>    However, Templates containing private information elements lack

"private" -> "Enterprise Specific". Also again below.

"Information Elements"

>    detailed type and semantic information; a Collecting Process
>    receiving data described by a template containing private Information
>    Elements it does not understand can only treat the data contained
>    within those Information Elements as octet arrays.  To be fully self-
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 7]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    describing, Enterprise-Specific Information Elements must be

"must be" -> this is certainly one option, though not the only possible one.

>    additionally described via IPFIX Options according to the Information
>    Element Semantics Options Template defined in "Extended Type
>    Information for IPFIX Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type].
> 
> 4.3.  Data Compression
> 
>    Regardless of the representation format, flow data describing traffic
>    on real networks tends to be highly compressible.  Compression tends

References!

>    to improve the scalability of flow collection systems, by reducing
>    the disk storage and I/O bandwidth requirement for a given workload.

- while increasing CPU requirements.

>    The ideal flow storage format should support applications which wish

Should?

>    to leverage this fact by supporting compression of stored data.
> 
>    The IPFIX message format has no support for data compression, as the
>    IPFIX protocol was designed for speed and simplicity of export.  Of
>    course, any flat file is readily compressible using a wide variety of
>    external data compression tools, formats, and algorithms; therefore,
>    this requirement can be met externally.

"external data compression tools" implies the file has already been made 
- in which case the I/O mentioned above is irrelevant.

> 
>    However, a couple of simple optimizations can be made by File Writers
>    to increase the integrity and usability of compressed IPFIX data;
>    these are outlined in the Recommended Compression Strategy section,

It's the "Recommended Compression Error Resilience Strategy" section.

>    which appears below.
> 
> 4.4.  Indexing and Searching
> 
>    Binary, record stream oriented file formats natively support only one
>    form of searching, sequential scan in file order.  By choosing the
>    order of records in a file carefully (e.g., by flow start or flow end

"By choosing to order records in"

>    time), a file can be indexed by a single key.

Multiple keys could be used, ie primary and secondary.

> 
>    Beyond this, properly addressing indexing is an application-specific
>    problem, as it inherently involves tradeoffs between storage
>    complexity and retrieval speed, and requirements vary widely based on
>    time scales and the types of queries used from site to site.
>    However, a generic standard flow storage format may provide limited

"may"? Is it a SHOULD?

>    direct support for indexing and searching.
> 
>    The ideal flow storage format will support a limited table of

"will"? Is it a MUST?

>    contents facility noting that the records in a file contain data
>    relating only to certain keys or values of keys, in order to keep
>    multi-file search implementations from having to scan a file for data
>    it does not contain.
> 
>    The IPFIX message format has no direct support for indexing.
>    However, its template mechanism and the technique described in
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 8]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    "Reducing Redundancy in IPFIX and PSAMP Reports"
>    [I-D.ietf-ipfix-reducing-redundancy] can be used to describe the
>    contents of a file in a limited way.  Additionally, as flow data is
>    often sorted and divided by time, the start and end time of the flows
>    in a file may be declared using the File Time Window Options Record
>    defined below.
> 
> 4.5.  Data Integrity
> 
>    When storing flow data over long time scales, especially for archival
>    purposes, it is important to ensure that hardware or software faults
>    do not introduce errors into the data over time.  The ideal flow
>    storage format will support the detection and correction of encoding-

"will"? Plus many times below too. Consider whether RFC 2119 language 
would be more appropriate - because what I hear is you describing a 
product you've built, rather than writing the requirements or spec for it.

>    level errors in the data.
> 
>    Note that more advanced error correction is almost certainly best

What about error detection?

>    handled at a layer below that addressed by this document.  Error
>    correction is a topic well addressed by the storage industry in
>    general (e.g. by RAID and other technolgies), and by specifying a
>    flow storage format based upon files, we can leverage these features
>    to meet this requirement.
> 
>    However, the ideal flow storage format will be resilient against
>    errors, providing an internal facility for the detection of errors
>    and the ability to isolate errors to as few data records as possible.
> 
>    Note that this requirement interacts with the choice of data
>    compression or encryption algorithm.  The use of block compression
>    algorithms can serve to isolate errors to a single compression block,
>    unlike stream compressors, which may fail to resynchronize after a
>    single bit error, invalidating the entire message stream.  Similarly,
>    the use of a stream cipher can serve to isloate errors in the
>    plaintext without amplifying them as, for example, a cipher in CBC

References please!

>    mode can.  See the "Recommended Compression Error Resilience
>    Strategy" and "Recommended Encryption Error Resilience Strategy"
>    sections below for more on this interaction.
> 
>    The IPFIX message format does not support data integrity assurance.
>    It is assumed that advanced error correction will be provided
>    externally.  For simple error detection support, checksums may be
>    attached to messages via IPFIX Options according to the Message
>    Checksum Options Template defined below.

I'd much prefer a csum IE.

> 
> 4.6.  Creator Authentication and Confidentiality
> 
>    Storage of flow data across long time scales may also require
>    assurance that no unauthorized entity can read or modify the stored
>    data.  Asymmetric-key cryptography can be applied to this problem, by
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008                [Page 9]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    signing flow data with the private key of the creator, and encrypting
>    it with the public keys of those authorized to read it.  The ideal
>    flow storage format will support the encryption and signing of flow
>    data.
> 
>    As with error correction, this problem has been addressed well at a
>    layer below that addressed by this document.  Instead of specifying a

Refs?

>    particular choice of encryption technology, we can leverage the fact
>    that existing cryptographic technologies work quite well on data

"quite well"?

>    stored in files to meet this requirement.
> 
>    Beyond support for the use of TLS for transport over TCP or DTLS for
>    transport over SCTP or UDP, both of which provide transient
>    authentication and confidentiality, the IPFIX protocol does not
>    support this requirement directly.  It is assumed that this

"It is assumed"? -> "This requirement MUST"

>    requirement will be met externally.
> 
> 4.7.  Anonymization and Obfuscation
> 
>    To ensure the privacy of individuals and organizations at the
>    endpoints of communications represented by flow records, it is often
>    necessary to obfuscate or anonymize stored and exported flow data.
>    The ideal flow storage format will provide for a notation that a
>    given information element on a given record type represents
>    anonymized, rather than real, data.
> 
>    The IPFIX message format presently has no support for anonymization
>    notation.  It should be noted that anonymization is one of the
>    requirements given for IPFIX in RFC 3917 [RFC3917].  The decision to
>    qualify this requirement with 'MAY' and not 'MUST' in the
>    requirements document, and its subsequent lack of specification in
>    the current version of the IPFIX protocol, is due to the fact that
>    anonymization algorithms are still a research issue, and that there
>    currently exist no standardized methods for anonymization.
> 
>    Simple anonymization notation may be attached to templates via IPFIX
>    Options according to the Template Anonymization Options Template
>    defined below.
> 
> 4.8.  Performance Characteristics
> 
>    The ideal standard flow storage format will not have a significant
>    negative impact on the performance of the application implementing
>    it.  This is a non-functional requirement, but it is important to
>    note that a standard that implies a performance penalty is unlikely
>    to be widely implemented and adopted.
> 
>    A static analysis of the IPFIX message format would seem to suggest
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 10]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    that implementations of it are not particularly prone to slowness;
>    indeed, a template-based data representation is more easily subject
>    to optimization for common cases than representations that embed
>    structural information directly in the data stream (e.g.  XML).
>    However, a full analysis of the impact of using IPFIX messages as a
>    basis for flow data storage on read/write performance will require
>    more implementation experience and performance measurement.
> 
> 
> 5.  Survey of Existing Flow and Trace File Formats

Who selected these formats and why? How was the selection made?

> 
> 5.1.  NetFlow V5/V7

I think we use lowercase v: v5 and v7.

Do you consider that v7 is widely used?

> 
>    One de facto standard for the storage of flow data collected via
>    Cisco NetFlow V5 or V7 is to serialize a stream of "raw" NetFlow
>    datagrams into files.  These NetFlow PDU files consist of a
>    collection of header- prefixed blocks (corresponding to the datagrams
>    as received on the wire) containing fixed-length binary flow records.
>    NetFlow V5 and V7 data may be mixed within a given file, as the
>    header on each datagram defines the NetFlow version of the records
>    following; there is indeed very little difference between the two
>    record formats.
> 
>    NetFlow V5/V7 PDU files are neither extensible nor self-describing;
>    however, their status as a de facto standard means the definition of
>    the data format is well-understood.  Indexing, compression, error
>    detection and correction, authentication, and confidentiality must be
>    handled externally.
> 
> 5.2.  Argus 2
> 
>    QoSient's Argus (as of version 2.0.6) uses a file format based upon a
>    stream of type-and-length prefixed records.  There are two general
>    types of records in this stream, management records and flow records.
>    Management records export flow collection statistics, much like the
>    recommended scoped data records in the IPFIX protocol.  Flow records
>    contain information about a single flow each, and are further typed
>    based upon the protocol of the flow (e.g., IP, ICMP, ARP).  The Argus
>    file format natively spports bidirectional flow export, as each flow
>    record contains both forward and reverse counters.
> 
>    The Argus tools support a transport protocol that simply encapsulates
>    a record stream over a TCP connection.  Transport is collector-
>    initiated; that is, a collector establishes a connection to an
>    exporter in order to read a record stream.
> 
>    Argus files are not self-describing; that is, only the Argus tools
>    themselves encapsulate the definition of each of the record types.
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 11]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    The Argus file format is not extensible without changing the Argus
>    implementation.  Argus provides no indexing facility for its file
>    format, though records are roughly sorted by record generation time.
>    Compression, error correction, authentication, and confidentiality
>    are handled externally to the format, and are available as with all
>    files.  There is no special support for data obfuscation in the
>    format.
> 
> 5.3.  SiLK
> 
>    The CERT/NetSA SiLK tools use a set of fixed-length binary record
>    formats.  Each file is prefixed with a header which denotes which
>    record format the file is stored in.  These record formats are
>    differentiated by the presence or absence of certain fields; in this
>    way, each format identifier is essentially a short-hand identifier
>    for a template describing the record.  This also implies that only
>    one type of record may be stored in any given file.
> 
>    As with Argus, SiLK files are not self-describing and are not
>    extensible.  SiLK provides no indexing facility, though files are
>    generally stored in flow end time order; and when used for archival
>    storage, information about sensors and flow times appearing in each
>    file is stored in the file path name.  Compression is handled

Actually this can be done for any format here.

>    internally to the file format, and allows the storage of compressed
>    data in a file with uncompressed headers, and a guarantee of
>    compression block boundary alignment with record boundaries.  Error
>    correction, authentication, and confidentiality can be handled
>    externally.  There is no special support for data obfuscation in the

obfuscation? Which IPFIX calls anonymisation?

>    SiLK file format.
> 
> 5.4.  libpcap dumpfile
> 
>    The libpcap dumpfile format is a packet trace format rather than a
>    flow file format, so it does not address any of the requirements
>    outlined above.  However, it is used widely in a use case (data
>    storage and distribution for network measurement research) similar to
>    one addressed by the format proposed in this draft, so we include it
>    here.
> 
>    libpcap dumpfiles consist of a file header containing information
>    common to the whole file (most importantly, the datalink layer, for
>    interpretation of the datalink headers on each frame), followed by a
>    set of raw captured frame records each prefixed by a frame header
>    containing timestamp and length information.  The format is not
>    particularly flexible or self-describing, nor does it need to be:
>    undecoded frames are about as semantically simple as network traffic
>    data can get.
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 12]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    However, the simplicity and ubiquity of the libpcap dumpfile format
>    has led to its becoming a de facto standard for the distribution of
>    packet trace data for Internet measurement applications.  We propose
>    the file format described in this draft in part as an analogue to the
>    libpcap dumpfile format for flow data.
> 
>    Note that libpcap dumpfiles could be used as a storage format for any
>    unidirectional, datagram-oriented protocol such as IPFIX or NetFlow,
>    simply by storing the captured export session.  However, this has
>    several important drawbacks.  First, the additional per-packet
>    headers provided by pcap are redundant in the case of IPFIX, as
>    length and export time are already available in the IPFIX Message
>    Header.  Second, the link, network, and transport layer headers are
>    stored in a dumpfile; these are not necessary for the successful
>    interpretation of an IPFIX Message, and add additional decode
>    overhead.  Third, a file created by capturing an export session may
>    require additional processing to reassemble fragmented datagrams in
>    the message stream.
> 
> 
> 6.  IPFIX File Format Description
> 
>    An IPFIX file, as defined by this draft and elaborated below, is at
>    its core simply an IPFIX Message stream serialized to some
>    filesystem.  Any valid serialized IPFIX Message stream MUST be
>    accepted by a File Reader as a valid IPFIX file.  In this way, the
>    filesystem is simply treated as another IPFIX Transport alongside
>    SCTP, TCP, and UDP, although one with unusually high latency, as the
>    File Reader and File Writer are not necessarily synchronized in time,
>    unlike IPFIX Collecting and Exporting Processes.

The EP and CP are not synch'd at all.

> 
>    An IPFIX File Reader MUST accept as valid any IPFIX message stream
>    that would be considered valid by one or more of the other defined
>    IPFIX transport layers.  Practically, this means that the union of
>    template management features supported by SCTP, TCP, and UDP MUST be
>    supported in IPFIX Files.  The following requirements apply to IPFIX
>    File Readers:
> 
>    o  File Readers MUST accept IPFIX Messages containing Template Sets,
>       Options Template Sets, and Data Sets within the same message, as
>       with IPFIX over TCP or UDP.
> 
>    o  File Readers MUST accept Template Sets that define templates
>       already defined within the file, as may occur with template
>       retransmission when using IPFIX over UDP as described in section
>       10.3.6 of the IPFIX Protocol draft [I-D.ietf-ipfix-protocol].  In
>       the event of a conflict between a resent definition and a previous
>       definition, the File Reader MUST assume that the new template
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 13]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>       replaces the old, as consistent with UDP template expiration and
>       ID reuse.
> 
>    o  File Readers MUST accept Template Withdrawals as described in
>       section 8 of the IPFIX Protocol draft [I-D.ietf-ipfix-protocol],
>       provided that the Template to be withdrawn is defined, as is the
>       case with IPFIX over TCP and SCTP.

I'm thinking that FILE is essentially a layer below EP / CP but above 
transport, something like this:

	+------+        +------+
	|  EP  |        |  CP  |
	+------+--------+------+
	|         File         |
	+----------------------+
	|       transport      |
	+----------------------+

> 
>    However, for representation simplicity and read performance, File
>    Writers SHOULD use the following template and scope management
>    strategy:
> 
>    o  File Writers SHOULD emit Template Sets and Options Template Sets

I think this is a MUST, since data ahead of the necessary Templates 
could be discarded and is therefore of no value. Or put another way, if 
the Template is in the file somewhere, rewrite the file to put the 
Template at the start.

>       to appear at the beginning of the file, before any Data Sets, to
>       ensure all Templates are available and can be inspected before any
>       data is read.  If the set of Templates used within a File is not
>       known when the File Writer starts writing the File, the File
>       Writer MAY interleave Template Sets and Options Template Sets with
>       Data Sets within the File, but SHOULD write each Template Set or
>       Options Template Set before any Data Set described by that
>       Template.
> 
>    o  File Writers SHOULD emit special Data Records described by Options
>       Templates at the beginning of the file after Template Sets and
>       Options Template Sets as above, but before any other Data Records,
>       in the following order:
> 
>       *  Time window order records described by the File Time Window
>          Options Template as defined in section 6.2.3 below; followed by
> 
>       *  commonPropertiesId definitions as described in "Reducing
>          Redundancy in IPFIX and PSAMP Reports"
>          [I-D.ietf-ipfix-reducing-redundancy]; followed by
> 
>       *  Semantics records as described in "Extended Type Information
>          for IPFIX Enterprise-Specific Information Elements"
>          [I-D.boschi-ipfix-extended-type]; followed by
> 
>       *  Anonymization notation records described by the Template
>          Anonymization Options Template as defined in section 6.2.2
>          below.
> 
>    o  File Writers SHOULD emit Data Records described by Options

Again, MUST.

>       Templates to appear in the file before any Data Records which
>       depend on the scopes defined by those options.
> 
>    o  File Writers SHOULD use Template Withdrawals to withdraw Templates

Again, MUST.

>       if template IDs need to be reused.  In this case, the new

You'd have to generate them for UDP, because they won't exist.

> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 14]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>       Templates reusing those IDs SHOULD appear directly in the file
>       after the Template Withdrawals making the IDs available for reuse.
>       Template Withdrawals SHOULD NOT be used unless necessary to reuse
>       template IDs.

Why?

> 
>    Each IPFIX File is generally synonymous with a single Transport
>    Session.  File Writers SHOULD store the Templates and Options
>    required to decode the data within the File in the File itself, and
>    File Readers SHOULD NOT use Templates or Options defined in one file
>    to decode or interpret Data Sets in another.

What if I want to save each SCTP stream to a different file?

> 
>    However, some applications, particularly those storing large
>    collections of data over long periods of time, may benefit from the
>    ability to treat a collection of IPFIX Files as a single Transport
>    Session.  A File Reader MAY be configurable to treat a collection of
>    Files (e.g., all the files in a directory) as a single Transport
>    Session.  However, a File Reader MUST NOT treat a single IPFIX File
>    as containing multiple Transport Sessions.

So we need a new file if/when the Transport Session shuts down?

> 
>    File Writers SHOULD write IPFIX Messages within an IPFIX File in
>    ascending Export Time order.  If a File Writer is writing data

Here, ascending order. Below...

>    collected from an IPFIX Collecting Process, the Export Time SHOULD be
>    the export time as reported by the remote IPFIX Exporting Process;
>    otherwise, the Export Time should be the time at which the message
>    was written to the file.
> 
>    By default, File Writers MAY write records to an IPFIX File in any
>    order.  However, File Writers that write flow records to an IPFIX

... any order. Confusing.

>    File in flowStartTime or flowEndTime order SHOULD be consistent in
>    this ordering within each File.

Why? And which are we recommending here, if it's a standard?

> 
>    If an IPFIX File uses the technique described in "Reducing Redundancy
>    in IPFIX and PSAMP Reports" [I-D.ietf-ipfix-reducing-redundancy] AND
>    all of the non-Options Templates in the File contain the

Do you mean "contain *only* the" ?

>    commonPropertiesId Information Element, a File Reader MAY assume the
>    set of commonPropertiesId definitions provides a complete table of
>    contents for the file, for searching purposes.
> 
> 6.1.  Recommended Information Elements for IPFIX Files
> 
>    The following information elements are used by the options templates
>    below to allow IPFIX message streams to meet the requirements
>    outlined above without extension to the message format or protocol.
>    IPFIX File Readers and Writers SHOULD support these Information

MUST?

>    Elements as defined below.
> 
>    In addition, IPFIX File Readers and Writers SHOULD support the
>    Information Elements defined in "Extended Type Information for IPFIX
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 15]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type] in order to support self-description
>    of Enterprise-Specific Information Elements and anonymization
>    notation.
> 
> 6.1.1.  collectionTimeMilliseconds
> 
>    Description:   The absolute timestamp at which the data within the
>       scope containing this IE was received by a Collecting Process.

When an Exporting Process writes to a file, there's no CP time.

>       This IE SHOULD be bound to its containing IPFIX Message via an
>       options record and the messageScope IE, as defined below.

Say where, ie 6.1.6.

> 
>    Abstract Data Type:   dateTimeMilliseconds
> 
>    ElementId:   TBD1
> 
>    Status:   Proposed
> 
> 6.1.2.  informationElementAnonymizationType

It's a flag, not a type.

> 
>    Description:   A description of the anonymization status of an IPFIX
>       information element within a template.  If this field is FALSE,

"Template"

>       the corresponding IE is not anonymized; to the best ability of the
>       Exporting Process to determine, it represents a real value.  If
>       this field is TRUE, the corresponding IE is anonymized; to the
>       best ability of the Exporting Process to determine, it represents
>       a value that has been transformed to maintain privacy.  Note that
>       if no informationElementAnonymizationType is specified for an
>       information element, it is assumed to be FALSE, or not anonymized.

"Information Element"

> 
>    Abstract Data Type:   boolean
> 
>    ElementId:   TBD2
> 
>    Status:   Proposed
> 
> 6.1.3.  maxExportSeconds
> 
>    Description:   The absolute Export Time of the latest IPFIX message
>       within the scope containing this IE.  This IE SHOULD be bound to
>       its containing IPFIX Transport Session (i.e., File) via an options
>       record and the sessionScope IE, as defined below, and SHOULD

Say where, ie 6.1.9.

>       appear only once in a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 16]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    ElementId:   TBD3
> 
>    Status:   Proposed
> 
>    Units:   seconds

Does this give good granularity?

> 
> 6.1.4.  maxFlowEndSeconds
> 
>    Description:   The latest absolute timestamp of the last packet
>       within any Flow within the scope containing this IE, rounded up to
>       the second.  This IE SHOULD be bound to its containing IPFIX
>       Transport Session (i.e., File) via an options record and the
>       sessionScope IE, as defined below, and SHOULD appear only once in
>       a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD4
> 
>    Status:   Proposed
> 
>    Units:   seconds

Again, does this give good granularity?

> 
> 6.1.5.  messageMD5Checksum
> 
>    Description:   The MD5 checksum of the IPFIX Message containing this
>       record.  This IE SHOULD be bound to its containing IPFIX Message
>       via an options record and the messageScope IE, as defined below,

Eeuuwww. The message should directly contain its own csum IE.

For "below", again say where.

>       and SHOULD appear only once in a given IPFIX Message.  To

Split to a new paragraph here.

>       calculate the value of this IE, first buffer the containing IPFIX
>       Message, setting the value of this IE to all zeroes.  Then
>       caluclate the MD5 checksum of the resulting buffer as defined in
>       RFC 1321 [RFC1321], place the resulting value in this IE, and
>       export the buffered message.
> 
>    Abstract Data Type:   octetArray (16 bytes)
> 
>    ElementId:   TBD5
> 
>    Status:   Proposed
> 
>    Reference:   RFC 1321, The MD5 Message-Digest Algorithm [RFC1321]
> 
> 6.1.6.  messageScope
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 17]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Description:   The presence of this Information Element as scope in
>       an Options Template signifies that the options described by the
>       Template apply to the IPFIX Message that contains them.  It is
>       defined for general purpose message scoping of options, and
>       proposed specifically to allow the attachment a checksum to a
>       message via IPFIX Options.  The value of this Information Element
>       MUST be written as 0 by the File Writer or Exporting Process.  The
>       value of this Information Element MUST be ignored by the File
>       Reader or the Collecting Process.
> 
>    Abstract Data Type:   octet

The size should really be zero, right?

> 
>    ElementId:   TBD6
> 
>    Status:   Proposed
> 
> 6.1.7.  minExportSeconds
> 
>    Description:   The absolute Export Time of the earliest IPFIX message
>       within the scope containing this IE.  This IE SHOULD be bound to
>       its containing IPFIX Transport Session (i.e., File) via an options
>       record and the sessionScope IE, as defined below, and SHOULD
>       appear only once in a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD7
> 
>    Status:   Proposed
> 
>    Units:   seconds
> 
> 6.1.8.  minFlowStartSeconds
> 
>    Description:   The earliest absolute timestamp of the first packet
>       within any Flow within the scope containing this IE, rounded down
>       to the second.  This IE SHOULD be bound to its containing IPFIX
>       Transport Session (i.e., File) via an options record and the
>       sessionScope IE, as defined below, and SHOULD appear only once in
>       a given IPFIX File.
> 
>    Abstract Data Type:   dateTimeSeconds
> 
>    ElementId:   TBD8
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 18]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Status:   Proposed
> 
>    Units:   seconds
> 
> 6.1.9.  sessionScope
> 
>    Description:   The presence of this Information Element as scope in
>       an Options Template signifies that the options described by the
>       Template apply to the IPFIX Transport Session that contains them.
>       Note that as all options are implicitly scoped to Transport
>       Session and Observation Domain, this Information Element is
>       equivalent to a "null" scope.  It is defined for general purpose
>       session scoping of options, and proposed specifically to allow the
>       attachment of time window to a file via IPFIX Options.  The value

Split to a new paragraph.

>       of this Information Element MUST be written as 0 by the File
>       Writer or Exporting Process.  The value of this Information
>       Element MUST be ignored by the File Reader or the Collecting
>       Process.
> 
>    Abstract Data Type:   octet

Again, the size should really be zero, right?

> 
>    ElementId:   TBD9
> 
>    Status:   Proposed
> 
> 6.2.  Recommended Options Templates for IPFIX Files
> 
>    The following Options Templates allow IPFIX message streams to meet
>    the requirements outlined above without extension to the message
>    format or protocol.  They are defined in terms of existing
>    Information Elements defined in the IPFIX Information Model
>    [I-D.ietf-ipfix-info], the extended type Information Elements defined
>    in "Extended Type Information for IPFIX Enterprise-Specific
>    Information Elements" [I-D.boschi-ipfix-extended-type], as well as
>    Information Elements defined in the section above.  IPFIX File

Say which section above.

>    Readers and Writers SHOULD support these options templates as defined
>    below.
> 
>    In addition, IPFIX File Readers and Writers SHOULD support the
>    Options Templates defined in "Extended Type Information for IPFIX
>    Enterprise-Specific Information Elements"
>    [I-D.boschi-ipfix-extended-type] in order to support self-description
>    of enterprise-specific Information Elements.
> 
> 6.2.1.  Message Checksum Options Template
> 
>    The Message Checksum Options Template specifies the structure of a
>    Data Record for attaching an MD5 message checksum to an IPFIX
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 19]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Message.  An MD5 message checksum as described MAY be used if long-
>    term data integrity is important to the application.  The described
>    Data Record MUST appear only once per IPFIX Message.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +--------------------+----------------------------------------------+
>    | IE                 | Description                                  |
>    +--------------------+----------------------------------------------+
>    | messageScope       | A marker denoting this Option applies to the |
>    |                    | whole IPFIX message; content is ignored.     |
>    |                    | This Information Element MUST be defined as  |
>    |                    | a Scope Field.                               |

Consider inserting some vertical whitespace here to make these more 
readable.

>    | messageMD5Checksum | The MD5 checksum of the containing IPFIX     |
>    |                    | Message.                                     |
>    +--------------------+----------------------------------------------+
> 
> 6.2.2.  Template Anonymization Options Template
> 
>    The Template Anonymization Options Template specifies the structure
>    of a Data Record for attaching anonymization notation information to
>    Information Elements in specified Template Records.  A Data Record
>    described by this Template SHOULD appear for each Information Element
>    within a Template known by the Exporting Process or File Writer to
>    contain anonymized data.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +-------------------------------------+-----------------------------+
>    | IE                                  | Description                 |
>    +-------------------------------------+-----------------------------+
>    | templateId                          | The Template ID of the      |
>    |                                     | template this record        |
>    |                                     | describes; it is assumed to |
>    |                                     | be valid within the         |
>    |                                     | Observation Domain ID of    |
>    |                                     | the containing IPFIX        |
>    |                                     | Message, and MUST identify  |
>    |                                     | a Template that has already |
>    |                                     | been exported.  This        |
>    |                                     | Information Element MUST be |
>    |                                     | defined as a Scope Field.   |
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 20]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | informationElementId                | The Information Element     |
>    |                                     | identifier of the           |
>    |                                     | Information Element within  |
>    |                                     | the specified Template this |
>    |                                     | record describes.  This     |
>    |                                     | Information Element MUST be |
>    |                                     | defined as a Scope Field.   |
>    | privateEnterpriseNumber             | The Private Enterprise      |
>    |                                     | number of the Information   |
>    |                                     | Element within the          |
>    |                                     | specified Template this     |
>    |                                     | record describes.  May be 0 |
>    |                                     | if this record describes a  |
>    |                                     | public Information Element. |
>    |                                     | This Information Element    |
>    |                                     | MUST be defined as a Scope  |
>    |                                     | Field.                      |

Put the PEN last so it can be omitted if zero.

>    | informationElementAnonymizationType | The anonymization type of   |
>    |                                     | the specified Information   |
>    |                                     | Element.                    |
>    +-------------------------------------+-----------------------------+
> 
> 6.2.3.  File Time Window Options Template
> 
>    The File Time Window Options Template specifies the structure of a
>    Data Record for attaching a time window to an IPFIX File; this Data
>    Record is referred to as a time window record.  A time window record
>    defines the earliest flow start time and the latest flow end time of
>    the flow records within a File.  One and only one time window record
>    MAY appear within an IPFIX File if the time window information is
>    available; a File Writer MUST NOT write more than one time window
>    record to an IPFIX File.  A File Writer that writes a time window
>    record to a File MUST NOT write any Flow with a start time before the
>    beginning of the window or an end time after the end of the window to
>    that File.
> 
>    The template SHOULD contain the following Information Elements:
> 
>    +---------------------+---------------------------------------------+
>    | IE                  | Description                                 |
>    +---------------------+---------------------------------------------+
>    | sessionScope        | A marker denoting this Option applies to    |
>    |                     | the whole IPFIX Transport Session (i.e.,    |
>    |                     | IPFIX File); content is ignored.  This      |
>    |                     | Information Element MUST be defined as a    |
>    |                     | Scope Field.                                |
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 21]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | minFlowStartSeconds | The start time of the earliest flow in the  |
>    |                     | Transport Session (i.e., File) in epoch     |
>    |                     | seconds.                                    |
>    | maxFlowEndSeconds   | The end time of the latest flow in the      |
>    |                     | Transport Session (i.e., File) in epoch     |
>    |                     | seconds.                                    |
>    +---------------------+---------------------------------------------+
> 
> 6.2.4.  Export Session Details Options Template
> 
>    The Export Session Details Options Template specifies the structure
>    of a Data Record for recording the details of an IPFIX Transport
>    Session in an IPFIX File.  It is intended for use in storing a single
>    complete IPFIX Transport Session in a single IPFIX File.  The
>    described Data Record SHOULD appear only once in a given IPFIX File.
> 
>    The template SHOULD contain the following Information Elements,
>    subject to applicability as noted on each Information Element:
> 
>    +----------------------------+--------------------------------------+
>    | IE                         | Description                          |
>    +----------------------------+--------------------------------------+
>    | sessionScope               | A marker denoting this Option        |
>    |                            | applies to the whole IPFIX Transport |
>    |                            | Session (i.e., IPFIX File); content  |
>    |                            | is ignored.  This Information        |
>    |                            | Element MUST be defined as a Scope   |
>    |                            | Field.                               |
>    | exporterIPv4Address        | IPv4 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv4     |
>    |                            | interface.  For multi-homed SCTP     |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Exporting Process.                   |
>    | exporterIPv6Address        | IPv6 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv6     |
>    |                            | interface.  For multi-homed SCTP     |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Exporting Process.                   |
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 22]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | exporterTransportPort      | The source port from which the       |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.                       |
>    | collectorIPv4Address       | IPv4 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv4 interface.  For multi-homed  |
>    |                            | SCTP associations, this SHOULD be    |
>    |                            | the primary path endpoint address of |
>    |                            | the Collecting Process.              |
>    | collectorIPv6Address       | IPv6 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv6 interface.  For multi-homed  |
>    |                            | SCTP associations, this SHOULD be    |
>    |                            | the primary path endpoint address of |
>    |                            | the Collecting Process.              |
>    | collectorTransportPort     | The destination port on which the    |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.                       |
>    | collectorTransportProtocol | The IP Protocol Identifier of the    |
>    |                            | transport protocol used to transport |
>    |                            | Messages within this Transport       |
>    |                            | Session.                             |

However, it's not specific to the Collector.

>    | collectorProtocolVersion   | The version of the IPFIX Protocol    |
>    |                            | used to transport Messages within    |
>    |                            | this Transport Session.              |

And again. Also below.

>    | minExportSeconds           | The Export Time of the first Message |
>    |                            | in the Transport Session.            |
>    | maxExportSeconds           | The Export Time of the last Message  |
>    |                            | in the Transport Session.            |
>    +----------------------------+--------------------------------------+
> 
> 6.2.5.  Message Details Options Template
> 
>    The Message Details Options Template specifies the structure of a
>    Data Record for attaching additional export details to an IPFIX
>    Message.  These details include the time at which a message was
>    received and information about the export and collection
>    infrastructure used to transport the Message.
> 
>    The template SHOULD contain the following Information Elements,
>    subject to applicability as noted for each Information Element.  Note
>    that when used in conjunction with the Export Session Details Options
>    Template, when storing a single complete IPFIX Transport Session in
>    an IPFIX File, this template SHOULD contain only the messageScope and
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 23]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    collectionTimeMilliseconds Information Elements.
> 
>    +----------------------------+--------------------------------------+
>    | IE                         | Description                          |
>    +----------------------------+--------------------------------------+
>    | messageScope               | A marker denoting this Option        |
>    |                            | applies to the whole IPFIX message;  |
>    |                            | content is ignored.  This            |
>    |                            | Information Element MUST be defined  |
>    |                            | as a Scope Field.                    |
>    | collectionTimeMilliseconds | The absolute time at which this      |
>    |                            | Message was received by the IPFIX    |
>    |                            | Collecting Process.                  |
>    | exporterIPv4Address        | IPv4 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv4     |
>    |                            | interface, and if this information   |
>    |                            | is not available via the Export      |
>    |                            | Session Details Options Template.    |
>    |                            | For multi-homed SCTP associations,   |
>    |                            | this SHOULD be the primary path      |
>    |                            | endpoint address of the Exporting    |
>    |                            | Process.                             |
>    | exporterIPv6Address        | IPv6 address of the IPFIX Exporting  |
>    |                            | Process from which the Messages in   |
>    |                            | this Transport Session were          |
>    |                            | received.  Present only for          |
>    |                            | Exporting Processes with an IPv6     |
>    |                            | interface, and if this information   |
>    |                            | is not available via the Export      |
>    |                            | Session Details Options Template.    |
>    |                            | For multi-homed SCTP associations,   |
>    |                            | this SHOULD be the primary path      |
>    |                            | endpoint address of the Exporting    |
>    |                            | Process.                             |
>    | exporterTransportPort      | The source port from which the       |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.  Present only if this |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 24]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    | collectorIPv4Address       | IPv4 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv4 interface, and if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.  For multi-homed SCTP      |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Collecting Process.                  |
>    | collectorIPv6Address       | IPv6 address of the IPFIX Collecting |
>    |                            | Process which received the Messages  |
>    |                            | in this Transport Session.  Present  |
>    |                            | only for Collecting Processes with   |
>    |                            | an IPv6 interface, and if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.  For multi-homed SCTP      |
>    |                            | associations, this SHOULD be the     |
>    |                            | primary path endpoint address of the |
>    |                            | Collecting Process.                  |
>    | collectorTransportPort     | The destination port on which the    |
>    |                            | Messages in this Transport Session   |
>    |                            | were received.  Present only if this |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
>    | collectorTransportProtocol | The IP Protocol Identifier of the    |
>    |                            | transport protocol used to transport |
>    |                            | Messages within this Transport       |
>    |                            | Session.  Present only if this       |
>    |                            | information is not available via the |
>    |                            | Export Session Details Options       |
>    |                            | Template.                            |
>    | collectorProtocolVersion   | The version of the IPFIX Protocol    |
>    |                            | used to transport Messages within    |
>    |                            | this Transport Session.  Present     |
>    |                            | only if this information is not      |
>    |                            | available via the Export Session     |
>    |                            | Details Options Template.            |
>    +----------------------------+--------------------------------------+
> 
> 6.3.  Recommended Compression Error Resilience Strategy
> 
>    Note that, since any file may be compressed and decompressed with a
>    variety of widely available tools implementing a variety of
>    compression standards (both specified and de facto), compression of
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 25]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    IPFIX File data can be accomplished externally.  However, compression
>    at the file level is not particularly resilient to errors; in the
>    worst case, a single bit error in a stream-compressed file may result
>    in the loss of the entire file.
> 
>    To limit the impact of errors on the recoverability of compressed
>    data, we recommend the use of block compression where possible.
>    Ideally, the block compression algorithm should support the
>    identification and isolation of blocks containing errors; bzip2 is an
>    example of such a block compressor.
> 
>    Since the block boundary of a block-compressed IPFIX File may fall in
>    the middle of an IPFIX Message, resynchronization of an IPFIX Message
>    stream by a File Reader after a compression error requires some care.
>    The beginning of an IPFIX Message may be identified by its header
>    signature (the Version field of the Message Header, 0x00 0x0A,
>    followed by a 16-bit Message Length), but simply searching for the
>    first occurance of the Version field is insufficient, since these two
>    bytes may occur in valid IPFIX Template or Data Sets.
> 
>    Therefore, we propose the following algorithm for File Readers to
>    resynchronize an IPFIX Message Stream after skipping a compressed
>    block containing errors:
> 
>    1.  Search after the error for the first occurance of the byte string
>        0x00, 0x0A (the IPFIX Message Header Version field.)
> 
>    2.  Treat this field as the beginning of a candidate IPFIX Message.
>        Read the two bytes following the Version field as a Message
>        Length, and seek to that offset from the beginning of the
>        candidate IPFIX Message.
> 
>    3.  If the first two bytes after the candidate IPFIX Message are
>        0x00, 0x0A (i.e., the IPFIX Message Header Version field of the
>        next message in the stream), or if the end of the file is reached
>        precisely at the end of the candidate IPFIX Message, presume that
>        the candidate IPFIX Message is valid, and begin reading the IPFIX
>        File from the start of the candidate IPFIX Message.

I think this is insufficient: one should iterate over the entire message 
to the end to be sure.

> 
>    4.  If not, or if the seek reaches end-of-file or another block
>        containing errors before finding the end of the candidate
>        message, go back to step 1, starting the search two bytes from
>        the start of the candidate IPFIX Message.
> 
>    The algorithm above will improperly identify a non-message as a
>    message approximately 1 in 2^32 times, assuming random IPFIX data.
>    It may be expanded to consider multiple candidate IPFIX Messages in
>    order to increase reliability.

It should be, since the random nature of the data means it'll probably 
fail 9 times out of 10.

> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 26]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    In applications (e.g. archival storage) in which error resilience is
>    very important, File Writers SHOULD use block compression algorithms,
>    and MAY attempt to align IPFIX Messages within compression blocks to
>    ease resynchronization after errors, if such is supported by the
>    chosen block compressor.  File Readers SHOULD use the
>    resynchronization algorithm above to minimize data loss due to
>    compression errors.
> 
> 6.4.  Recommended Encryption Error Resilience Strategy
> 
>    File-level encryption has error resiliency issues similar to file-
>    level compression.  Single bit errors in the encrypted data stream
>    can result in unreadability of the entire remaining file, dependent
>    on the encryption method used.  The use of CBC (Cipher Block
>    Chaining) mode, which suffers from this low error resilience, is
>    relatively common.
> 
>    In applications (e.g. archival storage) in which error resilience is
>    very important, File Writers SHOULD use a stream cipher, for example
>    a block cipher in OFB (Output Feedback) mode (often referred to as
>    stream mode) instead of modes like CBC when encrypting, since errors
>    are not amplified by stream ciphers: A single-bit error in the
>    ciphertext results in a single bit error in the plaintext.
>    Alternatively File Writers SHOULD use any other cipher which can
>    resynchronize after bit errors.  An example is a block cipher in CBC
>    mode that is reinitialized after a specific amount of data has been
>    encrypted.  The maximum data loss per bit-error is then up to the
>    next reinitialization point.  In this case, File Writers SHOULD also
>    use the Message Checksum Options Template to attach a checksum to
>    each IPFIX Message in the IPFIX File, in order to support the
>    recognition of errors in the decrypted data.
> 
> 
> 7.  Applicability of IPFIX Files
> 
>    This section describes the specific applicability of IPFIX Files to
>    various use cases.  IPFIX Files are particularly useful in a flow
>    collection and processing infrastructure using IPFIX for flow export.
>    We explore the applicability and provide guidelines for using IPFIX
>    files during the implementation and operation of IPFIX Collecting
>    Processes.
> 
> 7.1.  Testing IPFIX Collecting Processes
> 
>    IPFIX Files can be used to store IPFIX Messages for the testing of
>    IPFIX Collecting Processes.  A variety of test cases may be stored in
>    IPFIX Files.  First, IPFIX data sets collected in real network
>    environments and stored in an IPFIX File can be used as input to
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 27]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    check the behavior of new or extended implementations of IPFIX
>    Collectors.  Furthermore, IPFIX Files could be used to validate the
>    operation of a given IPFIX Collecting Process in a new environment,
>    i.e., to test with recorded IPFIX data from the target network before
>    installing the Collecting Process in the network.
> 
>    The IPFIX File format can also be used to store artificial, non-
>    compliant reference messages for specific Collecting Process test
>    cases.  Examples for such test cases are sets of IPFIX records with
>    undefined Information Elements, Data Records described by missing
>    Templates, or incorrectly framed messages or data sets.
>    Representative error handling test cases are defined in "IPFIX
>    Testing" [I-D.ietf-ipfix-testing].
> 
>    Furthermore, fast replay of IPFIX records stored in a file can be
>    used for stress/load tests (e.g., high rate of incoming Data Records,
>    large Templates with high Information Element counts), as described
>    in "IPFIX Testing" [I-D.ietf-ipfix-testing].  The provisioning and
>    use of a set of reference files for testing simplifies the
>    performance of tests and increases the comparability of test results.
> 
>    Note that an extremely simple IPFIX Exporting Process may be crafted
>    for testing purposes by simply reading an IPFIX File and transmitting
>    it directly to a Collecting Process.  Similarly, an extremely simple
>    Collecting Process may be crafted for testing purposes by simply
>    accepting connections and/or IPFIX Messages from Exporting Processes
>    and writing the session's message stream to an IPFIX File.
> 
> 7.2.  Storage of IPFIX-collected Flow Data
> 
>    IPFIX Files can also, naturally, be used to store flow data collected
>    by an IPFIX Collecting Process; indeed, this was one of the primary
>    initial motivations behind the file format described within this
>    document.  Using IPFIX Files as such allows IPFIX implementations to
>    leverage substantially the same code for flow export and flow
>    storage.  In addition, the storage of single Transport Sessions in
>    IPFIX Files is particularly important for network measurement
>    research, allowing repeatability of experiments by providing a format
>    for the storage and exchange of IPFIX flow trace data much as the
>    libpcap format is used for experiments on packet trace data.
> 
>    As noted in the section above, the simplest way for a Collecting
>    Process to store the data collected in a single Transport Session is
>    to simply write the incoming IPFIX Messages to a file as they are
>    read.  However, while the resulting files are valid IPFIX Files, they
>    are lacking information about the IPFIX Transport Session used to
>    export them, such as the network addresses of the Exporting and
>    Collecting Processes and the protocols used to transport them.  An
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 28]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    IPFIX File Writer MAY store a single IPFIX Transport Session in an
>    IPFIX File and record information about the Transport Session using
>    the Export Session Details Options Template described above.
> 
>    Additional per-Message information MAY be recorded by the File Writer
>    using the Message Details Options Template described above.  Per-
>    message information includes the time at which each IPFIX Message was
>    received at the Collecting Process, and can be used to resend IPFIX
>    Messages while keeping the original measurement plane traffic
>    profile.  This Options Template also allows the storage of the export
>    session metainformation provided the Export Session Details Options

Isn't it "meta information" ?

>    Template, for storing information from multiple Transport Sessions in
>    the same IPFIX File.
> 
> 
> 8.  Examples
> 
>    [TODO in revision -05 or later]
> 
> 
> 9.  Security Considerations
> 
>    The IPFIX-based file format itself does not directly introduce
>    security issues.  Rather it is used to store information which may
>    for privacy or business issues be considered sensitive.  The file
>    format must therefore provide appropriate procedures to guarantee the
>    integrity and confidentiality of the stored information.

The OS or storage system could also do this.

P.

> 
>    The underlying protocol used to exchange the information that will be
>    stored using the format proposed in this document must as well apply
>    appropriate procedures to guarantee the integrity and confidentiality
>    of the exported information.  Such issues are addressed in separate
>    documents, specifically in the IPFIX Protocol
>    [I-D.ietf-ipfix-protocol].
> 
> 
> 10.  IANA Considerations
> 
>    This document specifies the creation of several new IPFIX Information
>    Elements in the IPFIX Information Element registry located at
>    http://www.iana.org/assignments/ipfix, as defined in section 6.1
>    above.  IANA has assigned the following Information Element numbers
>    for their respective Information Elements as specified below:
> 
>    o  Information Element number TBD1 for the collectionTimeMilliseconds
>       Information Element.
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 29]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    o  Information Element number TBD2 for the
>       informationElementAnonymizationType Information Element.
> 
>    o  Information Element number TBD3 for the maxExportSeconds
>       Information Element.
> 
>    o  Information Element number TBD4 for the maxFlowEndSeconds
>       Information Element.
> 
>    o  Information Element number TBD5 for the messageMD5Checksum
>       Information Element.
> 
>    o  Information Element number TBD6 for the messageScope Information
>       Element.
> 
>    o  Information Element number TBD7 for the minExportSeconds
>       Information Element.
> 
>    o  Information Element number TBD8 for the minFlowStartSeconds
>       Information Element.
> 
>    o  Information Element number TBD9 for the sessionScope Information
>       Element.
> 
>    [NOTE for IANA: The text TBD1, TBD2, TBD3, TBD4, TBD5, TBD6, TBD7,
>    TBD8, and TBD9 should be replaced with the respective assigned
>    Information Element numbers where they appear in this document.]
> 
> 
> 11.  Acknowledgements
> 
>    Thanks to Maurizio Molina, Tom Kosnar, Andreas Kind, and Andrew
>    Johnson for technical assistance with the requirements and their
>    implementation within this specification.
> 
> 
> 12.  References
> 
> 12.1.  Normative References
> 
>    [I-D.ietf-ipfix-protocol]
>               Claise, B., "Specification of the IPFIX Protocol for the
>               Exchange", draft-ietf-ipfix-protocol-24 (work in
>               progress), November 2006.
> 
>    [I-D.ietf-ipfix-info]
>               Quittek, J., "Information Model for IP Flow Information
>               Export", draft-ietf-ipfix-info-15 (work in progress),
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 30]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>               February 2007.
> 
>    [I-D.ietf-ipfix-reducing-redundancy]
>               Boschi, E., "Reducing Redundancy in IP Flow Information
>               Export (IPFIX) and Packet  Sampling (PSAMP) Reports",
>               draft-ietf-ipfix-reducing-redundancy-04 (work in
>               progress), May 2007.
> 
>    [RFC1321]  Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
>               April 1992.
> 
>    [I-D.boschi-ipfix-extended-type]
>               Boschi, E., Mark, L., Trammell, B., and T. Zseby,
>               "Extended Type Information for IPFIX Enterprise-Specific
>               Information Elements", draft-boschi-ipfix-ext-type-00
>               (work in progress), June 2007.
> 
> 12.2.  Informative References
> 
>    [I-D.ietf-ipfix-biflow]
>               Trammell, B. and E. Boschi, "Bidirectional Flow Export
>               using IPFIX", draft-ietf-ipfix-biflow-05 (work in
>               progress), June 2007.
> 
>    [I-D.ietf-ipfix-testing]
>               Schmoll, C. and P. Aitken, "IP Flow Information eXport
>               (IPFIX) Testing", draft-ietf-ipfix-testing-01 (work in
>               progress), June 2007.
> 
>    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
>               "Requirements for IP Flow Information Export (IPFIX)",
>               RFC 3917, October 2004.
> 
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
> 
>    [SAINT2007]
>               Trammell, B., Boschi, E., Mark, L., and T. Zseby,
>               "Requirements for a standardized flow storage solution",
>                in Proceedings of the SAINT 2007 workshop on Internet
>               Measurement Technology, Hiroshima, Japan, January 2007.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 31]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> Authors' Addresses
> 
>    Brian H. Trammell
>    CERT Network Situational Awareness
>    Software Engineering Institute
>    4500 Fifth Avenue
>    Pittsburgh, Pennsylvania  15213
>    United States
> 
>    Phone: +1 412 268 9748
>    Email: bht@cert.org
> 
> 
>    Elisa Boschi
>    Hitachi Europe SAS
>    Immeuble Le Theleme
>    1503 Route les Dolines
>    06560 Valbonne
>    France
> 
>    Phone: +33 4 89874100
>    Email: elisa.boschi@hitachi-eu.com
> 
> 
>    Lutz Mark
>    Fraunhofer Institute for Open Communication Systems
>    Kaiserin-Augusta-Allee 31
>    10589 Berlin
>    Germany
> 
>    Phone: +49 30 3463 7306
>    Email: lutz.mark@fokus.fraunhofer.de
> 
> 
>    Tanja Zseby
>    Fraunhofer Institute for Open Communication Systems
>    Kaiserin-Augusta-Allee 31
>    10589 Berlin
>    Germany
> 
>    Phone: +49 30 3463 7153
>    Email: tanja.zseby@fokus.fraunhofer.de
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 32]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
>    Arno Wagner
>    Swiss Federal Institute of Technology Zurich
>    Gloriastrasse 35
>    8092 Zurich
>    Switzerland
> 
>    Phone: +41 44 632 70 04
>    Email: arno@wagner.name
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 33]
> 
> Internet-Draft                 IPFIX Files                     July 2007
> 
> 
> Full Copyright Statement
> 
>    Copyright (C) The IETF Trust (2007).
> 
>    This document is subject to the rights, licenses and restrictions
>    contained in BCP 78, and except as set forth therein, the authors
>    retain all their rights.
> 
>    This document and the information contained herein are provided on an
>    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
>    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
>    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
>    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Intellectual Property
> 
>    The IETF takes no position regarding the validity or scope of any
>    Intellectual Property Rights or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; nor does it represent that it has
>    made any independent effort to identify any such rights.  Information
>    on the procedures with respect to rights in RFC documents can be
>    found in BCP 78 and BCP 79.
> 
>    Copies of IPR disclosures made to the IETF Secretariat and any
>    assurances of licenses to be made available, or the result of an
>    attempt made to obtain a general license or permission for the use of
>    such proprietary rights by implementers or users of this
>    specification can be obtained from the IETF on-line IPR repository at
>    http://www.ietf.org/ipr.
> 
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights that may cover technology that may be required to implement
>    this standard.  Please address the information to the IETF at
>    ietf-ipr@ietf.org.
> 
> 
> Acknowledgment
> 
>    Funding for the RFC Editor function is provided by the IETF
>    Administrative Support Activity (IASA).
> 
> 
> 
> 
> 
> Trammell, et al.        Expires January 10, 2008               [Page 34]
> 
> 

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 18:13:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBae-0001jT-Ia; Thu, 26 Jul 2007 18:13:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBac-0001hO-RZ
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:13:46 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBab-0001nR-Ts
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:13:46 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id F081828016A83;
	Fri, 27 Jul 2007 00:13:46 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id K1wS4ptflWq1; Fri, 27 Jul 2007 00:13:46 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id CF62328014C90;
	Fri, 27 Jul 2007 00:13:31 +0200 (CEST)
Received: from 130.129.82.248 ([130.129.82.248]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 26 Jul 2007 22:13:30 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 27 Jul 2007 00:13:27 +0200
Subject: Re: [IPFIX] new work item candidate #4: extended types
From: Juergen Quittek <Quittek@netlab.nec.de>
To: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>,
	<muenz@informatik.uni-tuebingen.de>
Message-ID: <C2CEE927.1036F%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] new work item candidate #4: extended types
Thread-Index: AcfPzxo95ZI1Uv8xRJ++1i8BMypyEwAAxZsf
In-Reply-To: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Elisa,

Am 26.07.2007 23:51 Uhr schrieb "Boschi, Elisa" unter
<Elisa.Boschi@Hitachi-eu.com>:

> Gerhard,
> 
>> 
>> On the one hand, it's a nice idea to have some IEs which allow
>> describing the type and semantic of other IEs. On the other hand, my
>> impression is that the usefulness is very restricted and not as broad as
>> claimed in the introduction of the draft:
>> 
>>    ... Having to do some sort of tool-specific
>>    configuration (or code modification) on every tool just to tell which
>>    type each used Information Element has is a huge amount of work for
>>    users and implementors of enterprise-specific Information Elements.
>>    Many tools in fact only need to know the field's data type to work on
>>    them. ...
>> 
> 
> One of the use cases we have in mind here would be a collaborative measurement
> infrastructure where each exporter is implemented by a different vendor and
> exports slightly different enterprise IEs. In that case, having type
> information in the message stream allows ad-hoc preliminary analysis of the
> enterprise specific data.
> 
> Our claim that many tools only need to know the field's data types to work on
> them applies...so the usefulness of the draft is not too "restricted"

I have problems with fully accepting this claim.
You just know the data type.

When is is helpful to know the data type without having a clue about the
semantics?

Why would in such cases handling of opaque octet strings not be acceptle?

Thanks,

    Juergen

>> In my opinion, any deeper analysis and processing of metering data
>> requires knowledge about the semantic. Just knowing the data type may be
>> enough to display values correctly. Considering
>> informationElementSemanticType, you might also know if the calculation
>> of statistical properties (max, min, mean, variance etc.) makes sense or
>> not. But any further analysis would probably require more semantical
>> knowledge. That's why I assume that, in practice, analyzing and
>> processing enterprise-specific data will mostly be performed with
>> specialized analysis tools that have been implemented for this specific
>> purpose. And for these tools, there is no need to export the IE information.
>> 
> 
> ...but those ad hoc tools won't be reusable, unless tool specific
> configuration or code modification are done for any used Enterprise Specific
> IE. And what about if the tools are not updated?
> 
> A real life example that this draft would solve is mentioned in:
> http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html
> 
> ...which also contains the motivation for this draft.
> 
> Regards,
> Elisa
> 
> 
>> 
>> Juergen Quittek wrote:
>>> Dear all,
>>> 
>>> Candidates #4 to become a new IPFIX work item is described by
>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>> 
>>>> 4. Extended Types (Elisa Boschi)
>>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>    specify what operations make sense for an IE.
>>>>    Support shown for this as a WG item, as for File Format.
>>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>> It is a method for assigning data types to unknown IPFIX information
>>> elements by using option records that map data types to element identifiers.
>>> 
>>> It can be applied in cases where an IPFIX collector does not know the
>>> data type of received information elements. This may in particular happen
>>> if enterprise specific elements are used. Without this information the
>>> collector would treat these elements as if they were of type octet array.
>>> With this information it may be able to treat them more appropriately.
>>> 
>>> The current version of the IPFIX file format draft recommends using this
>>> method when IPFIX records are stored.
>>> 
>>> Do you think this is a useful extension of the IPFIX protocol?
>>> Do you think we should accept this as an IPFIX work item?
>>> Please have a look at the draft and send your comments.
>>> 
>>> Thanks,
>>> 
>>>     Juergen
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> IPFIX mailing list
>>> IPFIX@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ipfix
>> 
> 
> ******************************************************************************
> ********************
> E-mail Confidentiality Notice and Disclaimer.
> 
> This email and any files transmitted with it are confidential and are intended
> solely for the use of the individual or entity to which they are addressed.
> Access to this e-mail by anyone else is unauthorised. If you are not the
> intended recipient,any disclosure, copying, distribution or any action taken
> or omitted to be taken in reliance on it, is prohibited.
> E-mail messages are not necessarily secure.Hitachi does not accept
> responsibility for any changes made to this message after it was sent.
> 
> Please note that Hitachi checks outgoing e-mail messages for the presence of
> computer viruses.
> ******************************************************************************
> ********************
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 18:13:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEBae-0001jT-Ia; Thu, 26 Jul 2007 18:13:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBac-0001hO-RZ
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:13:46 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBab-0001nR-Ts
	for ipfix@ietf.org; Thu, 26 Jul 2007 18:13:46 -0400
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id F081828016A83;
	Fri, 27 Jul 2007 00:13:46 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id K1wS4ptflWq1; Fri, 27 Jul 2007 00:13:46 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id CF62328014C90;
	Fri, 27 Jul 2007 00:13:31 +0200 (CEST)
Received: from 130.129.82.248 ([130.129.82.248]) by mx1.office ([10.1.1.23])
	with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 26 Jul 2007 22:13:30 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 27 Jul 2007 00:13:27 +0200
Subject: Re: [IPFIX] new work item candidate #4: extended types
From: Juergen Quittek <Quittek@netlab.nec.de>
To: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>,
	<muenz@informatik.uni-tuebingen.de>
Message-ID: <C2CEE927.1036F%Quittek@netlab.nec.de>
Thread-Topic: [IPFIX] new work item candidate #4: extended types
Thread-Index: AcfPzxo95ZI1Uv8xRJ++1i8BMypyEwAAxZsf
In-Reply-To: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Hi Elisa,

Am 26.07.2007 23:51 Uhr schrieb "Boschi, Elisa" unter
<Elisa.Boschi@Hitachi-eu.com>:

> Gerhard,
> 
>> 
>> On the one hand, it's a nice idea to have some IEs which allow
>> describing the type and semantic of other IEs. On the other hand, my
>> impression is that the usefulness is very restricted and not as broad as
>> claimed in the introduction of the draft:
>> 
>>    ... Having to do some sort of tool-specific
>>    configuration (or code modification) on every tool just to tell which
>>    type each used Information Element has is a huge amount of work for
>>    users and implementors of enterprise-specific Information Elements.
>>    Many tools in fact only need to know the field's data type to work on
>>    them. ...
>> 
> 
> One of the use cases we have in mind here would be a collaborative measurement
> infrastructure where each exporter is implemented by a different vendor and
> exports slightly different enterprise IEs. In that case, having type
> information in the message stream allows ad-hoc preliminary analysis of the
> enterprise specific data.
> 
> Our claim that many tools only need to know the field's data types to work on
> them applies...so the usefulness of the draft is not too "restricted"

I have problems with fully accepting this claim.
You just know the data type.

When is is helpful to know the data type without having a clue about the
semantics?

Why would in such cases handling of opaque octet strings not be acceptle?

Thanks,

    Juergen

>> In my opinion, any deeper analysis and processing of metering data
>> requires knowledge about the semantic. Just knowing the data type may be
>> enough to display values correctly. Considering
>> informationElementSemanticType, you might also know if the calculation
>> of statistical properties (max, min, mean, variance etc.) makes sense or
>> not. But any further analysis would probably require more semantical
>> knowledge. That's why I assume that, in practice, analyzing and
>> processing enterprise-specific data will mostly be performed with
>> specialized analysis tools that have been implemented for this specific
>> purpose. And for these tools, there is no need to export the IE information.
>> 
> 
> ...but those ad hoc tools won't be reusable, unless tool specific
> configuration or code modification are done for any used Enterprise Specific
> IE. And what about if the tools are not updated?
> 
> A real life example that this draft would solve is mentioned in:
> http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html
> 
> ...which also contains the motivation for this draft.
> 
> Regards,
> Elisa
> 
> 
>> 
>> Juergen Quittek wrote:
>>> Dear all,
>>> 
>>> Candidates #4 to become a new IPFIX work item is described by
>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>> 
>>>> 4. Extended Types (Elisa Boschi)
>>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>    specify what operations make sense for an IE.
>>>>    Support shown for this as a WG item, as for File Format.
>>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>> It is a method for assigning data types to unknown IPFIX information
>>> elements by using option records that map data types to element identifiers.
>>> 
>>> It can be applied in cases where an IPFIX collector does not know the
>>> data type of received information elements. This may in particular happen
>>> if enterprise specific elements are used. Without this information the
>>> collector would treat these elements as if they were of type octet array.
>>> With this information it may be able to treat them more appropriately.
>>> 
>>> The current version of the IPFIX file format draft recommends using this
>>> method when IPFIX records are stored.
>>> 
>>> Do you think this is a useful extension of the IPFIX protocol?
>>> Do you think we should accept this as an IPFIX work item?
>>> Please have a look at the draft and send your comments.
>>> 
>>> Thanks,
>>> 
>>>     Juergen
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> IPFIX mailing list
>>> IPFIX@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ipfix
>> 
> 
> ******************************************************************************
> ********************
> E-mail Confidentiality Notice and Disclaimer.
> 
> This email and any files transmitted with it are confidential and are intended
> solely for the use of the individual or entity to which they are addressed.
> Access to this e-mail by anyone else is unauthorised. If you are not the
> intended recipient,any disclosure, copying, distribution or any action taken
> or omitted to be taken in reliance on it, is prohibited.
> E-mail messages are not necessarily secure.Hitachi does not accept
> responsibility for any changes made to this message after it was sent.
> 
> Please note that Hitachi checks outgoing e-mail messages for the presence of
> computer viruses.
> ******************************************************************************
> ********************
> 
> 
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From jmolsen@boxoffiz.com Thu Jul 26 19:07:56 2007
Return-path: <jmolsen@boxoffiz.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IECR1-0007Jm-Tu; Thu, 26 Jul 2007 19:07:55 -0400
Received: from astrasbourg-253-1-57-65.w86-213.abo.wanadoo.fr ([86.213.156.65])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IECR0-0002ot-3C; Thu, 26 Jul 2007 19:07:55 -0400
Received: from [86.213.156.65] by mail.boxoffiz.com; Thu, 26 Jul 2007 23:07:52 -0100
Message-ID: <01c7cfd9$cb24fc00$419cd556@jmolsen>
From: "Carrie Clement" <jmolsen@boxoffiz.com>
To: <ipfix-archive@lists.ietf.org>
Subject: Save US $ 1529.1 Adobe Creative 3
Date: Thu, 26 Jul 2007 23:07:52 -0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-2";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574

adobe acrobat 8.0 $79
http://Theoemlinksoft.com




From ipfix-bounces@ietf.org Thu Jul 26 19:16:35 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IECZH-0004xs-U6; Thu, 26 Jul 2007 19:16:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IECZH-0004uf-1m
	for ipfix@ietf.org; Thu, 26 Jul 2007 19:16:27 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IECZG-000294-6T
	for ipfix@ietf.org; Thu, 26 Jul 2007 19:16:26 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6QNGDtp075476;
	Fri, 27 Jul 2007 08:16:14 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 27 Jul 2007 08:16:16 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Message-Id: <20070727074625.4986.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 27 Jul 2007 08:16:15 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Nevil and all,

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.

I think IPFIX Aggregation-draft focuses on the aggregation method and
reporting methods of aggregation rule.
But, now Mediator-draft describes all-around topics of flow and protocol
mediation. It is different scope.

They seems to be compossible. Do you think integration is necessary ?
Do you mean that we consider more the part of aggregation, as first step?

Best Regards,
Atsushi KOBAYASHI

On Thu, 26 Jul 2007 10:08:16 +1200
Nevil Brownlee <nevil@auckland.ac.nz> wrote:

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Thu Jul 26 19:16:35 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IECZH-0004xs-U6; Thu, 26 Jul 2007 19:16:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IECZH-0004uf-1m
	for ipfix@ietf.org; Thu, 26 Jul 2007 19:16:27 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IECZG-000294-6T
	for ipfix@ietf.org; Thu, 26 Jul 2007 19:16:26 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6QNGDtp075476;
	Fri, 27 Jul 2007 08:16:14 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Fri, 27 Jul 2007 08:16:16 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Nevil Brownlee <nevil@auckland.ac.nz>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
Message-Id: <20070727074625.4986.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Fri, 27 Jul 2007 08:16:15 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Nevil and all,

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.

I think IPFIX Aggregation-draft focuses on the aggregation method and
reporting methods of aggregation rule.
But, now Mediator-draft describes all-around topics of flow and protocol
mediation. It is different scope.

They seems to be compossible. Do you think integration is necessary ?
Do you mean that we consider more the part of aggregation, as first step?

Best Regards,
Atsushi KOBAYASHI

On Thu, 26 Jul 2007 10:08:16 +1200
Nevil Brownlee <nevil@auckland.ac.nz> wrote:

> 5. IPFIX Mediation (Atayushi Kobayashi)
>    Needed by (at least) two large operators.
>    Could be integrated with Falko Dressler's draft on IPFIX Aggregation.
>    Possible future WG item, continue discussion on mailing list.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From csupport@hmoz.net Thu Jul 26 20:31:50 2007
Return-path: <csupport@hmoz.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEDkE-0001Uv-T5
	for ipfix-archive@megatron.ietf.org; Thu, 26 Jul 2007 20:31:50 -0400
Received: from [58.226.52.112] (helo=58.226.52.112)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IEDkD-0003vY-R1
	for ipfix-archive@megatron.ietf.org; Thu, 26 Jul 2007 20:31:50 -0400
Received: from [58.226.52.112] by (null); Fri, 27 Jul 2007 00:31:49 +0000
Message-ID: <000601c7cfe5$01e7e879$fa9828b2@rwjickj>
From: "Hmoz, Inc" <csupport@hmoz.net>
To: <ipfix-archive@megatron.ietf.org>
Subject: Hmoz.net: Your customer details confirmation
Date: Thu, 26 Jul 2007 22:44:26 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0003_01C7CFE5.01E366DA"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.2663
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01C7CFE5.01E366DA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  ---------------------------------------------
  Thank you for using Hmoz.net !
  ---------------------------------------------
  This account created  26 Jul 2007 05:18:20 PM
  from IP address=20
User Name: ipfix-archive@megatron.ietf.org
Password: 7DG9Jb5n
Click here to login:
http://www.hmoz.net/bb/index.php?u=3Dipfix-archive@megatron.ietf.org&w=3D=
session_IDmlb947J7=3Dt
Your account ID:10593659
If you use anti-spam email software, be sure to add 'csupport@hmoz.net' =
to your list of approved senders.

------=_NextPart_000_0003_01C7CFE5.01E366DA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.2759" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV align=3D"center">
  ---------------------------------------------<BR>
  Thank you for using Hmoz.net !<BR>
  ---------------------------------------------<BR>
  This account created  26 Jul 2007 05:18:20 PM<BR>
  from IP address < 69.116.165.232  ></DIV>
<P align=3D"center">User Name: ipfix-archive@megatron.ietf.org<BR>
Password: 7DG9Jb5n</P>
<P align=3D"center">Click here to login:<BR>
<A =
href=3D"http://www.hmoz.net/bb/index.php?c=3Dipfix-archive@megatron.ietf.=
org&n=3DsessionID_u3o377H2=3Dz">http://www.hmoz.net/bb/index.php?u=3Dipfi=
x-archive@megatron.ietf.org&w=3Dsession_IDmlb947J7=3Dt</A></P>
<P align=3D"center">Your account ID:10593659</P>
<P align=3D"center">If you use anti-spam email software, be sure to add =
'csupport@hmoz.net' to your list of approved senders.</P>
</BODY></HTML></BODY></HTML>
------=_NextPart_000_0003_01C7CFE5.01E366DA--





From ipfix-bounces@ietf.org Fri Jul 27 08:19:07 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEOmR-0002fC-1J; Fri, 27 Jul 2007 08:18:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEOmO-0002f7-CB
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:18:48 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEOmM-0002XK-J2
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:18:48 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCIhpY000827; 
	Fri, 27 Jul 2007 14:18:44 +0200
Message-ID: <46A9E28D.2060504@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:18:21 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
In-Reply-To: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.190; host: mx06)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1683862985=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1683862985==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020404070805000602050506"

This is a cryptographically signed message in MIME format.

--------------ms020404070805000602050506
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Elisa,

Boschi, Elisa wrote:
>> On the one hand, it's a nice idea to have some IEs which allow
>> describing the type and semantic of other IEs. On the other hand, my
>> impression is that the usefulness is very restricted and not as broad as
>> claimed in the introduction of the draft:
>>
>>    ... Having to do some sort of tool-specific
>>    configuration (or code modification) on every tool just to tell which
>>    type each used Information Element has is a huge amount of work for
>>    users and implementors of enterprise-specific Information Elements.
>>    Many tools in fact only need to know the field's data type to work on
>>    them. ...
>>
> 
> One of the use cases we have in mind here would be a collaborative
> measurement infrastructure where each exporter is implemented by a
> different vendor and exports slightly different enterprise IEs. In that
> case, having type information in the message stream allows ad-hoc
> preliminary analysis of the enterprise specific data.

If "preliminary analysis" means displaying the values correctly or
calculating some simple statistics, I fully agree.

If you are aware of any more sophisticated analysis method one could
apply without any further semantical knowledge, please let me know. This
would make my desicion on this topic easier :)

> Our claim that many tools only need to know the field's data types to
> work on them applies...so the usefulness of the draft is not too
> "restricted"

There may be cases where displaying values or calculating mean,
variance, min, max etc. is just enough to "analyze" the metering data.
Yet, traffic analysis methods are usually much more sophisticated and
specific to the semantics of the metering data.

>> In my opinion, any deeper analysis and processing of metering data
>> requires knowledge about the semantic. Just knowing the data type may be
>> enough to display values correctly. Considering
>> informationElementSemanticType, you might also know if the calculation
>> of statistical properties (max, min, mean, variance etc.) makes sense or
>> not. But any further analysis would probably require more semantical
>> knowledge. That's why I assume that, in practice, analyzing and
>> processing enterprise-specific data will mostly be performed with
>> specialized analysis tools that have been implemented for this specific
>> purpose. And for these tools, there is no need to export the IE
> information.
>>
> 
> ...but those ad hoc tools won't be reusable, unless tool specific
> configuration or code modification are done for any used Enterprise
> Specific IE. And what about if the tools are not updated?
> 
> A real life example that this draft would solve is mentioned in:
> http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html
> 
> ...which also contains the motivation for this draft.

The mentioned example is only about displaying the values correctly. I
would not call this "analysis".

I'm certainly not against your draft or the idea to describe
enterprise-specific IEs. I just think that the usability is restricted,
and that it might not be of high relevance in practice.

Regards,
Gerhard

> 
> Regards,
> Elisa
> 
> 
>>
>> Juergen Quittek wrote:
>>> Dear all,
>>>
>>> Candidates #4 to become a new IPFIX work item is described by
>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>>
>>>> 4. Extended Types (Elisa Boschi)
>>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>    specify what operations make sense for an IE.
>>>>    Support shown for this as a WG item, as for File Format.
>>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>> It is a method for assigning data types to unknown IPFIX information
>>> elements by using option records that map data types to element
> identifiers.
>>>
>>> It can be applied in cases where an IPFIX collector does not know the
>>> data type of received information elements. This may in particular happen
>>> if enterprise specific elements are used. Without this information the
>>> collector would treat these elements as if they were of type octet array.
>>> With this information it may be able to treat them more appropriately.
>>>
>>> The current version of the IPFIX file format draft recommends using this
>>> method when IPFIX records are stored.
>>>
>>> Do you think this is a useful extension of the IPFIX protocol?
>>> Do you think we should accept this as an IPFIX work item?
>>> Please have a look at the draft and send your comments.
>>>
>>> Thanks,
>>>
>>>     Juergen
>>>
>>>
>>>
>>> _______________________________________________
>>> IPFIX mailing list
>>> IPFIX@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ipfix
>>
> 
> **************************************************************************************************
> E-mail Confidentiality Notice and Disclaimer.
> 
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to which they
> are addressed. Access to this e-mail by anyone else is unauthorised. If
> you are not the intended recipient,any disclosure, copying, distribution
> or any action taken or omitted to be taken in reliance on it, is
> prohibited.
> E-mail messages are not necessarily secure.Hitachi does not accept
> responsibility for any changes made to this message after it was sent.
> 
> Please note that Hitachi checks outgoing e-mail messages for the
> presence of computer viruses.
> **************************************************************************************************
> 
> 

-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms020404070805000602050506
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDcyNzEyMTgyMVowIwYJKoZIhvcNAQkEMRYEFLl46VqnAwTC
zrVsOMnuF7CLbybeMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQB752tHk5L9t66c8vvEPae660gwPUDcyskQD7SLObOImbI5esDj5n34cPcm
Hx3eCVt8ANyLvv2MIS0jJbIzulVas02+VA+9D1r8W/JXrA69NIP7lUD1WHFX5xbq7pb2742E
57sV1H1b36ln9uhuBlh/yckuz9+w9IlkE8fmgV3RkbGHTUNSKJVxlJxoOFiaykx1naE7qwbg
mGJV9dkQOHMOyVhtyZ2+KQHZukkgWkqNF1WcLqBexXXg3Ix7OCI93UqdbaP3df1iX5SER8oX
ZvscdI6ZErTymIOsw2xIAmJ4vAcpgPwGZZ/gDNkzoaEH3HSdilmY0H9IPe+AUkI9qWUnAAAA
AAAA
--------------ms020404070805000602050506--


--===============1683862985==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1683862985==--




From ipfix-bounces@ietf.org Fri Jul 27 08:19:07 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEOmR-0002fC-1J; Fri, 27 Jul 2007 08:18:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEOmO-0002f7-CB
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:18:48 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEOmM-0002XK-J2
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:18:48 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCIhpY000827; 
	Fri, 27 Jul 2007 14:18:44 +0200
Message-ID: <46A9E28D.2060504@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:18:21 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
Subject: Re: [IPFIX] new work item candidate #4: extended types
References: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
In-Reply-To: <AEC82A8A9DA33047ABC0902A36E889130922AC@mhdexcb.adhel.hitachi-eu.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.190; host: mx06)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1683862985=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1683862985==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020404070805000602050506"

This is a cryptographically signed message in MIME format.

--------------ms020404070805000602050506
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Elisa,

Boschi, Elisa wrote:
>> On the one hand, it's a nice idea to have some IEs which allow
>> describing the type and semantic of other IEs. On the other hand, my
>> impression is that the usefulness is very restricted and not as broad as
>> claimed in the introduction of the draft:
>>
>>    ... Having to do some sort of tool-specific
>>    configuration (or code modification) on every tool just to tell which
>>    type each used Information Element has is a huge amount of work for
>>    users and implementors of enterprise-specific Information Elements.
>>    Many tools in fact only need to know the field's data type to work on
>>    them. ...
>>
> 
> One of the use cases we have in mind here would be a collaborative
> measurement infrastructure where each exporter is implemented by a
> different vendor and exports slightly different enterprise IEs. In that
> case, having type information in the message stream allows ad-hoc
> preliminary analysis of the enterprise specific data.

If "preliminary analysis" means displaying the values correctly or
calculating some simple statistics, I fully agree.

If you are aware of any more sophisticated analysis method one could
apply without any further semantical knowledge, please let me know. This
would make my desicion on this topic easier :)

> Our claim that many tools only need to know the field's data types to
> work on them applies...so the usefulness of the draft is not too
> "restricted"

There may be cases where displaying values or calculating mean,
variance, min, max etc. is just enough to "analyze" the metering data.
Yet, traffic analysis methods are usually much more sophisticated and
specific to the semantics of the metering data.

>> In my opinion, any deeper analysis and processing of metering data
>> requires knowledge about the semantic. Just knowing the data type may be
>> enough to display values correctly. Considering
>> informationElementSemanticType, you might also know if the calculation
>> of statistical properties (max, min, mean, variance etc.) makes sense or
>> not. But any further analysis would probably require more semantical
>> knowledge. That's why I assume that, in practice, analyzing and
>> processing enterprise-specific data will mostly be performed with
>> specialized analysis tools that have been implemented for this specific
>> purpose. And for these tools, there is no need to export the IE
> information.
>>
> 
> ...but those ad hoc tools won't be reusable, unless tool specific
> configuration or code modification are done for any used Enterprise
> Specific IE. And what about if the tools are not updated?
> 
> A real life example that this draft would solve is mentioned in:
> http://www1.ietf.org/mail-archive/web/ipfix/current/msg03040.html
> 
> ...which also contains the motivation for this draft.

The mentioned example is only about displaying the values correctly. I
would not call this "analysis".

I'm certainly not against your draft or the idea to describe
enterprise-specific IEs. I just think that the usability is restricted,
and that it might not be of high relevance in practice.

Regards,
Gerhard

> 
> Regards,
> Elisa
> 
> 
>>
>> Juergen Quittek wrote:
>>> Dear all,
>>>
>>> Candidates #4 to become a new IPFIX work item is described by
>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>>
>>>> 4. Extended Types (Elisa Boschi)
>>>>    Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>    specify what operations make sense for an IE.
>>>>    Support shown for this as a WG item, as for File Format.
>>>>    Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>> It is a method for assigning data types to unknown IPFIX information
>>> elements by using option records that map data types to element
> identifiers.
>>>
>>> It can be applied in cases where an IPFIX collector does not know the
>>> data type of received information elements. This may in particular happen
>>> if enterprise specific elements are used. Without this information the
>>> collector would treat these elements as if they were of type octet array.
>>> With this information it may be able to treat them more appropriately.
>>>
>>> The current version of the IPFIX file format draft recommends using this
>>> method when IPFIX records are stored.
>>>
>>> Do you think this is a useful extension of the IPFIX protocol?
>>> Do you think we should accept this as an IPFIX work item?
>>> Please have a look at the draft and send your comments.
>>>
>>> Thanks,
>>>
>>>     Juergen
>>>
>>>
>>>
>>> _______________________________________________
>>> IPFIX mailing list
>>> IPFIX@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ipfix
>>
> 
> **************************************************************************************************
> E-mail Confidentiality Notice and Disclaimer.
> 
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to which they
> are addressed. Access to this e-mail by anyone else is unauthorised. If
> you are not the intended recipient,any disclosure, copying, distribution
> or any action taken or omitted to be taken in reliance on it, is
> prohibited.
> E-mail messages are not necessarily secure.Hitachi does not accept
> responsibility for any changes made to this message after it was sent.
> 
> Please note that Hitachi checks outgoing e-mail messages for the
> presence of computer viruses.
> **************************************************************************************************
> 
> 

-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms020404070805000602050506
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDcyNzEyMTgyMVowIwYJKoZIhvcNAQkEMRYEFLl46VqnAwTC
zrVsOMnuF7CLbybeMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQB752tHk5L9t66c8vvEPae660gwPUDcyskQD7SLObOImbI5esDj5n34cPcm
Hx3eCVt8ANyLvv2MIS0jJbIzulVas02+VA+9D1r8W/JXrA69NIP7lUD1WHFX5xbq7pb2742E
57sV1H1b36ln9uhuBlh/yckuz9+w9IlkE8fmgV3RkbGHTUNSKJVxlJxoOFiaykx1naE7qwbg
mGJV9dkQOHMOyVhtyZ2+KQHZukkgWkqNF1WcLqBexXXg3Ix7OCI93UqdbaP3df1iX5SER8oX
ZvscdI6ZErTymIOsw2xIAmJ4vAcpgPwGZZ/gDNkzoaEH3HSdilmY0H9IPe+AUkI9qWUnAAAA
AAAA
--------------ms020404070805000602050506--


--===============1683862985==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============1683862985==--




From ipfix-bounces@ietf.org Fri Jul 27 08:49:53 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPGT-0003az-4i; Fri, 27 Jul 2007 08:49:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPGR-0003au-Rz
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:49:51 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEPGR-0003Vg-9f
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:49:51 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCnVcd016912; 
	Fri, 27 Jul 2007 14:49:35 +0200
Message-ID: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:49:08 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<20070727074625.4986.AKOBA@nttv6.net>
In-Reply-To: <20070727074625.4986.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6RCnVcd016912
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Kobayashi, all,

kobayashi atsushi wrote:
>> 5. IPFIX Mediation (Atayushi Kobayashi)
>>    Needed by (at least) two large operators.
>>    Could be integrated with Falko Dressler's draft on IPFIX Aggregatio=
n.
>=20
> I think IPFIX Aggregation-draft focuses on the aggregation method and
> reporting methods of aggregation rule.
> But, now Mediator-draft describes all-around topics of flow and protoco=
l
> mediation. It is different scope.
>=20
> They seems to be compossible. Do you think integration is necessary ?
> Do you mean that we consider more the part of aggregation, as first ste=
p?

The aggregation draft is very specific, while your mediator draft is
very broad.
A short summary of the aspects covered by the aggregation draft to
determine potential overlaps:

1) architecture of a concentrator
2) description language for configuring metering processes
   (essentially input filters and flow keys)
3) a couple of new IEs useful to report aggregates and applied input
   filters (e.g. port range IE)
4) a new template type to efficiently report information about applied
   input filters

I assume that item 1) is/will be covered in your draft.

Item 2) is related to configuration and covered by the configuration draf=
t.

The remaining items 3) and 4) might be interesting extensions to
efficiently report how a mediator modifies/filters the original data.
Yet, you would probably try to export this kind of information with
exiting protocol mechanisms at first.

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 08:49:54 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPGT-0003az-4i; Fri, 27 Jul 2007 08:49:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPGR-0003au-Rz
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:49:51 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEPGR-0003Vg-9f
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:49:51 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCnVcd016912; 
	Fri, 27 Jul 2007 14:49:35 +0200
Message-ID: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:49:08 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<20070727074625.4986.AKOBA@nttv6.net>
In-Reply-To: <20070727074625.4986.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6RCnVcd016912
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Kobayashi, all,

kobayashi atsushi wrote:
>> 5. IPFIX Mediation (Atayushi Kobayashi)
>>    Needed by (at least) two large operators.
>>    Could be integrated with Falko Dressler's draft on IPFIX Aggregatio=
n.
>=20
> I think IPFIX Aggregation-draft focuses on the aggregation method and
> reporting methods of aggregation rule.
> But, now Mediator-draft describes all-around topics of flow and protoco=
l
> mediation. It is different scope.
>=20
> They seems to be compossible. Do you think integration is necessary ?
> Do you mean that we consider more the part of aggregation, as first ste=
p?

The aggregation draft is very specific, while your mediator draft is
very broad.
A short summary of the aspects covered by the aggregation draft to
determine potential overlaps:

1) architecture of a concentrator
2) description language for configuring metering processes
   (essentially input filters and flow keys)
3) a couple of new IEs useful to report aggregates and applied input
   filters (e.g. port range IE)
4) a new template type to efficiently report information about applied
   input filters

I assume that item 1) is/will be covered in your draft.

Item 2) is related to configuration and covered by the configuration draf=
t.

The remaining items 3) and 4) might be interesting extensions to
efficiently report how a mediator modifies/filters the original data.
Yet, you would probably try to export this kind of information with
exiting protocol mechanisms at first.

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 08:58:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPOJ-0003HC-Rc; Fri, 27 Jul 2007 08:57:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPOI-0003H5-Hm
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:57:58 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPOG-0003NS-W2
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:57:58 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCvlPv020456; 
	Fri, 27 Jul 2007 14:57:47 +0200
Message-ID: <46A9EBB5.2020801@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:57:25 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] discussion on telco requirement prior to  re chartering
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>	<C2CEBA6B.10314%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6RCvlPv020456
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Emile, all,

STEPHAN Emile RD-CORE-LAN wrote:
> Hi Juergen and Nevil,
>=20
> It does not make sense to separate item 3 and 5 because they compliment=
 together regarding telco needs of standard I/O for IPFIX middlewares.=20

I do not understand your concerns about separating the file format from
the mediator draft.

Similar to the separation of the IPFIX protocol and the IPFIX
architecture, the IPFIX file format describes an interface while the
IPFIX mediator is about an architecture and specific application of
protocol mechanisms. I assume separating these two aspects is a common
approach in the IETF.

Regards,
Gerhard

> I don't support item 4 because it introduces a second level of datamode=
ling and because the datatype lists are not extensible.=20
>=20
>=20
> Regards
> Emile
>=20
>=20
>> -----Message d'origine-----
>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>> Envoy=E9 : jeudi 26 juillet 2007 20:54
>> =C0 : STEPHAN Emile RD-CORE-LAN; Nevil Brownlee; ipfix@ietf.org
>> Cc : Romascanu, Dan (Dan)
>> Objet : Re: requirements: Extraction, Distribution,
>> Duplication,Aggregation , Storage, Self Description, Anonymization,
>> Obfuscation ...
>>
>> Hi Emile,
>>
>>
>> Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
>> <emile.stephan@orange-ftgroup.com>:
>>
>>> HI Juergen and Nevil,
>>>
>>> Work item #3
>>> Storing IPFIX records in files requires interoperability only when
>> exchanging
>>> these files with some one else or some other application. So it's a
>> function
>>> of mediation.
>> I agree that one may see it this way and it is a very good point to
>> consider
>> when working on a file format.  However, for the discussions we are ha=
ving
>> I would prefer to separate the discussion on the file format work item
>> from
>> the discussion on the mediator work item.
>>
>>> Work item #4 points indirectly to a major point concern for telcos: h=
ow
>> to map
>>> a private IE on a standard one?
>> Now I understand your requirement.
>> However, as it is currently written, the proposed work does not sugges=
t to
>> map enterprise-specific IEs to standard ones, but to just assign data
>> types
>> to unknown (enterprise-specific) IEs. This is a use case different to
>> yours.
>>
>>> Work item #5 defines mediator arch & functions. Then it gives many us=
e
>> cases
>>> and requirements.
>> I fully agree.
>>
>>> Work items #3, #4 and #5 give many functions a mediator may implement.
>>> At this step, the functions required for interoperability between
>> mediators
>>> are not identified. So please consider the necessity to define the
>>> interoperability requirements prior to re charter.
>> Thank you  for this hint.
>> We will consider it if we charter a work item on mediation.
>>
>> Thanks,
>>
>>     Juergen
>>
>>> Regards
>>> Emile
>>>
>>>
>>>> -----Message d'origine-----
>>>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>>>> Envoy=E9 : jeudi 26 juillet 2007 08:28
>>>> =C0 : ipfix@ietf.org
>>>> Objet : [IPFIX] new work item candidate #4: extended types
>>>>
>>>> Dear all,
>>>>
>>>> Candidates #4 to become a new IPFIX work item is described by
>>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>>>
>>>>> 4. Extended Types (Elisa Boschi)
>>>>>     Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>>     specify what operations make sense for an IE.
>>>>>     Support shown for this as a WG item, as for File Format.
>>>>>     Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>>> It is a method for assigning data types to unknown IPFIX information
>>>> elements by using option records that map data types to element
>>>> identifiers.
>>>>
>>>> It can be applied in cases where an IPFIX collector does not know th=
e
>>>> data type of received information elements. This may in particular
>> happen
>>>> if enterprise specific elements are used. Without this information t=
he
>>>> collector would treat these elements as if they were of type octet
>> array.
>>>> With this information it may be able to treat them more appropriatel=
y.
>>>>
>>>> The current version of the IPFIX file format draft recommends using
>> this
>>>> method when IPFIX records are stored.
>>>>
>>>> Do you think this is a useful extension of the IPFIX protocol?
>>>> Do you think we should accept this as an IPFIX work item?
>>>> Please have a look at the draft and send your comments.
>>>>
>>>> Thanks,
>>>>
>>>>      Juergen
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> IPFIX mailing list
>>>> IPFIX@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 08:58:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPOJ-0003HC-Rc; Fri, 27 Jul 2007 08:57:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPOI-0003H5-Hm
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:57:58 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPOG-0003NS-W2
	for ipfix@ietf.org; Fri, 27 Jul 2007 08:57:58 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RCvlPv020456; 
	Fri, 27 Jul 2007 14:57:47 +0200
Message-ID: <46A9EBB5.2020801@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 14:57:25 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange-ftgroup.com>
Subject: Re: [IPFIX] discussion on telco requirement prior to  re chartering
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B75047@ftrdmel1.rd.francetelecom.fr>	<C2CEBA6B.10314%Quittek@netlab.nec.de>
	<DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <DD8B8FEBBFAF9E488F63FF0F1A69EDD103B7506F@ftrdmel1.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6RCvlPv020456
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Emile, all,

STEPHAN Emile RD-CORE-LAN wrote:
> Hi Juergen and Nevil,
>=20
> It does not make sense to separate item 3 and 5 because they compliment=
 together regarding telco needs of standard I/O for IPFIX middlewares.=20

I do not understand your concerns about separating the file format from
the mediator draft.

Similar to the separation of the IPFIX protocol and the IPFIX
architecture, the IPFIX file format describes an interface while the
IPFIX mediator is about an architecture and specific application of
protocol mechanisms. I assume separating these two aspects is a common
approach in the IETF.

Regards,
Gerhard

> I don't support item 4 because it introduces a second level of datamode=
ling and because the datatype lists are not extensible.=20
>=20
>=20
> Regards
> Emile
>=20
>=20
>> -----Message d'origine-----
>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>> Envoy=E9 : jeudi 26 juillet 2007 20:54
>> =C0 : STEPHAN Emile RD-CORE-LAN; Nevil Brownlee; ipfix@ietf.org
>> Cc : Romascanu, Dan (Dan)
>> Objet : Re: requirements: Extraction, Distribution,
>> Duplication,Aggregation , Storage, Self Description, Anonymization,
>> Obfuscation ...
>>
>> Hi Emile,
>>
>>
>> Am 26.07.2007 18:37 Uhr schrieb "STEPHAN Emile RD-CORE-LAN" unter
>> <emile.stephan@orange-ftgroup.com>:
>>
>>> HI Juergen and Nevil,
>>>
>>> Work item #3
>>> Storing IPFIX records in files requires interoperability only when
>> exchanging
>>> these files with some one else or some other application. So it's a
>> function
>>> of mediation.
>> I agree that one may see it this way and it is a very good point to
>> consider
>> when working on a file format.  However, for the discussions we are ha=
ving
>> I would prefer to separate the discussion on the file format work item
>> from
>> the discussion on the mediator work item.
>>
>>> Work item #4 points indirectly to a major point concern for telcos: h=
ow
>> to map
>>> a private IE on a standard one?
>> Now I understand your requirement.
>> However, as it is currently written, the proposed work does not sugges=
t to
>> map enterprise-specific IEs to standard ones, but to just assign data
>> types
>> to unknown (enterprise-specific) IEs. This is a use case different to
>> yours.
>>
>>> Work item #5 defines mediator arch & functions. Then it gives many us=
e
>> cases
>>> and requirements.
>> I fully agree.
>>
>>> Work items #3, #4 and #5 give many functions a mediator may implement.
>>> At this step, the functions required for interoperability between
>> mediators
>>> are not identified. So please consider the necessity to define the
>>> interoperability requirements prior to re charter.
>> Thank you  for this hint.
>> We will consider it if we charter a work item on mediation.
>>
>> Thanks,
>>
>>     Juergen
>>
>>> Regards
>>> Emile
>>>
>>>
>>>> -----Message d'origine-----
>>>> De : Juergen Quittek [mailto:Quittek@netlab.nec.de]
>>>> Envoy=E9 : jeudi 26 juillet 2007 08:28
>>>> =C0 : ipfix@ietf.org
>>>> Objet : [IPFIX] new work item candidate #4: extended types
>>>>
>>>> Dear all,
>>>>
>>>> Candidates #4 to become a new IPFIX work item is described by
>>>> draft draft-boschi-ipfix-extended-type-00.txt.
>>>>
>>>>> 4. Extended Types (Elisa Boschi)
>>>>>     Needed for IPFIX files, most useful for Enterprise IEs; need to
>>>>>     specify what operations make sense for an IE.
>>>>>     Support shown for this as a WG item, as for File Format.
>>>>>     Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>>>> It is a method for assigning data types to unknown IPFIX information
>>>> elements by using option records that map data types to element
>>>> identifiers.
>>>>
>>>> It can be applied in cases where an IPFIX collector does not know th=
e
>>>> data type of received information elements. This may in particular
>> happen
>>>> if enterprise specific elements are used. Without this information t=
he
>>>> collector would treat these elements as if they were of type octet
>> array.
>>>> With this information it may be able to treat them more appropriatel=
y.
>>>>
>>>> The current version of the IPFIX file format draft recommends using
>> this
>>>> method when IPFIX records are stored.
>>>>
>>>> Do you think this is a useful extension of the IPFIX protocol?
>>>> Do you think we should accept this as an IPFIX work item?
>>>> Please have a look at the draft and send your comments.
>>>>
>>>> Thanks,
>>>>
>>>>      Juergen
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> IPFIX mailing list
>>>> IPFIX@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/ipfix
>=20
>=20
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipfix

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 09:23:45 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPn3-00069Y-KO; Fri, 27 Jul 2007 09:23:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPn3-00069S-0s
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:23:33 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPn1-0003w3-Lo
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:23:32 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RDNAnc009582; 
	Fri, 27 Jul 2007 15:23:10 +0200
Message-ID: <46A9F1A7.7030000@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 15:22:47 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
In-Reply-To: <89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6RDNAnc009582
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Brian,

Brian Trammell wrote:
>> 4. Extended Types (Elisa Boschi)
>>   Needed for IPFIX files, most useful for Enterprise IEs; need to
>>   specify what operations make sense for an IE.
>>   Support shown for this as a WG item, as for File Format.
>>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> Another point to reiterate here - the File Format draft includes a
> normative reference to this draft, as it uses the Options Template
> defined there to meet the self-description requirement when a file
> contains Enterprise-Specific Information Elements. The two should be
> considered for adoption together. The primary reason the extended type
> draft was created (from text originally in the file draft) was that we
> (the file draft authors) thought that the method might be useful on the
> wire, and we received feedback during and after the meeting in Prague
> that we were not the only ones who thought so.

The file format should allow to store all the information which is
*available* to the collector when it receives the data. Information
which is not available will just not be stored.

The self-description issue can be considered as an orthogonal problem.
You might recommend in your draft that the exporter should export
self-descriptive data. How this is done does not have to be specified by
the file format, i.e. the reference to the extended types draft is not
necessary.

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 09:23:45 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEPn3-00069Y-KO; Fri, 27 Jul 2007 09:23:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEPn3-00069S-0s
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:23:33 -0400
Received: from mx06.uni-tuebingen.de ([134.2.3.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEPn1-0003w3-Lo
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:23:32 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6RDNAnc009582; 
	Fri, 27 Jul 2007 15:23:10 +0200
Message-ID: <46A9F1A7.7030000@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 15:22:47 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>
	<89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
In-Reply-To: <89DC91CA-2F86-4A85-A443-6A6512F184B2@cert.org>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx06)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx06.uni-tuebingen.de
	id l6RDNAnc009582
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Brian,

Brian Trammell wrote:
>> 4. Extended Types (Elisa Boschi)
>>   Needed for IPFIX files, most useful for Enterprise IEs; need to
>>   specify what operations make sense for an IE.
>>   Support shown for this as a WG item, as for File Format.
>>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> Another point to reiterate here - the File Format draft includes a
> normative reference to this draft, as it uses the Options Template
> defined there to meet the self-description requirement when a file
> contains Enterprise-Specific Information Elements. The two should be
> considered for adoption together. The primary reason the extended type
> draft was created (from text originally in the file draft) was that we
> (the file draft authors) thought that the method might be useful on the
> wire, and we received feedback during and after the meeting in Prague
> that we were not the only ones who thought so.

The file format should allow to store all the information which is
*available* to the collector when it receives the data. Information
which is not available will just not be stored.

The self-description issue can be considered as an orthogonal problem.
You might recommend in your draft that the exporter should export
self-descriptive data. How this is done does not have to be specified by
the file format, i.e. the reference to the extended types draft is not
necessary.

Regards,
Gerhard

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 09:49:50 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQCU-0005oB-97; Fri, 27 Jul 2007 09:49:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQCT-0005o6-94
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:49:49 -0400
Received: from franclinus.red.cert.org ([192.88.209.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQCS-0004cW-K5
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:49:49 -0400
Received: from franclinus.red.cert.org (localhost [127.0.0.1])
	by franclinus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6RDnWNH029484 for <ipfix@ietf.org>; Fri, 27 Jul 2007 09:49:45 -0400
Received: (from defang@localhost)
	by franclinus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6RDmFBr029410
	for <ipfix@ietf.org>; Fri, 27 Jul 2007 09:48:15 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by franclinus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6RDmEWc029407;
	Fri, 27 Jul 2007 09:48:15 -0400 (EDT)
Received: from [172.28.169.45] (vpn-10-25-4-19.remote.cert.org [10.25.4.19])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6RDlu1o028596; Fri, 27 Jul 2007 09:48:14 -0400
In-Reply-To: <C2CEE927.1036F%Quittek@netlab.nec.de>
References: <C2CEE927.1036F%Quittek@netlab.nec.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7CDB1CBF-C65E-4BBA-AA88-7C5743514A46@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] new work item candidate #4: extended types
Date: Fri, 27 Jul 2007 08:48:12 -0500
To: Juergen Quittek <Quittek@netlab.nec.de>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>, ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

All,

There seems to be some confusion on the list as to the intent of and  
method described by the extended type information draft. Speaking  
here as a coauthor of the draft and the editor of the file draft from  
which the method was taken, I'd like to see if I can clarify this.

In discussing the draft this week, we have realized what we aim to  
define here is a general method for representing the information  
element properties available in the IPFIX Information Model within an  
IPFIX Message stream using IPFIX Options. Information Elements can  
thus be described inline, framed and encoded the same way as the  
templates and data they're used to define.

The primary use case for this mechanism is the addition of type  
(signed, unsigned, octet array, address, etc.) and semantic (counter,  
flags, etc.) information to Enterprise Specific Information Elements  
to improve the interoperability of this feature. We first defined the  
mechanism in the file draft as it struck us as most useful to keep  
this information around in the archival case, so some number of years  
later when you pull data from tape received from an exporter that you  
no longer have access to you can at least do some exploratory data  
analysis. After discussions at the third IPFIX interop in Berlin and  
the subsequent IETF meeting in Prague, we decided that the mechanism  
might also be useful on the wire, so we separated the drafts.

The draft may need to provide for the encoding of a few more  
properties (e.g., units, name, perhaps a terse description string, as  
have been suggested in reviews of the draft and on the list) but  
these are at this point details, new IEs to be added to section 3,  
without changing the fundamental approach described.

To address two suggestions related to this draft I'm not sure are in  
scope:

First, information element mapping to define a direct equivalence  
between two IEs: yes, this may be useful, and indeed probably quite  
simple to implement using an approach like the one we describe, but  
as there is no concept of equivalence in the IPFIX Information Model,  
I don't think we should address it here.

Second, a complete "capability based" semantic system for enterprise  
specific IEs (or indeed, any IE), which would essentially enumerate  
the operations available on any given Information Element: this is  
summable, this is averageable, this is unionable, and so on. Two  
things to say here. First, a lot of the operations in this list are  
aggregation operations, so it would probably make more sense to  
define this mechanism when we address aggregation as an IE (whether  
in an aggregation draft or separately at the same time). Second, and  
again, this draft is simply a mechanism for representing the  
information model and its properties inline. As IPFIX-INFO does not  
handle operation enumerations, this draft should not either.

Juergen: I have one additional comment inline, below.

On Jul 26, 2007, at 5:13 PM, Juergen Quittek wrote:

> Hi Elisa,
>
> Am 26.07.2007 23:51 Uhr schrieb "Boschi, Elisa" unter
> <Elisa.Boschi@Hitachi-eu.com>:
>
>> Gerhard,
>>
>>>
>>> On the one hand, it's a nice idea to have some IEs which allow
>>> describing the type and semantic of other IEs. On the other hand, my
>>> impression is that the usefulness is very restricted and not as  
>>> broad as
>>> claimed in the introduction of the draft:
>>>
>>>    ... Having to do some sort of tool-specific
>>>    configuration (or code modification) on every tool just to  
>>> tell which
>>>    type each used Information Element has is a huge amount of  
>>> work for
>>>    users and implementors of enterprise-specific Information  
>>> Elements.
>>>    Many tools in fact only need to know the field's data type to  
>>> work on
>>>    them. ...
>>>
>>
>> One of the use cases we have in mind here would be a collaborative  
>> measurement
>> infrastructure where each exporter is implemented by a different  
>> vendor and
>> exports slightly different enterprise IEs. In that case, having type
>> information in the message stream allows ad-hoc preliminary  
>> analysis of the
>> enterprise specific data.
>>
>> Our claim that many tools only need to know the field's data types  
>> to work on
>> them applies...so the usefulness of the draft is not too "restricted"
>
> I have problems with fully accepting this claim.
> You just know the data type.
>
> When is is helpful to know the data type without having a clue  
> about the
> semantics?

You _do_ know the semantics, though, in many cases. These are the  
cases we're largely concerned with. The information model defines  
five semantics: quantity, totalCounter, deltaCounter, identifier, and  
flags; these are representable using this method. A collector that  
knows something is a total counter can do quite a lot with it - time- 
series binning, aggregation, correlation with other counters,  
graphical representations of these and other operations, etc. Even  
with just the type a collector knows how to decode and display a value.

Regards,

Brian



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 09:49:50 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQCU-0005oB-97; Fri, 27 Jul 2007 09:49:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQCT-0005o6-94
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:49:49 -0400
Received: from franclinus.red.cert.org ([192.88.209.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQCS-0004cW-K5
	for ipfix@ietf.org; Fri, 27 Jul 2007 09:49:49 -0400
Received: from franclinus.red.cert.org (localhost [127.0.0.1])
	by franclinus.red.cert.org (8.13.1/8.13.1/2.24) with ESMTP id
	l6RDnWNH029484 for <ipfix@ietf.org>; Fri, 27 Jul 2007 09:49:45 -0400
Received: (from defang@localhost)
	by franclinus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id l6RDmFBr029410
	for <ipfix@ietf.org>; Fri, 27 Jul 2007 09:48:15 -0400
Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5])
	by franclinus.red.cert.org (envelope-sender <bht@cert.org>)
	(MIMEDefang) with ESMTP id l6RDmEWc029407;
	Fri, 27 Jul 2007 09:48:15 -0400 (EDT)
Received: from [172.28.169.45] (vpn-10-25-4-19.remote.cert.org [10.25.4.19])
	by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.66) with ESMTP
	id l6RDlu1o028596; Fri, 27 Jul 2007 09:48:14 -0400
In-Reply-To: <C2CEE927.1036F%Quittek@netlab.nec.de>
References: <C2CEE927.1036F%Quittek@netlab.nec.de>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7CDB1CBF-C65E-4BBA-AA88-7C5743514A46@cert.org>
Content-Transfer-Encoding: 7bit
From: Brian Trammell <bht@cert.org>
Subject: Re: [IPFIX] new work item candidate #4: extended types
Date: Fri, 27 Jul 2007 08:48:12 -0500
To: Juergen Quittek <Quittek@netlab.nec.de>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.001009
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>, ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

All,

There seems to be some confusion on the list as to the intent of and  
method described by the extended type information draft. Speaking  
here as a coauthor of the draft and the editor of the file draft from  
which the method was taken, I'd like to see if I can clarify this.

In discussing the draft this week, we have realized what we aim to  
define here is a general method for representing the information  
element properties available in the IPFIX Information Model within an  
IPFIX Message stream using IPFIX Options. Information Elements can  
thus be described inline, framed and encoded the same way as the  
templates and data they're used to define.

The primary use case for this mechanism is the addition of type  
(signed, unsigned, octet array, address, etc.) and semantic (counter,  
flags, etc.) information to Enterprise Specific Information Elements  
to improve the interoperability of this feature. We first defined the  
mechanism in the file draft as it struck us as most useful to keep  
this information around in the archival case, so some number of years  
later when you pull data from tape received from an exporter that you  
no longer have access to you can at least do some exploratory data  
analysis. After discussions at the third IPFIX interop in Berlin and  
the subsequent IETF meeting in Prague, we decided that the mechanism  
might also be useful on the wire, so we separated the drafts.

The draft may need to provide for the encoding of a few more  
properties (e.g., units, name, perhaps a terse description string, as  
have been suggested in reviews of the draft and on the list) but  
these are at this point details, new IEs to be added to section 3,  
without changing the fundamental approach described.

To address two suggestions related to this draft I'm not sure are in  
scope:

First, information element mapping to define a direct equivalence  
between two IEs: yes, this may be useful, and indeed probably quite  
simple to implement using an approach like the one we describe, but  
as there is no concept of equivalence in the IPFIX Information Model,  
I don't think we should address it here.

Second, a complete "capability based" semantic system for enterprise  
specific IEs (or indeed, any IE), which would essentially enumerate  
the operations available on any given Information Element: this is  
summable, this is averageable, this is unionable, and so on. Two  
things to say here. First, a lot of the operations in this list are  
aggregation operations, so it would probably make more sense to  
define this mechanism when we address aggregation as an IE (whether  
in an aggregation draft or separately at the same time). Second, and  
again, this draft is simply a mechanism for representing the  
information model and its properties inline. As IPFIX-INFO does not  
handle operation enumerations, this draft should not either.

Juergen: I have one additional comment inline, below.

On Jul 26, 2007, at 5:13 PM, Juergen Quittek wrote:

> Hi Elisa,
>
> Am 26.07.2007 23:51 Uhr schrieb "Boschi, Elisa" unter
> <Elisa.Boschi@Hitachi-eu.com>:
>
>> Gerhard,
>>
>>>
>>> On the one hand, it's a nice idea to have some IEs which allow
>>> describing the type and semantic of other IEs. On the other hand, my
>>> impression is that the usefulness is very restricted and not as  
>>> broad as
>>> claimed in the introduction of the draft:
>>>
>>>    ... Having to do some sort of tool-specific
>>>    configuration (or code modification) on every tool just to  
>>> tell which
>>>    type each used Information Element has is a huge amount of  
>>> work for
>>>    users and implementors of enterprise-specific Information  
>>> Elements.
>>>    Many tools in fact only need to know the field's data type to  
>>> work on
>>>    them. ...
>>>
>>
>> One of the use cases we have in mind here would be a collaborative  
>> measurement
>> infrastructure where each exporter is implemented by a different  
>> vendor and
>> exports slightly different enterprise IEs. In that case, having type
>> information in the message stream allows ad-hoc preliminary  
>> analysis of the
>> enterprise specific data.
>>
>> Our claim that many tools only need to know the field's data types  
>> to work on
>> them applies...so the usefulness of the draft is not too "restricted"
>
> I have problems with fully accepting this claim.
> You just know the data type.
>
> When is is helpful to know the data type without having a clue  
> about the
> semantics?

You _do_ know the semantics, though, in many cases. These are the  
cases we're largely concerned with. The information model defines  
five semantics: quantity, totalCounter, deltaCounter, identifier, and  
flags; these are representable using this method. A collector that  
knows something is a total counter can do quite a lot with it - time- 
series binning, aggregation, correlation with other counters,  
graphical representations of these and other operations, etc. Even  
with just the type a collector knows how to decode and display a value.

Regards,

Brian



_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 10:27:30 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQmj-0002oO-2q; Fri, 27 Jul 2007 10:27:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQmh-0002lr-AF
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:27:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQmh-0005Py-0i
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:27:15 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 27 Jul 2007 16:27:15 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFadqUaQ/uCLZmdsb2JhbACPaQsKJA
X-IronPort-AV: i="4.16,589,1175464800"; 
	d="scan'208"; a="149185757:sNHT27578796"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6RERET8015986; 
	Fri, 27 Jul 2007 16:27:14 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6RER8kt029415; 
	Fri, 27 Jul 2007 14:27:13 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA03183;
	Fri, 27 Jul 2007 15:27:06 +0100 (BST)
Message-ID: <46AA00C1.7020206@cisco.com>
Date: Fri, 27 Jul 2007 15:27:13 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<20070727074625.4986.AKOBA@nttv6.net>
	<46A9E9C4.3010708@informatik.uni-tuebingen.de>
In-Reply-To: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=375; t=1185546434;
	x=1186410434; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items,
	=20take=20t wo |Sender:=20;
	bh=Zvi6eNZV786Yf7ZwY0nNH8s2YC7rwRDhD+bl0OB7nlM=;
	b=QzcUDKaag9DdOVNMP4DutBwyDHnDRBKyyW1wpWjvVdJInbkNGqBq3QVfp9wAEA1ruSBL0hoB
	JvxqHn0/2TyThlxUShjbFl0bEBoNA0/0kGCTuemILg8PceVkl+Ww7HsX;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Gerhard Muenz wrote:

> The aggregation draft is very specific, while your mediator draft is
> very broad.

This is a good point. I wonder whether it would be better to divide the 
mediator into several separate and more general drafts which vendors 
could implement in a single product?

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 10:27:30 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEQmj-0002oO-2q; Fri, 27 Jul 2007 10:27:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQmh-0002lr-AF
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:27:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQmh-0005Py-0i
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:27:15 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 27 Jul 2007 16:27:15 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFadqUaQ/uCLZmdsb2JhbACPaQsKJA
X-IronPort-AV: i="4.16,589,1175464800"; 
	d="scan'208"; a="149185757:sNHT27578796"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6RERET8015986; 
	Fri, 27 Jul 2007 16:27:14 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6RER8kt029415; 
	Fri, 27 Jul 2007 14:27:13 GMT
Received: from [10.21.127.227] (sjc-vpn6-2019.cisco.com [10.21.127.227])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA03183;
	Fri, 27 Jul 2007 15:27:06 +0100 (BST)
Message-ID: <46AA00C1.7020206@cisco.com>
Date: Fri, 27 Jul 2007 15:27:13 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <20070726100816.6mauos2yo008k44k@webmail.auckland.ac.nz>	<20070727074625.4986.AKOBA@nttv6.net>
	<46A9E9C4.3010708@informatik.uni-tuebingen.de>
In-Reply-To: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=375; t=1185546434;
	x=1186410434; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items,
	=20take=20t wo |Sender:=20;
	bh=Zvi6eNZV786Yf7ZwY0nNH8s2YC7rwRDhD+bl0OB7nlM=;
	b=QzcUDKaag9DdOVNMP4DutBwyDHnDRBKyyW1wpWjvVdJInbkNGqBq3QVfp9wAEA1ruSBL0hoB
	JvxqHn0/2TyThlxUShjbFl0bEBoNA0/0kGCTuemILg8PceVkl+Ww7HsX;
Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Gerhard Muenz wrote:

> The aggregation draft is very specific, while your mediator draft is
> very broad.

This is a good point. I wonder whether it would be better to divide the 
mediator into several separate and more general drafts which vendors 
could implement in a single product?

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 10:45:45 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IER4a-0001nv-CQ; Fri, 27 Jul 2007 10:45:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IER4Z-0001kz-19
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:45:43 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IER4X-0005s4-S2
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:45:43 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6REjdwu005513; 
	Fri, 27 Jul 2007 16:45:40 +0200
Message-ID: <46AA04FD.2000901@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 16:45:17 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6REjdwu005513
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear Hitoshi, all,

I had a look at your slides. Here are some thoughts about it.

With respect to the Template structure, I see three aspects which affect
the performance of the collector:

- Order of IEs.
- Reduced size encoding.
- Position of variable length IEs in the record.

Let's assume the collector has to copy the record data into an internal
data structure positioned at a certain address in memory.
(Only) if the following two conditions are fulfilled, a performance gain
can be achieved by copying blocks of consecutive IEs:

1. Order of IEs (within the block) is the same in the Template and in
   the internal data structure
2. No reduced size encoding is applied.

As you wrote in your email, your collector makes use of this block
copying feature. And this feature is the main reason why your collector
is so fast when using the "suggested order" at both exporter and collecto=
r.

J=FCrgen: Common collectors not supporting this block copying feature
won't show the same performance gain. So, just repeating the experiments
with other collector implementations does not seem to be very promising.

Here are some further thoughts:
- Having the same order of IEs while using reduced size encoding at
  the same time does not enable to copy multiple IEs at once.
  =3D> no performance gain
- Not using reduced size encoding at all while allowing random IE
  orders, we can omit type casts in the collector, but casts usually
  do not actually require computational resources.
  =3D> no performance gain
- The treatment of variable length IEs always results in performance
  drawbacks because the offsets of the different IEs cannot be
  calculated in advance. So, you would probably not use variable length
  IEs at all if performance is an issue. Also, I do not see how the
  performance can be increased significantly if variable length IEs are
  positioned at the end of the record. You still need to calculate all
  offsets to determine record and set boundaries.

A final comment: You often need to convert values from network-byte
order to host-byte order. If you do this, you have to process the
corresponding IEs separately and cannot use the block copy.

Conclusion: Only under the specific conditions described above, using a
specialized collector, the performance can be improved.

Regards,
Gerhard


Hitoshi Irino wrote:
> Dear all,
>=20
> (2007/07/26 15:38), Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #6 to become a new IPFIX work item is described by
>> draft draft-irino-ipfix-ie-order-02.txt.
>>
>>> 6. Order of Information Elements (Irino)
>>>    Interesting, need more people to measure possible efficiency gain.
>>>    Would this be better as an individual draft?
>>
>> This draft suggests a special ordering of information elements in a
>> flow record.  At the very brief presentation at our session, the autho=
r
>> explained that he can improve the performance of IPFIX exporter and
>> collector significantly. To prove this, he compared a random order
>> of information elements with an order according to his proposal
>> and achieved significant performance improvements.
>>
>> Speaking as technical contributor, I think that if these results would
>> be the same also for other implementations of IPFIX, then this looks l=
ike
>> a very good IPFIX work item.
>>
>> Speaking as co-chair, I would like to ask everybody who has an IPFIX
>> implementation to conduct a short experiment in order to find out if
>> the improvement is the same for his/her implementations.
>>
>> Would any implementor be willing to do so?
>> If yes, until when would you have results?
>>
>> Thanks,
>>
>>     Juergen
>=20
> A day before yesterday, I had a presentation about a performance result
> when exporters and collectors use same order, however I didn't have any
> time to talk about the reason of difference of performance.
>=20
> In the slide,
> ( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
> I use very primitive collector which I implemented. This collector
> receive data records and write the data to file.
> This collector has internal proprietary format to store to data to file.
> The format consists of some Information Elements whose size are full
> size. (For example, bgpSourceAsNumber is 4 octets.)
>=20
> This collector process following steps:
>  1) read the data record.
>  2) convert received data records to the collector's format on memory.
>  3) write to file from memory.
>=20
> I tested each combination of 3 kind of orders for template of exporter
> and format of collector.
>  1) An order same as NetFlow version 5
>  2) Suggested Order in my draft (separating constant fixed length IEs
> and reduced size encoding applicable IEs)
>  3) Random order
> In this test, exporter's template includes set of Information Elements
> same as NetFlow version 5 fields.
> These templates and formats are shown in page 9 in the slide.
>=20
> I measured 10 times this test.
> The matrix table in page 4 is the result of this test. Upper one shows
> total time, lower one shows ratio.
>=20
> My collector program can process bulk of sequential Information
> Elements. For example in the case reading from date records ordered by
> suggested order to writing format formed by suggested order, my
> collector program copies first 20 octets (from sourceIPv4Address to
> ipClassOfService) at once.
>=20
> I described counts for processing in from page 10 to 12 in the slide.
> For example, in the best case that a exporter uses suggested order and =
a
> collector uses suggested order, the counts for processing (processing
> means coping data in this case) is 8 (on middle table in page 11). In
> the worst case a exporter uses random order and collector uses random
> order, the counts is 17 (on right table in page 11). Difference of the
> counts for processing effects their performance.
> my presentation shows one of the best case.
>=20
> Therefore, there are effective case and ineffective case by ordering.
>=20
> Example of effective case
>  writing to files
>  real time flow filtering (comparing bulk data)
>=20
> Example of ineffective case
>  when process each Information Element
>=20
> By the way, if all exporter supports draft-muenz-ipfix-configuration an=
d
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these
> implementations. If this state continues in future, reference order is
> valuable for these exporters' implementations and collectors'
> implementations. Therefore I've thought a reference order should be
> defined as Informational. I suggested an order adjusted for collector's
> performance, however perhaps it is not suitable for exporter. So I hope
> to discuss on WG.
>=20
> thanks,
> Hitoshi Irino
>=20

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Fri Jul 27 10:45:46 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IER4a-0001nv-CQ; Fri, 27 Jul 2007 10:45:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IER4Z-0001kz-19
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:45:43 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IER4X-0005s4-S2
	for ipfix@ietf.org; Fri, 27 Jul 2007 10:45:43 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6REjdwu005513; 
	Fri, 27 Jul 2007 16:45:40 +0200
Message-ID: <46AA04FD.2000901@informatik.uni-tuebingen.de>
Date: Fri, 27 Jul 2007 16:45:17 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Hitoshi Irino <irino.hitoshi@lab.ntt.co.jp>
Subject: Re: [IPFIX] new work item candidate #6: order of information elements
References: <C2CE0E0C.1023D%Quittek@netlab.nec.de>
	<46A8B2EB.6090800@lab.ntt.co.jp>
In-Reply-To: <46A8B2EB.6090800@lab.ntt.co.jp>
Content-Type: text/plain; charset=ISO-8859-1
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.50;
	VDF: 6.39.0.192; host: mx05)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx05.uni-tuebingen.de
	id l6REjdwu005513
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: ipfix@ietf.org, Juergen Quittek <Quittek@netlab.nec.de>
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Dear Hitoshi, all,

I had a look at your slides. Here are some thoughts about it.

With respect to the Template structure, I see three aspects which affect
the performance of the collector:

- Order of IEs.
- Reduced size encoding.
- Position of variable length IEs in the record.

Let's assume the collector has to copy the record data into an internal
data structure positioned at a certain address in memory.
(Only) if the following two conditions are fulfilled, a performance gain
can be achieved by copying blocks of consecutive IEs:

1. Order of IEs (within the block) is the same in the Template and in
   the internal data structure
2. No reduced size encoding is applied.

As you wrote in your email, your collector makes use of this block
copying feature. And this feature is the main reason why your collector
is so fast when using the "suggested order" at both exporter and collecto=
r.

J=FCrgen: Common collectors not supporting this block copying feature
won't show the same performance gain. So, just repeating the experiments
with other collector implementations does not seem to be very promising.

Here are some further thoughts:
- Having the same order of IEs while using reduced size encoding at
  the same time does not enable to copy multiple IEs at once.
  =3D> no performance gain
- Not using reduced size encoding at all while allowing random IE
  orders, we can omit type casts in the collector, but casts usually
  do not actually require computational resources.
  =3D> no performance gain
- The treatment of variable length IEs always results in performance
  drawbacks because the offsets of the different IEs cannot be
  calculated in advance. So, you would probably not use variable length
  IEs at all if performance is an issue. Also, I do not see how the
  performance can be increased significantly if variable length IEs are
  positioned at the end of the record. You still need to calculate all
  offsets to determine record and set boundaries.

A final comment: You often need to convert values from network-byte
order to host-byte order. If you do this, you have to process the
corresponding IEs separately and cannot use the block copy.

Conclusion: Only under the specific conditions described above, using a
specialized collector, the performance can be improved.

Regards,
Gerhard


Hitoshi Irino wrote:
> Dear all,
>=20
> (2007/07/26 15:38), Juergen Quittek wrote:
>> Dear all,
>>
>> Candidates #6 to become a new IPFIX work item is described by
>> draft draft-irino-ipfix-ie-order-02.txt.
>>
>>> 6. Order of Information Elements (Irino)
>>>    Interesting, need more people to measure possible efficiency gain.
>>>    Would this be better as an individual draft?
>>
>> This draft suggests a special ordering of information elements in a
>> flow record.  At the very brief presentation at our session, the autho=
r
>> explained that he can improve the performance of IPFIX exporter and
>> collector significantly. To prove this, he compared a random order
>> of information elements with an order according to his proposal
>> and achieved significant performance improvements.
>>
>> Speaking as technical contributor, I think that if these results would
>> be the same also for other implementations of IPFIX, then this looks l=
ike
>> a very good IPFIX work item.
>>
>> Speaking as co-chair, I would like to ask everybody who has an IPFIX
>> implementation to conduct a short experiment in order to find out if
>> the improvement is the same for his/her implementations.
>>
>> Would any implementor be willing to do so?
>> If yes, until when would you have results?
>>
>> Thanks,
>>
>>     Juergen
>=20
> A day before yesterday, I had a presentation about a performance result
> when exporters and collectors use same order, however I didn't have any
> time to talk about the reason of difference of performance.
>=20
> In the slide,
> ( http://www3.ietf.org/proceedings/07jul/slides/ipfix-10.pdf )
> I use very primitive collector which I implemented. This collector
> receive data records and write the data to file.
> This collector has internal proprietary format to store to data to file.
> The format consists of some Information Elements whose size are full
> size. (For example, bgpSourceAsNumber is 4 octets.)
>=20
> This collector process following steps:
>  1) read the data record.
>  2) convert received data records to the collector's format on memory.
>  3) write to file from memory.
>=20
> I tested each combination of 3 kind of orders for template of exporter
> and format of collector.
>  1) An order same as NetFlow version 5
>  2) Suggested Order in my draft (separating constant fixed length IEs
> and reduced size encoding applicable IEs)
>  3) Random order
> In this test, exporter's template includes set of Information Elements
> same as NetFlow version 5 fields.
> These templates and formats are shown in page 9 in the slide.
>=20
> I measured 10 times this test.
> The matrix table in page 4 is the result of this test. Upper one shows
> total time, lower one shows ratio.
>=20
> My collector program can process bulk of sequential Information
> Elements. For example in the case reading from date records ordered by
> suggested order to writing format formed by suggested order, my
> collector program copies first 20 octets (from sourceIPv4Address to
> ipClassOfService) at once.
>=20
> I described counts for processing in from page 10 to 12 in the slide.
> For example, in the best case that a exporter uses suggested order and =
a
> collector uses suggested order, the counts for processing (processing
> means coping data in this case) is 8 (on middle table in page 11). In
> the worst case a exporter uses random order and collector uses random
> order, the counts is 17 (on right table in page 11). Difference of the
> counts for processing effects their performance.
> my presentation shows one of the best case.
>=20
> Therefore, there are effective case and ineffective case by ordering.
>=20
> Example of effective case
>  writing to files
>  real time flow filtering (comparing bulk data)
>=20
> Example of ineffective case
>  when process each Information Element
>=20
> By the way, if all exporter supports draft-muenz-ipfix-configuration an=
d
> operators can set configuration about template completely freely, my
> draft is not important, because operator can adjust configuration for
> collector.
> However currently NetFlow v9 implementations of some router makers are
> not configurable at all. Operators can choice preset template on these
> implementations. If this state continues in future, reference order is
> valuable for these exporters' implementations and collectors'
> implementations. Therefore I've thought a reference order should be
> defined as Informational. I suggested an order adjusted for collector's
> performance, however perhaps it is not suitable for exporter. So I hope
> to discuss on WG.
>=20
> thanks,
> Hitoshi Irino
>=20

--=20
Dipl.-Ing. Gerhard M=FCnz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From clnozekra@wlacpa.com Fri Jul 27 11:27:17 2007
Return-path: <clnozekra@wlacpa.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IERii-0006k5-Ig; Fri, 27 Jul 2007 11:27:12 -0400
Received: from [218.31.50.158] (helo=wlacpa.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IERic-00074s-4n; Fri, 27 Jul 2007 11:27:10 -0400
Message-ID: <30b001c7d046$6ccb0100$5e3f082e@clnozekra>
Reply-To: "Tawna" <clnozekra@wlacpa.com>
From: "Tawna" <clnozekra@wlacpa.com>
To: "Elmer Carr" <ipfix-archive@lists.ietf.org>
Cc: "Chana" <idmr-archive@lists.ietf.org>,
	"Dierdre Nguyen" <ipsec-archive@lists.ietf.org>,
	"Vinnie" <6lowpan@lists.ietf.org>,
	"Kiara" <kitten@lists.ietf.org>
Subject: What about ur suggestion
Date: Fri, 27 Jul 2007 12:05:29 -0300
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_649_8C2B_45FC7805.CA452FCB"
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1

This is a multi-part message in MIME format.

------=_NextPart_649_8C2B_45FC7805.CA452FCB
Content-Type: multipart/alternative;
	boundary="----=_NextPart_002_28DA_FF57FC72.97D06ED7"

------=_NextPart_002_28DA_FF57FC72.97D06ED7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 
"Ah! ye were sorry to spilled dirty leave school for ok good pig-minding,=
 weren't ye?" "Look angrily 'ee here, Jan Lake," said he. program "Do 'ee=
 thenk THEE could complete paint the scale sign? I dunno what I'd give ' =
body "I don't remember, my story dear," reaction said concerned Mr. Ford'=
s client.
 
"Well, well, Master Chuter," said the painter and rely stretch decorator,=
 rising to test go, "let the skip boy draw pigs an control They include m=
embers of very politely eye saw diverse corporations. Some, more industri=
ous and equipped with better t deep Still support butter manage influence=
 and comfort me." Whilst the painter breakable was rapidly still thank ga=
zing across the water-meadows, Master Swift, who was the stocking soul of=
 hosp  
Not at refuse all: the bag is woven around nothing, bet as accurate in de=
light shape, robust as finished in structure as under Total abstinence fr=
om food open string could be understood, if it were cholic accompanied by=
 inertia: poorly immobility is not In both cases, act the fight laying ro=
ll chase is taken as complete, for the same reasons as above. Let us in t=
he first place ink consult the old nests of journey the Mason-bee of the =
Shrubs. move I have sanguineous said that the Like the Osmiae kept hearin=
g and the Leaf-cutters, the Anthidium shows mine an inquisitive urgent ne=
ed of a ready-made home. She n Jan shook field steam dusty his head. "I l=
ikes pigs," fancy said he. "I axed Master Salter to let me mind his. I ge=
ts a shil
"You're looking very tired," said telephone Lady Adelaide, gently; lonely=
 "but about the awoken child. It were is Lady Louisa Amm idea Another, di=
stracted from her work by some startling stretch vibration, fit leaves bo=
w her nest at the moment when th  bravely Master Linseed's army parting o=
ff words produced upon eye the company that somewhat unreasonable depress=
ion which
 
"Here's a cause pretty caddle look about giving a boy's due!" said the hi=
gh-pitched innkeeper. "But I knows ornament the points of a 
You can blush tell wire these plane borrowed dwellings by the unequal fuz=
zy size of the storeys. When the worker has hersel We will end with bat s=
ome series that appear colour warm dreamt to me incomplete, in view of th=
e small number of cells and Jan felt as if his brain were on fire. flag d=
ead "If 'ee'll get me triangular the things, Master Chuter," tremble he g=
asped, "and  trick The tears flowed down Jan's cheeks. It had start been =
a favorite egg hymn of his foster-mother, and vesical he had oft
The innkeeper was not insensible to this chess consideration, but kill ye=
ar his chief wish was to pencil spite Master Linse In spite healthy of hi=
s tears, Jan was fain to join as the hymn went on, and jump he zoom sang =
like cry a bird, - But there is evidence crime of waste when the occipita=
l insect makes use of split a bramble stretch hollowed by another. This i=
s t As Lady Adelaide went canine out, her son came in, chance and rushed =
degree up to his father. If discussion Mr. Ford's client had fa  
------=_NextPart_002_28DA_FF57FC72.97D06ED7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:75e6e01c7d046f6cfd82b0f2e4946b@c=
lnozekra" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"Ah! ye were sorry to spilled dirty leave school =
for ok good pig-minding, weren't ye?" "Look angrily 'ee here, Jan Lake," =
said he. program "Do 'ee thenk THEE could complete paint the scale sign? =
I dunno what I'd give ' body "I don't remember, my story dear," reaction =
said concerned Mr. Ford's client.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"Well, well, Master Chuter," said the painter and=
 rely stretch decorator, rising to test go, "let the skip boy draw pigs a=
n control They include members of very politely eye saw diverse corporati=
ons. Some, more industrious and equipped with better t&nbsp;deep Still su=
pport butter manage influence and comfort me."&nbsp;Whilst the painter br=
eakable was rapidly still thank gazing across the water-meadows, Master S=
wift, who was the stocking soul of hosp&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>Not at refuse all: the bag is woven around nothin=
g, bet as accurate in delight shape, robust as finished in structure as u=
nder Total abstinence from food open string could be understood, if it we=
re cholic accompanied by inertia: poorly immobility is not In both cases,=
 act the fight laying roll chase is taken as complete, for the same reaso=
ns as above. Let us in the first place ink consult the old nests of journ=
ey the Mason-bee of the Shrubs. move I have sanguineous said that the Lik=
e the Osmiae kept hearing and the Leaf-cutters, the Anthidium shows mine =
an inquisitive urgent need of a ready-made home. She n Jan shook field st=
eam dusty his head. "I likes pigs," fancy said he. "I axed Master Salter =
to let me mind his. I gets a shil</FONT></DIV>
<DIV><FONT face=3DArial>"You're looking very tired," said telephone Lady =
Adelaide, gently; lonely "but about the awoken child. It were is Lady Lou=
isa Amm idea Another, distracted from her work by some startling stretch =
vibration, fit leaves bow her nest at the moment when th&nbsp;&nbsp;brave=
ly Master Linseed's army parting off words produced upon eye the company =
that somewhat unreasonable depression which</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"Here's a cause pretty caddle look about giving a=
 boy's due!" said the high-pitched innkeeper. "But I knows ornament the p=
oints of a </FONT></DIV>
<DIV><FONT face=3DArial>You can blush tell wire these plane borrowed dwel=
lings by the unequal fuzzy size of the storeys. When the worker has herse=
l We will end with bat some series that appear colour warm dreamt to me i=
ncomplete, in view of the small number of cells and Jan felt as if his br=
ain were on fire. flag dead "If 'ee'll get me triangular the things, Mast=
er Chuter," tremble he gasped, "and&nbsp;&nbsp;trick The tears flowed dow=
n Jan's cheeks. It had start been a favorite egg hymn of his foster-mothe=
r, and vesical he had oft</FONT></DIV>
<DIV><FONT face=3DArial>The innkeeper was not insensible to this chess co=
nsideration, but kill year his chief wish was to pencil spite Master Lins=
e In spite healthy of his tears, Jan was fain to join as the hymn went on=
, and jump he zoom sang like cry a bird, - But there is evidence crime of=
 waste when the occipital insect makes use of split a bramble stretch hol=
lowed by another. This is t As Lady Adelaide went canine out, her son cam=
e in, chance and rushed degree up to his father. If discussion Mr. Ford's=
 client had fa&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_002_28DA_FF57FC72.97D06ED7--

------=_NextPart_649_8C2B_45FC7805.CA452FCB
Content-Type: image/gif;
	name="64i4Ve.gif"
Content-Transfer-Encoding: base64
Content-ID: <75e6e01c7d046f6cfd82b0f2e4946b@clnozekra>

R0lGODdhUgEuAeMAAPz+/HFrrDHupnfvYniEqLJzaPwQhNKtmhBHxAyI4MzTF5AMZDwCHPwC1BIL
rgAAACwAAAAAUgEuAQAE/hDISau9OOvNu/9gGIRkaZ6kgK5s675wTI5ybZfqrb9DS+zAoHBILBqP
yKRyafsxn9CodKpzMgvUrHbL5dK2hq54PMV6yei02nVYu9/weBJBTSAScko7z+936CwJB3eEdnEK
fomKFYAnhAd2kY2LlJWWF5EACZJ4FJmXoGidoRSEFZ8Shi2IpK2uIT0gqKl3N6yvJwu4frEepqe1
AJO7TLrEr7MSv8nHzcRWO7/AndKahaQ5YmFixkvDSczLwdacob3O6DrVtJ2bgKiqqeTf6W/b9TXh
qsvx8srl+AJ2+ULk2gRJ7A4i9KSqHyd6AiOCeghQmMOKDumooNiImcSP/nIKIRhZjg6zhcK+qTAI
b5ymEqMsmYkYE846i4Cq8cMwK57OhhATgiRVMxGqce7+dWPUT1zMT0lRktPwcKhVb6Wq+tsq9dPP
nBQnGOQp0uPVsyuKZigEbaTQr+wmQXUa12XWskjtokVxjgnBI2o53Do4Fifhdi5/FVYs1VOwsqn6
DYV2ou+Sv3EKT8VJLSPip0AlMx3GOOje03PwwNt099+kO51Nbz4sFPUHM5Ztp73p9J3LuYFdl44d
Y0/A3Lpv4CUudp9oxxxjV1xhPN0AXYMtYR7j3PfTYGZdh407/eWlbB3ueYi1VDsfsMOSGs7QMma1
ljdltAeJfs1MN8Bt/pBfc3I9ppo04ZWwXwyUJYdPRwMmONuECrVT1XNx/MeFhk9wiEZ1ArJ2wYDi
MUTPcKZkQuIbDTrYBYgoJDgLggK4E+BdAEnYRYsuGgGjEHq1RhtnCxESX2869qgkkBZkQgNdmyXz
VWfQrbjkWleicJ+B73R3ioizIYhXlmQi0RtLdsFG4JBNxjdPmSGoF9F/DNhgpFeS1acQRPLNA5xs
Tfq5VwMuMGDooXx4CAsJKuY5jjRqkhfpQo0eSdVyFtTJRXBcHOqpodbFKFqfevrJkkMHDQKAGZnA
GJ2VVzKAgKae9qEpFEfl2iWXrmFSgE8eTaeZFopK8KMUiEqQ7Ec8/sKUF3NCmSUmn6PCGhcSihaL
bK0A3AoqPs22AKVBK4I5EkSRjsbpkEkG9Omt3YLKAAHwHhNuIARK0lE831kYlLSGqEhBLFCe9ikF
7xJQ3bfFPYjYmhMasmKEtdi4UA/tCpTswcpu7C3HHCxrW792sYZhbRaYcg1KfRrM8LIwI/ouwx13
u2rH9To41h6FcDrsVDPi6Z0c977g8cdIx/stt0obWrR/XfwsVn4qe9brWwGrsV0N7/bQRsx1vrvA
0jLDK3IGZ+eRsw06FmajSYmFdvVygO7CNAAHcFt22GOT/THOCKeddmZBNLbWq1djPfSb8x1Wtwn9
oTGzvINX/vK7/hMMnkF2oLRYHgdvUxr34qU57vjJKEQuOeVm+w14pq6/rnnIcxTOk+EhiiSk4tGO
XhvqJ6guxuxNX07z64EfTQLIRTiwwtZKjP7Z3FZrAuzjIQjf6fEXHK83rcZzLDPsdx/M/LFQQE+B
+jFUX3DQ8AUc5AraWwLy97FbjnnTmd+tJJRCg87pDMK+vRgPefjr3t5wNjM4jSYyi6MehNalJLCJ
j3sI9NvkHDgiubFrfhzcT62UR77+JY2BtBKA//ClA+RsoSndCY62bLOgCpDQhgdUmgmTV761TcGF
AJATEHxIn0eNZwIz5GD/MLA38J1QhzXbIQYjQkQQQEaJMmgg/hS3ODknapB4V6KgDWp4FeaBzYT7
E5nHdpiB+mFxdZU4I/KUJQEVts5sc7yAG984vHrJSxFqJFsdz2ZGBuyxAgZIZCL5OAaaUS5zMAAi
ETa4RRRWcQOKzOQN0DcU5xnhclGs5AokOYQeco95cVLPItUgRpctMV4MNA8bbZVD/pVglRPAJSOP
AChBwhKWoBqFL7tAxg3kb4oZ0KUuQfC0Xa7gkbILW+sCZ0layvEDmRRiEBXZgWY60wTQBCb4cMhE
byEsA6TMAhgvoMlcZnOVy/ymEJgWTlAq8G95nEA646BMbUoAnnKKpzyz6Ehp1pNW5Ayl//pzyTRU
Z5m4jOg2/iT6z20KdKAsuOMTc2hPm03RoA0lw0NVOdEwZPOf9wDoSTGqA0KO85X7oyMG/QhJP2Tz
ACV1p063idKUCvGibMBoR335slCe04bOcyQ/FTnSnObSoiilQDz7WVHqPKGYoRjhS21GR6N29ahh
q2lIWcBJGLyTpBJ9pwWoylNuYsCf3gQCVluBzygOs6Zg5SpXczbWD5Q1A0l8K0/dGdB7HIutZ2Wn
P1kKAjzGzoaZ+mpX14bHtQbhr9j86TZwqllEmpSiUjUAA4DKTgfONWQFhWxk9zpZqX51bW51g09j
u9Oo9rS2PUXAbJPZzjxg1g2nVK0fEVrV1iIyiKG1B21r/utWZS4orRddZG8tuljGasCcMpUsNWGL
3M8O9gS/1UBc06PW75rXttzEgkBBS12fWhdtaoQkcbv31uXaNrTV1YMJsJdK6ZbUqZ6973mhil54
PjW/WUUmFKap19Wu1b5TnehT7dHT6d7WvOtdKVX9e1xLLIWofS3CHuYrgW4Qcbkozml516BSxeI2
wu2MLYfZ+oICxqCAxkhtaqGwMDNqQMYRjipAZYtg6ha4sBIW8IxTygT+XsDGXp3jOqdQRZMS9sFC
BnAaSIvfCge5wMklMHLFMN7rUvZvw6WwlQds2wB4l81PKDN5kxzmwaa1tGRGAYhmiua6LvGQSgAy
b7Ms/uAoyJkFZwXweotbiR4rcIkdfeUAUPmE2VK0uW/mshwATVhlXrjO9o3jme3qZ1LjVRsoVcCQ
W3yWlU44y0VW2ym3SrZh3DXEUlC1Jg1gDE0HBMLJ9bUN9mk083lRmsr6hiHzeU8FVyFObhb2UAoL
ZyCkM7AlGOeO+YxGMx+1wc82QaxtE2pieA/ZCUWhBBpERKU6I7x8GLfd0E1NHLZ7tWE1rgsOTQV+
DwXeSLigZD9qgVvkm7WqNYG/pbDw98KgqFHWLsKJ68PKdvgVnNslsYdIaYlTvKvbwS6WGeFwSmxc
B/Km6cSVFfJfujagTsaivEVaaXBmrhP5rji4K2pl/gOXHAQZh4OzJykyYSKcvorVJowvge0dnPYS
3kNWQu+d9M6G2b1qeDoStG4/Brtcrh0gsYMfjOQAt/XNaOA6Lpp+A47u+Ak+/jF7r57pmf98k8/E
5x9f2akfj9nIZudwte+uBr3Te9YSl0LPC83cuhOeDwd1OeIlj2sgYHrQZ2e8AWu+LXRD/OumJjXb
b2DpYKtYy3IYPQrU/grPaypvdw39Lw9lhikLYdWn1/zj13A0gcNOoU4sse2TcNIhDyXot8GFAtYI
Vr7Wvq4j7Fuzo+BeaXdTnsiX+nbr5EnZCxKkSB+7BRqeSjRweve//1b3hynIMNRJhQlXaPytcn4J
/qiepd8DfscKENZlf1usCVd5EQFw6Md3hudRoKcpX4BQ2KVyBWh/G3B/NVB/VHA/BpWA+KZXYtdg
PmR3QECAi5B9RECBjbR987dyR4dXHeiBD9gjwSVcxkVZiYd2LNiCFVRvRbWBCFhaPWdhMACCrwBl
zlQ+8pV4ESdmdYZbIECCYyCEJAAREthIQ8cEDKZzvKV01GYAAMeEQsB6V3ADrbQBTrh9AhhwRlhl
GeZZAsBZ7WWDRzCG+gd6WhB3V3hlnhUGAiB41ueGSWBPfliGQSBy9bVbgVd3NciH8/SHS7R8HYdq
axZquKd7LOAA3YeIKKBVRhV7R/gB5OcB0lVt/pE4eChQiaCTB15IS8DneyUkTlrAaiOnh4foAmH4
gNxGanx1a43IBDHmeMaXPZaYiI9mahb0dQW1QlDwX9zUix/Ahb8YArU4e6NGb8TYgIAYBNV3iKc4
UFGYUQeYfoFUbzw0hYG2h0tycmpjgJoCDY81jb9ni0Nhjrf0ZEYAj4A0a1uVifRkeE/kAdvoBxK4
WHDYAf3oAQHZeeiYPOBIa14UTUaoBkCYBFzIKQM5b3zHju0IjazzUpFGc8jwRl4nhx51QOCHke7I
TM2IC3L2ds0HaSEZTRp5gc0ggqgxkUoQUwfYfy8ZTrNCOwKZBDJ5knMIUypQNsIIjaBjjBxA/pOU
wIwlByrwR5RGiT9WiHMVmRxMmSWzWAE58H0vyZByyFeZeGohtAtXOYGA1ZVQpGBguYMayEjZqAUy
WZafFHyyF34AKHIOCJRE8JN8MJT3aJcx+FoOhkGxqJf4gJQyCEyCGYAuppduRIpHoJQ7MFMwqG8y
eCuNYIiFyYlXpTHSSAKS2YfzZU6CeE7c5VSbaZgtWTPiWI//15aA2WVmd4dkwpdL8EhLcwxeZ4Vr
NQAQ9WWqNAQFaQPVGAdcuXN0JZbKKQG+eWevqFLkqJqm6XoNKWowI3cXR3dgxpksNQoPeV2s+Zmk
YBxVNnJ3aHzSJpe6kZUcUEDQtHeWgFlr/paE6HUzmWddMXd73giSrbBrqGdnuSedZnicuzBdCQCL
23mS6tkCuFmceXCgjndkMJCfKNCJa1B/w3kBGGMBupCb8IkLGvZfeWCh2KIGG0o770mhLUUEgieg
kgM44VSTRRCdlRCaBuR6B+eibmCblNCgG+JAhFIMPGoJfhmeE5ChLRikSvCWioAePsqfQ7GgOnoC
x+mgFmCjb/Cdb4CkIMClt8mKUBoCWOqQu0CiHeClUaBt4rkCQ9ojWhoE2aiipbA9UTmCSvKmF0CT
TMoCclpwgYhsrVkBXCelk9EjbZpRUWmlwbMBZjqlUPNo7zkEhOqoi5BEIIacSTCmFoCn/pQacICa
o0aQmh7AqTLAqfT4Xk/aAqeaBL0wqRtAqmmAphUAq6VEnYE6BGO6qg4iq8dYbGGqBDaqqEHQp9wh
EOzZqYTXqE15q8gaBRunqZ/UocJ6AqLqHorAq28wrS1Qg8fqDK6aHIm5Bt3KA0Swp3dHhJ9nFbra
rB6wlqylKd/Krrugeu76l2tKArSqAUEHrfKap9k2mB63kCfAr+XokQC7c1aAl8wKBeaaCOtKCocK
nvZZL/SigosJquJHrYmAfPm6e+m6mEeXk9r6av0qBB3rqxcLgCDbkAtrAgGgrHp5shkQkNSosrB5
lyN7JfG6JGtJmoRkV7/6TUVDrBJA/hAEuwjXybIW2202SLQAYLQ3KH6jmV2Z06FsiUU7u6PZ+oIN
CJvSF6k1mgQNl7VFALNmCJsHN7VR1rNqcLSMZbbLc5c2i5cy9ZclC1g9OQTjOkSVebM9i7Gk0LCu
4LZkkLRtiQVdO3HDd6R3O5lygJe1V7cfh7ZQurhyAJmxgrR5FZhoq4N7VZqD6yA5m6ZMi4Ihy0Sb
OwSCiwKEq7l7W3icO3vLyYHVeQLqg7ljELFTUD8yqbaxaZw757urOJot27iWOUvh+rifx5uVlbzG
G37EK5iCAwOhCYigm3jEJVpGaoP8mrgpiL3CWr0xkJditUIMOLrOgAUq2r3Hi0DQ/ptVJ3i6rCm9
YIS+8kSZfftt3msrYedx8re0qdupemOz/0dxlkucc5mbAye8CEhEr4t+hlvAfhtLHCCq9ttYGyNf
/iOyW9EF6DEKuusKL0i1lKtvVZcIwUV1NgN/XUWVoqAIMou6CTm3c0aIkOe82JUNw6WWDBIQ1UG2
YqnAuYhfyEif+0WFIyy/kOR+FNwtTvt4jvW9NfxZmJZYJYC7Yso17au/9CsraFO7HhvAs3vCIVrF
/pROzIil08vFtBu812uDUbeKU1xeZeycHuBGq5ttI6y2aWa68fshpBBSl5RYiWZpyFh6JuCF2Hqw
+wtuJPaxDkVuxWfFXtZeh7xi/jUQhebItq85uV78xpSqVolGxFZcx8HZX5oWwwipXXUyE5OrDJ7b
qa6GyZZcyGZcxKjcAapcTpv7yiR8o8oFXTDmnytmyl62WK7WadXKjSq7w8bbW5SszP6FyZN8y1c4
zFi3BAnLubGsy3+nAV54wXG7c9vQUOQ3kD54zFSsSAuAVqPchtd8nu6sBOHibpeEVQfQzh2wH0Bs
NHWbgbawreU2y7Q8yoWcAe0MzQTdT8l8m6Dsia0HtFKUBwvNTUth0NFcdYZMxKTc0CfJwOcLB9NF
y7Vcy6TVAwpNWyNdALZsxAVIa8IVvXKAdh0tzUWW0gztzu/cU5yVSHmcuTcL/rK+PAXeFF047Wka
bcnnScpK7U49zc7k+NMb8MCFu7Lya3H94yHiHAMVndNIts5frdPKbNPFrGlSnQixJoIqR40/uyrT
5K5goNNizdENPdJ2DWS2PM8QnLZWDYEGDFP6hAbJ7NHJCGEqLcq71tSUPNjlJhBp3L8mTD58rLIP
y6LyTHaEfdh5PdbSPAEJLczLTCYbTMOf65VEhoUeDXjqzNiIvVyf3V13ndoOp5Gkvb9b3Vi3JNux
DdZyvdMVBs9kTaMs8DRwuwV7572+G9LGhHeINtC7/WnB7YMH3dEkDQTeRNXKm8GWedzlC9enbQDZ
INvUrdsZ3dUfbbgwLcZE/qQt2N3ceM1lFX3Njf134j0BxQ2uDDzD02dT6UzEvdbfJT3FhHeVA/xa
4SqwIg3fR43ZAC7Poe0glZ1+dJQ3jDl1mAqOTJBO5i1V0Vbd/j3fU5rEE1zacnzbXI3TB0pY0aba
VZfQc/zgSBDhhXeLk1XgXIyUY9BPEMrZLE5YuqZp002yaSDjfbmDjVzCYKwNu7jgNf3img3iNriV
NB68BMzWwfyJPN7Uc6zaLf3NSNDe5pZzjAxZH6q0W7bbDV7Jv23Sl+zlQFmvrHzVQcxixLzZ8Bzf
Sg2dvi2gNk61mpIAIB20cW3nGw54dZ3XMN6U77vFPRDH5foC72zKh6zm/p3t4Y5qdAa+siz8uXQ5
RqSn52NtzJdN6TxGBq973wexwApM5Vuc5FyA5ku+SmbQ1YkOA4uszZ+EWo5c5UUY2UAwpottYYVu
FWDeRxY+4jna6d896jxe3/hQ7MCVlkuLkzW+yoVyBJld2DH2eLWOAfVHtw3MgGwMuFzVzyRg2F3+
vMRpzxtVvqhbvLoY5OchVBIrPuVE7jk+zVCeHn1w6+5StUgeWXYE7yz65N3uBv5+mJBMdQpr4hWQ
fYh+8MZbkPYuw8j9z5Um7xFhGk/sBpApq1U02Ua560iw5xvvAh3PBFicRX2LNKtOUwRPApQh8QGR
8sm5XQQ8cMeO7z6g/u7gnAYNBZaTNueZbks+X0EM0wsOmNzWjkRzogioTmX+HOfbvcWeQieu7oZR
H5kS21KvDJNwLtFHPwZY0LrvDu72Nrt/5PAuctZnoSmuHJv7WNpY3fQD5fZnUSzoPXaTzbUxvyNj
z6B7X9tEH/guyLXuTvInyPaxahs2T7oT7FIwb7ctAO2q2yON0Im73K4Bj29EJfZQ/wF4X6ZQl/PJ
+3ELzyIaYPYuyjkinrIaKO5j3EZdwPoCGl6GsuklPD6snvWG75mwT9st//ffBEQJ/xFDTeV0+9Bu
YPtIcPwg8X0Bu/yz71c1xgLOP/aga8AZzPhn+vso7Os8D/5l0vd9gmD5cUap8WUUi7D1+Jol3g+X
ybH5aECP8X+nPezDJmD/xAD9JpD9EABAktVenPXm3X8wFEeyLAvzClL2Qiy0lWe6tu9WwXe+f3vT
ADgknna6YlK5TMaYT2hUOqVWWU5rVgtcbHkrb1g85pLNZ3RavWa33QSr0D2n10NwO9CQp+L5nwgA
Ow==
------=_NextPart_649_8C2B_45FC7805.CA452FCB--




From details@atseurope.net Fri Jul 27 16:50:37 2007
Return-path: <details@atseurope.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEWlh-0003bO-LM
	for ipfix-archive@lists.ietf.org; Fri, 27 Jul 2007 16:50:37 -0400
Received: from [200.246.138.2] (helo=200.246.138.2)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IEWlg-000713-Gz
	for ipfix-archive@lists.ietf.org; Fri, 27 Jul 2007 16:50:37 -0400
Received: from [200.246.138.2] by (null); Fri, 27 Jul 2007 20:49:49 +0000
Message-ID: <000901c7d08f$04c29018$053dcd84@uffuclne>
From: "Atseurope Service" <details@atseurope.net>
To: <ipfix-archive@lists.ietf.org>
Subject: Account details confirmation
Date: Fri, 27 Jul 2007 19:02:26 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0006_01C7D08F.04BE6A7C"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.2663
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C7D08F.04BE6A7C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  ---------------------------------------------
  Thank you for using Atseurope.net !
  ---------------------------------------------
  This account created  27 Jul 2007 04:24:47 PM
  from IP address=20
User Name: ipfix-archive@lists.ietf.org
Password: Z4IiG62U
Click here to login:
http://www.atseurope.net/index.php?n=3Dipfix-archive@lists.ietf.org&v=3Ds=
ession_ID3AkFIc3Z=3Dd
Your account ID:10687405
If you use anti-spam email software, be sure to add =
'details@atseurope.net' to your list of approved senders.

------=_NextPart_000_0006_01C7D08F.04BE6A7C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.2759" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV align=3D"center">
  ---------------------------------------------<BR>
  Thank you for using Atseurope.net !<BR>
  ---------------------------------------------<BR>
  This account created  27 Jul 2007 04:24:47 PM<BR>
  from IP address < 65.114.146.211  ></DIV>
<P align=3D"center">User Name: ipfix-archive@lists.ietf.org<BR>
Password: Z4IiG62U</P>
<P align=3D"center">Click here to login:<BR>
<A =
href=3D"http://www.atseurope.net/index.php?m=3Dipfix-archive@lists.ietf.o=
rg&u=3DsessionID_vQ1aXIO8=3Ds">http://www.atseurope.net/index.php?n=3Dipf=
ix-archive@lists.ietf.org&v=3Dsession_ID3AkFIc3Z=3Dd</A></P>
<P align=3D"center">Your account ID:10687405</P>
<P align=3D"center">If you use anti-spam email software, be sure to add =
'details@atseurope.net' to your list of approved senders.</P>
</BODY></HTML></BODY></HTML>
------=_NextPart_000_0006_01C7D08F.04BE6A7C--





From support@atseurope.net Fri Jul 27 17:15:44 2007
Return-path: <support@atseurope.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEXA0-0004fA-6E
	for ipfix-archive@lists.ietf.org; Fri, 27 Jul 2007 17:15:44 -0400
Received: from c-76-30-96-212.hsd1.tx.comcast.net ([76.30.96.212])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IEX9z-0007XH-HY
	for ipfix-archive@lists.ietf.org; Fri, 27 Jul 2007 17:15:44 -0400
Received: from [76.30.96.212] by eptf.atseurope.net; Sun, 27 Jul 2003 21:15:20 +0000
Message-ID: <000801c35484$0128eb3d$3b2c54b0@fmywumre>
From: "Atseurope.net Service" <support@atseurope.net>
To: <ipfix-archive@lists.ietf.org>
Subject: Atseurope: account details confirmation
Date: Sun, 27 Jul 2003 19:27:58 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C35484.01250049"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.2663
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C35484.01250049
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  ---------------------------------------------
  Thank you for using Atseurope.net !
  ---------------------------------------------
  This account created  27 Jul 2007 07:59:35 PM
  from IP address=20
User Name: ipfix-archive@lists.ietf.org
Password: hiZYTf70
Click here to login:
http://www.atseurope.net/index.php?p=3Dipfix-archive@lists.ietf.org&x=3Ds=
ession_IDx6tapWDh=3Dz
Your account ID:10863851
If you use anti-spam email software, be sure to add =
'support@atseurope.net' to your list of approved senders.

------=_NextPart_000_0005_01C35484.01250049
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3790.2759" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV align=3D"center">
  ---------------------------------------------<BR>
  Thank you for using Atseurope.net !<BR>
  ---------------------------------------------<BR>
  This account created  27 Jul 2007 07:59:35 PM<BR>
  from IP address < 64.121.156.254  ></DIV>
<P align=3D"center">User Name: ipfix-archive@lists.ietf.org<BR>
Password: hiZYTf70</P>
<P align=3D"center">Click here to login:<BR>
<A =
href=3D"http://www.atseurope.net/index.php?c=3Dipfix-archive@lists.ietf.o=
rg&l=3DsessionID_j0Z9cPK5=3Dl">http://www.atseurope.net/index.php?p=3Dipf=
ix-archive@lists.ietf.org&x=3Dsession_IDx6tapWDh=3Dz</A></P>
<P align=3D"center">Your account ID:10863851</P>
<P align=3D"center">If you use anti-spam email software, be sure to add =
'support@atseurope.net' to your list of approved senders.</P>
</BODY></HTML></BODY></HTML>
------=_NextPart_000_0005_01C35484.01250049--





From sniderjgycoo@pdp.ch Sat Jul 28 04:17:02 2007
Return-path: <sniderjgycoo@pdp.ch>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEhTx-0002ze-Ts; Sat, 28 Jul 2007 04:17:01 -0400
Received: from [203.113.131.154] (helo=pdp.ch)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IEhTv-0006Z6-VC; Sat, 28 Jul 2007 04:17:01 -0400
Message-ID: <3e3101c7d105$20d88190$58829d54@sniderjgycoo>
Reply-To: "Nicki Spencer" <sniderjgycoo@pdp.ch>
From: "Nicki Spencer" <sniderjgycoo@pdp.ch>
To: "Kyle Thomas" <ipfix-archive@lists.ietf.org>
Cc: "Rossana Bradley" <idmr-archive@lists.ietf.org>,
	"Lisa Perez" <ipsec-archive@lists.ietf.org>,
	"Shana" <6lowpan@lists.ietf.org>
Subject: Happy or sad, we care
Date: Sat, 28 Jul 2007 10:50:35 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

Assisting over 220,000 consumers Discount-Pharmacy is your safety medicine
supply for the cheapest value for all your email order medicine
treatment(s). At DiscountPharmacy your health is our number one concern. Our
skilled team of physicians and pharmacists will do their greatest to make
your  experience stress-free and satisfying, to make sure that you get the
best quality service. When it turns to excellent customer service,
economical amount and express shipping, we set the standards.

We propose a choice of brand name and standard drugs at low cost for all
your prescription needs. If you find your medical recommendation cost lower
, we will match that amount for you. With Discount-Pharmacy you will receive
the best cost on your medical instruction.
If you do not already have a medicine then our doctor of medicines can work
with you to provide you with your medicine treatment.

For more Information, Try this Link: www.onlysale.org


squash approve Jan's very blood seemed to stand still. As Master Swift bad
cat put on his spectacles, each fault in the pai wave Deep emotion kept the
old man silent. food It was pause a mixed wonderful feeling, ~ first,
intense pride and pleasure, a My pencil forces a third family upon the
notice already overburdened Spider; and view this too loss bear is
peacefully acc 
For some gestic years the ex-servant before stare of the windmill had been
rather favored by fortune wrong than otherwise. He The back slain gallery, 5
or 6 millimetres (.195 to .234 inch.-- Translator's design Note.) wide,
woman is shear too narrow t






From skenyonmiale@ttn.net Sat Jul 28 13:03:29 2007
Return-path: <skenyonmiale@ttn.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEphR-0007wV-9n; Sat, 28 Jul 2007 13:03:29 -0400
Received: from 114.136.132.202.dynamic.ttn.net ([202.132.136.114] helo=ttn.net)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1IEphL-0005sE-OL; Sat, 28 Jul 2007 13:03:29 -0400
Message-ID: <289801c7d162$ecc93d00$8d03513f@skenyonmiale>
From: "Darnell Stevens" <skenyonmiale@ttn.net>
To: "Irma Richardson" <ipfix-archive@lists.ietf.org>
Cc: "Marlys" <idmr-archive@lists.ietf.org>,
	"Coletta Perry" <ipsec-archive@lists.ietf.org>,
	"Carman Reid" <6lowpan@lists.ietf.org>,
	"Kami Cruz" <kitten@lists.ietf.org>,
	"Karie" <iporpr-archive@lists.ietf.org>
Subject: Listen to your heart
Date: Sat, 28 Jul 2007 22:02:01 +0500
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_59B_0098_2465B9BC.04F28C22"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 410b68b37343617c6913e76d02180b14

This is a multi-part message in MIME format.

------=_NextPart_59B_0098_2465B9BC.04F28C22
Content-Type: multipart/alternative;
	boundary="----=_NextPart_8A0_2EC7_B2F000EB.480D769A"

------=_NextPart_8A0_2EC7_B2F000EB.480D769A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


 
The development old man chew winced as if some one had struck him in the =
bury face, then he muttered, bind "The wood! Ay, to be "Then I can go dus=
t into the cellar in excited hide the sold day, and the wood at night," r=
etorted Amabel; but in her heart noise sleepily "Will find adjustment be =
get round, sir?" he asked.
 
No trousers further misfortune befell him. William, if loutish and a bit =
of a bully sped on curve occasion, was blade not an i On hearing the feli=
ne story, the detective say expressed his trade opinion (founded on delig=
ht acquaintance with Sal) that Ge try The hunchback began to reply with a=
ngry oaths, but Sal made through signs to him to circle be nuptial silent=
, and said, "It gun The windmiller was beyond no great scholar, as was ex=
ercise interest shown by his reply: -  
It consists of a self cotton bag, closed all round, copy save for a small=
 opening force at the space side, just sufficient The Lycosa always plain=
 blood works at night, a play regrettable circumstance, which does knife =
not allow me to follow the report army M M hand F built M F M M M Should =
surprise all chess the rooms be slung available, a rare company occurrenc=
e, there still remains a method of distinguishing Can animal industry, ta=
ble like our own, obey the law of economy, the sovran law hot that thread=
 long governs our industri Then he suddenly addressed Jan. dig kettle dog=
 "Do ye measure know me, my lad?"
The doctor shook his head, and Master Swift felt pass a double pang. He p=
urpose was sorry copy about Abel, offer but the rea The early-ripening se=
edlets of the widows attract and poplars furnish the materials pain for p=
leasant the only work. There brea  For William's sufferings clock under t=
hat instrument of discipline were not march fair to pull be measured by h=
is doleful
 
"What be 'ee so voolish for as to bang say frantically nothin' when glamo=
rous her wollops crime 'ee?" he asked of Jan, in a very frie 
poorly arm With his mother's letter (it had been written at Moerdyk, ring=
 on her way clean to England) before them, Jan an F sang memorise fill M =
F spin F M M For some days Nurse's fable ugly availed. Amabel had suffere=
d a good deal smoke shame from Bogy; and, right though the fear  Jan was =
profuse of thanks, and sprout pled by the woman's desire sagittal he sat =
down brass to share their breakfast. The hunch
leave I think, as a rule, children are street very brave. talk But a ligh=
t heart goes depend a long way towards courage. At f substance float gree=
dily "Before I tore could get paper, I did, sir," said Jan. The gentle re=
ader will willingly verse book leave a veil over that meeting, which the =
artist courageous euxine felt a generous sh "I'm example just as wound so=
rry as bind yourself. He's a fine guide lad, with something angelic about=
 the face, when ye sepa  
------=_NextPart_8A0_2EC7_B2F000EB.480D769A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT face=3DArial size=3D1>
<DIV>
<DIV><IMG alt=3D"" hspace=3D0 src=3D"cid:fe90d01c7d1620ece32da024c4ffaa@s=
kenyonmiale" align=3Dbaseline border=3D0></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>The development old man chew winced as if some on=
e had struck him in the bury face, then he muttered, bind "The wood! Ay, =
to be "Then I can go dust into the cellar in excited hide the sold day, a=
nd the wood at night," retorted Amabel; but in her heart noise sleepily "=
Will find adjustment be get round, sir?" he asked.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>No trousers further misfortune befell him. Willia=
m, if loutish and a bit of a bully sped on curve occasion, was blade not =
an i On hearing the feline story, the detective say expressed his trade o=
pinion (founded on delight acquaintance with Sal) that Ge&nbsp;try The hu=
nchback began to reply with angry oaths, but Sal made through signs to hi=
m to circle be nuptial silent, and said, "It&nbsp;gun The windmiller was =
beyond no great scholar, as was exercise interest shown by his reply: -&n=
bsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial>It consists of a self cotton bag, closed all roun=
d, copy save for a small opening force at the space side, just sufficient=
 The Lycosa always plain blood works at night, a play regrettable circums=
tance, which does knife not allow me to follow the report army M M hand F=
 built M F M M M Should surprise all chess the rooms be slung available, =
a rare company occurrence, there still remains a method of distinguishing=
 Can animal industry, table like our own, obey the law of economy, the so=
vran law hot that thread long governs our industri Then he suddenly addre=
ssed Jan. dig kettle dog "Do ye measure know me, my lad?"</FONT></DIV>
<DIV><FONT face=3DArial>The doctor shook his head, and Master Swift felt =
pass a double pang. He purpose was sorry copy about Abel, offer but the r=
ea The early-ripening seedlets of the widows attract and poplars furnish =
the materials pain for pleasant the only work. There brea&nbsp;&nbsp;For =
William's sufferings clock under that instrument of discipline were not m=
arch fair to pull be measured by his doleful</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>"What be 'ee so voolish for as to bang say franti=
cally nothin' when glamorous her wollops crime 'ee?" he asked of Jan, in =
a very frie </FONT></DIV>
<DIV><FONT face=3DArial>poorly arm With his mother's letter (it had been =
written at Moerdyk, ring on her way clean to England) before them, Jan an=
 F sang memorise fill M F spin F M M For some days Nurse's fable ugly ava=
iled. Amabel had suffered a good deal smoke shame from Bogy; and, right t=
hough the fear&nbsp;&nbsp;Jan was profuse of thanks, and sprout pled by t=
he woman's desire sagittal he sat down brass to share their breakfast. Th=
e hunch</FONT></DIV>
<DIV><FONT face=3DArial>leave I think, as a rule, children are street ver=
y brave. talk But a light heart goes depend a long way towards courage. A=
t f substance float greedily "Before I tore could get paper, I did, sir,"=
 said Jan. The gentle reader will willingly verse book leave a veil over =
that meeting, which the artist courageous euxine felt a generous sh "I'm =
example just as wound sorry as bind yourself. He's a fine guide lad, with=
 something angelic about the face, when ye sepa&nbsp;&nbsp;
</DIV></FONT></BODY></HTML>

------=_NextPart_8A0_2EC7_B2F000EB.480D769A--

------=_NextPart_59B_0098_2465B9BC.04F28C22
Content-Type: image/gif;
	name="u2.gif"
Content-Transfer-Encoding: base64
Content-ID: <fe90d01c7d1620ece32da024c4ffaa@skenyonmiale>

R0lGODdhygFzAcYAAPz+/Ci4YPTaXHCenFwx2ew+DySPpHx8YGwehKSUFDw6hFEYYu4TTnQ+VLSu
ZOdCyY42zK8b5bTrn+R44JSejMi+hLovZBQGbFDJEFTQtFQ1mw5NGHTP8jyr3/HzWbTxGXxj2fCZ
WrGyjCxjl0SINNz61LeX3KlC5xRSjNkCWRl5Wft3I0jkjDbVl2nvjLy+7KyDz2kLm3HTLMfGVI9i
5+GtVxCaIJRCrBLNoYzWLDyKFCpoPzTebMy5KWiRXfxeFLHH/Ew+D7QIbESe9K/XH/iGzJgyaHS+
LLFwoax+7Om0pPwKlNQSkMRK5Kxm3AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwA
AAAAygFzAQAH/oAAgoOEhYaHiImKi4yNjo+QkZKLAQGTl5iZmpucnZ6foKGihwKjpqeoqaqrrK2u
r7CGpbG0tba3uLm6u7yvA72YBMDDjQWHBsQHxIsIy6DKzo8J0aIKuwvUkdCLDNmfBrO5Dd6KDuTn
j9jojA+sEIcRwwLI64Pv9fiaEvm1E67xhABGo1DvHj9dFQpZOIjpAsNhGAgtfEixosVLDi/eiqgx
U8aOoTKAHEmypCANijZo5HCqg0lznjyY9GZsHcqZONF9yPlqn6Oa2UDwZERvE0tD1oYqHebzYtOl
UKM6CyG16kMRVrNOmqb1UdGui3Yuwgp2E1dT/sqqrSh2rdu3/qNGyIX7iESqr3TzPpTLt6/eR8I4
GSjxl5aJwpz6Kh6BeNHHxpCVyj0BQK4BFJcL8YWVQqoKdCsiY3oaTd0nvoQHoZg7SG5qauNgsQD1
WfTM173wmtpMiLczkYZiv2phuzgx3aJ8t2bNmJhL49BRNc/nAhLQRsoF8c4O9YWthNG9TedXPRRq
Q9tZa/cbnhH49rdgFOeOusL5yovh69/Piz7z/yMQVoJ62uFHIH8IJgiKf82lN15lyymmy3UKVggW
e+sBGOGBfRFGYH4WVjVbVGSBZNlqig2WYW8SZviaeovBeCA+v4Si0lsxIDJiiK7E2BcKERYyoG/c
ZRiggUH2/jbJg76sIkNZOToyQzaW0FLlMqkNqSKLR/o2ZIMH3qScjA+mp8h9PKaJk3CJyRihh8oF
hmSS2Tlo4HhFDkJDi2rqV1tOR0EyIJd8FeVaaxtyuaKid2KIoSEL+MgkJDVAMhFUNsD3pymm7QJc
Jh0y6uCLhz46Z6gO8nWjZvmRKUo7+UTZZy2PJdLNOrgR8uWhi57Kq4sGfnXeiYytupyKxII56azM
InJDTqHSaaeovw6LJnojACkInMpKhcMtAjUrVa6D7DrClnVqKO2RiaTbLSe1kvMtLeHahpxx0SZ5
54q1TYsIiOzlOUlS4sZCcMGjkLthodry9pm/hzCcIrd8/iK8TL3aphkvLcOu1quvy66HAwokKJaa
xOlarHJeXf4K8pmslVwtr18uHPLKOHeSQz65WsvuvwT2/OF/FOub89GChAPJzudQqOt0pr4JM54z
AlBzo3NVjbQpodVy71LGApNnnjrsazSEIHe4mcBb1wMrAF8rtQM1Cn+M7ZYGnuwjsHoDrPUtN7eN
Ew+ZZLyNeMvmKFfGafeFrLstVyw4zoRjYjgit0ri9CsXjAmggIuvh3feG3JL6N+Tq3Vpgp6/6yvj
c5KOnwIE7z1JjQpSldfqiPUQidDKMnai3UTCqAAKjGfpsvBsp66ID8634nsmuNnurr5R9xqjkYIc
fmaj/tG/8sMuF5Rv/ikyaeQht1djTybU299p+rWoSxo+KwXUzbn5/G/sSVuPqNQ52Mcq+BkweAwD
VoE+NjZJoe5+m4DdLcxHGP7tQoD1INd9HJUqD3lsTp2KXfZMZjWzQXAUEqRV+QZxPqW8DRXVO1ff
SkDARTXQgAq7Fn4y44jsnXAVcppE/yrIQv915IWxKF7waggTFp3tiZVBUQ9L9cAfNoIGjggiRoZY
RIe0UEGDspmrFmhDlzEKW92aFMQcYURPsAkVz+IJFjWhv0P0jxD9+yIAVlihIcFpXU7U4RkLaKRH
eWkSQLCiK85XgjsKgn8V/EgeH6FHyIwgU1Yj4XL8/tguM64rQBwMXCMCxYlEKjIRX6TgI8uXGgvm
kY9FtCMsiXElYGDSSMCrX5H4chg0BUxdtjDlKWWZkVTCkoKQ3KMxLbiOedGtkzzspBpHcJjYkW6D
GhLlICgzTFTk8TXLVOYrI8lKPVYSEedETPNMCD4D3eRl17RdIrjZTW9WkpnmkwAyyxeDYh6TjyFg
ZRfjVb7K2YJpnFCadAQZMcUEIVpyeSc8O2hN7kFFVn8h1yvLqcpCpFOcLAyCI0HKgh3pzjGRCCEt
D1HN09VRSIrZQPGEpa5RWbSQ2nSF906B0UGQki77vAA4+djCjxZVoCBN6iBOyog2XqSlhYxEsn6G
/h/GTQtiFB3SIoQAH4Mc5KOrTKY4N3aBHRAUn7OkJDOV8lJHAI9QZXRd2qCoF4mCYgjRAGsRcYNW
f0rylWFF5UjH6sW1RsZzj4tc36jll3UqSKUm+WZY/SrUpBoVsADQQEcHS43y7EJoDavpzNjlQHFB
FieNfIwqN3tU/0HyfAjYKFIR8aRo8K4XVx3aEjMpw1dkrp6gWCYXO2qIcBJ2koeoLXRIJddU3aIb
ZVNEvUDx21YIBTGvJeoFeKAw1lZWnK3sq16LE0PGVnEV0YVHKqqriutCJrzF5IFr/+nXLg51sGnd
Y2GIMMUDSk4XzsTEdEGy00Owlx+pFWxhtfvX/gZra5bnyy98NKjJZrkXFQdWRdxSgVnjHre1AsUs
MT4VCuXCUDttjcSO9HJhsKRQElwMrIwJi4LW3hcr9H1FLQvxnE0UIREEAW4+JCwKg5pCozkO62sa
OWOl6tfJrMjwJ358CGEOwrNCzmutVujUephTu/D1qFih3AgGmNnMD2FBi7P8CiOgE4+qLSwLQbLR
Jh83E2fOM5tjocWOHEyZewW0nSkyZsNOtsuKQPMgFL3nVPSUJGETtKAZTFYikyNXxF0hORGNueoy
utE8lYp2V7nKBMM5kusIQopJDV4yM+LTnwZ1eDDI0TADGsIOiYepkfuQkY7XwHo2RJ6lLOtz/uCu
FTDh8l9TG0m+XuDRymwlITDAaSyJudqECLYghh3sWBf7EOkDy1qVHUtWF/ef07a0SWAt5TNv29PE
/rZWMr1gObN6y99FKmd5EmtG+1vR/942ALQ9MFnbhSJrjrO+0S1jhkebyPUGCbvfPfBhU/zi3I63
vCPxZ1F0Zn/4NvekY3xrspbrySjHxOYkAVVNDPsIt/p35hQdg5gHvBDe3rgjOj4JYn98gn8td4iX
LWk8FlfkKf9JI4KwiJbj/BEWP8K7bf7bbpg5ShPHedVjbrEiUFljEfbnnM2dX4I+ksljxzYjFrBq
U2R86zK3uNazbfOKtzs84e4Fz03BgZ/C/qKC4R1qw83u0UemvJhH54fV4Q3vV2996gRftMa7UmBC
KDQRe5/E+BaReZ6oltlKTrzRk/5kk4/96ejw9s3pPnd3X1zyrod6LtLCCuh5Qu2fmJtV7rlljZ59
0oYX/cZifxC5s17ysEc+3WMf+eXn3BC2DwXtIaN7tZTdo0QUc/ATHy+rH58XHHF8zmX++ooDG/bE
Zz3BIx99NeF1P5KMZWW/q336L3rg+Efz84eRd25wu/yqR3Xf931xN3OTp3P8UGh7hXjopDDNZ35a
d4CuAECJ5m4Ad4HnB4HKt3zK53ozh38I2Am/9gqYpn1J517+03wBKHAsiA9UBwLpZ3fl/qeBzoeB
yKd/7CWBmJBTRzN0SOdWi7R9g3BdRpR+Rlh3/+eCAihsBkgIQRCA3RZwODh3OeFmdEE4uFZ06qYr
sMBrpMeBU8eEFGeD67B/zndxO3CEXAeAi0eDOhiCq7RjTjaCmxBgv2NHiQaCMkiFU0iD52CGYJhx
Yohxj7eHfsgfcugNrGSHC9dIzjYKdjgK3ld3GdiHgIgIiegN3TaI5vcD5CdsaZKJWiZL8kd0cKaJ
qzeIlviGgyCKxZdx45OK99eCcMhGlVaK5XaKhzYMBsh8i4eElAgWFpcaSziAMQhcAwYJEgZmklZ2
/pQaTLcIXZMLwDiGxagVX8eFxkeL/hZ4iSeUjMrojGQndibIR0zXZWcBDBZHhs4wfargdMmHelMn
BN5Yi4dWWJtmb+KYVC+1b8Swjc4wjeoYgYdoClaoFkhADIBXckPVbOc2UI5Bf/EXDazIC3HEi8c4
CkLQdjiRBACQkJvAg4SwKeFYf2d1X+pmRBCGE+GXFRVJCOkYFfKxCO6IC7cEL0K1j3DWRoSXk2ln
j5vQfoNgZFqBRK7wNceGk0clhJZmf3skbRNpeo0QiUApCERpMWsGAEnpCY+4fU1JCFJXTNk3f3Wj
WgZGCy9WlRURjRfhhYX3lgzIgMUlbRl4QqSxFK5IC9XXESm2ZcF3Ad0gl0eXX943/oCT43eIsHkd
kZeZcJWikW8shAOCWXhOmX/5t4aagGWYUHmFoZieQGUguTJbiAlZ2VTmxEJox5OddmBQ6Ah3KWTZ
GJp/QU+hkFa4Fwp81ZWqCWwreHxNqJa8wFXUQJuQEDhZ+IMTtJCoZCv91pzWWJC1cFqf0GfdJHUJ
2GBNNpqt4IWVCYaG2IFtCJ2S0HnSKXoggUHAqYvR9nDqqQs0ZJ6gmDk9YGYzyYGryAmdJ5xdgZ7p
6ZVi53BCRwicWQuTSHFbKYXBeGRl4VWZQJWicXmbAI/ohI+kBqD3JklvRI3syIfhWY/9aQgkWRz7
VGr++ZDNWF/UiH7qV43iCVyy/pkVTEU+65lk+8hwHqahz2l+G8osMQmUIJZMsyV0QadU55ReurCO
CWoLSrAU1pmeR7Vk5Hhq6zmlrnRZ2hllN/hb+hkL7/GhomaS50YApjZyjjhmeJR9p4ejXsoQ4MgQ
HHVuJUAANupFT3l96umXQrakBdOmbbmUYzpqdGqno2d/EykIJXJC/VcIjNkKW3pKgleiD8dkgvqT
UUkIOOY8twUAiVowBzcUMaZsOdmjPYlyk8mUmEMlmmCUINGka/oISyAkUlpy8Fl6YymEp5eCL+kK
i6oIqpo6bFkY5XkIkRYJQWqrpfeXxoqs8fmBraqXULGVkfCrqWBio0eix/SU/l+oX91ZoAC5cT2G
CuH2ontWaK2UmvpDZMfobRqQq87zrarQVtCaCLuqEXToCiUYoA3InKxZXevaokcTo+4pCjfZC4hJ
CNBmi6nlWsBQqmnKhPvKoXbnobMCsKcwrIUgriTBg42qVkKaDdzpf73osDkqsbJmsYSQkJppHHPa
sb0ATg0rsmEIsRfIrqPwqs1Kryt7oYaWCZ6pCgX6neAJgSR7s7ZRpQ55oUh2DjV3mcw5sjS7Fh5J
tGKGavc4f/P1n7cpCsO6tEAbtDsqtfBXaeE1aKslkf64Cp0HeU4rtE/LZp1qIcs4pBzVYPZGoveo
CjYrCVTXjTN4CveSto2Q/rcWEq+igLEVEbcsO7U5GWexOqT/mKVg2ywdkLMmeZzI6ZbqOLS80Lae
MLDRE6y0kG+iS4oJ255xO7aulhV7GQnXQYGRiw/n1Fqma1hzip2b4JiMwF/8AKEA4Lq4QLGva5qm
OFtfRpcnOlmDh5yioLv4QAC8KwmGCwoCGbxAmIu49qgmOnKgSo7GZCE9WwgIRb26wLi5eGreVaZL
OVY6C2qra0Ws2guWu02jVqF1arWUhbT16hZCKb6J8L5aNm5ym5OS+oyERaVdlrX8y2ZJe6EgNb/I
tGvduZNXegvTk2W+e0rbFXaLu77i9WYlRKoIrAo9UMERcxGg2yxbmY1K/sFdM6qP9VW6LTyrUUqq
0cAkK7YOJ8wsUWsIKjxv3MtgymusYlmoIRwLNwwMEuCgetGjb5GyXWi/AawIo0rEb2kbScwIuGsb
0iqaVltHo/pk+kl4RTeLCQwXmdqnEOd72OoQQlCot0ouGVnGWXHGAJCh7TtAY2yr8/eTyUqn8QmC
D0gR1CnHD0lkGbrFrkABB1mbchl/+dZdaPd0v8m5wCCmhNxUoCerkjCvmNAAViYKxFvFCruademd
sJDFZVGaF+EdC5tdxprDbnqnHuywOdibVQcMSpwgwHsKrEwNgOpFRxwKqmwLblyttByPHLq3lFyH
+vG9g7ByqwDLvCBn/vNrCL1qEb5WgZ5WiZSoufzAvJAQvWppe+RmaQd7EPd6qo1Hy928zLVAuJ7A
xKPwmlvTfuR2a1rxsxvYgSt6NE68ChLaGIJ3z1BxZj6xozbYh47ApwhDx44Q0IWwyGrhuYb3y/x2
hv3Mtn3LLEzACQ4tCh8NF+XMsKgQzATaoZOcYQyqCM+rCiHdquJMzBlBBNQcFXL3tZHQ0qnw0s06
zOOryRM8Egp9NHdclfaryUrhzTxS1P1Zaw2sH9QKAJx8yZ66wflL1VjdgEsZ1EgzvVlNDiMdxEfj
1W0D0dFh0UUcGYCLM9AMDDXZEVY9wwqy1lWx0gWXE9c8Elibx9Ch/qeqgMqSIJJfrQn3zGXz0QqA
rQhTPSuCDRWCF1t8zTKe4K61KEqIvHsjF9mD3aqb6hHUTNKbzQrSLC5TgpNUa9ihLdrRU9qb4IP4
vNkb5gkbuzXgzMgQnK0z8X6msMuQkMu3URa+3RG1HdZLwdOTwNtYjQPubAsSXZIWXRLG3RiJ/Re6
LY9WMdBpnZ7T7QwmC5RY5tPA6deFGwndfT92NQkpC96pfbIwxtV0Mdvr3RVWGx3wPQm1nQrwvAkc
GQl5/RD/fArV7QzZ/QnhKxX3rQr5zRPn7ApRvQoBHgtvXcXG3AoOPaCqYOH3E2RpEuFKaZbXiguN
Hd+F8N884pSQ/qmtvFDgIh49YkzAc+benDDIamLWkUHPrcDQ8Ct8QgzFSvG2Q1Gf7WHjsRDcE6Tj
pCdJdIkEVz0IOI4LPr7ikRGXRl56Sn6sTuUQdt2q/Cm1F2AQLc7HpcfjqlDfjNDktxDdB0HC9RTT
m5DlH36syoqtSceTA24Rt6XmUN4JFxkLj9yMXtmwiHdM+y0VeP7VMk5ocynnETeoe7zk4oLhea6U
b5yvNLzGjl4cXboI3kNikW4KUvmX5UqrlIrb4sLpQ9HR41qsjRzn8w3Unb4IaN5Nqw7noq7oZ8V9
vdDcr64KDY7NaccYleqVhFEBcSnXOXHZqPA1ZH4LkI4YvT4S/gn359vH2oxO6hqRoYjQ1jixU2yO
CEwNh5t1q7cal2N56TrX7YcQomcNDM1ASeIO6jBM7sjalDBODdoua8vt6UhxCvcuCKONfWAO57Me
YodgBK1u7bKm4btAHHRWCHStiPClb6wOAAVQzGkK2mly3lCx3YaQ4EWOCOqdCg//COa6xoFX6eaJ
8YiA7buuCA8+zdKOh95Q6IPJfaFOTKxe74LQ2Zow8vAR8nrBNET85hN+nSeerUdf60Ufglk+CTRP
EmZp67+nrZMKRKxg8X2MpnvdERrPH1teElGP5Ee+wDiBpx61E/sW6HWOC29U3kiT1yF+e2Buu1+Y
9Hot4XP2/gFHX07SvrN4TwxuvxZN1B9AV5lfLMoBjwpA39qNUKoH33tCnKy2ENvXwGb4lPimGuY6
r5WMoMoqvtC3V1QXT8VG58e6QPmeYOavIN5uwfCFsL+S4Gx2b6p9rvkOYQzInu+xIPti+ZeG1up+
f0TEwPprQbiwH/opH8lRWa4Vr806SOLj25NlmXbGK9ad8HN58e8VEnJ9/7K8+Ym9NsrvXsxnK/m8
oNODTajFPoI3TXxKfQshgGll57Iob7f3a/4qc+iIgP2F8XlepJyAACA4SFjIcIgIgHgouOhYCBkp
OUlZKRliOXgheFEC0MnpSXixyRlqSloqWaqa6foKG+tq/iJbO0lgm2uLoNvrW9jKGtla+fiouNiY
+MvcnApJHOwZDFACOqpK3Lz9isv9Df6NFE7uSipqCn3u6tjOoLx8jMxYLslC/gw8mv45DXyR4lM6
bfzq+fJmMNaGhN8KMHy4KhNBQu7eVXwHj167QckgJqQmcCAwTwymmdRUashEjyy3LWwJM6ZMd/Pk
1bS48WbObxlgahO2LyjQTSo1yTyKNKnSpYY2VqR4UWNHmxhh2UyaSlQ0fSG3hmQKNqzYsb927swY
9ZjaZVbZjiUldOCmrdfI2r27FC5eSfLOopVqdqrgjpGu3gyrt2vBT4kZotgLGayCyG3Z0my69qyx
wfQK/hPmSNit0qED/UGcTDm1WKARIyMKwDfnU9AX0VJCZARz58NkG7MmJ0C1cFqrUTUWifczVLeX
aW9u7tlI58DM/SLNVs+D8O1vOV1r5QLuSrExYldXrpPR7El9P1OtzT1+0iLybVkrSMyF6fHJRVun
Cd9tlrlHYFRQ1YdggohNs4kFgjgkFCjZ8OeaaH85xxZCkITmnhDnBZjebgqOhdqIzBzxCyslOHgc
dqV9VZ+IGGJYlSIEPedfgeq9l5aJPiIV0DcopshPi6f0A+NPxy0GWXs61lgTbzQuNx2HaVVlITjo
AMCDUgekhsM2sEUSJGRGfsVKKnWhiQ2MTI61m2bK/iVzFQMTfFijkz06Z9CWPxo05p/biGcUkm7G
xZhWvzGkAzNzopcIpE/uOCBnyYwgZZSCbsqpOYUSlKZeLn5nWoKGrTcjjc3V6QimGU3ZaVgaxNqS
miMhpxhj3qUpX5bQpfqXnLIt8gOVimSK6lK5xUQCM/TRypKfXbFG7ZESBvUQDYKEyY11tqnK45UA
rMAnq8lCi26tjxWiHT6dVMtmvIotOUx/Mn6bqoVXyghiiOilC/BDrbQrsK3xTjiXtbv+FCOBC9yr
W7/gRgxswBbTuqWaWmnCYKEcL0ahvXEe8nAxVkKc3m0VXxwJtyzXI4EEHom6MSGu6vrmwj4aRrFO
/uwxIMC/nmX58jddbvsQB0W/YrCLjIFas8GpCYGZyZXqu0jQUP4s9Fi8yOfy0rIsq2WbKoL88SD7
4UwJvQxFYIueIhoooLcMOSh23kytw5XHo3YcCRKJrVnh1YbjhHLKlvyqd+M+ZvXPfk1Li53Uwo18
Mpa+Mr5hv1s7DrqC73YVdb2n1BWyyICx9cOjXUcsLNGhzy4c3yi9OSq2ofZNztFl0TnICuEmDruU
dH/+ctixwp3uOYsWibZ4fq6Ueia+GzT86/hmNizwtP/J/MUEdfCpPtd6Jy8/jRZO6Z7cax7PZsHy
/P33N0eWQT7R3Hewx6is/5BxbGNf28scvuZH/r/65Q1voqOc36CHjYxNojzNSAA5ZvM+jHRvbjgi
ngJjEhxLfKkeDPwTqdCXvoOJym1NWh382ufCzhlOWR8URA9eMcIaDoIJ+IHcCXVnLQk2DHMYdF2V
tOcRsulwibFgAkEylrBRaKVUbHJa9VQ3Qyq9EHnCkcGPXiCInjDxITtgGwrhhaQofoqFLeSXEbc4
Ii/+SIz1swFY3iWqB/YjYcJQ49NMJalIJTAhDqjEEMaot3WxJFDQ0ONcrME/holkInkkC9bo1hIK
ZMIAlDkkIvHBEh8wzXZ9RIkVvSOtFKYGk59sJeiysSXJ6W8Vz7hiWASJxATJ8SEwcOXSTmmo/udx
bBoUYCNYnkSrXTKkl5awpS/lA7lDUS9tCIOTuFwps0/SkYlqckHO5HW2eTnzgo6AAQN6wMUlZnOJ
1/skOggHRFyliYqHqgUjK2NOdKbzmfzUIbf2F8SFodE4tShWM/ZZw2b185nkiwa8CIc6aKxtnAut
qEVrETJJwlKK1pJQPi4K0pBCJJpOg+APg2FMkcZCmXsJgkq5U9L+nRGCT9NoOEoIunuo5iUvFZ1X
9lhJjiZJmL9QgUXDZ4kH+IJ8PW1GDt5ije/4z5RTNVs9m/qKCCzAFUrFqlJYurdGilUQpfrox5yH
rX9Q1JUKSGUO9wKBXuDUq+6SakHo+VAz/p4upQrc6gfnSleGaIym8lRYWrdxApb5NbCdAgF3oAgq
ky4qsmNlrGV7AdZmvkxCUwyFWf+4D/2tlRAzUJCGoDVadGVWgWok6l7nKZdv6kKU9fjAJJQGixIV
AqmX7WcqZ1a+wx7pRXOJ6VWRYtveKrc+tsMdSvajKFQId7lMJJdwZrUNl9rFchOSyyMNlbbjbud+
1N2GHQVh3cCGUBaA6y7pcGbTXeFFBCKgBHnLa95vpNeylZRkaKmpSvzixbEC3ss6CCXNwRnFuAWW
hVEp0c5CKJJlhWyqXTkaqgODt8G1eHArK0zdoUyPfxwuMX9NKl5KvNXELEYkKZowXVis/rjFdL2n
SOHJMuXR+C42BmlqTaTjWOB2x2DBAOiCbDqD8BBdNwhLaYkMiyFD4mu1GwSSoRy6+xZNyoWgMpZj
oS1X1EDAWv4yUgjc023Wg7dmbjOt1OxmlkygEhaMczM06WYndIo4djZRA/oM6EALOl1l/CCft7HO
QSPyhq5gdCG0q8BDK7q8jrZEpSeN6Uxr2kdG3rSnHdfpSaOZEov9tA7Pa+olLjnVrNZFnVWz6lbL
uhaYSA2bZ23qUAvq1n1OdOO6CrAh4ToXE6bdpRMCbKYYgJNJqcCwI1FsQiixGclWzbEv5uuWONsj
f37mqyFRal8IEBzVdnO2OXWAGROi/se0+3ZSrvzsgKGaqV/WqWrgHO9t0Ds+Br3ofpmBbx9blqd2
4fVRxt0MhOebEHqWybmLA4uHp0vhC69Hw2MicbzEdRIZn0S5FWTviotcEAR3xQBG/r1+Q+LJKBdE
rV0B2JYzQ+Uyj4QLXp6JmNfi5DUnh857DnSl/DzogfYm0SER7aOnJsKZTrotrq10SwCwHOyOOmWA
0Nupk6MFVpcP1oP+466LHaNIwW4sksBiSSeE6WPXhdlhkYTfivTflVB72xvX7WfS/e755vKsDY4u
wO9433z/BaRjIvjCp2vOpi65L8JeDsebmvHyua9uFaTuTEheF5BXfKw6H5a8ez4s614efWTK7GYK
mn5TbF89ZQi/cOLAW+xESMismO3L+iJo9mOv/RLDDRFhYxrVric1TIBf/ORPAvnKB12hm1+JxKNL
7ixJrHCeXw7r5xvY0hcU1Jcy9EFsnBBPBQfPof8Qpwvn++DwezPGX4jV5gL16K9/nzNv/3Co/9P4
L9rmLSZ6CrR3xUdzlPB/AcN8szOACeJudFWArXSA9adQruQno5YuEYh+xEcrLPcL6LCA+fcjH5Bc
meB7vYB9e8GBIAhlJ7hcuKeCS1N6lqUE2xCAL4NnL/gyM/gLNfhppwVS1IeDigeEQVh4Q/hlgQAA
Ow==
------=_NextPart_59B_0098_2465B9BC.04F28C22--




From ipfix-bounces@ietf.org Sat Jul 28 15:40:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEs9B-0006DU-Dj; Sat, 28 Jul 2007 15:40:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEs99-00062L-L5
	for ipfix@ietf.org; Sat, 28 Jul 2007 15:40:15 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEs91-0005kQ-My
	for ipfix@ietf.org; Sat, 28 Jul 2007 15:40:15 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6SJdtab000165;
	Sun, 29 Jul 2007 04:39:55 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Sun, 29 Jul 2007 04:39:57 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
In-Reply-To: <46A7D10F.3050509@cisco.com>
References: <46A7D10F.3050509@cisco.com>
Message-Id: <20070729030242.485A.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Sun, 29 Jul 2007 04:39:56 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 485c16ccf4ca6ef309699ad6279bf354
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,
 
Thank you for your valuable comments.
Please see in-line.

Atsushi KOBAYASHI

On Wed, 25 Jul 2007 23:39:11 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Please see my comments inline.
> 
> 
> > IPFIX Working Group                                         A. Kobayashi
> > Internet-Draft                                              K. Ishibashi
> > Intended status: Informational                                 T. Kondoh
> > Expires: December 25, 2007                                   NTT PF Lab.
> >                                                             D. Matsubara
> >                                                                  Hitachi
> >                                                            June 23, 2007
> > 
> > 
> >                   Reference Model for IPFIX Mediators
> >               draft-kobayashi-ipfix-mediator-model-00.txt
> > 
> > Status of this Memo
> > 
> >    By submitting this Internet-Draft, each author represents that any
> >    applicable patent or other IPR claims of which he or she is aware
> >    have been or will be disclosed, and any of which he or she becomes
> >    aware will be disclosed, in accordance with Section 6 of BCP 79.
> > 
> >    Internet-Drafts are working documents of the Internet Engineering
> >    Task Force (IETF), its areas, and its working groups.  Note that
> >    other groups may also distribute working documents as Internet-
> >    Drafts.
> > 
> >    Internet-Drafts are draft documents valid for a maximum of six months
> >    and may be updated, replaced, or obsoleted by other documents at any
> >    time.  It is inappropriate to use Internet-Drafts as reference
> >    material or to cite them other than as "work in progress."
> > 
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/ietf/1id-abstracts.txt.
> > 
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html.
> > 
> >    This Internet-Draft will expire on December 25, 2007.
> > 
> > Copyright Notice
> > 
> >    Copyright (C) The IETF Trust (2007).
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 1]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Abstract
> > 
> >    An IPFIX Mediator is an intermediate node between IPFIX devices and
> 
> "devices" -> "Exporting Processes"
> 
> >    traffic collectors.  This node acts as an IPFIX proxy, IPFIX
> 
> "traffic collectors" -> "IPFIX Collecting Processes".
> 
> "This node" -> "A mediator"
> 

Yes. I will correct them in next version. 

> >    firewall, and IPFIX concentrator.  An IPFIX Mediator mediates the
> >    IPFIX protocol using several functions.  That enables the traffic
> >    monitoring system to become a high-capacity system and accommodate a
> >    variety of traffic monitoring methods.  This document describes each
> >    function that is provided by IPFIX Mediators and the method of
> >    handling the Flow Records of each function.  In addition, this
> >    describes the model of the solution scenario using IPFIX Mediator.
> 
> It's unclear what this last line means.
> 

"this" indicates this draft.
This document describes the model of the solution scenario using IPFIX Mediator
which refer to chapter 5. 

> > 
> > 
> > Table of Contents
> > 
> >    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
> >    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
> >    3.  Internal Components Model  . . . . . . . . . . . . . . . . . .  8
> >      3.1.  Collecting Process . . . . . . . . . . . . . . . . . . . .  8
> >      3.2.  Metering Process . . . . . . . . . . . . . . . . . . . . .  9
> >        3.2.1.  Selection Process  . . . . . . . . . . . . . . . . . .  9
> >        3.2.2.  Aggregation Process  . . . . . . . . . . . . . . . . .  9
> >        3.2.3.  Modification Process . . . . . . . . . . . . . . . . . 10
> >      3.3.  Exporting Process  . . . . . . . . . . . . . . . . . . . . 12
> >      3.4.  Storing Process  . . . . . . . . . . . . . . . . . . . . . 12
> >    4.  IPFIX Protocol Considerations  . . . . . . . . . . . . . . . . 14
> >      4.1.  Export Time Issue  . . . . . . . . . . . . . . . . . . . . 14
> >      4.2.  Observation Domain ID Management . . . . . . . . . . . . . 14
> >      4.3.  Template Management  . . . . . . . . . . . . . . . . . . . 14
> >      4.4.  Transport Session Management . . . . . . . . . . . . . . . 15
> >      4.5.  Option Template Management . . . . . . . . . . . . . . . . 15
> >      4.6.  Reporting of Exporter Information  . . . . . . . . . . . . 15
> >    5.  Solution Scenarios with IPFIX Mediators  . . . . . . . . . . . 16
> >      5.1.  Flexible Aggregation . . . . . . . . . . . . . . . . . . . 16
> >      5.2.  Distributed Aggregation  . . . . . . . . . . . . . . . . . 16
> >      5.3.  Duplication of Flow Records  . . . . . . . . . . . . . . . 17
> >      5.4.  Distribution of Flow Records . . . . . . . . . . . . . . . 18
> >      5.5.  Extraction of Suspicious Flow  . . . . . . . . . . . . . . 19
> >    6.  Mediator Option Template Presentation  . . . . . . . . . . . . 20
> >      6.1.  Exporter Information Option Template . . . . . . . . . . . 20
> >      6.2.  Usage of Scope Field . . . . . . . . . . . . . . . . . . . 22
> >    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
> >    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
> >    9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
> >      9.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
> >      9.2.  Informative References . . . . . . . . . . . . . . . . . . 26
> >    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
> >    Intellectual Property and Copyright Statements . . . . . . . . . . 28
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 2]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 1.  Introduction
> > 
> >    Several problems regarding traffic monitoring have occurred in
> >    several networks, as follows.
> 
> Can you cite some references for this?
> 

I can't cite some references now. Until submitting the next version, I will
search for some references.

> > 
> >    o  Scalability of collector on large-scale networks
> > 
> >       As the sizes of networks become larger, the number of Flow Records
> >       becomes greater.  Large numbers of Flow Records have been
> >       burdening management networks and the collecting process.
> >       Maintaining scalability is difficult as a particular network
> >       grows.  Generally, network operations need to monitor overall
> >       wide-scale traffic behavior and investigate detailed traffic
> >       information when traffic incidents happen.  Meeting these
> >       requirements seems to be difficult for a single collector node
> >       because of large numbers of Flow Records.
> > 
> >    o  Handling multifaceted network environment
> > 
> >       On the other hand, networks such as IPv4, IPv6, and VPN on MPLS
> >       have recently become more multifaceted.  These sorts of Flow
> 
> What do you mean by "multifaceted"?
> 

Simply, I mean that the variety of packets, such as IPv4 and IPv6, are passed
thought in the same network. Especially, MPLS network handles the
several customer's traffic as VPN traffic, such as pseudo wire or L3VPN.

I means that networks are integrating variety of traffic.

I will add the explanation in this paragraph.


> >       Records need to be analyzed separately from a different
> >       perspective.  However, handling them separately without improving
> >       the capability of the Collector is difficult.
> > 
> >    o  Exchanging traffic information between different networks
> > 
> >       Traffic information is considered to be necessary for ISP network
> >       providers as well as each customer.  To that end, the network
> >       provider needs to export specified Flow Records while avoiding
> >       privacy violations.  In addition, exchanging traffic information
> >       between the associated networks could be necessary when traffic
> >       incidents happen.  In that case, the Flow Records should be
> >       checked according to the service provider's policy before
> >       exporting.  Therefore, Flow Records exported from Exporter
> >       directly without modification can not be fed each customer or
> 
> "can not be fed *to* each customer"

yes. I will correct it in the next version.

> 
> >       associated network operators without modification.
> > 
> >    IPFIX Mediators enable us to overcome these problems by preprocessing
> >    Flow Records.  By defining IPFIX Mediators, we can take increasing
> >    advantage of an extensive template format, and handle Flow Records in
> >    accordance with our preference.  This document describes some
> >    solutions using IPFIX Mediators that solve these problems and
> >    components that are needed in the internal process.
> > 
> >    The IPFIX Mediator, which is located between one or more Exporting
> >    Processes and one or more Collecting Processes, has a main function
> >    for handling Flow Records.  That function stores original Flow
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 3]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    Records and mediates them.  In addition, renewed Flow Records are
> 
> It's worth defining what mediation is.

I will add the description about Flow Mediation and IPFIX protocol
Mediation presented by my slide.

> Also, what are "renewed Flow Records"?

This part is described about Flow Mediation.

I means that the "renewed Flow Records" is modified Flow Records or
aggregated Flow Records.

Modification of Flow Records means that some fields are added and deleted,
and whose value are modified.

I will adds the description in the next version.

> >    generated and distributed to an appropriate Collector or traffic
> >    analyzer in accordance with flow content.
> 
> Must the mediator understand the content? eg, what about Enterprise 
> Specific elements?
> 

Mediator doesn't need to understand all content, as semantic. After decoding
by the collecting process, Flow Records are distributed in accordance
with specified elements contents, such as input IF indexes or Peering AS.
In this case, Mediator doesn't need to understand other field contents.
In the distribution of Flow Records, Some fields which should be understood
are restricted.

> >    The internal model of a Mediator is composed of Collecting Processes,
> >    Metering Processes, and Exporting Processes.  IPFIX Mediator acts as
> >    a Collector by receiving Flow Records, and it acts as an Exporter by
> >    sending Flow Records.  This dual-role architecture enables cascading
> >    Mediators and building a combination of several solutions.
> > 
> >    This document describes a model of a solution scenario by using IPFIX
> >    Mediator and its key component.
> > 
> >    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >    document are to be interpreted as described in [RFC2119].
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 4]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 2.  Terminology
> > 
> >    The definitions of basic IPFIX and PSAMP terms are identical with
> >    those in [I-D.ietf-psamp-framework], [RFC3917],
> >    [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info], and
> >    [I-D.ietf-ipfix-architecture].  Other than the above terminology, the
> >    following terminology related to IPFIX Mediator is used in this
> >    document.  Therefore, the terms defined in the IPFIX terminology are
> >    capitalized in this document.
> > 
> >    IPFIX Mediator
> > 
> >       An IPFIX Mediator hosts at least one pair of Exporting Process and
> >       Collecting Process.  An IPFIX Mediator may have the Metering
> 
> "at least one Exporting Process and one Collecting Process".
> 
> >       Process and Storing Process as optional.  An IPFIX Proxy, an IPFIX
> 
> "may optionally have Metering Processes and Storing Processes".
> 

Yes. I will correct them in the next version.

> >       Firewall and an IPFIX concentrator are one node of IPFIX
> >       Mediators.
> 
> This last line is unclear.
> 

In next version, I will add the description about what is IPFIX Mediator.
I means that IPFIX Mediator is generic name of the several nodes, such as
the IPFIX proxy, IPFIX firewall and IPFIX concentrator.


> > 
> >    Original Exporter
> > 
> >       An Original Exporter hosts Observation Points where IP packets can
> >       be observed.
> > 
> >    IPFIX Proxy
> > 
> >       An IPFIX Proxy acts as a proxy for Original Exporter, which hosts
> 
> "Exporters"
> 
Yes.

> >       Observation Points.  An IPFIX Proxy may receive Flow Records from
> >       one or multiple Exporting Processes, and send them to one or
> >       multiple Collecting Processes.  An IPFIX Proxy does not send the
> >       information about an Original Exporter to the Collector to act as
> >       an Original Exporter.
> 
> This last line is unclear.
> 

IPFIX proxy does not send the the information about an Original
Exporter, such as "exporterIPv{4|6}Address" to the Collector.

> > 
> >    IPFIX Firewall
> > 
> >       An IPFIX Firewall exports the Flow Records to a different network
> >       domain at the edge of the self-network domain.  From the
> >       Collector's point of view, an IPFIX Firewall acts as an Original
> >       Exporter, just like an IPFIX Proxy.  In addition, an IPFIX
> >       Firewall reviews whether received Flow Records are passed forward
> >       to the Collector to hide the network topology or privacy
> >       information.
> 
> Does it block records, or modify them? eg, does it anonymise them?
> 
I think that above functions are included in the IPFIX Firewall.
At least, IPFIX Firewall has one function of above functions, such as
filtering, modifying and anonymizing.

I will add the description about it in the next version.
> > 
> >    Metering Process
> > 
> >       The Metering Process in IPFIX Mediators can be considered the
> >       partial Metering Process separated from the Metering Process in
> >       the Original Exporter.  The Metering Process in IPFIX Mediators
> >       consists of a set of subprocesses that includes the Selection
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 5]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       Process, the Aggregation Process and the Modification Process.
> >       The Metering Process generates the final Flow Records that should
> >       be exported.
> > 
> >    Selection Process
> > 
> >       The Selection Process in an IPFIX Mediator is similar to that of
> >       PSAMP Devices, which is described in [I-D.ietf-psamp-framework].
> >       However, the Selection Process in an IPFIX Mediator differs from
> >       the following functions.  The Selection Process in PSAMP Devices
> >       has two types of selection functions: Filtering and Sampling.  In
> >       addition, the filtering function has two types of filtering
> >       methods: field-match filtering and hash-based selection.  The
> >       Selection Process in an IPFIX Mediator has only the field-match
> >       filtering functions.  This filtering function selects Flow Records
> >       based on Flow Record content.  The Selection Process is one of the
> >       subprocesses in the Metering Process.
> > 
> >    Aggregation Process
> > 
> >       The Aggregation Process creates aggregated Flow Records from
> >       inputted Flow Records, in accordance with aggregation rules that
> >       are described in [I-D.dressler-ipfix-aggregation].  The
> >       Aggregation Process is one of the subprocesses in the Metering
> >       Process.
> > 
> >    Modification Process
> > 
> >       The Modification Process carries out the addition, deletion, and
> >       modification of the Information Elements included in inputted Flow
> >       Records.  The Modification Process adds Information Elements like
> >       derived packet properties that canot be extracted in the Original
> >       Exporter.  Information Elements related to derived packet
> >       properties are described in [I-D.ietf-ipfix-info].  In addition,
> >       the Modification Process modifies the values of the specific
> >       Information Element.  For example, the modification of values is
> 
> "the values of specific Information Elements"

Yes. I will correct this term in the draft.
> 
> >       like anonymizing some Information Elements to avoid violating
> >       privacy.  The Modification Process deletes some Information
> >       Elements included in inputted Flow Records.  The Modification
> >       Process is one of the subprocesses in the Metering Process.
> 
> - and presumably this is a key part of a firewall?

Yes.
But, the modification process is not limited as the functions of IPFIX
firewall.
If the Modification Process adds the BGP Next Hop Address into the Flow
Records, this node is not implied to the IPFIX Firewall.

> > 
> >    Storing Process
> > 
> >       The Storing Process selects specified Information Elements
> >       according to the storing rules, and then stores inputted Flow
> >       Records in a storage system such as a database or flat-file
> >       system.  Information Elements are specified in storing rules.  In
> >       addition, the Observation Domain ID and Export Time in the header
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 6]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       of IPFIX messages are specified in the storing rules.
> 
> How does information get *out* of the Storing Process?

This part is out of scope of this document.
As solution, several solution can be considered.

In case of our system, other node, such as analyzer, submitted the query
that contains the specified time slot as XML, IPFIX Mediator replies this
query by replaying the NetFlow packets. 
> 
> > 
> >    Distribute Function
> > 
> >       The Distribute Function distributes final Flow Records based on
> >       the Flow content.  The final Flow Records are handled by the
> >       Exporting Process to export them to Collector.  Each classified
> >       Flow Record is exported to each Collector.
> 
> To all collectors, or to a subset?
> 

To a subset.
I mean that the classified Flow Records are exported to the specified Collector.

> > 
> >    Observation Domain ID
> > 
> >       An IPFIX Mediator doesn't host the Observation Point and
> >       Observation Domain.  Though, the Observation Domain ID in IPFIX
> >       header sent by IPFIX Mediator also indicates the largest set of
> >       Observation Points in the Original Exporter, but this value does
> >       not indicate the physical entity of the Original Exporter.  If
> >       inputted Flow Records are aggregated in the Metering Process, the
> >       Observation Domain ID value in IPFIX header SHOULD be 0.
> 
> I think only if the mediator is spoofing the original source exorter. 
> Arguably a whole new set of Observation Domain values applies on the 
> mediation device.

This part need a discussion with IPFIX members.
If IPFIX Proxy handles one exporting session and one collecting session,
simply IPFIX Proxy doesn't need to change the observation domain values.

I think, If IPFIX Proxy handles multiple session on the both sides,
IPFIX Proxy needs to assign the new Observation Domain values.

> >    Transport Session Information
> > 
> >       In SCTP, the Transport Session Information is the SCTP
> >       association.  In TCP and UDP, the Transport Session Information
> >       corresponds to a 5 tuple {exporter IP address, collector IP
> >       address, exporter transport port, collector transport port,
> >       transport protocol}.  In IPFIX Mediator, the Collecting Process
> >       manages this information.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 7]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 3.  Internal Components Model
> > 
> >    The following figure indicates four components (Collecting Process,
> >    Metering Process, Exporting Process, and Storing Process) within the
> >    IPFIX Mediator that are referred to in [RFC3917].  The Metering
> >    Process can have one or multiple subprocesses.  These subprocesses
> >    are the Selection Process, Aggregation Process, and Modification
> >    Process that can be connected to each other in any sequence defined
> >    by the user.  The Metering Process and Storing Process are options.
> > 
> > 
> >      +--------------------------------------------------------------+
> >      |                        IPFIX Mediator                        |
> >      | .----------.                                     .---------. |
> >      | |          |  .-------------------------------.  |         | |
> >      | |Collecting|  |        Metering Process       |  |Exporting| |
> >      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
> >      | |          |-->|sub    |->|sub    |->|sub    |-->|         | |
> >    IPFIX          |  ||process|  |process|  |process||  |         |IPFIX
> >    --> |          |  ||#1     |  |#2     |  |#3     ||  |         |-->
> >      | |          |  |'-------'  '-------'  '-------'|  |         | |
> >      | |          |  '-------------------------------'  |         | |
> >      | |          |------------------------------------>|         | |
> >      | |          |  .-------.                          |         | |
> >      | |          |->|Storing|                          |         | |
> >      | |          |  |Process|                          |         | |
> >      | |          |  '-------'                          |         | |
> >      | '----------'                                     '---------' |
> >      +--------------------------------------------------------------+
> 
> I think any of the metering sub-processes should be able to send data to 
> the storing process. Also, the Exporting process may send data there too 
> (consider Brian's file draft). Finally, there should be a route *out* of 
> the storing process - either to the outside, and/or to the Metering 
> Process, and/or to the Exporting Process.
> 

Good idea. Roughly, I can image following figure.

      +--------------------------------------------------------------+
      |                        IPFIX Mediator                        |
      | .----------.                                     .---------. |
      | |          |  .-------------------------------.  |         | |
      | |Collecting|  |        Metering Process       |  |Exporting| |
      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
      | |          |--->sub    |-->sub    |->|sub    |-->|         | |
    IPFIX          |  ||process|  |process|  |process||  |         IPFIX
    --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
      | |          || |'-------'  '-------'  '-------'|  |         | |
      | |          || '----|----------|----------|----'  |         | |
      | |          ||      |          |          |       |         | |
      | |          ||   .--\/---------\/---------\/--.   |         | |
      | |          |'---|       Storing Process      |<--|         | |
      | |          |--->|                            |-->|         | |
      | |          |    '----------------------------'   |         | |
      | |          |------------------------------------>|         | |
      | '----------'                                     '---------' |
      +--------------------------------------------------------------+



> 
> >    Figure A: Key components within IPFIX Mediator.
> > 
> >    Each process is associated with a common identifier in the IPFIX
> >    Mediator.  This method is similar to PSAMP associations in
> >    [I-D.ietf-psamp-sample-tech].
> > 
> > 3.1.  Collecting Process
> > 
> >    This process receives Flow Records from the previous Exporter.  The
> >    instance of this process is created according to the IPFIX session.
> >    This process has functions that are described in
> >    [I-D.ietf-ipfix-protocol].  The Collecting Process also forwards
> >    received Flow Records with IPFIX header information and Transport
> >    Session Information to multiple Metering Processes or Storing
> >    Processes.  In other words, Flow Records can be duplicated by
> >    forwarding several Metering Processes.  In addition, the Collecting
> 
> Or Exporting Processes.
> 
Yes. 
Flow Records can be duplicated by forwarding several Metering Processes
or Exporting Processes.


> >    Process can directly forward Flow Records to Exporting Process.
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 8]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 3.2.  Metering Process
> > 
> >    This process generates the renewed Flow Records from inputted Flow
> >    Records with received IPFIX header information, such as "Export Time"
> >    and "Observation Domain ID".  This process hosts the several
> >    subprocesses.  The processing order of these functions, which could
> >    be located by user definitions, would lead to different renewed Flow
> >    Records.
> > 
> > 3.2.1.  Selection Process
> > 
> >    This process decides whether each Flow Record passes through to the
> >    next process.  Theprocess has a filtering function and selects Flow
> 
> Typo, "Theprocess".

Thanks.

> 
> >    Records that are matched under given conditions.  Prior to receiving
> >    Flow Records, this process has instruction pattern data that are
> >    defined by the user, which specifies how the Flow Records are treated
> >    by this process.  If the value of some Information Elements in the
> >    Flow Record match the instruction pattern, this process selects Flow
> >    Records with all fields and forwards these Flow Records to the next
> >    process.  For example, this process selects the Flow Records that are
> >    included in the specified destination IP address.
> > 
> > 3.2.2.  Aggregation Process
> 
> As a general question, is it valid to aggregate fields which were not 
> originally key fields?
> 

I think that the aggregate key field does not depend on the original key
fields.

> > 
> >    This process gathers Flow Records within a given time interval and
> >    then distinguishes Flow Records that have common properties.  If
> >    values of a given key field are the same, that means these Flow
> >    Records have common properties.  This process merges Flow Records
> >    that have a common property and creates an aggregated Flow Record.
> >    Therefore, for example, aggregated Flow Records have an aggregation
> >    counter that indicates the number of packets.  These functions are
> >    defined in accordance with the IPFIX aggregation rule in
> >    [I-D.dressler-ipfix-aggregation].
> > 
> >    The process has instructions that are user defined prior to receiving
> >    Flow Records.  The process indicates the Information Elements that
> >    should become aggregated flow keys and other Information Elements
> >    that should be kept or discarded.  In addition, these instruction
> >    rules include Information Elements that should be added to aggregated
> >    Flow Records.  The aggregated Flow Records may need to complement
> >    information that is discarded during the aggregation process.  They
> >    help the Collector to analyze aggregated Flow Records.  For example,
> >    these Information Elements correspond to "averageActiveTime",
> >    "synCount", and "flowCount" elements, as follows.
> > 
> >    o  averageActiveTime
> > 
> >       This Information Element indicates average time in milliseconds of
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 9]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       difference between flow start time and end time of each flow
> >       included in the aggregated flow.  This Information Element is
> >       created from the flow time stamp Information Elements.  There are
> >       "flowStartSeconds", "flowEndSeconds", "flowStartMilliSeconds",
> >       "flowEndMilliSeconds", "flowStartSysUpTime", and
> >       "flowEndSysUpTime".  Moreover, "minimumActiveTime" and
> >       "maxmumActiveTime" might be considered in addition to the element.
> > 
> >    o  synCount
> > 
> >       This Information Elements the number of Flow Records that have
> >       "tcpControlBits" which the SYN bit sets to 1 in an aggregated
> >       flow.  Using this element, we can determine the number of SYN
> >       packets throughout the network.  Moreover, "ackCount", "finCount",
> >       "pshCount", "urgCount", and "rstCount" might be considered in
> >       addition to this element.
> > 
> >    o  flowCount
> > 
> >       This Information Element is the number of Flow Records included in
> >       the aggregated flow.
> > 
> > 3.2.3.  Modification Process
> > 
> >    This process modifies the received Flow Records.  This process can
> >    add the new Information Elements, delete included Information
> >    Elements, or modify the value of included Information Elements, as
> >    follows.  If this process modify the original template, it SHOULD
> >    revise the received "flowKeyIndicator".
> > 
> >    Addition of new Information Element
> > 
> >       This function adds specified Information Elements into the
> >       inputted Flow Records.  The values of Information Elements are
> >       extracted by searching some database based on the inputted content
> >       of Flow Records.  The added Information Elements and used
> >       Information Elements are configured according to instructions by
> >       the user to obtain the value.  The method to obtain the value from
> >       some Information Elements is outside the scope of this document.
> > 
> >       The IPFIX Mediator instead of the Original Exporter adds a derived
> >       packet property parameter, which is useful for the traffic
> >       monitoring technique.  Doing that can compensate for the inability
> >       of some Exporters to add a derived packet property parameter.
> >       Hereby, the Collector does not need to recognize the difference
> >       between implementations of routers from several vendors.  For
> >       example, the addition of "bgpNextHop{IPv4|IPv6}Address" and
> >       "bgpCommunity" Information Elements is useful for making a traffic
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 10]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       matrix that covers the whole network domain. "bgpNextHop{IPv4|
> >       IPv6}Address" can indicate the egress router of some network
> >       domain.  In addition, "bgpCommunity" can indicate the same group
> >       of destination or source IP addresses.  This value can be given by
> >       looking for the BGP route database based on the destination or
> >       source IP address.  In addition, "mplsVpnRouteDistinguisher",
> >       which can not be extracted from the core router in MPLS networks,
> >       indicates the customer's identification.  We can monitor the
> >       traffic behavior per customer by adding
> >       "mplsVpnRouteDistinguisher" to the Flow Records.  This value can
> >       be given by looking for the BGP route database based on the
> >       "mplsTopLabelStackSection" and "mplsTopLabel{IPv4|IPv6}Address".
> > 
> >    Deletion of Information Element
> > 
> >       This function deletes specified Information Elements according to
> >       the instructions that are configured by the user, which indicate
> >       whether an Information Element should be removed.  Hiding network
> >       topology information and private information by using this
> >       function is possible.
> > 
> >       In the case of exchanging Flow Records with different network
> >       domains or customers, this function can avoid making a
> >       vulnerability by deleting unnecessary Information Elements.  By
> >       deleting unnecessary Information Elements, this function can hide
> >       the network topology and another customer's information.  In
> >       particular, "ipNextHopIP{v4|v6}Address", "bgpNextHopIP{v4|
> >       v6}Address", and "bgp{Next|Prev}AdjacentAsNumber" correspond to
> >       network topology information.  In addition, MPLS-related
> >       Information Elements, such as "mplsLabelStackSection", that are
> >       useless for customers might be removed in the case of feeding the
> >       Flow Records to VPN customers.
> > 
> >    Modification of the value of Information Element
> > 
> >       This function modifies the value of specified Information Elements
> >       according to instructions configured by the user.
> > 
> >       For example, this function enables us to overwrite private
> >       information with zeros or the maximum value.  In particular, IP
> >       address and port number is sensitive private information.  In the
> >       case of monitoring traffic trends and traffic engineering, these
> >       Information Elements are not essential factors for those purposes.
> >       In that case, modification anonymizes the relevant Information
> >       Elements to prevent a violation of privacy.  If modification can
> >       anonymize some Information Elements, it might need to report which
> >       Information Elements are anonymized.  For example,
> >       "anonymizationIndicator" indicates which Information Elements have
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 11]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       been anonymized as a bitmap, just like the "flowKeyIndicator".
> >       The anonymization method is outside the scope of this document.
> 
> Why would we not just modify the template and remove these Information 
> Elements?

This point has been already discussed in ML.


> > 
> > 3.3.  Exporting Process
> > 
> >    This process forwards Flow Records to the next Collector.  These
> >    processes manage the reporting template and make an IPFIX datagram.
> > 
> >    In addition, this process has the Distribution Function as an option.
> >    If this function is enabled, this process distributes Flow Records
> >    based on Flow content and then exports each classified Flow Record to
> >    each Collector.
> > 
> >    The Exporting Process distributes Flow Records on the basis of the
> >    peering AS, as shown in the following figure.  Each classified Flow
> 
> Peer AS in the incoming data, or on the Exporting side? Is BGP required?
> 
> Surely this would/should be user configurable?

I means this is example. Which field is selected in order to distribute Flow
Records should be configurable.
I will modify next version. It is too short description
 
> >    Record is exported to a dedicated Collector on the basis of the
> >    Peering AS.
> > 
> >      +-------------------------------------------+
> >      | IPFIX Mediator               .----------. |
> >      |                              |Exporting | |
> >      |                              |Process   | |
> >      |   .----------.  .---------.  |          | | PeerAS#100
> >  Flow -->|Collecting|->|Metering |----->/------------> Collector#A
> >  Records |Process   |  |Process  |  |   |      | | PeerAS#200
> >      |   '----------'  '---------'  |   /------------> Collector#B
> >      |                              |   |      | | PeerAS#300
> >      |                              |   /------------> Collector#C
> >      |                              |   |      | | PeerAS#400
> >      |                              |   /------------> Collector#D
> >      |                              |          | |
> >      |                              '----------' |
> >      +-------------------------------------------+
> > 
> >  Figure B: Exporting each classified Flow Record to dedicated Collector.
> > 
> > 3.4.  Storing Process
> > 
> >    This process selects specified Information Elements using the storing
> >    instruction from the inputted Flow Records.  Prior to receiving Flow
> 
> What is the "storing instruction" ?
> 

The Flow Records which are wanted to store by user might not be equal to
received Flow Records. The meaningless fields could be discarded by user.
The storing instruction means the configured information by user.
It indicates fields which should be stored and field which should not be
stored.

I will adds the explanation in next version. And also, I used "storing
instruction" and "storing rule" as same meaning. I will correct it.


> >    Records, this process has instructions that are configured by the
> >    user, which indicate whether each field should be stored or
> >    discarded.  The field modifier indicates "keep" or "discard", which
> >    is similar to the instruction of the aggregation process.  The field
> >    modifier specifies how these Information Elements are treated by the
> >    process.  This field modifier is applied to Information Elements
> >    within Flow Record and IPFIX header, such as "Observation Domain ID"
> >    and "Export time".  This header information MAY be used when IPFIX
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 12]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    datagrams are made of past Flow Records.
> > 
> >    When another node retrieves past Flow Records, we can consider
> 
> How does it retrieve them?
> 

Simply, the specified past Flow Records can be retrieved on the basis of
time period which is given by user. The retrieving mechanism is out of
scope of this document.


> >    several specifications.  One solution is that another node gets a
> >    specified flat file from a Mediator and decodes that flat file by
> >    itself.  Other solutions are that another node sends out the query
> >    command to the IPFIX Mediator through XML-RPC, SNMP, or NETCONF, and
> >    then the IPFIX Mediator exports the specified past Flow Records.
> >    This function is outside the scope of this document.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 13]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 4.  IPFIX Protocol Considerations
> > 
> >    This section describes IPFIX protocol considerations with regard to
> >    IPFIX Mediator.
> > 
> > 4.1.  Export Time Issue
> > 
> >    If the Exporting Process writes the "Export Time" of the IPFIX
> >    message when an IPFIX message leaves, an IPFIX Mediator needs to
> >    compensate for the delta time Information Elements contained in each
> 
> "the" -> "any"
> 
> >    Flow Record.  An IPFIX Proxy SHOULD reuse the "Export Time" of
> 
> "SHOULD" -> "MUST"
> 
Yes. I will correct it.


> >    received IPFIX messages from the Original Exporter.
> > 
> > 4.2.  Observation Domain ID Management
> > 
> >    To comply with the IPFIX protocol the Observation Domain ID value is
> >    RECOMMENDED to be assigned uniquely per IPFIX Mediator.  In addition,
> >    Observation Domain ID SHOULD be 0 when IPFIX Mediator exports
> >    aggregated Flow Records and cannot manage the specific Observation
> >    Domain ID of the Original Exporter.  If an IPFIX Proxy relays an
> >    IPFIX datagram from a transport session to a transport session, IPFIX
> >    Proxy does not need to overwrite the Observation Domain ID with
> >    another value.  If an IPFIX Proxy relays an IPFIX datagram from
> >    multiple transport sessions to a single ransport session, IPFIX Proxy
> >    needs to overwrite the Observation Domain ID.  In that case, IPFIX
> >    Proxy assigns the Observation Domain ID based on received Transport
> >    Session Information and the original Observation Domain ID.  The
> >    renewed Observation Domain ID SHOULD be managed using the received
> >    Transport Session Information and original Observation Domain ID.
> >    This linkage information is available for overwriting the scope field
> >    of the option template.
> > 
> > 4.3.  Template Management
> > 
> >    The template ID of a generated template SHOULD be unique on the basis
> 
> "Template". Please be sure to capitalise IPFIX terminology!
> 
Yes. I will correct it.


> >    of the Observation Domain ID assigned by an IPFIX Mediator.  The
> >    template ID needs to be unique on the basis of IPFIX Mediator when
> >    the Observation Domain ID is 0.  If the IPFIX Mediator overwrites the
> >    received template ID to relay a received template or modified
> >    template, the renewed template ID SHOULD be managed using received
> >    Transport Session Information and received Observation Domain ID.
> >    This linkage information is available for overwriting scope field of
> >    an option template and template handling.  If IPFIX Mediator receives
> >    a "template withdraw message", it SHOULD modify this message to
> >    indicate relevant templates, and send "template withdraw message".
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 14]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 4.4.  Transport Session Management
> > 
> >    Each session of the Collecting Process and Exporting Process should
> >    operate independently.  Even if one session is reset, the status of
> >    the other session is kept current.  However, templates for resetting
> >    collecting session SHOULD be withdrawn for the exporting session.
> > 
> > 4.5.  Option Template Management
> > 
> >    IPFIX Mediator MUST check whether the scope field is applicable, if
> >    received Data Records associated Options templates are exported.  If
> >    an IPFIX Mediator rewrites the Observation Domain ID or template ID,
> >    these values included in scope fields SHOULD be rewritten before
> >    exporting.  Instead of exporting the Options Template Records and
> >    associated Data Records, Information Elements exported using the
> >    Options template Record from the Original Exporter, such as sampling
> >    rate or sampling method, could be merged in a Flow Record in an IPFIX
> >    Mediator.  In that case, IPFIX Mediator MUST modify the relevant
> >    Template Record.  Several sorts of received statistics Options
> >    Template Records and associated Data Records could be exported in
> >    different ways as other templates.  In IPFIX Proxy, the Data Record
> >    associated by statistics Options Template Records can be exported
> >    after merging its counter.  In addition, statistics Options Template
> >    Records and associated Data Records can be exported by indicating the
> >    source of the statistics data as a scope field instead of merging the
> >    counter.  This method is described in Section 6.  The user policy
> >    determines whether IPFIX Mediator and the above methods should export
> >    Option Templates Records and associated Data Records.
> > 
> > 4.6.  Reporting of Exporter Information
> > 
> >    Reporting of Exporter Information, such as Exporter IP address, is
> 
> Surely that's a loss of privacy?

It is depends on the role of IPFIX Mediator.
If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
becomes to grow the vulnerability.
On the other hand, if it is other nodes, such as concentrator, Exporter
IP address is important information for traffic analysis, such as traffic
engineering.

In case of making traffic matrix, Exporter IP address can indicate the
ingress router of network domain.
> 
> >    useful to identify the Original Exporter.  There are various methods
> >    as follows.  An IPFIX Mediator can directly merge Exporter
> >    Information into Flow Records or use Options Templates described in
> >    Section 6.  If an IPFIX Mediator received fields related to the
> >    Exporter information, IPFIX Mediator SHOULD NOT rewrite its own
> >    previous Exporter information.  The IPFIX Mediator can append its own
> >    previous Exporter Information instead of rewriting.  In the
> >    Collecting Process, the order of the Exporter information means the
> >    Original Exporter and the route of IPFIX Mediator.  These methods
> >    defined by user policy determine whether IPFIX Mediator should report
> >    that information has been exported
> 
> Some text seems to be missing here?
> 

Oops, I miss the period. I will correct it.


> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 15]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 5.  Solution Scenarios with IPFIX Mediators
> > 
> > 5.1.  Flexible Aggregation
> > 
> >    An IPFIX Mediator can aggregate Flow Records in the same manner as
> >    that of IPFIX concentrator and reduce the number of Flow Records
> >    received by a traffic collector.
> > 
> >    The following figure indicates a cascade connection of IPFIX
> >    Mediators.  If a Collector measures a traffic matrix to obtain
> >    traffic demand, the Collector needs Flow Records of the whole network
> >    domain, but does not need detailed Flow Records.  In the first step,
> >    a Mediator receives Flow Records from IPFIX Devices and then creates
> 
> "a first level Mediator"
> 
> >    aggregated low-level Flow Records.  For example, this step is prefix
> >    mask aggregation.  Next, the Mediator receives aggregated Flow
> 
> "Next, a second level Mediator"
> 
Yes. I will correct it.


> >    Records and aggregates them further.  For example, the second step is
> >    the aggregation of the BGP next-hop address and exporter address.
> >    After this, the collector receives high-level aggregated Flow Records
> >    and then stores them.  This method enables step-by-step aggregation
> >    of Flow Records without overloading a single node.
> > 
> >    .--------.     .--------.
> >    |IPFIX   |     |IPFIX   |
> >    |router#1|---->|Mediator|---.
> >    |        |     |*1      |   |
> >    '--------'     '--------'   |    .--------.     .---------.
> >                                '--->|IPFIX   |     |Traffic  |
> >    .--------.     .--------.   .--->|Mediator|---->|Collector|
> >    |IPFIX   |     |IPFIX   |   |    |*2      |     |         |
> >    |router#2|---->|Mediator|---'    '--------'     '---------'
> >    |        |     |*1      |
> >    '--------'     '--------'
> > 
> >    Figure C: Flexible Aggregation with cascading IPFIX Mediators.
> > 
> > 5.2.  Distributed Aggregation
> > 
> >    When the network is used globally, the distances between PoPs become
> >    longer, and the maintenance of a dedicated management network is very
> >    expensive.  Therefore, the huge number of Flow Records has burdened
> >    the management networks of global ISPs.  If we place Mediators at
> >    each PoP, the number of Flow Records exported from each PoP can be
> >    reduced.  Mediators can minimize the number of Flow Records exported
> >    to the Collector.  If the Collector needs detailed information, it
> >    can retrieve Flow Records from Mediators that store original Flow
> >    Records.
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 16]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    A management network of a global ISP is shown in the following
> >    figure.  The Mediators are located at each PoP of the network, and
> >    they collect Flow Records from routers in each PoP domain.  The
> >    Mediator reduces the number of Flow Records by aggregating or
> >    filtering, so this system reduces the load of a management network.
> > 
> >                 POP#Asia
> >         .--------.
> >       .--------. |      .---------.
> >     .--------. | |----->|IPFIX    |
> >     |IPFIX   | |------->|Mediator |----.
> >     |router  |---'----->|#1       |    |
> >     |#1      |-'        '---------'    |
> >     '--------'                         |
> >                                        |
> >                 POP#America            |
> >         .--------.                     |
> >       .--------. |      .---------.    |     .---------.
> >     .--------. | |----->|IPFIX    |    '---->|Traffic  |
> >     |IPFIX   | |------->|Mediator |--------->|Collector|
> >     |router  |---'----->|#2       |    .---->|         |
> >     |#4      |-'        '---------'    |     '---------'
> >     '--------'                         |
> >                                        |
> >                 POP#Europe             |
> >         .--------.                     |
> >       .--------. |      .---------.    |
> >     .--------. | |----->|IPFIX    |    |
> >     |IPFIX   | |------->|Mediator |----'
> >     |router  |---'----->|#3       |
> >     |#7      |-'        '---------'
> >     '--------'
> > 
> >    Figure D: Traffic monitoring architecture in global network.
> > 
> > 5.3.  Duplication of Flow Records
> > 
> >    An IPFIX Mediator duplicates Flow Records to achieve redundant
> >    storage or utilizes them for several purposes.  The pair of
> >    Collecting Process and Metering Processes is similar to the pair of
> >    the Observation Point and Metering Process.  The Collecting Process
> >    duplicates Flow records by forwarding them to the multi-Metering
> >    Process.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 17]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    Several departments in an ISP want to use the same traffic
> >    information for each intended purpose.  For example, the network
> >    design department measures the traffic matrix to obtain traffic
> >    demand, and the customer service division uses traffic information
> >    for performing accounting services for each customer while the
> >    network operation center uses traffic information for trouble
> >    shooting analysis.  That case is shown in the following figure.  An
> >    IPFIX Mediator distributes Flow Records to several Collectors that
> >    have the appropriate aggregated granularity.  In addition, when a NOC
> >    conducts troubleshooting, past Flow Records from Mediators can be
> >    retrieved.
> > 
> >                                          Measurement traffic matrix.
> >    .--------.                               .---------.
> >    |IPFIX   |                               |Traffic  |
> >    |router#1|----.                    .---->|Collector|
> >    |        |    |                    |     |#1       |
> >    '--------'    |                    |     '---------'
> >                  |                    |  Using Accounting info.
> >    .--------.    |     .---------.    |     .---------.
> >    |IPFIX   |    '---->|IPFIX    |----'     |Traffic  |
> >    |router#2|--------->|Mediator |--------->|Collector|
> >    |        |    .---->|         |----.     |#2       |
> >    '--------'    |     '---------'    |     '---------'
> >                  |                    |  Using Trouble shooting.
> >    .--------.    |                    |     .---------.
> >    |IPFIX   |    |                    |     |Traffic  |
> >    |router#1|----'                    '---->|Collector|
> >    |        |                               |#3       |
> >    '--------'                               '---------'
> 
> The bottom left router should be "router#3"
> 
Yes. I will correct it.

> > 
> >    Figure E: Duplication of Flow Records for several purposes.
> > 
> > 5.4.  Distribution of Flow Records
> > 
> >    An IPFIX Mediator distributes Flow Records based on Flow Record
> 
> "MAY distribute"
> 
Yes. I will correct it.

> >    content.  This function enables load balancing of Collector and
> >    sorting Flow Records without extra Collector functions.  If the Flow
> >    Records are used as accounting information, this solution is useful.
> 
> It's unclear to me what this means.
> 

Surely, it is too short explanation. For example, if an IPFIX Mediator
distributes Flow Records on the basis of input IF indexes which
indicates customer, measuring total traffic volume by each Collector can
indicate each customer's accounting information.

On careful thought, it is better that this sentence is omitted.

> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 18]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    When we disclose traffic information to each customer, security or
> 
> "we"? -> The mediator, perhaps?
> 
I was confused how to use "we". I mean it is network service provider. 
The Mediator is preferable.

> >    the privacy policy should be considered.  In that case, IPFIX
> >    Mediator hides private information about each customer.  For example,
> >    Mediator distributes traffic information based on RD (Route
> >    Distinguisher), egress IF, peering AS number, or BGP next hop, which
> >    identify the customer.  In the following figure, the IPFIX Mediator
> >    distributes Flow Records based on RD.  The system securely allows
> >    each customer to access only their own records.
> > 
> >    .--------.                               .---------.
> >    |IPFIX   |                               |Traffic  |
> >    |router#1|----.                    .---->|Collector|<===> Customer#A
> >    |        |    |                    |     |#1       |
> >    '--------'    |                    |     '---------'
> >                  |                 RD=100:1
> >                  |     .---------.    |
> >    .--------.    '---->|IPFIX    |----'     .---------.
> >    |IPFIX   |          |Mediator | RD=100:2 |Traffic  |
> >    |router#2|--------->|         |--------->|Collector|<===> Customer#B
> >    |        |          |         |          |#2       |
> >    '--------'    .---->|         |----.     '---------'
> >                  |     '---------'    |
> >                  |                 RD=100:3
> >    .--------.    |                    |     .---------.
> >    |IPFIX   |    |                    |     |Traffic  |
> >    |router#1|----'                    '---->|Collector|<===> Customer#C
> >    |        |                               |#3       |
> >    '--------'                               '---------'
> > 
> >    Figure F: Distribution of Flow Records for each customer.
> > 
> > 5.5.  Extraction of Suspicious Flow
> > 
> >    An IPFIX Mediator performs filtering based on Flow Record content.
> >    If the filter conditions are set depending on the suspicious flow as
> >    follows, the Collector receives the specified suspicious flow and
> >    detects an anomalous flow by simply monitoring the traffic volume of
> >    each suspicious flow.
> > 
> >    o  TCP Flow Records whose "tcpControlBits" value is set to "null"
> > 
> >    o  TCP Flow Records whose "tcpControlBits" value is set to the SYN
> >       bit only and the packet counter is only 1.
> 
> This will always happen for TCP flows of 1 or more packets. It might be 
> suspicious if the count was still 1 after some time.
> 
Yes.

> > 
> >    o  ICMP Flow Records whose length is too long.
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 19]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 6.  Mediator Option Template Presentation
> > 
> >    This section describes Option Templates that are used by IPFIX
> >    Mediators.
> > 
> > 6.1.  Exporter Information Option Template
> > 
> >    Each IPFIX Mediator and final destination Collector needs to know the
> >    Original Exporter and route of IPFIX Mediators.  Therefore, each
> >    IPFIX Mediator informs the next Collector about previous Exporter
> >    information, which is the Exporter Information Option Template that
> >    specified the Original Exporter and the route of the IPFIX Mediator.
> >    The final destination Collector can recognize them by receiving this
> >    template.  This template is composed of the following Information
> >    Elements.
> > 
> >    o  exporter{IPv4|IPv6}Address
> > 
> >    o  collector{IPv4|IPv6}Address
> > 
> >    o  exporterTransportPort
> > 
> >    o  collectorTransportPort
> > 
> >    o  collectorTransportProtocol
> > 
> >    o  observationDomainId
> > 
> >    The Observation Domain ID of the Original Exporter or IPFIX Mediator
> >    is identified by specifying exporter/collector Information Elements,
> >    such as "collector{IPv4|IPv6}Address", "collectorTransportPort",
> >    "collectorTransportProtocol", ,"exporter{IPv4|IPv6}Address",
> >    "exporterTransportPort", and "observationDomainId".  The set of
> >    "observationDomainId" and "templateId" or "observationDomainId" might
> >    be used as a scope field.  Not all Information Elements are
> >    necessary.  For example, the exporter{IPv4|IPv6}Address is necessary
> >    to inform the next Collector the Original Exporter which created Flow
> >    Records.  If the IPFIX Mediator receives this template, it SHOULD not
> >    overwrite each field.  The IPFIX Mediator appends its own previous
> >    Exporter information onto received Data Records specified by the
> >    Exporter Option Template and sends that information to the Collector.
> >    In this manner, the route is maintained until the final destination
> >    Collector.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 20]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    The following example describes the cascade connection of IPFIX
> >    Mediators.  Each Mediator informs the next Collector about previous
> >    Exporter information.
> > 
> >           Session#a            Session#b            Session#c
> >    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
> >    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
> >    SrcPort:10       DstPort:20           DstPort:40
> >    ODID:10          SrcPort:30           SrcPort:50
> >                     ODID:0               ODID:0
> > 
> >    Figure G: Cascade connection of IPFIX Mediators.
> > 
> >    Mediator#1 or Mediator#2 sends a Data Record specified by the
> >    Exporter Option Template.  The Data records are shown in Session#b or
> >    Session#c, as follows.
> > 
> >    Session#b Data Record:
> >       Field Count = 7
> >       Scope Count = 1
> >       templateId = XXX
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> 
> Could you use real-world values in the examples here and below?
> 
> P.
> 
Is it preferable using private address? 
Surely, the destination port number should be 4739.

> > 
> >    Session#c Data Record:
> >       Field Count = 13
> >       Scope Count = 1
> >       templateId = XXX
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> >       exporterIPv4Address = 2.2.2.2
> >       collectorIPv4Address = 3.3.3.3
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 30
> >       collectorTransportPort = 40
> >       observationDomainId = 0
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 21]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 6.2.  Usage of Scope Field
> > 
> >    An IPFIX Mediator needs to send forward a Options Template Records
> >    and associated Data Records from the Original Exporter.  However,
> >    IPFIX Mediator can not export an original Option Template Records and
> >    associated Data Records without modification because changing a
> >    session from an Exporting Process to a Collecting Process causes the
> >    scope fields to become a useless value.  When an IPFIX Mediator
> >    relays the Options Template Records that included Observation Domain
> >    ID as a scope field and associated Data Records, an IPFIX Mediator
> >    uses the Exporter Information Option Template.  The Options Template
> >    Records that were created from an Original Exporter can use the
> >    entire fields of the Exporter Information Option template as multiple
> >    scope fields.  The Options Template Records that were created from
> >    anIPFIX Mediator can uses the some fields of the Exporter Information
> >    Option template as multiple scope fields.  An IPFIX Mediator needs to
> >    modify the associated Data Records according to the modified Options
> >    Template Record.  However, if each node uses another field except for
> >    the Observation Domain ID as the scope, the scope field should be
> >    considered on a case-by-case basis.
> > 
> >    The following example describes the cascade connection of IPFIX
> >    Mediators.  Router#1 and Mediator#1 export the Metering Process
> >    Statistics Option Template.
> > 
> > 
> >           Session#a            Session#b            Session#c
> >    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
> >    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
> >    SrcPort:10       DstPort:20           DstPort:40
> >    ODID:10          SrcPort:30           SrcPort:50
> >                     ODID:0               ODID:0
> > 
> >    Figure H: Cascade connection of IPFIX Mediators.
> > 
> >    Mediator#2 exports each Option Template and its Data Record with a
> >    suitable scope.
> > 
> >    Session#c Metering Process Statistics Data Records from the Original
> >    Exporter:
> >       Field Count = 15
> >       Scope Count = 12
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 22]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       exporterIPv4Address = 2.2.2.2
> >       collectorIPv4Address = 3.3.3.3
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 30
> >       collectorTransportPort = 40
> >       observationDomainId = 0
> >       exportedMessageTotalCount
> >       exportedFlowTotalCount
> >       exportedOctetTotalCount
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 23]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 7.  Security Considerations
> > 
> >    The IPFIX concentrator uses the IPFIX protocol.  Security
> >    considerations about flow information are described in
> >    [I-D.ietf-ipfix-protocol].
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 24]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 8.  IANA Considerations
> > 
> >    This document has no actions for IANA.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 25]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 9.  References
> > 
> > 9.1.  Normative References
> > 
> >    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
> >               Requirement Levels", BCP 14, RFC 2119, March 1997.
> > 
> > 9.2.  Informative References
> > 
> >    [I-D.dressler-ipfix-aggregation]
> >               Dressler, F., Sommer, C., and G. Munz, "IPFIX
> >               Aggregation", draft-dressler-ipfix-aggregation-03.txt
> >               (work in progress) , June 2006.
> > 
> >    [I-D.ietf-ipfix-architecture]
> >               Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
> >               "Architecture for IP Flow Information Export",
> >               draft-ietf-ipfix-architecture-12.txt(work in progress) ,
> >               September 2006.
> > 
> >    [I-D.ietf-ipfix-info]
> >               Quittek, J., Bryant, S., Claise, B., and J. Meyer,
> >               "Information Model for IP Flow Information Export",
> >               draft-ietf-ipfix-info-13.txt(work in progress) ,
> >               June 2006.
> > 
> >    [I-D.ietf-ipfix-protocol]
> >               Claise, B., "IPFIX Protocol Specification",
> >               draft-ietf-ipfix-protocol-23 (work in progress) ,
> >               October 2006.
> > 
> >    [I-D.ietf-psamp-framework]
> >               Duffield, N., "A Framework for Packet Selection and
> >               Reporting", draft-ietf-psamp-framework-10.txt ,
> >               January 2005.
> > 
> >    [I-D.ietf-psamp-sample-tech]
> >               Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
> >               Raspall, "Sampling and Filtering Techniques for IP Packet
> >               Selection", draft-ietf-psamp-sample-tech-07.txt ,
> >               July 2005.
> > 
> >    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
> >               "Requirements for IP Flow Information Export(IPFIX)",
> >               October 2004.
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 26]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Authors' Addresses
> > 
> >    Atsushi Kobayashi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-3978
> >    Email: akoba@nttv6.net
> > 
> > 
> >    Keisuke Ishibashi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-3407
> >    Email: ishibashi.keisuke@lab.ntt.co.jp
> > 
> > 
> >    Kondoh Tsuyoshi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-2419
> >    Email: kondoh.tsuyoshi@lab.ntt.co.jp
> > 
> > 
> >    Daisuke Matsubara
> >    Hitachi, Ltd., Central Reseach Laboratory
> >    1-280 Higashi-koigakubo
> >    Kokubunji-shi, Tokyo  185-8601
> >    Japan
> > 
> >    Phone: +81-42-323-1111
> >    Email: d-matuba@crl.hitachi.co.jp
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 27]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Full Copyright Statement
> > 
> >    Copyright (C) The IETF Trust (2007).
> > 
> >    This document is subject to the rights, licenses and restrictions
> >    contained in BCP 78, and except as set forth therein, the authors
> >    retain all their rights.
> > 
> >    This document and the information contained herein are provided on an
> >    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
> >    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
> >    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
> >    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
> >    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
> >    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> > 
> > 
> > Intellectual Property
> > 
> >    The IETF takes no position regarding the validity or scope of any
> >    Intellectual Property Rights or other rights that might be claimed to
> >    pertain to the implementation or use of the technology described in
> >    this document or the extent to which any license under such rights
> >    might or might not be available; nor does it represent that it has
> >    made any independent effort to identify any such rights.  Information
> >    on the procedures with respect to rights in RFC documents can be
> >    found in BCP 78 and BCP 79.
> > 
> >    Copies of IPR disclosures made to the IETF Secretariat and any
> >    assurances of licenses to be made available, or the result of an
> >    attempt made to obtain a general license or permission for the use of
> >    such proprietary rights by implementers or users of this
> >    specification can be obtained from the IETF on-line IPR repository at
> >    http://www.ietf.org/ipr.
> > 
> >    The IETF invites any interested party to bring to its attention any
> >    copyrights, patents or patent applications, or other proprietary
> >    rights that may cover technology that may be required to implement
> >    this standard.  Please address the information to the IETF at
> >    ietf-ipr@ietf.org.
> > 
> > 
> > Acknowledgment
> > 
> >    Funding for the RFC Editor function is provided by the IETF
> >    Administrative Support Activity (IASA).
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 28]
> > 
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Sat Jul 28 15:40:25 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEs9B-0006DU-Dj; Sat, 28 Jul 2007 15:40:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEs99-00062L-L5
	for ipfix@ietf.org; Sat, 28 Jul 2007 15:40:15 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEs91-0005kQ-My
	for ipfix@ietf.org; Sat, 28 Jul 2007 15:40:15 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6SJdtab000165;
	Sun, 29 Jul 2007 04:39:55 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Sun, 29 Jul 2007 04:39:57 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
In-Reply-To: <46A7D10F.3050509@cisco.com>
References: <46A7D10F.3050509@cisco.com>
Message-Id: <20070729030242.485A.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Sun, 29 Jul 2007 04:39:56 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 485c16ccf4ca6ef309699ad6279bf354
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,
 
Thank you for your valuable comments.
Please see in-line.

Atsushi KOBAYASHI

On Wed, 25 Jul 2007 23:39:11 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Please see my comments inline.
> 
> 
> > IPFIX Working Group                                         A. Kobayashi
> > Internet-Draft                                              K. Ishibashi
> > Intended status: Informational                                 T. Kondoh
> > Expires: December 25, 2007                                   NTT PF Lab.
> >                                                             D. Matsubara
> >                                                                  Hitachi
> >                                                            June 23, 2007
> > 
> > 
> >                   Reference Model for IPFIX Mediators
> >               draft-kobayashi-ipfix-mediator-model-00.txt
> > 
> > Status of this Memo
> > 
> >    By submitting this Internet-Draft, each author represents that any
> >    applicable patent or other IPR claims of which he or she is aware
> >    have been or will be disclosed, and any of which he or she becomes
> >    aware will be disclosed, in accordance with Section 6 of BCP 79.
> > 
> >    Internet-Drafts are working documents of the Internet Engineering
> >    Task Force (IETF), its areas, and its working groups.  Note that
> >    other groups may also distribute working documents as Internet-
> >    Drafts.
> > 
> >    Internet-Drafts are draft documents valid for a maximum of six months
> >    and may be updated, replaced, or obsoleted by other documents at any
> >    time.  It is inappropriate to use Internet-Drafts as reference
> >    material or to cite them other than as "work in progress."
> > 
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/ietf/1id-abstracts.txt.
> > 
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html.
> > 
> >    This Internet-Draft will expire on December 25, 2007.
> > 
> > Copyright Notice
> > 
> >    Copyright (C) The IETF Trust (2007).
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 1]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Abstract
> > 
> >    An IPFIX Mediator is an intermediate node between IPFIX devices and
> 
> "devices" -> "Exporting Processes"
> 
> >    traffic collectors.  This node acts as an IPFIX proxy, IPFIX
> 
> "traffic collectors" -> "IPFIX Collecting Processes".
> 
> "This node" -> "A mediator"
> 

Yes. I will correct them in next version. 

> >    firewall, and IPFIX concentrator.  An IPFIX Mediator mediates the
> >    IPFIX protocol using several functions.  That enables the traffic
> >    monitoring system to become a high-capacity system and accommodate a
> >    variety of traffic monitoring methods.  This document describes each
> >    function that is provided by IPFIX Mediators and the method of
> >    handling the Flow Records of each function.  In addition, this
> >    describes the model of the solution scenario using IPFIX Mediator.
> 
> It's unclear what this last line means.
> 

"this" indicates this draft.
This document describes the model of the solution scenario using IPFIX Mediator
which refer to chapter 5. 

> > 
> > 
> > Table of Contents
> > 
> >    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
> >    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
> >    3.  Internal Components Model  . . . . . . . . . . . . . . . . . .  8
> >      3.1.  Collecting Process . . . . . . . . . . . . . . . . . . . .  8
> >      3.2.  Metering Process . . . . . . . . . . . . . . . . . . . . .  9
> >        3.2.1.  Selection Process  . . . . . . . . . . . . . . . . . .  9
> >        3.2.2.  Aggregation Process  . . . . . . . . . . . . . . . . .  9
> >        3.2.3.  Modification Process . . . . . . . . . . . . . . . . . 10
> >      3.3.  Exporting Process  . . . . . . . . . . . . . . . . . . . . 12
> >      3.4.  Storing Process  . . . . . . . . . . . . . . . . . . . . . 12
> >    4.  IPFIX Protocol Considerations  . . . . . . . . . . . . . . . . 14
> >      4.1.  Export Time Issue  . . . . . . . . . . . . . . . . . . . . 14
> >      4.2.  Observation Domain ID Management . . . . . . . . . . . . . 14
> >      4.3.  Template Management  . . . . . . . . . . . . . . . . . . . 14
> >      4.4.  Transport Session Management . . . . . . . . . . . . . . . 15
> >      4.5.  Option Template Management . . . . . . . . . . . . . . . . 15
> >      4.6.  Reporting of Exporter Information  . . . . . . . . . . . . 15
> >    5.  Solution Scenarios with IPFIX Mediators  . . . . . . . . . . . 16
> >      5.1.  Flexible Aggregation . . . . . . . . . . . . . . . . . . . 16
> >      5.2.  Distributed Aggregation  . . . . . . . . . . . . . . . . . 16
> >      5.3.  Duplication of Flow Records  . . . . . . . . . . . . . . . 17
> >      5.4.  Distribution of Flow Records . . . . . . . . . . . . . . . 18
> >      5.5.  Extraction of Suspicious Flow  . . . . . . . . . . . . . . 19
> >    6.  Mediator Option Template Presentation  . . . . . . . . . . . . 20
> >      6.1.  Exporter Information Option Template . . . . . . . . . . . 20
> >      6.2.  Usage of Scope Field . . . . . . . . . . . . . . . . . . . 22
> >    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 24
> >    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 25
> >    9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
> >      9.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
> >      9.2.  Informative References . . . . . . . . . . . . . . . . . . 26
> >    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
> >    Intellectual Property and Copyright Statements . . . . . . . . . . 28
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 2]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 1.  Introduction
> > 
> >    Several problems regarding traffic monitoring have occurred in
> >    several networks, as follows.
> 
> Can you cite some references for this?
> 

I can't cite some references now. Until submitting the next version, I will
search for some references.

> > 
> >    o  Scalability of collector on large-scale networks
> > 
> >       As the sizes of networks become larger, the number of Flow Records
> >       becomes greater.  Large numbers of Flow Records have been
> >       burdening management networks and the collecting process.
> >       Maintaining scalability is difficult as a particular network
> >       grows.  Generally, network operations need to monitor overall
> >       wide-scale traffic behavior and investigate detailed traffic
> >       information when traffic incidents happen.  Meeting these
> >       requirements seems to be difficult for a single collector node
> >       because of large numbers of Flow Records.
> > 
> >    o  Handling multifaceted network environment
> > 
> >       On the other hand, networks such as IPv4, IPv6, and VPN on MPLS
> >       have recently become more multifaceted.  These sorts of Flow
> 
> What do you mean by "multifaceted"?
> 

Simply, I mean that the variety of packets, such as IPv4 and IPv6, are passed
thought in the same network. Especially, MPLS network handles the
several customer's traffic as VPN traffic, such as pseudo wire or L3VPN.

I means that networks are integrating variety of traffic.

I will add the explanation in this paragraph.


> >       Records need to be analyzed separately from a different
> >       perspective.  However, handling them separately without improving
> >       the capability of the Collector is difficult.
> > 
> >    o  Exchanging traffic information between different networks
> > 
> >       Traffic information is considered to be necessary for ISP network
> >       providers as well as each customer.  To that end, the network
> >       provider needs to export specified Flow Records while avoiding
> >       privacy violations.  In addition, exchanging traffic information
> >       between the associated networks could be necessary when traffic
> >       incidents happen.  In that case, the Flow Records should be
> >       checked according to the service provider's policy before
> >       exporting.  Therefore, Flow Records exported from Exporter
> >       directly without modification can not be fed each customer or
> 
> "can not be fed *to* each customer"

yes. I will correct it in the next version.

> 
> >       associated network operators without modification.
> > 
> >    IPFIX Mediators enable us to overcome these problems by preprocessing
> >    Flow Records.  By defining IPFIX Mediators, we can take increasing
> >    advantage of an extensive template format, and handle Flow Records in
> >    accordance with our preference.  This document describes some
> >    solutions using IPFIX Mediators that solve these problems and
> >    components that are needed in the internal process.
> > 
> >    The IPFIX Mediator, which is located between one or more Exporting
> >    Processes and one or more Collecting Processes, has a main function
> >    for handling Flow Records.  That function stores original Flow
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 3]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    Records and mediates them.  In addition, renewed Flow Records are
> 
> It's worth defining what mediation is.

I will add the description about Flow Mediation and IPFIX protocol
Mediation presented by my slide.

> Also, what are "renewed Flow Records"?

This part is described about Flow Mediation.

I means that the "renewed Flow Records" is modified Flow Records or
aggregated Flow Records.

Modification of Flow Records means that some fields are added and deleted,
and whose value are modified.

I will adds the description in the next version.

> >    generated and distributed to an appropriate Collector or traffic
> >    analyzer in accordance with flow content.
> 
> Must the mediator understand the content? eg, what about Enterprise 
> Specific elements?
> 

Mediator doesn't need to understand all content, as semantic. After decoding
by the collecting process, Flow Records are distributed in accordance
with specified elements contents, such as input IF indexes or Peering AS.
In this case, Mediator doesn't need to understand other field contents.
In the distribution of Flow Records, Some fields which should be understood
are restricted.

> >    The internal model of a Mediator is composed of Collecting Processes,
> >    Metering Processes, and Exporting Processes.  IPFIX Mediator acts as
> >    a Collector by receiving Flow Records, and it acts as an Exporter by
> >    sending Flow Records.  This dual-role architecture enables cascading
> >    Mediators and building a combination of several solutions.
> > 
> >    This document describes a model of a solution scenario by using IPFIX
> >    Mediator and its key component.
> > 
> >    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >    document are to be interpreted as described in [RFC2119].
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 4]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 2.  Terminology
> > 
> >    The definitions of basic IPFIX and PSAMP terms are identical with
> >    those in [I-D.ietf-psamp-framework], [RFC3917],
> >    [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info], and
> >    [I-D.ietf-ipfix-architecture].  Other than the above terminology, the
> >    following terminology related to IPFIX Mediator is used in this
> >    document.  Therefore, the terms defined in the IPFIX terminology are
> >    capitalized in this document.
> > 
> >    IPFIX Mediator
> > 
> >       An IPFIX Mediator hosts at least one pair of Exporting Process and
> >       Collecting Process.  An IPFIX Mediator may have the Metering
> 
> "at least one Exporting Process and one Collecting Process".
> 
> >       Process and Storing Process as optional.  An IPFIX Proxy, an IPFIX
> 
> "may optionally have Metering Processes and Storing Processes".
> 

Yes. I will correct them in the next version.

> >       Firewall and an IPFIX concentrator are one node of IPFIX
> >       Mediators.
> 
> This last line is unclear.
> 

In next version, I will add the description about what is IPFIX Mediator.
I means that IPFIX Mediator is generic name of the several nodes, such as
the IPFIX proxy, IPFIX firewall and IPFIX concentrator.


> > 
> >    Original Exporter
> > 
> >       An Original Exporter hosts Observation Points where IP packets can
> >       be observed.
> > 
> >    IPFIX Proxy
> > 
> >       An IPFIX Proxy acts as a proxy for Original Exporter, which hosts
> 
> "Exporters"
> 
Yes.

> >       Observation Points.  An IPFIX Proxy may receive Flow Records from
> >       one or multiple Exporting Processes, and send them to one or
> >       multiple Collecting Processes.  An IPFIX Proxy does not send the
> >       information about an Original Exporter to the Collector to act as
> >       an Original Exporter.
> 
> This last line is unclear.
> 

IPFIX proxy does not send the the information about an Original
Exporter, such as "exporterIPv{4|6}Address" to the Collector.

> > 
> >    IPFIX Firewall
> > 
> >       An IPFIX Firewall exports the Flow Records to a different network
> >       domain at the edge of the self-network domain.  From the
> >       Collector's point of view, an IPFIX Firewall acts as an Original
> >       Exporter, just like an IPFIX Proxy.  In addition, an IPFIX
> >       Firewall reviews whether received Flow Records are passed forward
> >       to the Collector to hide the network topology or privacy
> >       information.
> 
> Does it block records, or modify them? eg, does it anonymise them?
> 
I think that above functions are included in the IPFIX Firewall.
At least, IPFIX Firewall has one function of above functions, such as
filtering, modifying and anonymizing.

I will add the description about it in the next version.
> > 
> >    Metering Process
> > 
> >       The Metering Process in IPFIX Mediators can be considered the
> >       partial Metering Process separated from the Metering Process in
> >       the Original Exporter.  The Metering Process in IPFIX Mediators
> >       consists of a set of subprocesses that includes the Selection
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 5]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       Process, the Aggregation Process and the Modification Process.
> >       The Metering Process generates the final Flow Records that should
> >       be exported.
> > 
> >    Selection Process
> > 
> >       The Selection Process in an IPFIX Mediator is similar to that of
> >       PSAMP Devices, which is described in [I-D.ietf-psamp-framework].
> >       However, the Selection Process in an IPFIX Mediator differs from
> >       the following functions.  The Selection Process in PSAMP Devices
> >       has two types of selection functions: Filtering and Sampling.  In
> >       addition, the filtering function has two types of filtering
> >       methods: field-match filtering and hash-based selection.  The
> >       Selection Process in an IPFIX Mediator has only the field-match
> >       filtering functions.  This filtering function selects Flow Records
> >       based on Flow Record content.  The Selection Process is one of the
> >       subprocesses in the Metering Process.
> > 
> >    Aggregation Process
> > 
> >       The Aggregation Process creates aggregated Flow Records from
> >       inputted Flow Records, in accordance with aggregation rules that
> >       are described in [I-D.dressler-ipfix-aggregation].  The
> >       Aggregation Process is one of the subprocesses in the Metering
> >       Process.
> > 
> >    Modification Process
> > 
> >       The Modification Process carries out the addition, deletion, and
> >       modification of the Information Elements included in inputted Flow
> >       Records.  The Modification Process adds Information Elements like
> >       derived packet properties that canot be extracted in the Original
> >       Exporter.  Information Elements related to derived packet
> >       properties are described in [I-D.ietf-ipfix-info].  In addition,
> >       the Modification Process modifies the values of the specific
> >       Information Element.  For example, the modification of values is
> 
> "the values of specific Information Elements"

Yes. I will correct this term in the draft.
> 
> >       like anonymizing some Information Elements to avoid violating
> >       privacy.  The Modification Process deletes some Information
> >       Elements included in inputted Flow Records.  The Modification
> >       Process is one of the subprocesses in the Metering Process.
> 
> - and presumably this is a key part of a firewall?

Yes.
But, the modification process is not limited as the functions of IPFIX
firewall.
If the Modification Process adds the BGP Next Hop Address into the Flow
Records, this node is not implied to the IPFIX Firewall.

> > 
> >    Storing Process
> > 
> >       The Storing Process selects specified Information Elements
> >       according to the storing rules, and then stores inputted Flow
> >       Records in a storage system such as a database or flat-file
> >       system.  Information Elements are specified in storing rules.  In
> >       addition, the Observation Domain ID and Export Time in the header
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 6]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       of IPFIX messages are specified in the storing rules.
> 
> How does information get *out* of the Storing Process?

This part is out of scope of this document.
As solution, several solution can be considered.

In case of our system, other node, such as analyzer, submitted the query
that contains the specified time slot as XML, IPFIX Mediator replies this
query by replaying the NetFlow packets. 
> 
> > 
> >    Distribute Function
> > 
> >       The Distribute Function distributes final Flow Records based on
> >       the Flow content.  The final Flow Records are handled by the
> >       Exporting Process to export them to Collector.  Each classified
> >       Flow Record is exported to each Collector.
> 
> To all collectors, or to a subset?
> 

To a subset.
I mean that the classified Flow Records are exported to the specified Collector.

> > 
> >    Observation Domain ID
> > 
> >       An IPFIX Mediator doesn't host the Observation Point and
> >       Observation Domain.  Though, the Observation Domain ID in IPFIX
> >       header sent by IPFIX Mediator also indicates the largest set of
> >       Observation Points in the Original Exporter, but this value does
> >       not indicate the physical entity of the Original Exporter.  If
> >       inputted Flow Records are aggregated in the Metering Process, the
> >       Observation Domain ID value in IPFIX header SHOULD be 0.
> 
> I think only if the mediator is spoofing the original source exorter. 
> Arguably a whole new set of Observation Domain values applies on the 
> mediation device.

This part need a discussion with IPFIX members.
If IPFIX Proxy handles one exporting session and one collecting session,
simply IPFIX Proxy doesn't need to change the observation domain values.

I think, If IPFIX Proxy handles multiple session on the both sides,
IPFIX Proxy needs to assign the new Observation Domain values.

> >    Transport Session Information
> > 
> >       In SCTP, the Transport Session Information is the SCTP
> >       association.  In TCP and UDP, the Transport Session Information
> >       corresponds to a 5 tuple {exporter IP address, collector IP
> >       address, exporter transport port, collector transport port,
> >       transport protocol}.  In IPFIX Mediator, the Collecting Process
> >       manages this information.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 7]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 3.  Internal Components Model
> > 
> >    The following figure indicates four components (Collecting Process,
> >    Metering Process, Exporting Process, and Storing Process) within the
> >    IPFIX Mediator that are referred to in [RFC3917].  The Metering
> >    Process can have one or multiple subprocesses.  These subprocesses
> >    are the Selection Process, Aggregation Process, and Modification
> >    Process that can be connected to each other in any sequence defined
> >    by the user.  The Metering Process and Storing Process are options.
> > 
> > 
> >      +--------------------------------------------------------------+
> >      |                        IPFIX Mediator                        |
> >      | .----------.                                     .---------. |
> >      | |          |  .-------------------------------.  |         | |
> >      | |Collecting|  |        Metering Process       |  |Exporting| |
> >      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
> >      | |          |-->|sub    |->|sub    |->|sub    |-->|         | |
> >    IPFIX          |  ||process|  |process|  |process||  |         |IPFIX
> >    --> |          |  ||#1     |  |#2     |  |#3     ||  |         |-->
> >      | |          |  |'-------'  '-------'  '-------'|  |         | |
> >      | |          |  '-------------------------------'  |         | |
> >      | |          |------------------------------------>|         | |
> >      | |          |  .-------.                          |         | |
> >      | |          |->|Storing|                          |         | |
> >      | |          |  |Process|                          |         | |
> >      | |          |  '-------'                          |         | |
> >      | '----------'                                     '---------' |
> >      +--------------------------------------------------------------+
> 
> I think any of the metering sub-processes should be able to send data to 
> the storing process. Also, the Exporting process may send data there too 
> (consider Brian's file draft). Finally, there should be a route *out* of 
> the storing process - either to the outside, and/or to the Metering 
> Process, and/or to the Exporting Process.
> 

Good idea. Roughly, I can image following figure.

      +--------------------------------------------------------------+
      |                        IPFIX Mediator                        |
      | .----------.                                     .---------. |
      | |          |  .-------------------------------.  |         | |
      | |Collecting|  |        Metering Process       |  |Exporting| |
      | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
      | |          |--->sub    |-->sub    |->|sub    |-->|         | |
    IPFIX          |  ||process|  |process|  |process||  |         IPFIX
    --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
      | |          || |'-------'  '-------'  '-------'|  |         | |
      | |          || '----|----------|----------|----'  |         | |
      | |          ||      |          |          |       |         | |
      | |          ||   .--\/---------\/---------\/--.   |         | |
      | |          |'---|       Storing Process      |<--|         | |
      | |          |--->|                            |-->|         | |
      | |          |    '----------------------------'   |         | |
      | |          |------------------------------------>|         | |
      | '----------'                                     '---------' |
      +--------------------------------------------------------------+



> 
> >    Figure A: Key components within IPFIX Mediator.
> > 
> >    Each process is associated with a common identifier in the IPFIX
> >    Mediator.  This method is similar to PSAMP associations in
> >    [I-D.ietf-psamp-sample-tech].
> > 
> > 3.1.  Collecting Process
> > 
> >    This process receives Flow Records from the previous Exporter.  The
> >    instance of this process is created according to the IPFIX session.
> >    This process has functions that are described in
> >    [I-D.ietf-ipfix-protocol].  The Collecting Process also forwards
> >    received Flow Records with IPFIX header information and Transport
> >    Session Information to multiple Metering Processes or Storing
> >    Processes.  In other words, Flow Records can be duplicated by
> >    forwarding several Metering Processes.  In addition, the Collecting
> 
> Or Exporting Processes.
> 
Yes. 
Flow Records can be duplicated by forwarding several Metering Processes
or Exporting Processes.


> >    Process can directly forward Flow Records to Exporting Process.
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 8]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 3.2.  Metering Process
> > 
> >    This process generates the renewed Flow Records from inputted Flow
> >    Records with received IPFIX header information, such as "Export Time"
> >    and "Observation Domain ID".  This process hosts the several
> >    subprocesses.  The processing order of these functions, which could
> >    be located by user definitions, would lead to different renewed Flow
> >    Records.
> > 
> > 3.2.1.  Selection Process
> > 
> >    This process decides whether each Flow Record passes through to the
> >    next process.  Theprocess has a filtering function and selects Flow
> 
> Typo, "Theprocess".

Thanks.

> 
> >    Records that are matched under given conditions.  Prior to receiving
> >    Flow Records, this process has instruction pattern data that are
> >    defined by the user, which specifies how the Flow Records are treated
> >    by this process.  If the value of some Information Elements in the
> >    Flow Record match the instruction pattern, this process selects Flow
> >    Records with all fields and forwards these Flow Records to the next
> >    process.  For example, this process selects the Flow Records that are
> >    included in the specified destination IP address.
> > 
> > 3.2.2.  Aggregation Process
> 
> As a general question, is it valid to aggregate fields which were not 
> originally key fields?
> 

I think that the aggregate key field does not depend on the original key
fields.

> > 
> >    This process gathers Flow Records within a given time interval and
> >    then distinguishes Flow Records that have common properties.  If
> >    values of a given key field are the same, that means these Flow
> >    Records have common properties.  This process merges Flow Records
> >    that have a common property and creates an aggregated Flow Record.
> >    Therefore, for example, aggregated Flow Records have an aggregation
> >    counter that indicates the number of packets.  These functions are
> >    defined in accordance with the IPFIX aggregation rule in
> >    [I-D.dressler-ipfix-aggregation].
> > 
> >    The process has instructions that are user defined prior to receiving
> >    Flow Records.  The process indicates the Information Elements that
> >    should become aggregated flow keys and other Information Elements
> >    that should be kept or discarded.  In addition, these instruction
> >    rules include Information Elements that should be added to aggregated
> >    Flow Records.  The aggregated Flow Records may need to complement
> >    information that is discarded during the aggregation process.  They
> >    help the Collector to analyze aggregated Flow Records.  For example,
> >    these Information Elements correspond to "averageActiveTime",
> >    "synCount", and "flowCount" elements, as follows.
> > 
> >    o  averageActiveTime
> > 
> >       This Information Element indicates average time in milliseconds of
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007               [Page 9]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       difference between flow start time and end time of each flow
> >       included in the aggregated flow.  This Information Element is
> >       created from the flow time stamp Information Elements.  There are
> >       "flowStartSeconds", "flowEndSeconds", "flowStartMilliSeconds",
> >       "flowEndMilliSeconds", "flowStartSysUpTime", and
> >       "flowEndSysUpTime".  Moreover, "minimumActiveTime" and
> >       "maxmumActiveTime" might be considered in addition to the element.
> > 
> >    o  synCount
> > 
> >       This Information Elements the number of Flow Records that have
> >       "tcpControlBits" which the SYN bit sets to 1 in an aggregated
> >       flow.  Using this element, we can determine the number of SYN
> >       packets throughout the network.  Moreover, "ackCount", "finCount",
> >       "pshCount", "urgCount", and "rstCount" might be considered in
> >       addition to this element.
> > 
> >    o  flowCount
> > 
> >       This Information Element is the number of Flow Records included in
> >       the aggregated flow.
> > 
> > 3.2.3.  Modification Process
> > 
> >    This process modifies the received Flow Records.  This process can
> >    add the new Information Elements, delete included Information
> >    Elements, or modify the value of included Information Elements, as
> >    follows.  If this process modify the original template, it SHOULD
> >    revise the received "flowKeyIndicator".
> > 
> >    Addition of new Information Element
> > 
> >       This function adds specified Information Elements into the
> >       inputted Flow Records.  The values of Information Elements are
> >       extracted by searching some database based on the inputted content
> >       of Flow Records.  The added Information Elements and used
> >       Information Elements are configured according to instructions by
> >       the user to obtain the value.  The method to obtain the value from
> >       some Information Elements is outside the scope of this document.
> > 
> >       The IPFIX Mediator instead of the Original Exporter adds a derived
> >       packet property parameter, which is useful for the traffic
> >       monitoring technique.  Doing that can compensate for the inability
> >       of some Exporters to add a derived packet property parameter.
> >       Hereby, the Collector does not need to recognize the difference
> >       between implementations of routers from several vendors.  For
> >       example, the addition of "bgpNextHop{IPv4|IPv6}Address" and
> >       "bgpCommunity" Information Elements is useful for making a traffic
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 10]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       matrix that covers the whole network domain. "bgpNextHop{IPv4|
> >       IPv6}Address" can indicate the egress router of some network
> >       domain.  In addition, "bgpCommunity" can indicate the same group
> >       of destination or source IP addresses.  This value can be given by
> >       looking for the BGP route database based on the destination or
> >       source IP address.  In addition, "mplsVpnRouteDistinguisher",
> >       which can not be extracted from the core router in MPLS networks,
> >       indicates the customer's identification.  We can monitor the
> >       traffic behavior per customer by adding
> >       "mplsVpnRouteDistinguisher" to the Flow Records.  This value can
> >       be given by looking for the BGP route database based on the
> >       "mplsTopLabelStackSection" and "mplsTopLabel{IPv4|IPv6}Address".
> > 
> >    Deletion of Information Element
> > 
> >       This function deletes specified Information Elements according to
> >       the instructions that are configured by the user, which indicate
> >       whether an Information Element should be removed.  Hiding network
> >       topology information and private information by using this
> >       function is possible.
> > 
> >       In the case of exchanging Flow Records with different network
> >       domains or customers, this function can avoid making a
> >       vulnerability by deleting unnecessary Information Elements.  By
> >       deleting unnecessary Information Elements, this function can hide
> >       the network topology and another customer's information.  In
> >       particular, "ipNextHopIP{v4|v6}Address", "bgpNextHopIP{v4|
> >       v6}Address", and "bgp{Next|Prev}AdjacentAsNumber" correspond to
> >       network topology information.  In addition, MPLS-related
> >       Information Elements, such as "mplsLabelStackSection", that are
> >       useless for customers might be removed in the case of feeding the
> >       Flow Records to VPN customers.
> > 
> >    Modification of the value of Information Element
> > 
> >       This function modifies the value of specified Information Elements
> >       according to instructions configured by the user.
> > 
> >       For example, this function enables us to overwrite private
> >       information with zeros or the maximum value.  In particular, IP
> >       address and port number is sensitive private information.  In the
> >       case of monitoring traffic trends and traffic engineering, these
> >       Information Elements are not essential factors for those purposes.
> >       In that case, modification anonymizes the relevant Information
> >       Elements to prevent a violation of privacy.  If modification can
> >       anonymize some Information Elements, it might need to report which
> >       Information Elements are anonymized.  For example,
> >       "anonymizationIndicator" indicates which Information Elements have
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 11]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       been anonymized as a bitmap, just like the "flowKeyIndicator".
> >       The anonymization method is outside the scope of this document.
> 
> Why would we not just modify the template and remove these Information 
> Elements?

This point has been already discussed in ML.


> > 
> > 3.3.  Exporting Process
> > 
> >    This process forwards Flow Records to the next Collector.  These
> >    processes manage the reporting template and make an IPFIX datagram.
> > 
> >    In addition, this process has the Distribution Function as an option.
> >    If this function is enabled, this process distributes Flow Records
> >    based on Flow content and then exports each classified Flow Record to
> >    each Collector.
> > 
> >    The Exporting Process distributes Flow Records on the basis of the
> >    peering AS, as shown in the following figure.  Each classified Flow
> 
> Peer AS in the incoming data, or on the Exporting side? Is BGP required?
> 
> Surely this would/should be user configurable?

I means this is example. Which field is selected in order to distribute Flow
Records should be configurable.
I will modify next version. It is too short description
 
> >    Record is exported to a dedicated Collector on the basis of the
> >    Peering AS.
> > 
> >      +-------------------------------------------+
> >      | IPFIX Mediator               .----------. |
> >      |                              |Exporting | |
> >      |                              |Process   | |
> >      |   .----------.  .---------.  |          | | PeerAS#100
> >  Flow -->|Collecting|->|Metering |----->/------------> Collector#A
> >  Records |Process   |  |Process  |  |   |      | | PeerAS#200
> >      |   '----------'  '---------'  |   /------------> Collector#B
> >      |                              |   |      | | PeerAS#300
> >      |                              |   /------------> Collector#C
> >      |                              |   |      | | PeerAS#400
> >      |                              |   /------------> Collector#D
> >      |                              |          | |
> >      |                              '----------' |
> >      +-------------------------------------------+
> > 
> >  Figure B: Exporting each classified Flow Record to dedicated Collector.
> > 
> > 3.4.  Storing Process
> > 
> >    This process selects specified Information Elements using the storing
> >    instruction from the inputted Flow Records.  Prior to receiving Flow
> 
> What is the "storing instruction" ?
> 

The Flow Records which are wanted to store by user might not be equal to
received Flow Records. The meaningless fields could be discarded by user.
The storing instruction means the configured information by user.
It indicates fields which should be stored and field which should not be
stored.

I will adds the explanation in next version. And also, I used "storing
instruction" and "storing rule" as same meaning. I will correct it.


> >    Records, this process has instructions that are configured by the
> >    user, which indicate whether each field should be stored or
> >    discarded.  The field modifier indicates "keep" or "discard", which
> >    is similar to the instruction of the aggregation process.  The field
> >    modifier specifies how these Information Elements are treated by the
> >    process.  This field modifier is applied to Information Elements
> >    within Flow Record and IPFIX header, such as "Observation Domain ID"
> >    and "Export time".  This header information MAY be used when IPFIX
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 12]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    datagrams are made of past Flow Records.
> > 
> >    When another node retrieves past Flow Records, we can consider
> 
> How does it retrieve them?
> 

Simply, the specified past Flow Records can be retrieved on the basis of
time period which is given by user. The retrieving mechanism is out of
scope of this document.


> >    several specifications.  One solution is that another node gets a
> >    specified flat file from a Mediator and decodes that flat file by
> >    itself.  Other solutions are that another node sends out the query
> >    command to the IPFIX Mediator through XML-RPC, SNMP, or NETCONF, and
> >    then the IPFIX Mediator exports the specified past Flow Records.
> >    This function is outside the scope of this document.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 13]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 4.  IPFIX Protocol Considerations
> > 
> >    This section describes IPFIX protocol considerations with regard to
> >    IPFIX Mediator.
> > 
> > 4.1.  Export Time Issue
> > 
> >    If the Exporting Process writes the "Export Time" of the IPFIX
> >    message when an IPFIX message leaves, an IPFIX Mediator needs to
> >    compensate for the delta time Information Elements contained in each
> 
> "the" -> "any"
> 
> >    Flow Record.  An IPFIX Proxy SHOULD reuse the "Export Time" of
> 
> "SHOULD" -> "MUST"
> 
Yes. I will correct it.


> >    received IPFIX messages from the Original Exporter.
> > 
> > 4.2.  Observation Domain ID Management
> > 
> >    To comply with the IPFIX protocol the Observation Domain ID value is
> >    RECOMMENDED to be assigned uniquely per IPFIX Mediator.  In addition,
> >    Observation Domain ID SHOULD be 0 when IPFIX Mediator exports
> >    aggregated Flow Records and cannot manage the specific Observation
> >    Domain ID of the Original Exporter.  If an IPFIX Proxy relays an
> >    IPFIX datagram from a transport session to a transport session, IPFIX
> >    Proxy does not need to overwrite the Observation Domain ID with
> >    another value.  If an IPFIX Proxy relays an IPFIX datagram from
> >    multiple transport sessions to a single ransport session, IPFIX Proxy
> >    needs to overwrite the Observation Domain ID.  In that case, IPFIX
> >    Proxy assigns the Observation Domain ID based on received Transport
> >    Session Information and the original Observation Domain ID.  The
> >    renewed Observation Domain ID SHOULD be managed using the received
> >    Transport Session Information and original Observation Domain ID.
> >    This linkage information is available for overwriting the scope field
> >    of the option template.
> > 
> > 4.3.  Template Management
> > 
> >    The template ID of a generated template SHOULD be unique on the basis
> 
> "Template". Please be sure to capitalise IPFIX terminology!
> 
Yes. I will correct it.


> >    of the Observation Domain ID assigned by an IPFIX Mediator.  The
> >    template ID needs to be unique on the basis of IPFIX Mediator when
> >    the Observation Domain ID is 0.  If the IPFIX Mediator overwrites the
> >    received template ID to relay a received template or modified
> >    template, the renewed template ID SHOULD be managed using received
> >    Transport Session Information and received Observation Domain ID.
> >    This linkage information is available for overwriting scope field of
> >    an option template and template handling.  If IPFIX Mediator receives
> >    a "template withdraw message", it SHOULD modify this message to
> >    indicate relevant templates, and send "template withdraw message".
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 14]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 4.4.  Transport Session Management
> > 
> >    Each session of the Collecting Process and Exporting Process should
> >    operate independently.  Even if one session is reset, the status of
> >    the other session is kept current.  However, templates for resetting
> >    collecting session SHOULD be withdrawn for the exporting session.
> > 
> > 4.5.  Option Template Management
> > 
> >    IPFIX Mediator MUST check whether the scope field is applicable, if
> >    received Data Records associated Options templates are exported.  If
> >    an IPFIX Mediator rewrites the Observation Domain ID or template ID,
> >    these values included in scope fields SHOULD be rewritten before
> >    exporting.  Instead of exporting the Options Template Records and
> >    associated Data Records, Information Elements exported using the
> >    Options template Record from the Original Exporter, such as sampling
> >    rate or sampling method, could be merged in a Flow Record in an IPFIX
> >    Mediator.  In that case, IPFIX Mediator MUST modify the relevant
> >    Template Record.  Several sorts of received statistics Options
> >    Template Records and associated Data Records could be exported in
> >    different ways as other templates.  In IPFIX Proxy, the Data Record
> >    associated by statistics Options Template Records can be exported
> >    after merging its counter.  In addition, statistics Options Template
> >    Records and associated Data Records can be exported by indicating the
> >    source of the statistics data as a scope field instead of merging the
> >    counter.  This method is described in Section 6.  The user policy
> >    determines whether IPFIX Mediator and the above methods should export
> >    Option Templates Records and associated Data Records.
> > 
> > 4.6.  Reporting of Exporter Information
> > 
> >    Reporting of Exporter Information, such as Exporter IP address, is
> 
> Surely that's a loss of privacy?

It is depends on the role of IPFIX Mediator.
If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
becomes to grow the vulnerability.
On the other hand, if it is other nodes, such as concentrator, Exporter
IP address is important information for traffic analysis, such as traffic
engineering.

In case of making traffic matrix, Exporter IP address can indicate the
ingress router of network domain.
> 
> >    useful to identify the Original Exporter.  There are various methods
> >    as follows.  An IPFIX Mediator can directly merge Exporter
> >    Information into Flow Records or use Options Templates described in
> >    Section 6.  If an IPFIX Mediator received fields related to the
> >    Exporter information, IPFIX Mediator SHOULD NOT rewrite its own
> >    previous Exporter information.  The IPFIX Mediator can append its own
> >    previous Exporter Information instead of rewriting.  In the
> >    Collecting Process, the order of the Exporter information means the
> >    Original Exporter and the route of IPFIX Mediator.  These methods
> >    defined by user policy determine whether IPFIX Mediator should report
> >    that information has been exported
> 
> Some text seems to be missing here?
> 

Oops, I miss the period. I will correct it.


> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 15]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 5.  Solution Scenarios with IPFIX Mediators
> > 
> > 5.1.  Flexible Aggregation
> > 
> >    An IPFIX Mediator can aggregate Flow Records in the same manner as
> >    that of IPFIX concentrator and reduce the number of Flow Records
> >    received by a traffic collector.
> > 
> >    The following figure indicates a cascade connection of IPFIX
> >    Mediators.  If a Collector measures a traffic matrix to obtain
> >    traffic demand, the Collector needs Flow Records of the whole network
> >    domain, but does not need detailed Flow Records.  In the first step,
> >    a Mediator receives Flow Records from IPFIX Devices and then creates
> 
> "a first level Mediator"
> 
> >    aggregated low-level Flow Records.  For example, this step is prefix
> >    mask aggregation.  Next, the Mediator receives aggregated Flow
> 
> "Next, a second level Mediator"
> 
Yes. I will correct it.


> >    Records and aggregates them further.  For example, the second step is
> >    the aggregation of the BGP next-hop address and exporter address.
> >    After this, the collector receives high-level aggregated Flow Records
> >    and then stores them.  This method enables step-by-step aggregation
> >    of Flow Records without overloading a single node.
> > 
> >    .--------.     .--------.
> >    |IPFIX   |     |IPFIX   |
> >    |router#1|---->|Mediator|---.
> >    |        |     |*1      |   |
> >    '--------'     '--------'   |    .--------.     .---------.
> >                                '--->|IPFIX   |     |Traffic  |
> >    .--------.     .--------.   .--->|Mediator|---->|Collector|
> >    |IPFIX   |     |IPFIX   |   |    |*2      |     |         |
> >    |router#2|---->|Mediator|---'    '--------'     '---------'
> >    |        |     |*1      |
> >    '--------'     '--------'
> > 
> >    Figure C: Flexible Aggregation with cascading IPFIX Mediators.
> > 
> > 5.2.  Distributed Aggregation
> > 
> >    When the network is used globally, the distances between PoPs become
> >    longer, and the maintenance of a dedicated management network is very
> >    expensive.  Therefore, the huge number of Flow Records has burdened
> >    the management networks of global ISPs.  If we place Mediators at
> >    each PoP, the number of Flow Records exported from each PoP can be
> >    reduced.  Mediators can minimize the number of Flow Records exported
> >    to the Collector.  If the Collector needs detailed information, it
> >    can retrieve Flow Records from Mediators that store original Flow
> >    Records.
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 16]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    A management network of a global ISP is shown in the following
> >    figure.  The Mediators are located at each PoP of the network, and
> >    they collect Flow Records from routers in each PoP domain.  The
> >    Mediator reduces the number of Flow Records by aggregating or
> >    filtering, so this system reduces the load of a management network.
> > 
> >                 POP#Asia
> >         .--------.
> >       .--------. |      .---------.
> >     .--------. | |----->|IPFIX    |
> >     |IPFIX   | |------->|Mediator |----.
> >     |router  |---'----->|#1       |    |
> >     |#1      |-'        '---------'    |
> >     '--------'                         |
> >                                        |
> >                 POP#America            |
> >         .--------.                     |
> >       .--------. |      .---------.    |     .---------.
> >     .--------. | |----->|IPFIX    |    '---->|Traffic  |
> >     |IPFIX   | |------->|Mediator |--------->|Collector|
> >     |router  |---'----->|#2       |    .---->|         |
> >     |#4      |-'        '---------'    |     '---------'
> >     '--------'                         |
> >                                        |
> >                 POP#Europe             |
> >         .--------.                     |
> >       .--------. |      .---------.    |
> >     .--------. | |----->|IPFIX    |    |
> >     |IPFIX   | |------->|Mediator |----'
> >     |router  |---'----->|#3       |
> >     |#7      |-'        '---------'
> >     '--------'
> > 
> >    Figure D: Traffic monitoring architecture in global network.
> > 
> > 5.3.  Duplication of Flow Records
> > 
> >    An IPFIX Mediator duplicates Flow Records to achieve redundant
> >    storage or utilizes them for several purposes.  The pair of
> >    Collecting Process and Metering Processes is similar to the pair of
> >    the Observation Point and Metering Process.  The Collecting Process
> >    duplicates Flow records by forwarding them to the multi-Metering
> >    Process.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 17]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    Several departments in an ISP want to use the same traffic
> >    information for each intended purpose.  For example, the network
> >    design department measures the traffic matrix to obtain traffic
> >    demand, and the customer service division uses traffic information
> >    for performing accounting services for each customer while the
> >    network operation center uses traffic information for trouble
> >    shooting analysis.  That case is shown in the following figure.  An
> >    IPFIX Mediator distributes Flow Records to several Collectors that
> >    have the appropriate aggregated granularity.  In addition, when a NOC
> >    conducts troubleshooting, past Flow Records from Mediators can be
> >    retrieved.
> > 
> >                                          Measurement traffic matrix.
> >    .--------.                               .---------.
> >    |IPFIX   |                               |Traffic  |
> >    |router#1|----.                    .---->|Collector|
> >    |        |    |                    |     |#1       |
> >    '--------'    |                    |     '---------'
> >                  |                    |  Using Accounting info.
> >    .--------.    |     .---------.    |     .---------.
> >    |IPFIX   |    '---->|IPFIX    |----'     |Traffic  |
> >    |router#2|--------->|Mediator |--------->|Collector|
> >    |        |    .---->|         |----.     |#2       |
> >    '--------'    |     '---------'    |     '---------'
> >                  |                    |  Using Trouble shooting.
> >    .--------.    |                    |     .---------.
> >    |IPFIX   |    |                    |     |Traffic  |
> >    |router#1|----'                    '---->|Collector|
> >    |        |                               |#3       |
> >    '--------'                               '---------'
> 
> The bottom left router should be "router#3"
> 
Yes. I will correct it.

> > 
> >    Figure E: Duplication of Flow Records for several purposes.
> > 
> > 5.4.  Distribution of Flow Records
> > 
> >    An IPFIX Mediator distributes Flow Records based on Flow Record
> 
> "MAY distribute"
> 
Yes. I will correct it.

> >    content.  This function enables load balancing of Collector and
> >    sorting Flow Records without extra Collector functions.  If the Flow
> >    Records are used as accounting information, this solution is useful.
> 
> It's unclear to me what this means.
> 

Surely, it is too short explanation. For example, if an IPFIX Mediator
distributes Flow Records on the basis of input IF indexes which
indicates customer, measuring total traffic volume by each Collector can
indicate each customer's accounting information.

On careful thought, it is better that this sentence is omitted.

> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 18]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    When we disclose traffic information to each customer, security or
> 
> "we"? -> The mediator, perhaps?
> 
I was confused how to use "we". I mean it is network service provider. 
The Mediator is preferable.

> >    the privacy policy should be considered.  In that case, IPFIX
> >    Mediator hides private information about each customer.  For example,
> >    Mediator distributes traffic information based on RD (Route
> >    Distinguisher), egress IF, peering AS number, or BGP next hop, which
> >    identify the customer.  In the following figure, the IPFIX Mediator
> >    distributes Flow Records based on RD.  The system securely allows
> >    each customer to access only their own records.
> > 
> >    .--------.                               .---------.
> >    |IPFIX   |                               |Traffic  |
> >    |router#1|----.                    .---->|Collector|<===> Customer#A
> >    |        |    |                    |     |#1       |
> >    '--------'    |                    |     '---------'
> >                  |                 RD=100:1
> >                  |     .---------.    |
> >    .--------.    '---->|IPFIX    |----'     .---------.
> >    |IPFIX   |          |Mediator | RD=100:2 |Traffic  |
> >    |router#2|--------->|         |--------->|Collector|<===> Customer#B
> >    |        |          |         |          |#2       |
> >    '--------'    .---->|         |----.     '---------'
> >                  |     '---------'    |
> >                  |                 RD=100:3
> >    .--------.    |                    |     .---------.
> >    |IPFIX   |    |                    |     |Traffic  |
> >    |router#1|----'                    '---->|Collector|<===> Customer#C
> >    |        |                               |#3       |
> >    '--------'                               '---------'
> > 
> >    Figure F: Distribution of Flow Records for each customer.
> > 
> > 5.5.  Extraction of Suspicious Flow
> > 
> >    An IPFIX Mediator performs filtering based on Flow Record content.
> >    If the filter conditions are set depending on the suspicious flow as
> >    follows, the Collector receives the specified suspicious flow and
> >    detects an anomalous flow by simply monitoring the traffic volume of
> >    each suspicious flow.
> > 
> >    o  TCP Flow Records whose "tcpControlBits" value is set to "null"
> > 
> >    o  TCP Flow Records whose "tcpControlBits" value is set to the SYN
> >       bit only and the packet counter is only 1.
> 
> This will always happen for TCP flows of 1 or more packets. It might be 
> suspicious if the count was still 1 after some time.
> 
Yes.

> > 
> >    o  ICMP Flow Records whose length is too long.
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 19]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 6.  Mediator Option Template Presentation
> > 
> >    This section describes Option Templates that are used by IPFIX
> >    Mediators.
> > 
> > 6.1.  Exporter Information Option Template
> > 
> >    Each IPFIX Mediator and final destination Collector needs to know the
> >    Original Exporter and route of IPFIX Mediators.  Therefore, each
> >    IPFIX Mediator informs the next Collector about previous Exporter
> >    information, which is the Exporter Information Option Template that
> >    specified the Original Exporter and the route of the IPFIX Mediator.
> >    The final destination Collector can recognize them by receiving this
> >    template.  This template is composed of the following Information
> >    Elements.
> > 
> >    o  exporter{IPv4|IPv6}Address
> > 
> >    o  collector{IPv4|IPv6}Address
> > 
> >    o  exporterTransportPort
> > 
> >    o  collectorTransportPort
> > 
> >    o  collectorTransportProtocol
> > 
> >    o  observationDomainId
> > 
> >    The Observation Domain ID of the Original Exporter or IPFIX Mediator
> >    is identified by specifying exporter/collector Information Elements,
> >    such as "collector{IPv4|IPv6}Address", "collectorTransportPort",
> >    "collectorTransportProtocol", ,"exporter{IPv4|IPv6}Address",
> >    "exporterTransportPort", and "observationDomainId".  The set of
> >    "observationDomainId" and "templateId" or "observationDomainId" might
> >    be used as a scope field.  Not all Information Elements are
> >    necessary.  For example, the exporter{IPv4|IPv6}Address is necessary
> >    to inform the next Collector the Original Exporter which created Flow
> >    Records.  If the IPFIX Mediator receives this template, it SHOULD not
> >    overwrite each field.  The IPFIX Mediator appends its own previous
> >    Exporter information onto received Data Records specified by the
> >    Exporter Option Template and sends that information to the Collector.
> >    In this manner, the route is maintained until the final destination
> >    Collector.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 20]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >    The following example describes the cascade connection of IPFIX
> >    Mediators.  Each Mediator informs the next Collector about previous
> >    Exporter information.
> > 
> >           Session#a            Session#b            Session#c
> >    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
> >    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
> >    SrcPort:10       DstPort:20           DstPort:40
> >    ODID:10          SrcPort:30           SrcPort:50
> >                     ODID:0               ODID:0
> > 
> >    Figure G: Cascade connection of IPFIX Mediators.
> > 
> >    Mediator#1 or Mediator#2 sends a Data Record specified by the
> >    Exporter Option Template.  The Data records are shown in Session#b or
> >    Session#c, as follows.
> > 
> >    Session#b Data Record:
> >       Field Count = 7
> >       Scope Count = 1
> >       templateId = XXX
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> 
> Could you use real-world values in the examples here and below?
> 
> P.
> 
Is it preferable using private address? 
Surely, the destination port number should be 4739.

> > 
> >    Session#c Data Record:
> >       Field Count = 13
> >       Scope Count = 1
> >       templateId = XXX
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> >       exporterIPv4Address = 2.2.2.2
> >       collectorIPv4Address = 3.3.3.3
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 30
> >       collectorTransportPort = 40
> >       observationDomainId = 0
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 21]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 6.2.  Usage of Scope Field
> > 
> >    An IPFIX Mediator needs to send forward a Options Template Records
> >    and associated Data Records from the Original Exporter.  However,
> >    IPFIX Mediator can not export an original Option Template Records and
> >    associated Data Records without modification because changing a
> >    session from an Exporting Process to a Collecting Process causes the
> >    scope fields to become a useless value.  When an IPFIX Mediator
> >    relays the Options Template Records that included Observation Domain
> >    ID as a scope field and associated Data Records, an IPFIX Mediator
> >    uses the Exporter Information Option Template.  The Options Template
> >    Records that were created from an Original Exporter can use the
> >    entire fields of the Exporter Information Option template as multiple
> >    scope fields.  The Options Template Records that were created from
> >    anIPFIX Mediator can uses the some fields of the Exporter Information
> >    Option template as multiple scope fields.  An IPFIX Mediator needs to
> >    modify the associated Data Records according to the modified Options
> >    Template Record.  However, if each node uses another field except for
> >    the Observation Domain ID as the scope, the scope field should be
> >    considered on a case-by-case basis.
> > 
> >    The following example describes the cascade connection of IPFIX
> >    Mediators.  Router#1 and Mediator#1 export the Metering Process
> >    Statistics Option Template.
> > 
> > 
> >           Session#a            Session#b            Session#c
> >    Router --------> Mediator#1 --------> Mediator#2 -------->Collector
> >    IP:1.1.1.1       IP:2.2.2.2           IP:3.3.3.3
> >    SrcPort:10       DstPort:20           DstPort:40
> >    ODID:10          SrcPort:30           SrcPort:50
> >                     ODID:0               ODID:0
> > 
> >    Figure H: Cascade connection of IPFIX Mediators.
> > 
> >    Mediator#2 exports each Option Template and its Data Record with a
> >    suitable scope.
> > 
> >    Session#c Metering Process Statistics Data Records from the Original
> >    Exporter:
> >       Field Count = 15
> >       Scope Count = 12
> >       exporterIPv4Address = 1.1.1.1
> >       collectorIPv4Address = 2.2.2.2
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 10
> >       collectorTransportPort = 20
> >       observationDomainId = 10
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 22]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> >       exporterIPv4Address = 2.2.2.2
> >       collectorIPv4Address = 3.3.3.3
> >       collectorTransportProtocol = 16
> >       exporterTransportPort = 30
> >       collectorTransportPort = 40
> >       observationDomainId = 0
> >       exportedMessageTotalCount
> >       exportedFlowTotalCount
> >       exportedOctetTotalCount
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 23]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 7.  Security Considerations
> > 
> >    The IPFIX concentrator uses the IPFIX protocol.  Security
> >    considerations about flow information are described in
> >    [I-D.ietf-ipfix-protocol].
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 24]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 8.  IANA Considerations
> > 
> >    This document has no actions for IANA.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 25]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > 9.  References
> > 
> > 9.1.  Normative References
> > 
> >    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
> >               Requirement Levels", BCP 14, RFC 2119, March 1997.
> > 
> > 9.2.  Informative References
> > 
> >    [I-D.dressler-ipfix-aggregation]
> >               Dressler, F., Sommer, C., and G. Munz, "IPFIX
> >               Aggregation", draft-dressler-ipfix-aggregation-03.txt
> >               (work in progress) , June 2006.
> > 
> >    [I-D.ietf-ipfix-architecture]
> >               Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,
> >               "Architecture for IP Flow Information Export",
> >               draft-ietf-ipfix-architecture-12.txt(work in progress) ,
> >               September 2006.
> > 
> >    [I-D.ietf-ipfix-info]
> >               Quittek, J., Bryant, S., Claise, B., and J. Meyer,
> >               "Information Model for IP Flow Information Export",
> >               draft-ietf-ipfix-info-13.txt(work in progress) ,
> >               June 2006.
> > 
> >    [I-D.ietf-ipfix-protocol]
> >               Claise, B., "IPFIX Protocol Specification",
> >               draft-ietf-ipfix-protocol-23 (work in progress) ,
> >               October 2006.
> > 
> >    [I-D.ietf-psamp-framework]
> >               Duffield, N., "A Framework for Packet Selection and
> >               Reporting", draft-ietf-psamp-framework-10.txt ,
> >               January 2005.
> > 
> >    [I-D.ietf-psamp-sample-tech]
> >               Zseby, T., Molina, M., Duffield, N., Niccolini, S., and F.
> >               Raspall, "Sampling and Filtering Techniques for IP Packet
> >               Selection", draft-ietf-psamp-sample-tech-07.txt ,
> >               July 2005.
> > 
> >    [RFC3917]  Quittek, J., Zseby, T., Claise, B., and S. Zander,
> >               "Requirements for IP Flow Information Export(IPFIX)",
> >               October 2004.
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 26]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Authors' Addresses
> > 
> >    Atsushi Kobayashi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-3978
> >    Email: akoba@nttv6.net
> > 
> > 
> >    Keisuke Ishibashi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-3407
> >    Email: ishibashi.keisuke@lab.ntt.co.jp
> > 
> > 
> >    Kondoh Tsuyoshi
> >    NTT Information Sharing Platform Laboratories
> >    3-9-11 Midori-cho
> >    Musashino-shi, Tokyo  180-8585
> >    Japan
> > 
> >    Phone: +81-422-59-2419
> >    Email: kondoh.tsuyoshi@lab.ntt.co.jp
> > 
> > 
> >    Daisuke Matsubara
> >    Hitachi, Ltd., Central Reseach Laboratory
> >    1-280 Higashi-koigakubo
> >    Kokubunji-shi, Tokyo  185-8601
> >    Japan
> > 
> >    Phone: +81-42-323-1111
> >    Email: d-matuba@crl.hitachi.co.jp
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 27]
> > 
> > Internet-Draft     Reference Model for IPFIX Mediators         June 2007
> > 
> > 
> > Full Copyright Statement
> > 
> >    Copyright (C) The IETF Trust (2007).
> > 
> >    This document is subject to the rights, licenses and restrictions
> >    contained in BCP 78, and except as set forth therein, the authors
> >    retain all their rights.
> > 
> >    This document and the information contained herein are provided on an
> >    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
> >    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
> >    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
> >    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
> >    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
> >    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
> > 
> > 
> > Intellectual Property
> > 
> >    The IETF takes no position regarding the validity or scope of any
> >    Intellectual Property Rights or other rights that might be claimed to
> >    pertain to the implementation or use of the technology described in
> >    this document or the extent to which any license under such rights
> >    might or might not be available; nor does it represent that it has
> >    made any independent effort to identify any such rights.  Information
> >    on the procedures with respect to rights in RFC documents can be
> >    found in BCP 78 and BCP 79.
> > 
> >    Copies of IPR disclosures made to the IETF Secretariat and any
> >    assurances of licenses to be made available, or the result of an
> >    attempt made to obtain a general license or permission for the use of
> >    such proprietary rights by implementers or users of this
> >    specification can be obtained from the IETF on-line IPR repository at
> >    http://www.ietf.org/ipr.
> > 
> >    The IETF invites any interested party to bring to its attention any
> >    copyrights, patents or patent applications, or other proprietary
> >    rights that may cover technology that may be required to implement
> >    this standard.  Please address the information to the IETF at
> >    ietf-ipr@ietf.org.
> > 
> > 
> > Acknowledgment
> > 
> >    Funding for the RFC Editor function is provided by the IETF
> >    Administrative Support Activity (IASA).
> > 
> > 
> > 
> > 
> > 
> > Kobayashi, et al.       Expires December 25, 2007              [Page 28]
> > 
> 
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From hagathiumsatanusbut@athiumsatanus.net Sat Jul 28 17:44:21 2007
Return-path: <hagathiumsatanusbut@athiumsatanus.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IEu5F-0007NC-Ou; Sat, 28 Jul 2007 17:44:21 -0400
Received: from chello089078187082.chello.pl ([89.78.187.82])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IEu5F-0008VR-7b; Sat, 28 Jul 2007 17:44:21 -0400
Received: from [89.78.187.82] by mail-incoming2.gate.com; Sat, 28 Jul 2007 21:44:35 -0100
Date:	Sat, 28 Jul 2007 21:44:35 -0100
From:	"Stewart Sykes" <hagathiumsatanusbut@athiumsatanus.net>
X-Mailer: The Bat! (v2.12.00) Business
Reply-To: hagathiumsatanusbut@athiumsatanus.net
X-Priority: 3 (Normal)
Message-ID: <435346962.81825117454261@athiumsatanus.net>
To: idmr-archive@lists.ietf.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------71254096ECF8B6"
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

------------71254096ECF8B6
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

LegalRX drug store presents all preparations you feel necessity in in order to recover your health with a little cost. 
We work through the whole world with clients from Europe, America and Asia. 
At present time you don't have to seek out drug-store at your region.
We certainly deliver medicinal preparations of the best quality world-wide.
Visit our site to acquire preparations that you immediately demand direct to your location. 
http://onface.cn/ 

We are endorsed by VeriSign and VISA then we ensure secure & dependable purchasing.

------------71254096ECF8B6
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRX</em></font> drug store presents all preparations you feel necessity in in order to recover your health with a little cost. <br>
We work through the whole world with clients from Europe, America and Asia. <br>
At present time you don't have to seek out drug-store at your region.<br>
We certainly deliver medicinal preparations of the best quality world-wide.
<br>
<br>
<a href="http://onface.cn/" target="_blank"><em>Visit our site to acquire preparations that you immediately demand direct to your location.</em></a></b> 
<br>
<font color="#D9EDFF">http://onface.cn/</font> 

<br><b>We are endorsed by <font color="#FF0000"><em>VeriSign</em></font> and <font color="#FF0000"><em>VISA</em></font> then we ensure secure & dependable purchasing.
</b>

</BODY></HTML>
------------71254096ECF8B6--




From ipfix-bounces@ietf.org Sun Jul 29 06:34:39 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IF66X-0006Ym-BI; Sun, 29 Jul 2007 06:34:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IF66V-0006Yg-Ns
	for ipfix@ietf.org; Sun, 29 Jul 2007 06:34:27 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IF66U-0005Iu-9d
	for ipfix@ietf.org; Sun, 29 Jul 2007 06:34:27 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by sj-iport-3.cisco.com with ESMTP; 29 Jul 2007 03:34:24 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPcJrEaQ/uCK/2dsb2JhbAA
X-IronPort-AV: i="4.19,195,1183359600"; 
	d="scan'208"; a="508123596:sNHT34757816"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6TAYNQg003629; 
	Sun, 29 Jul 2007 12:34:23 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6TAYMkt009167; 
	Sun, 29 Jul 2007 10:34:23 GMT
Received: from [10.61.65.33] (ams3-vpn-dhcp289.cisco.com [10.61.65.33])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA24484;
	Sun, 29 Jul 2007 11:34:21 +0100 (BST)
Message-ID: <46AC6D38.4010806@cisco.com>
Date: Sun, 29 Jul 2007 11:34:32 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
References: <46A7D10F.3050509@cisco.com> <20070729030242.485A.AKOBA@nttv6.net>
In-Reply-To: <20070729030242.485A.AKOBA@nttv6.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=11090; t=1185705263;
	x=1186569263; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20Review=3A=20draft-kobayashi-ipfix-mediator-model-00
	|Sender:=20; bh=jFHe1eEqQJdjSGYtAnV3Vt6tpBpdUEc8Z3FFQm9QybA=;
	b=qq7SZLETXbeuURCEYlCz33JJiF263ZibdGO3kFzKpCq16UqK6oJc1Bxf+8314IU71BZyOgSk
	8wv6MjyvUWUApAWxbJQ5GBRdz4ltAoeGVuIa43q3iHyzFmtohc5M4oVj;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Here with a few replies to some of your points. I was happy with your 
replies to all the other points, so I snipped out all that text for brevity.


>>>    handling the Flow Records of each function.  In addition, this
>>>    describes the model of the solution scenario using IPFIX Mediator.
>>
>> It's unclear what this last line means.
> 
> "this" indicates this draft.
> This document describes the model of the solution scenario using IPFIX Mediator
> which refer to chapter 5. 

"Solution" to what? First there would have to be a problem to solve.


>> Also, what are "renewed Flow Records"?
> 
> This part is described about Flow Mediation.
> 
> I means that the "renewed Flow Records" is modified Flow Records or
> aggregated Flow Records.
> 
> Modification of Flow Records means that some fields are added and deleted,
> and whose value are modified.

That's two different kinds of modification:

1. changing the value of the fields
2. changing the template and record structure (adding / removing fields)

It would be good to make this clear - and indicate when each would be done.


>>>    generated and distributed to an appropriate Collector or traffic
>>>    analyzer in accordance with flow content.
>>
>> Must the mediator understand the content? eg, what about Enterprise 
>> Specific elements?
> 
> Mediator doesn't need to understand all content, as semantic. After decoding
> by the collecting process, Flow Records are distributed in accordance
> with specified elements contents, such as input IF indexes or Peering AS.

If the mediator doesn't understand the content, then it cannot do this. 
Or at least, not do it very well.

eg, if it sees that a field is one octet, it may choose to distribute to 
four collectors as follows:

0x00 - 0x3F -> Collector 1
0x40 - 0x7F -> Collector 2
0x80 - 0xBF -> Collector 3
0xC0 - 0xFF -> Collector 4

However, the octet may only contain 6 bits of information (ie, 0x00 - 
0x3F) so all the traffic will go to Collector 1.

Or the field may be a counter - so traffic will be divided across the 
collectors, depending how much was counted. That doesn't seem to make a 
lot of sense (except perhaps, a special collector to analyse extra-small 
or extra-large flows).


> In this case, Mediator doesn't need to understand other field contents.
> In the distribution of Flow Records, Some fields which should be understood
> are restricted.

You mean, distribution can only be made according to some well 
understood fields?


>>>       Firewall and an IPFIX concentrator are one node of IPFIX
>>>       Mediators.
>>
>> This last line is unclear.
> 
> In next version, I will add the description about what is IPFIX Mediator.
> I means that IPFIX Mediator is generic name of the several nodes, such as
> the IPFIX proxy, IPFIX firewall and IPFIX concentrator.

In another mail, I had suggested that since this draft is already quite 
complex, it might be better to divide into seperate drafts covering 
different functions. eg, from the titles above, you could have three 
drafts describing proxy, firewall and concentrator. You would still be 
able to made a mediator product which complies with all three of these 
drafts together.


>> How does information get *out* of the Storing Process?
> 
> This part is out of scope of this document.
> As solution, several solution can be considered.
> 
> In case of our system, other node, such as analyzer, submitted the query
> that contains the specified time slot as XML, IPFIX Mediator replies this
> query by replaying the NetFlow packets. 

OK. I think it would be good to add a small note indicating that data 
may be retrieved from the Storing Process in different ways which are 
outside the scope of the current work.



>>>    Observation Domain ID
>>>
>>>       An IPFIX Mediator doesn't host the Observation Point and
>>>       Observation Domain.  Though, the Observation Domain ID in IPFIX
>>>       header sent by IPFIX Mediator also indicates the largest set of
>>>       Observation Points in the Original Exporter, but this value does
>>>       not indicate the physical entity of the Original Exporter.  If
>>>       inputted Flow Records are aggregated in the Metering Process, the
>>>       Observation Domain ID value in IPFIX header SHOULD be 0.
>> I think only if the mediator is spoofing the original source exorter. 
>> Arguably a whole new set of Observation Domain values applies on the 
>> mediation device.
> 
> This part need a discussion with IPFIX members.
> If IPFIX Proxy handles one exporting session and one collecting session,
> simply IPFIX Proxy doesn't need to change the observation domain values.

I agree, because it's a transparent device, ie it's invisible to the 
collector.


> I think, If IPFIX Proxy handles multiple session on the both sides,
> IPFIX Proxy needs to assign the new Observation Domain values.

I think it would be possible for a device to receive information from 
other devices, process the information and re-report the information as 
if it had been observed locally.

Viewed another way, we could have three IPFIX devices (A, B, C) 
reporting to a fourth device (D) as so:

	+----------+    +----------+    +----------+
	| device A |    | device B |    | device C |
	+----------+    +----------+    +----------+
	      |               |               |
	      +---------------+---------------+
	                      |
	                +----------+
	                | device D |
	                +----------+


I believe device D could report a new observation domain as so:


	+----------------------------------------------+
	|                                              |
	| +----------+    +----------+    +----------+ |
	| | device A |    | device B |    | device C | |
	| +----------+    +----------+    +----------+ |
	|                                              |
	|                                     device D |
	+----------------------------------------------+


In this case, device D would use its own Observation Domain IDs and not 
have to report OD ID 0.


>> I think any of the metering sub-processes should be able to send data to 
>> the storing process. Also, the Exporting process may send data there too 
>> (consider Brian's file draft). Finally, there should be a route *out* of 
>> the storing process - either to the outside, and/or to the Metering 
>> Process, and/or to the Exporting Process.
>>
> 
> Good idea. Roughly, I can image following figure.
> 
>       +--------------------------------------------------------------+
>       |                        IPFIX Mediator                        |
>       | .----------.                                     .---------. |
>       | |          |  .-------------------------------.  |         | |
>       | |Collecting|  |        Metering Process       |  |Exporting| |
>       | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
>       | |          |--->sub    |-->sub    |->|sub    |-->|         | |
>     IPFIX          |  ||process|  |process|  |process||  |         IPFIX
>     --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
>       | |          || |'-------'  '-------'  '-------'|  |         | |
>       | |          || '----|----------|----------|----'  |         | |
>       | |          ||      |          |          |       |         | |
>       | |          ||   .--\/---------\/---------\/--.   |         | |
>       | |          |'---|       Storing Process      |<--|         | |
>       | |          |--->|                            |-->|         | |
>       | |          |    '----------------------------'   |         | |
>       | |          |------------------------------------>|         | |
>       | '----------'                                     '---------' |
>       +--------------------------------------------------------------+

Yes, this is exactly what I had in mind.


>>> 3.2.2.  Aggregation Process
>>
>> As a general question, is it valid to aggregate fields which were not 
>> originally key fields?
> 
> I think that the aggregate key field does not depend on the original key
> fields.

For sure it's possible - even if statistically it might not make any sense.


>>> 4.6.  Reporting of Exporter Information
>>>
>>>    Reporting of Exporter Information, such as Exporter IP address, is
>> Surely that's a loss of privacy?
> 
> It is depends on the role of IPFIX Mediator.
> If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
> becomes to grow the vulnerability.
> On the other hand, if it is other nodes, such as concentrator, Exporter
> IP address is important information for traffic analysis, such as traffic
> engineering.
> 
> In case of making traffic matrix, Exporter IP address can indicate the
> ingress router of network domain.

Very true. So it's worth indicating this in the draft.



>>> 5.4.  Distribution of Flow Records
>>>
>>>    An IPFIX Mediator distributes Flow Records based on Flow Record
>>>    content.  This function enables load balancing of Collector and
>>>    sorting Flow Records without extra Collector functions.  If the Flow
>>>    Records are used as accounting information, this solution is useful.
>>
>> It's unclear to me what this means.
> 
> Surely, it is too short explanation. For example, if an IPFIX Mediator
> distributes Flow Records on the basis of input IF indexes which
> indicates customer, measuring total traffic volume by each Collector can
> indicate each customer's accounting information.

I see how this could work if the mediator knows which interface connects 
to which customer or it's able to tell the collector by some means.

> On careful thought, it is better that this sentence is omitted.

Oh?


>>>    When we disclose traffic information to each customer, security or
>>
>> "we"? -> The mediator, perhaps?
>
> I was confused how to use "we". I mean it is network service provider. 
> The Mediator is preferable.

Sometimes people write "I" or "we" instead of the device, eg "I will 
export" -> no, you personally won't export anything. Your device will 
export...


>>>    Session#b Data Record:
>>>       Field Count = 7
>>>       Scope Count = 1
>>>       templateId = XXX
>>>       exporterIPv4Address = 1.1.1.1
>>>       collectorIPv4Address = 2.2.2.2
>>>       collectorTransportProtocol = 16
>>>       exporterTransportPort = 10
>>>       collectorTransportPort = 20
>>>       observationDomainId = 10
>>
>> Could you use real-world values in the examples here and below?
>
> Is it preferable using private address?

You could use 10. or 192. addresses.

> Surely, the destination port number should be 4739.

Exactly. And also real looking exporterTransportPort, 
observationDomainId and so on.

Thanks.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Sun Jul 29 06:34:39 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IF66X-0006Ym-BI; Sun, 29 Jul 2007 06:34:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IF66V-0006Yg-Ns
	for ipfix@ietf.org; Sun, 29 Jul 2007 06:34:27 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IF66U-0005Iu-9d
	for ipfix@ietf.org; Sun, 29 Jul 2007 06:34:27 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by sj-iport-3.cisco.com with ESMTP; 29 Jul 2007 03:34:24 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPcJrEaQ/uCK/2dsb2JhbAA
X-IronPort-AV: i="4.19,195,1183359600"; 
	d="scan'208"; a="508123596:sNHT34757816"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6TAYNQg003629; 
	Sun, 29 Jul 2007 12:34:23 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6TAYMkt009167; 
	Sun, 29 Jul 2007 10:34:23 GMT
Received: from [10.61.65.33] (ams3-vpn-dhcp289.cisco.com [10.61.65.33])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id LAA24484;
	Sun, 29 Jul 2007 11:34:21 +0100 (BST)
Message-ID: <46AC6D38.4010806@cisco.com>
Date: Sun, 29 Jul 2007 11:34:32 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB;
	rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
References: <46A7D10F.3050509@cisco.com> <20070729030242.485A.AKOBA@nttv6.net>
In-Reply-To: <20070729030242.485A.AKOBA@nttv6.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=11090; t=1185705263;
	x=1186569263; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20Review=3A=20draft-kobayashi-ipfix-mediator-model-00
	|Sender:=20; bh=jFHe1eEqQJdjSGYtAnV3Vt6tpBpdUEc8Z3FFQm9QybA=;
	b=qq7SZLETXbeuURCEYlCz33JJiF263ZibdGO3kFzKpCq16UqK6oJc1Bxf+8314IU71BZyOgSk
	8wv6MjyvUWUApAWxbJQ5GBRdz4ltAoeGVuIa43q3iHyzFmtohc5M4oVj;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,

Here with a few replies to some of your points. I was happy with your 
replies to all the other points, so I snipped out all that text for brevity.


>>>    handling the Flow Records of each function.  In addition, this
>>>    describes the model of the solution scenario using IPFIX Mediator.
>>
>> It's unclear what this last line means.
> 
> "this" indicates this draft.
> This document describes the model of the solution scenario using IPFIX Mediator
> which refer to chapter 5. 

"Solution" to what? First there would have to be a problem to solve.


>> Also, what are "renewed Flow Records"?
> 
> This part is described about Flow Mediation.
> 
> I means that the "renewed Flow Records" is modified Flow Records or
> aggregated Flow Records.
> 
> Modification of Flow Records means that some fields are added and deleted,
> and whose value are modified.

That's two different kinds of modification:

1. changing the value of the fields
2. changing the template and record structure (adding / removing fields)

It would be good to make this clear - and indicate when each would be done.


>>>    generated and distributed to an appropriate Collector or traffic
>>>    analyzer in accordance with flow content.
>>
>> Must the mediator understand the content? eg, what about Enterprise 
>> Specific elements?
> 
> Mediator doesn't need to understand all content, as semantic. After decoding
> by the collecting process, Flow Records are distributed in accordance
> with specified elements contents, such as input IF indexes or Peering AS.

If the mediator doesn't understand the content, then it cannot do this. 
Or at least, not do it very well.

eg, if it sees that a field is one octet, it may choose to distribute to 
four collectors as follows:

0x00 - 0x3F -> Collector 1
0x40 - 0x7F -> Collector 2
0x80 - 0xBF -> Collector 3
0xC0 - 0xFF -> Collector 4

However, the octet may only contain 6 bits of information (ie, 0x00 - 
0x3F) so all the traffic will go to Collector 1.

Or the field may be a counter - so traffic will be divided across the 
collectors, depending how much was counted. That doesn't seem to make a 
lot of sense (except perhaps, a special collector to analyse extra-small 
or extra-large flows).


> In this case, Mediator doesn't need to understand other field contents.
> In the distribution of Flow Records, Some fields which should be understood
> are restricted.

You mean, distribution can only be made according to some well 
understood fields?


>>>       Firewall and an IPFIX concentrator are one node of IPFIX
>>>       Mediators.
>>
>> This last line is unclear.
> 
> In next version, I will add the description about what is IPFIX Mediator.
> I means that IPFIX Mediator is generic name of the several nodes, such as
> the IPFIX proxy, IPFIX firewall and IPFIX concentrator.

In another mail, I had suggested that since this draft is already quite 
complex, it might be better to divide into seperate drafts covering 
different functions. eg, from the titles above, you could have three 
drafts describing proxy, firewall and concentrator. You would still be 
able to made a mediator product which complies with all three of these 
drafts together.


>> How does information get *out* of the Storing Process?
> 
> This part is out of scope of this document.
> As solution, several solution can be considered.
> 
> In case of our system, other node, such as analyzer, submitted the query
> that contains the specified time slot as XML, IPFIX Mediator replies this
> query by replaying the NetFlow packets. 

OK. I think it would be good to add a small note indicating that data 
may be retrieved from the Storing Process in different ways which are 
outside the scope of the current work.



>>>    Observation Domain ID
>>>
>>>       An IPFIX Mediator doesn't host the Observation Point and
>>>       Observation Domain.  Though, the Observation Domain ID in IPFIX
>>>       header sent by IPFIX Mediator also indicates the largest set of
>>>       Observation Points in the Original Exporter, but this value does
>>>       not indicate the physical entity of the Original Exporter.  If
>>>       inputted Flow Records are aggregated in the Metering Process, the
>>>       Observation Domain ID value in IPFIX header SHOULD be 0.
>> I think only if the mediator is spoofing the original source exorter. 
>> Arguably a whole new set of Observation Domain values applies on the 
>> mediation device.
> 
> This part need a discussion with IPFIX members.
> If IPFIX Proxy handles one exporting session and one collecting session,
> simply IPFIX Proxy doesn't need to change the observation domain values.

I agree, because it's a transparent device, ie it's invisible to the 
collector.


> I think, If IPFIX Proxy handles multiple session on the both sides,
> IPFIX Proxy needs to assign the new Observation Domain values.

I think it would be possible for a device to receive information from 
other devices, process the information and re-report the information as 
if it had been observed locally.

Viewed another way, we could have three IPFIX devices (A, B, C) 
reporting to a fourth device (D) as so:

	+----------+    +----------+    +----------+
	| device A |    | device B |    | device C |
	+----------+    +----------+    +----------+
	      |               |               |
	      +---------------+---------------+
	                      |
	                +----------+
	                | device D |
	                +----------+


I believe device D could report a new observation domain as so:


	+----------------------------------------------+
	|                                              |
	| +----------+    +----------+    +----------+ |
	| | device A |    | device B |    | device C | |
	| +----------+    +----------+    +----------+ |
	|                                              |
	|                                     device D |
	+----------------------------------------------+


In this case, device D would use its own Observation Domain IDs and not 
have to report OD ID 0.


>> I think any of the metering sub-processes should be able to send data to 
>> the storing process. Also, the Exporting process may send data there too 
>> (consider Brian's file draft). Finally, there should be a route *out* of 
>> the storing process - either to the outside, and/or to the Metering 
>> Process, and/or to the Exporting Process.
>>
> 
> Good idea. Roughly, I can image following figure.
> 
>       +--------------------------------------------------------------+
>       |                        IPFIX Mediator                        |
>       | .----------.                                     .---------. |
>       | |          |  .-------------------------------.  |         | |
>       | |Collecting|  |        Metering Process       |  |Exporting| |
>       | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
>       | |          |--->sub    |-->sub    |->|sub    |-->|         | |
>     IPFIX          |  ||process|  |process|  |process||  |         IPFIX
>     --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
>       | |          || |'-------'  '-------'  '-------'|  |         | |
>       | |          || '----|----------|----------|----'  |         | |
>       | |          ||      |          |          |       |         | |
>       | |          ||   .--\/---------\/---------\/--.   |         | |
>       | |          |'---|       Storing Process      |<--|         | |
>       | |          |--->|                            |-->|         | |
>       | |          |    '----------------------------'   |         | |
>       | |          |------------------------------------>|         | |
>       | '----------'                                     '---------' |
>       +--------------------------------------------------------------+

Yes, this is exactly what I had in mind.


>>> 3.2.2.  Aggregation Process
>>
>> As a general question, is it valid to aggregate fields which were not 
>> originally key fields?
> 
> I think that the aggregate key field does not depend on the original key
> fields.

For sure it's possible - even if statistically it might not make any sense.


>>> 4.6.  Reporting of Exporter Information
>>>
>>>    Reporting of Exporter Information, such as Exporter IP address, is
>> Surely that's a loss of privacy?
> 
> It is depends on the role of IPFIX Mediator.
> If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
> becomes to grow the vulnerability.
> On the other hand, if it is other nodes, such as concentrator, Exporter
> IP address is important information for traffic analysis, such as traffic
> engineering.
> 
> In case of making traffic matrix, Exporter IP address can indicate the
> ingress router of network domain.

Very true. So it's worth indicating this in the draft.



>>> 5.4.  Distribution of Flow Records
>>>
>>>    An IPFIX Mediator distributes Flow Records based on Flow Record
>>>    content.  This function enables load balancing of Collector and
>>>    sorting Flow Records without extra Collector functions.  If the Flow
>>>    Records are used as accounting information, this solution is useful.
>>
>> It's unclear to me what this means.
> 
> Surely, it is too short explanation. For example, if an IPFIX Mediator
> distributes Flow Records on the basis of input IF indexes which
> indicates customer, measuring total traffic volume by each Collector can
> indicate each customer's accounting information.

I see how this could work if the mediator knows which interface connects 
to which customer or it's able to tell the collector by some means.

> On careful thought, it is better that this sentence is omitted.

Oh?


>>>    When we disclose traffic information to each customer, security or
>>
>> "we"? -> The mediator, perhaps?
>
> I was confused how to use "we". I mean it is network service provider. 
> The Mediator is preferable.

Sometimes people write "I" or "we" instead of the device, eg "I will 
export" -> no, you personally won't export anything. Your device will 
export...


>>>    Session#b Data Record:
>>>       Field Count = 7
>>>       Scope Count = 1
>>>       templateId = XXX
>>>       exporterIPv4Address = 1.1.1.1
>>>       collectorIPv4Address = 2.2.2.2
>>>       collectorTransportProtocol = 16
>>>       exporterTransportPort = 10
>>>       collectorTransportPort = 20
>>>       observationDomainId = 10
>>
>> Could you use real-world values in the examples here and below?
>
> Is it preferable using private address?

You could use 10. or 192. addresses.

> Surely, the destination port number should be 4739.

Exactly. And also real looking exporterTransportPort, 
observationDomainId and so on.

Thanks.
-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From sogavantgardeonlineboh@avantgardeonline.com Sun Jul 29 16:06:21 2007
Return-path: <sogavantgardeonlineboh@avantgardeonline.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFF1w-0000et-QT; Sun, 29 Jul 2007 16:06:20 -0400
Received: from [81.214.112.161] (helo=dsl.dynamic81214112161.ttnet.net.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IFF1w-0004D2-53; Sun, 29 Jul 2007 16:06:20 -0400
Received: from [81.214.112.161] by mail.avantgardeonline.com; Sun, 29 Jul 2007 20:06:18 -0200
Date:	Sun, 29 Jul 2007 20:06:18 -0200
From:	"Tania Little" <sogavantgardeonlineboh@avantgardeonline.com>
X-Mailer: The Bat! (v3.62.14) Educational
Reply-To: sogavantgardeonlineboh@avantgardeonline.com
X-Priority: 3 (Normal)
Message-ID: <154465438.16329435494109@avantgardeonline.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------FB2C6E7A525250"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

------------FB2C6E7A525250
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hello there!!! 
Matchless proposal for you Our Dear Client!!!
Only at these five days for our clients incredible offer!!! 
On all medications you need!!!   
Fill in your life with colours of mirth!!!  
http://verywatch.cn/ 

Sincerely yours, 
Online association of pharmaceutists
------------FB2C6E7A525250
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Hello there!!! </em></font><br>
Matchless proposal for you <font color="#FF0000"><em>Our Dear Client!!!</em></font><br>
Only at these <font color="#FF0000"><em>five days</em></font> for our clients incredible offer!!! <br>
On all medications you need!!! </strong> <strong><br><br> 
<a href="http://verywatch.cn/" target="_blank"><em>Fill in your life with colours of mirth!!! </em></a></strong> 
<font color="#D9EDFF">http://verywatch.cn/</font><br><br> 

<strong>Sincerely yours,<br> 
<em>Online association of pharmaceutists</em></strong></p>

</BODY></HTML>
------------FB2C6E7A525250--




From nogbaanafiw@baana.org Mon Jul 30 05:57:03 2007
Return-path: <nogbaanafiw@baana.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFRzr-0004FT-42; Mon, 30 Jul 2007 05:57:03 -0400
Received: from [88.251.240.246] (helo=[88.251.240.246])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IFRzm-00072I-R5; Mon, 30 Jul 2007 05:57:00 -0400
Received: from [88.251.240.246] by ASPMX.L.GOOGLE.COM; Mon, 30 Jul 2007 09:56:59 -0200
Date:	Mon, 30 Jul 2007 09:56:59 -0200
From:	"Lee Irwin" <nogbaanafiw@baana.org>
X-Mailer: The Bat! (v2.00) Personal
Reply-To: nogbaanafiw@baana.org
X-Priority: 3 (Normal)
Message-ID: <352375217.77172558038732@baana.org>
To: idmr-archive@lists.ietf.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------56EA9888FB256E"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

------------56EA9888FB256E
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

LegalRX drug store introduce all drugs you have a need in to recover your health at low cost. 
We work across the world with clients from Europe, America, and Asia. 
Now you got no need to search for drug store at your local area.
We necessarily bring high quality drugs to all parts of the planet.
Come to our site to acquire pharmas that you immediately need straight to your abode. 
http://shoulderbell.cn/ 

We are verified by VeriSign & VISA so we provide effective and dependable buying.

------------56EA9888FB256E
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRX</em></font> drug store introduce all drugs you have a need in to recover your health at low cost. <br>
We work across the world with clients from Europe, America, and Asia. <br>
Now you got no need to search for drug store at your local area.<br>
We necessarily bring high quality drugs to all parts of the planet.
<br>
<br>
<a href="http://shoulderbell.cn/" target="_blank"><em>Come to our site to acquire pharmas that you immediately need straight to your abode.</em></a></b> 
<br>
<font color="#D9EDFF">http://shoulderbell.cn/</font> 

<br><b>We are verified by <font color="#FF0000"><em>VeriSign</em></font> & <font color="#FF0000"><em>VISA</em></font> so we provide effective and dependable buying.
</b>

</BODY></HTML>
------------56EA9888FB256E--




From ipfix-bounces@ietf.org Mon Jul 30 11:36:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFXHw-0002TG-Tk; Mon, 30 Jul 2007 11:36:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFXHv-0002T5-RY
	for ipfix@ietf.org; Mon, 30 Jul 2007 11:36:03 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFXHv-0008EN-0s
	for ipfix@ietf.org; Mon, 30 Jul 2007 11:36:03 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6UFZoYc018474;
	Tue, 31 Jul 2007 00:35:52 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 31 Jul 2007 00:35:54 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
References: <20070727074625.4986.AKOBA@nttv6.net>
	<46A9E9C4.3010708@informatik.uni-tuebingen.de>
Message-Id: <20070730211130.ED7C.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 31 Jul 2007 00:35:53 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Gerhard,

> > 
> > They seems to be compossible. Do you think integration is necessary ?
> > Do you mean that we consider more the part of aggregation, as first step?
> 
> The aggregation draft is very specific, while your mediator draft is
> very broad.
> A short summary of the aspects covered by the aggregation draft to
> determine potential overlaps:
> 
> 1) architecture of a concentrator
> 2) description language for configuring metering processes
>    (essentially input filters and flow keys)
> 3) a couple of new IEs useful to report aggregates and applied input
>    filters (e.g. port range IE)
> 4) a new template type to efficiently report information about applied
>    input filters
> 
> I assume that item 1) is/will be covered in your draft.
> 
> Item 2) is related to configuration and covered by the configuration draft.
> 
> The remaining items 3) and 4) might be interesting extensions to
> efficiently report how a mediator modifies/filters the original data.
> Yet, you would probably try to export this kind of information with
> exiting protocol mechanisms at first.

Thank you for your suggestion.
Surely, the mechanism of exporting method might be one of my action
items.

Does the overview of final documents become as follows ?

1) Architecture of IPFIX Concentrator/Mediator
Maybe, the internal component part of IPFIX Mediator draft covers the
architecture of IPFIX Concentrator.

2) Configuration Data Model for IPFIX and PSAMP
Your draft will covers the cofiguration data model for IPFIX
Concentrator/Mediator devices? I will check your draft, again.

3) New information Elements for IPFIX Concentrator/Mediator
My draft proposes a couple of new IEs. But, they are different from what
you think. After discussing item#1 and item#4, I think it is better that
we consider what information elements are needed.

4) Reporting Method for IPFIX Concentrator/Mediator
This draft will cover the reporting method of aggregation draft.
But, I am not sure clearly that the necessity of the reporting method is
for only IPFIX Concentrator/Mediator or whole of Exporter. I think that
we will discuss this item after our agreement for definition of
mediator/concentrator.

At first, I would like to achieve the consensus of IPFIX members about
item#1 in order to progress the approach.

> 
> Regards,
> Gerhard
> 
> -- 
> Dipl.-Ing. Gerhard M$B".(Bz
> Computer Networks and Internet
> Wilhelm Schickard Institute for Computer Science
> University of Tuebingen
> Sand 13 (Room B309), D-72076 Tuebingen, Germany
> Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
> E-mail: muenz@informatik.uni-tuebingen.de
> WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 30 11:36:13 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFXHw-0002TG-Tk; Mon, 30 Jul 2007 11:36:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFXHv-0002T5-RY
	for ipfix@ietf.org; Mon, 30 Jul 2007 11:36:03 -0400
Received: from mail.nttv6.net ([192.68.245.115])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFXHv-0008EN-0s
	for ipfix@ietf.org; Mon, 30 Jul 2007 11:36:03 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6UFZoYc018474;
	Tue, 31 Jul 2007 00:35:52 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 31 Jul 2007 00:35:54 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
References: <20070727074625.4986.AKOBA@nttv6.net>
	<46A9E9C4.3010708@informatik.uni-tuebingen.de>
Message-Id: <20070730211130.ED7C.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 31 Jul 2007 00:35:53 +0900 (JST)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Gerhard,

> > 
> > They seems to be compossible. Do you think integration is necessary ?
> > Do you mean that we consider more the part of aggregation, as first step?
> 
> The aggregation draft is very specific, while your mediator draft is
> very broad.
> A short summary of the aspects covered by the aggregation draft to
> determine potential overlaps:
> 
> 1) architecture of a concentrator
> 2) description language for configuring metering processes
>    (essentially input filters and flow keys)
> 3) a couple of new IEs useful to report aggregates and applied input
>    filters (e.g. port range IE)
> 4) a new template type to efficiently report information about applied
>    input filters
> 
> I assume that item 1) is/will be covered in your draft.
> 
> Item 2) is related to configuration and covered by the configuration draft.
> 
> The remaining items 3) and 4) might be interesting extensions to
> efficiently report how a mediator modifies/filters the original data.
> Yet, you would probably try to export this kind of information with
> exiting protocol mechanisms at first.

Thank you for your suggestion.
Surely, the mechanism of exporting method might be one of my action
items.

Does the overview of final documents become as follows ?

1) Architecture of IPFIX Concentrator/Mediator
Maybe, the internal component part of IPFIX Mediator draft covers the
architecture of IPFIX Concentrator.

2) Configuration Data Model for IPFIX and PSAMP
Your draft will covers the cofiguration data model for IPFIX
Concentrator/Mediator devices? I will check your draft, again.

3) New information Elements for IPFIX Concentrator/Mediator
My draft proposes a couple of new IEs. But, they are different from what
you think. After discussing item#1 and item#4, I think it is better that
we consider what information elements are needed.

4) Reporting Method for IPFIX Concentrator/Mediator
This draft will cover the reporting method of aggregation draft.
But, I am not sure clearly that the necessity of the reporting method is
for only IPFIX Concentrator/Mediator or whole of Exporter. I think that
we will discuss this item after our agreement for definition of
mediator/concentrator.

At first, I would like to achieve the consensus of IPFIX members about
item#1 in order to progress the approach.

> 
> Regards,
> Gerhard
> 
> -- 
> Dipl.-Ing. Gerhard M$B".(Bz
> Computer Networks and Internet
> Wilhelm Schickard Institute for Computer Science
> University of Tuebingen
> Sand 13 (Room B309), D-72076 Tuebingen, Germany
> Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
> E-mail: muenz@informatik.uni-tuebingen.de
> WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 30 12:36:45 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFYEa-0001ix-Sc; Mon, 30 Jul 2007 12:36:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFYEY-0001iL-LP
	for ipfix@ietf.org; Mon, 30 Jul 2007 12:36:38 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFYEW-00027m-CA
	for ipfix@ietf.org; Mon, 30 Jul 2007 12:36:38 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6UGaVVD018821;
	Tue, 31 Jul 2007 01:36:32 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 31 Jul 2007 01:36:33 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46AA00C1.7020206@cisco.com>
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com>
Message-Id: <20070731002507.ED83.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 31 Jul 2007 01:36:32 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

On Fri, 27 Jul 2007 15:27:13 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
>=20
> Gerhard Muenz wrote:
>=20
> > The aggregation draft is very specific, while your mediator draft is
> > very broad.
>=20
> This is a good point. I wonder whether it would be better to divide the=
=20
> mediator into several separate and more general drafts which vendors=20
> could implement in a single product?

Do you mean my draft should be separated into each device, as follows?

- IPFIX concentrator
- IPFIX proxy
- IPFIX firewall
- IPFIX distributor=20
It distributes Flow Records to several collectors. My draft has not
described enough, yet.
=2E..

I can't name the flow mediation device that modifies the Flow Records.

Surely, making up the drafts of each device is one of approaches.

But, IPFIX protocol considerations and internal component might become
similar description. Other things could be common parts.
I think that making up the document of similar devices might be unhappy.
Even if becoming the separated drafts, the overview draft of IPFIX
Mediators might be necessary for common parts.

Roughly, it could be separated into the IPFIX protocol Mediation draft
and the Flow Mediation draft.

And also, the Flow Mediation could be separated into changing the
granularity of Flow, such as filtering and aggregation, and changing the
content of Flow Records, such as modification.

But yet, should my draft be separated into some devices?

> --=20
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

---=20
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 30 12:36:45 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFYEa-0001ix-Sc; Mon, 30 Jul 2007 12:36:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFYEY-0001iL-LP
	for ipfix@ietf.org; Mon, 30 Jul 2007 12:36:38 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFYEW-00027m-CA
	for ipfix@ietf.org; Mon, 30 Jul 2007 12:36:38 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6UGaVVD018821;
	Tue, 31 Jul 2007 01:36:32 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Tue, 31 Jul 2007 01:36:33 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46AA00C1.7020206@cisco.com>
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com>
Message-Id: <20070731002507.ED83.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Tue, 31 Jul 2007 01:36:32 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

On Fri, 27 Jul 2007 15:27:13 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
>=20
> Gerhard Muenz wrote:
>=20
> > The aggregation draft is very specific, while your mediator draft is
> > very broad.
>=20
> This is a good point. I wonder whether it would be better to divide the=
=20
> mediator into several separate and more general drafts which vendors=20
> could implement in a single product?

Do you mean my draft should be separated into each device, as follows?

- IPFIX concentrator
- IPFIX proxy
- IPFIX firewall
- IPFIX distributor=20
It distributes Flow Records to several collectors. My draft has not
described enough, yet.
=2E..

I can't name the flow mediation device that modifies the Flow Records.

Surely, making up the drafts of each device is one of approaches.

But, IPFIX protocol considerations and internal component might become
similar description. Other things could be common parts.
I think that making up the document of similar devices might be unhappy.
Even if becoming the separated drafts, the overview draft of IPFIX
Mediators might be necessary for common parts.

Roughly, it could be separated into the IPFIX protocol Mediation draft
and the Flow Mediation draft.

And also, the Flow Mediation could be separated into changing the
granularity of Flow, such as filtering and aggregation, and changing the
content of Flow Records, such as modification.

But yet, should my draft be separated into some devices?

> --=20
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.

---=20
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 30 16:26:48 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFbp8-0004Eb-3K; Mon, 30 Jul 2007 16:26:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFbp7-0004EN-PU
	for ipfix@ietf.org; Mon, 30 Jul 2007 16:26:37 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFbp6-0008Py-HV
	for ipfix@ietf.org; Mon, 30 Jul 2007 16:26:37 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 30 Jul 2007 22:26:37 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAPjlrUaQ/uCKh2dsb2JhbACOIAEBCQon
X-IronPort-AV: i="4.19,200,1183327200"; 
	d="scan'208"; a="149386919:sNHT26785514"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6UKQZqP017061; 
	Mon, 30 Jul 2007 22:26:35 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6UKQUkt025838; 
	Mon, 30 Jul 2007 20:26:30 GMT
Received: from [10.61.81.162] (ams3-vpn-dhcp4515.cisco.com [10.61.81.162])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id VAA28027;
	Mon, 30 Jul 2007 21:26:28 +0100 (BST)
Message-ID: <46AE4984.3050109@cisco.com>
Date: Mon, 30 Jul 2007 21:26:44 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB;
	rv:1.8.1.5) Gecko/20070719 SeaMonkey/1.1.3
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com> <20070731002507.ED83.AKOBA@nttv6.net>
In-Reply-To: <20070731002507.ED83.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1667; t=1185827195;
	x=1186691195; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items,
	=20take=20t wo |Sender:=20;
	bh=OGAuC3NBUU17PTz8Nw83uWbEplKCI4j4+iOliICR7Gs=;
	b=m0nBaVRE/TUE+7+R+mnsP40ZUyObxu1XIUBonIRuPkS2NwKBAb8dHx+7rdfRqnWkrjnK4HoT
	okfIO+w0jdwcUmo5Ds7Ldm42yxx36SfAfOKpMQHMIkCcTWagUZXcwF7q;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,


>>> The aggregation draft is very specific, while your mediator draft is
>>> very broad.
>>
>> This is a good point. I wonder whether it would be better to divide the 
>> mediator into several separate and more general drafts which vendors 
>> could implement in a single product?
> 
> Do you mean my draft should be separated into each device, as follows?
> 
> - IPFIX concentrator
> - IPFIX proxy
> - IPFIX firewall
> - IPFIX distributor 
> It distributes Flow Records to several collectors. My draft has not
> described enough, yet.
> ...
> 
> I can't name the flow mediation device that modifies the Flow Records.
> 
> Surely, making up the drafts of each device is one of approaches.

Exactly, instead of covering such a broad scope in one draft. However, 
it's only one possible approach.


> But, IPFIX protocol considerations and internal component might become
> similar description. Other things could be common parts.
> I think that making up the document of similar devices might be unhappy.
> Even if becoming the separated drafts, the overview draft of IPFIX
> Mediators might be necessary for common parts.

True.


> Roughly, it could be separated into the IPFIX protocol Mediation draft
> and the Flow Mediation draft.
> 
> And also, the Flow Mediation could be separated into changing the
> granularity of Flow, such as filtering and aggregation, and changing the
> content of Flow Records, such as modification.
> 
> But yet, should my draft be separated into some devices?

I had hoped some other IPFIX-ers would comment.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Mon Jul 30 16:26:48 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFbp8-0004Eb-3K; Mon, 30 Jul 2007 16:26:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFbp7-0004EN-PU
	for ipfix@ietf.org; Mon, 30 Jul 2007 16:26:37 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFbp6-0008Py-HV
	for ipfix@ietf.org; Mon, 30 Jul 2007 16:26:37 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 30 Jul 2007 22:26:37 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAPjlrUaQ/uCKh2dsb2JhbACOIAEBCQon
X-IronPort-AV: i="4.19,200,1183327200"; 
	d="scan'208"; a="149386919:sNHT26785514"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6UKQZqP017061; 
	Mon, 30 Jul 2007 22:26:35 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6UKQUkt025838; 
	Mon, 30 Jul 2007 20:26:30 GMT
Received: from [10.61.81.162] (ams3-vpn-dhcp4515.cisco.com [10.61.81.162])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id VAA28027;
	Mon, 30 Jul 2007 21:26:28 +0100 (BST)
Message-ID: <46AE4984.3050109@cisco.com>
Date: Mon, 30 Jul 2007 21:26:44 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB;
	rv:1.8.1.5) Gecko/20070719 SeaMonkey/1.1.3
MIME-Version: 1.0
To: kobayashi atsushi <akoba@nttv6.net>
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com> <20070731002507.ED83.AKOBA@nttv6.net>
In-Reply-To: <20070731002507.ED83.AKOBA@nttv6.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1667; t=1185827195;
	x=1186691195; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=paitken@cisco.com;
	z=From:=20Paul=20Aitken=20<paitken@cisco.com>
	|Subject:=20Re=3A=20[IPFIX]=20*Proposed*=20new=20work=20items,
	=20take=20t wo |Sender:=20;
	bh=OGAuC3NBUU17PTz8Nw83uWbEplKCI4j4+iOliICR7Gs=;
	b=m0nBaVRE/TUE+7+R+mnsP40ZUyObxu1XIUBonIRuPkS2NwKBAb8dHx+7rdfRqnWkrjnK4HoT
	okfIO+w0jdwcUmo5Ds7Ldm42yxx36SfAfOKpMQHMIkCcTWagUZXcwF7q;
Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org

Kobayashi-san,


>>> The aggregation draft is very specific, while your mediator draft is
>>> very broad.
>>
>> This is a good point. I wonder whether it would be better to divide the 
>> mediator into several separate and more general drafts which vendors 
>> could implement in a single product?
> 
> Do you mean my draft should be separated into each device, as follows?
> 
> - IPFIX concentrator
> - IPFIX proxy
> - IPFIX firewall
> - IPFIX distributor 
> It distributes Flow Records to several collectors. My draft has not
> described enough, yet.
> ...
> 
> I can't name the flow mediation device that modifies the Flow Records.
> 
> Surely, making up the drafts of each device is one of approaches.

Exactly, instead of covering such a broad scope in one draft. However, 
it's only one possible approach.


> But, IPFIX protocol considerations and internal component might become
> similar description. Other things could be common parts.
> I think that making up the document of similar devices might be unhappy.
> Even if becoming the separated drafts, the overview draft of IPFIX
> Mediators might be necessary for common parts.

True.


> Roughly, it could be separated into the IPFIX protocol Mediation draft
> and the Flow Mediation draft.
> 
> And also, the Flow Mediation could be separated into changing the
> granularity of Flow, such as filtering and aggregation, and changing the
> content of Flow Records, such as modification.
> 
> But yet, should my draft be separated into some devices?

I had hoped some other IPFIX-ers would comment.

-- 
Paul Aitken
Cisco Systems Ltd, Edinburgh, Scotland.

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 31 05:09:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFnja-0002jd-S9; Tue, 31 Jul 2007 05:09:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFnjZ-0002eS-QS
	for ipfix@ietf.org; Tue, 31 Jul 2007 05:09:41 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFnjY-0006Ud-49
	for ipfix@ietf.org; Tue, 31 Jul 2007 05:09:41 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6V99cGF021651
	for <ipfix@ietf.org>; Tue, 31 Jul 2007 11:09:39 +0200
Message-ID: <46AEFC3B.1090505@informatik.uni-tuebingen.de>
Date: Tue, 31 Jul 2007 11:09:15 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix@ietf.org
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com> <20070731002507.ED83.AKOBA@nttv6.net>
	<46AE4984.3050109@cisco.com>
In-Reply-To: <46AE4984.3050109@cisco.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.54;
	VDF: 6.39.0.200; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2042588151=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============2042588151==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020507070002080803000502"

This is a cryptographically signed message in MIME format.

--------------ms020507070002080803000502
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Kobayashi, Paul, all,

Paul Aitken wrote:
> Kobayashi-san,
> 
> 
>>>> The aggregation draft is very specific, while your mediator draft is
>>>> very broad.
>>>
>>> This is a good point. I wonder whether it would be better to divide
>>> the mediator into several separate and more general drafts which
>>> vendors could implement in a single product?
>>
>> Do you mean my draft should be separated into each device, as follows?
>>
>> - IPFIX concentrator
>> - IPFIX proxy
>> - IPFIX firewall
>> - IPFIX distributor It distributes Flow Records to several collectors.
>> My draft has not
>> described enough, yet.
>> ...
>>
>> I can't name the flow mediation device that modifies the Flow Records.
>>
>> Surely, making up the drafts of each device is one of approaches.
> 
> Exactly, instead of covering such a broad scope in one draft. However,
> it's only one possible approach.

IPFIX concentrator, IPFIX proxy, IPFIX firewall, IPFIX distributor etc.,
do we really need to distinguish between this whole bunch of new devices?

I think these expressions reflect more the role or function of a
mediator within a given network.

The question is also, if operators really need all of these new
functionalities, or if we talk about potentially useful things that will
never be used in practice.

>> But, IPFIX protocol considerations and internal component might become
>> similar description. Other things could be common parts.
>> I think that making up the document of similar devices might be unhappy.
>> Even if becoming the separated drafts, the overview draft of IPFIX
>> Mediators might be necessary for common parts.
> 
> True.
> 
> 
>> Roughly, it could be separated into the IPFIX protocol Mediation draft
>> and the Flow Mediation draft.
>>
>> And also, the Flow Mediation could be separated into changing the
>> granularity of Flow, such as filtering and aggregation, and changing the
>> content of Flow Records, such as modification.
>>
>> But yet, should my draft be separated into some devices?
> 
> I had hoped some other IPFIX-ers would comment.

I see the following two aspects:

1) *Relaying and multiplexing of IPFIX transport sessions* without
changing or filtering the data. This is currently called "protocol
mediation". If this function is really requested by operators, there are
some issues to be solved, like:
- how to translate knowledge about the original observation domain into
option data?
- how to convert relative timestamps?
- how to do the template management, especially in case of multiplexing?

2) *Filtering, anonymization and aggregation* of measurement data.
This is currently called "flow mediation", yet I think that it should
not be restricted to flow data, and also not be restricted to mediators.
The issues here are mostly related to the reporting of what is going on
in the Metering Process, i.e. what kind of filtering, what kind of
anonymization, what kind of aggregation etc. takes place.
I think that all these functions are not specific to the Mediator, i.e.
they can also be implemented in a usual exporter. So I would not cover
them in a mediator draft, but in a more generic draft (or several
problem-specific ones) describing advanced functions within the Metering
Process and how to report them.

Regards,
Gerhard


-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms020507070002080803000502
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDczMTA5MDkxNVowIwYJKoZIhvcNAQkEMRYEFGdqLrpRCVIJ
AMDNHIu9z9ZsZxRxMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQAemVv5yCqLz53OiXNGHohKPiGKLJz0Na8biyn4C/u51tyqzuMdQ8nAFyDm
XmlKRiJrBqeTc0bsPNp+Ew5fSO5PJGLvvuvlA788MMODlOfZAkXiFHBTArT3nYI/a0uQPmFp
hmUYMfProLU6wmzBYS1ffioL9/So5pnlYB+T10Dtesk5D/6c7W6fIDL4klcrZ4dp/fveKv6f
QnSgl1eyLbnuYYgFXsPj/E49Gh8QBIokfcKkvV3OPhVVhN3ysGPGsdkh97Y1Ox+TeIVFjTWr
6Etqvm/PHJVZ+QZ99MzhC8gIKrLY2kfDyXhp9B2DLA0f5Jb5Txc3ROQggXDGz1cu5p83AAAA
AAAA
--------------ms020507070002080803000502--


--===============2042588151==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============2042588151==--




From ipfix-bounces@ietf.org Tue Jul 31 05:09:49 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFnja-0002jd-S9; Tue, 31 Jul 2007 05:09:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFnjZ-0002eS-QS
	for ipfix@ietf.org; Tue, 31 Jul 2007 05:09:41 -0400
Received: from mx05.uni-tuebingen.de ([134.2.3.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFnjY-0006Ud-49
	for ipfix@ietf.org; Tue, 31 Jul 2007 05:09:41 -0400
Received: from [134.2.172.138] (u-172-c138.cs.uni-tuebingen.de [134.2.172.138])
	by mx05.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id l6V99cGF021651
	for <ipfix@ietf.org>; Tue, 31 Jul 2007 11:09:39 +0200
Message-ID: <46AEFC3B.1090505@informatik.uni-tuebingen.de>
Date: Tue, 31 Jul 2007 11:09:15 +0200
From: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipfix@ietf.org
Subject: Re: [IPFIX] *Proposed* new work items, take two
References: <46A9E9C4.3010708@informatik.uni-tuebingen.de>
	<46AA00C1.7020206@cisco.com> <20070731002507.ED83.AKOBA@nttv6.net>
	<46AE4984.3050109@cisco.com>
In-Reply-To: <46AE4984.3050109@cisco.com>
X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-11; AVE: 7.4.0.54;
	VDF: 6.39.0.200; host: mx05)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2042588151=="
Errors-To: ipfix-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============2042588151==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020507070002080803000502"

This is a cryptographically signed message in MIME format.

--------------ms020507070002080803000502
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


Kobayashi, Paul, all,

Paul Aitken wrote:
> Kobayashi-san,
> 
> 
>>>> The aggregation draft is very specific, while your mediator draft is
>>>> very broad.
>>>
>>> This is a good point. I wonder whether it would be better to divide
>>> the mediator into several separate and more general drafts which
>>> vendors could implement in a single product?
>>
>> Do you mean my draft should be separated into each device, as follows?
>>
>> - IPFIX concentrator
>> - IPFIX proxy
>> - IPFIX firewall
>> - IPFIX distributor It distributes Flow Records to several collectors.
>> My draft has not
>> described enough, yet.
>> ...
>>
>> I can't name the flow mediation device that modifies the Flow Records.
>>
>> Surely, making up the drafts of each device is one of approaches.
> 
> Exactly, instead of covering such a broad scope in one draft. However,
> it's only one possible approach.

IPFIX concentrator, IPFIX proxy, IPFIX firewall, IPFIX distributor etc.,
do we really need to distinguish between this whole bunch of new devices?

I think these expressions reflect more the role or function of a
mediator within a given network.

The question is also, if operators really need all of these new
functionalities, or if we talk about potentially useful things that will
never be used in practice.

>> But, IPFIX protocol considerations and internal component might become
>> similar description. Other things could be common parts.
>> I think that making up the document of similar devices might be unhappy.
>> Even if becoming the separated drafts, the overview draft of IPFIX
>> Mediators might be necessary for common parts.
> 
> True.
> 
> 
>> Roughly, it could be separated into the IPFIX protocol Mediation draft
>> and the Flow Mediation draft.
>>
>> And also, the Flow Mediation could be separated into changing the
>> granularity of Flow, such as filtering and aggregation, and changing the
>> content of Flow Records, such as modification.
>>
>> But yet, should my draft be separated into some devices?
> 
> I had hoped some other IPFIX-ers would comment.

I see the following two aspects:

1) *Relaying and multiplexing of IPFIX transport sessions* without
changing or filtering the data. This is currently called "protocol
mediation". If this function is really requested by operators, there are
some issues to be solved, like:
- how to translate knowledge about the original observation domain into
option data?
- how to convert relative timestamps?
- how to do the template management, especially in case of multiplexing?

2) *Filtering, anonymization and aggregation* of measurement data.
This is currently called "flow mediation", yet I think that it should
not be restricted to flow data, and also not be restricted to mediators.
The issues here are mostly related to the reporting of what is going on
in the Metering Process, i.e. what kind of filtering, what kind of
anonymization, what kind of aggregation etc. takes place.
I think that all these functions are not specific to the Mediator, i.e.
they can also be implemented in a usual exporter. So I would not cover
them in a mediator draft, but in a more generic draft (or several
problem-specific ones) describing advanced functions within the Metering
Process and how to report them.

Regards,
Gerhard


-- 
Dipl.-Ing. Gerhard Münz
Computer Networks and Internet
Wilhelm Schickard Institute for Computer Science
University of Tuebingen
Sand 13 (Room B309), D-72076 Tuebingen, Germany
Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
E-mail: muenz@informatik.uni-tuebingen.de
WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--------------ms020507070002080803000502
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJdTCC
AxUwggJ+oAMCAQICEGU5u1eI8WeEkIox6PdwkFAwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxMzEwMzMxOVoX
DTA4MDIxMzEwMzMxOVowbDEOMAwGA1UEBBMFTXVlbnoxEDAOBgNVBCoTB0dlcmhhcmQxFjAU
BgNVBAMTDUdlcmhhcmQgTXVlbnoxMDAuBgkqhkiG9w0BCQEWIW11ZW56QGluZm9ybWF0aWsu
dW5pLXR1ZWJpbmdlbi5kZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL4m902z
LbJz14mLB1geOi/Z0ptEzogRqG7O4E0D+BD77zd2mfVbGO27ocJ3D/10BW1SE/Ob/DsvLZV7
rXKJu+cpyW36qoqg4YJEMipOSJOPgYHXRjuVRyLNamyCli7tqbBonR/KfhQexwT1McEA3G/e
Hbtv9XByhXofJ+07+oDZwd/cg9LebNBf1FxMX5HVgqlALFh3Stv7T1gOmr4HO4mOUBYsLFWp
79JUYpChJt7iQhZ9GDvfBxnin0brBStl0B59xZosWPTw+tRxnussP5PY5fsUBWtTh28miFZU
siHp1ZUxajPeCVdErstZY6o9NF2Ncu7TQeAr6W679WA4FcECAwEAAaM+MDwwLAYDVR0RBCUw
I4EhbXVlbnpAaW5mb3JtYXRpay51bmktdHVlYmluZ2VuLmRlMAwGA1UdEwEB/wQCMAAwDQYJ
KoZIhvcNAQEFBQADgYEAtScrBwt79QtKll2itdySgXKm7bMeP8t00l9r4MrFscF/y5G1ulpZ
TnnzLGYhXs2EuVzHIie7Y/3tpUsXvRqGO9AhWMBDhE1/c4bBi4ppw7LF8NIefvsWBT3xDIuZ
eP6g6PJrF2f/mVOl9sCtKkYhPtbi3oI7Vto1yOcpzqj0HhEwggMVMIICfqADAgECAhBlObtX
iPFnhJCKMej3cJBQMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNzAyMTMxMDMzMTlaFw0wODAyMTMxMDMzMTlaMGwx
DjAMBgNVBAQTBU11ZW56MRAwDgYDVQQqEwdHZXJoYXJkMRYwFAYDVQQDEw1HZXJoYXJkIE11
ZW56MTAwLgYJKoZIhvcNAQkBFiFtdWVuekBpbmZvcm1hdGlrLnVuaS10dWViaW5nZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+JvdNsy2yc9eJiwdYHjov2dKbRM6I
EahuzuBNA/gQ++83dpn1Wxjtu6HCdw/9dAVtUhPzm/w7Ly2Ve61yibvnKclt+qqKoOGCRDIq
TkiTj4GB10Y7lUcizWpsgpYu7amwaJ0fyn4UHscE9THBANxv3h27b/VwcoV6HyftO/qA2cHf
3IPS3mzQX9RcTF+R1YKpQCxYd0rb+09YDpq+BzuJjlAWLCxVqe/SVGKQoSbe4kIWfRg73wcZ
4p9G6wUrZdAefcWaLFj08PrUcZ7rLD+T2OX7FAVrU4dvJohWVLIh6dWVMWoz3glXRK7LWWOq
PTRdjXLu00HgK+luu/VgOBXBAgMBAAGjPjA8MCwGA1UdEQQlMCOBIW11ZW56QGluZm9ybWF0
aWsudW5pLXR1ZWJpbmdlbi5kZTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBALUn
KwcLe/ULSpZdorXckoFypu2zHj/LdNJfa+DKxbHBf8uRtbpaWU558yxmIV7NhLlcxyInu2P9
7aVLF70ahjvQIVjAQ4RNf3OGwYuKacOyxfDSHn77FgU98QyLmXj+oOjyaxdn/5lTpfbArSpG
IT7W4t6CO1baNcjnKc6o9B4RMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL
MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du
MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT
ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx
NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0
ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl
bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4
oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j
cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy
LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4
Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg
T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEB
MHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0
ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBlObtX
iPFnhJCKMej3cJBQMAkGBSsOAwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw
HAYJKoZIhvcNAQkFMQ8XDTA3MDczMTA5MDkxNVowIwYJKoZIhvcNAQkEMRYEFGdqLrpRCVIJ
AMDNHIu9z9ZsZxRxMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3
EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
ZTm7V4jxZ4SQijHo93CQUDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw
IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUg
UGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQZTm7V4jxZ4SQijHo93CQUDANBgkqhkiG
9w0BAQEFAASCAQAemVv5yCqLz53OiXNGHohKPiGKLJz0Na8biyn4C/u51tyqzuMdQ8nAFyDm
XmlKRiJrBqeTc0bsPNp+Ew5fSO5PJGLvvuvlA788MMODlOfZAkXiFHBTArT3nYI/a0uQPmFp
hmUYMfProLU6wmzBYS1ffioL9/So5pnlYB+T10Dtesk5D/6c7W6fIDL4klcrZ4dp/fveKv6f
QnSgl1eyLbnuYYgFXsPj/E49Gh8QBIokfcKkvV3OPhVVhN3ysGPGsdkh97Y1Ox+TeIVFjTWr
6Etqvm/PHJVZ+QZ99MzhC8gIKrLY2kfDyXhp9B2DLA0f5Jb5Txc3ROQggXDGz1cu5p83AAAA
AAAA
--------------ms020507070002080803000502--


--===============2042588151==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============2042588151==--




From mujbassolsyasociadosfek@bassolsyasociados.com Tue Jul 31 05:54:06 2007
Return-path: <mujbassolsyasociadosfek@bassolsyasociados.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFoQX-00009P-Su; Tue, 31 Jul 2007 05:54:05 -0400
Received: from nat-tor-1.aster.pl ([212.76.37.188])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IFoQW-0000gz-Nx; Tue, 31 Jul 2007 05:54:05 -0400
Received: from [212.76.37.188] by smtp-01.piensasolutions.com; Tue, 31 Jul 2007 09:54:05 -0100
Date:	Tue, 31 Jul 2007 09:54:05 -0100
From:	"Gavin Marrero" <mujbassolsyasociadosfek@bassolsyasociados.com>
X-Mailer: The Bat! (v2.11) Educational
Reply-To: mujbassolsyasociadosfek@bassolsyasociados.com
X-Priority: 3 (Normal)
Message-ID: <486279773.45815322682995@bassolsyasociados.com>
To: idmr-archive@lists.ietf.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------6758B6E16758BDAE"
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

------------6758B6E16758BDAE
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

LegalRX drug-store acquaints you with all meds that you have a necessity in in order to renew your health with a little price. 
We operate all over the world with customers from Europe, America and Asia. 
At the time you got no need to look for drug shop somewhere at your area.
We deliver high-quality pharmas to all parts of the globe.
Come to our site to acquire pharmas that you require instantly direct to your residence. 
http://covervalue.cn/ 

We are ratified by VISA & VeriSign consequently we provide certain & confidential purchase.

------------6758B6E16758BDAE
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRX</em></font> drug-store acquaints you with all meds that you have a necessity in in order to renew your health with a little price. <br>
We operate all over the world with customers from Europe, America and Asia. <br>
At the time you got no need to look for drug shop somewhere at your area.<br>
We deliver high-quality pharmas to all parts of the globe.
<br>
<br>
<a href="http://covervalue.cn/" target="_blank"><em>Come to our site to acquire pharmas that you require instantly direct to your residence.</em></a></b> 
<br>
<font color="#D9EDFF">http://covervalue.cn/</font> 

<br><b>We are ratified by <font color="#FF0000"><em>VISA</em></font> & <font color="#FF0000"><em>VeriSign</em></font> consequently we provide certain & confidential purchase.
</b>

</BODY></HTML>
------------6758B6E16758BDAE--




From ipfix-bounces@ietf.org Tue Jul 31 11:54:27 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFu37-0001oD-6M; Tue, 31 Jul 2007 11:54:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFu36-0001o7-7Y
	for ipfix@ietf.org; Tue, 31 Jul 2007 11:54:16 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFu35-0006r3-5q
	for ipfix@ietf.org; Tue, 31 Jul 2007 11:54:16 -0400
X-ASG-Debug-ID: 1185897253-01cf004c0000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1185897253
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 90E6880838
	for <ipfix@ietf.org>; Tue, 31 Jul 2007 16:54:13 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B46af5b250000>; Tue, 31 Jul 2007 15:54:13 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:54:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: Re: [IPFIX] *Proposed* new work items, work item # 2
Subject: Re: [IPFIX] *Proposed* new work items, work item # 2
Date: Tue, 31 Jul 2007 16:54:12 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922AD@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items, work item # 2
Thread-Index: AcfTiZ15Tn9B9Hi3QBOclj1Ny7O4UA==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <bht@cert.org>
X-OriginalArrivalTime: 31 Jul 2007 15:54:12.0251 (UTC)
	FILETIME=[09D976B0:01C7D38B]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0314250734=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0314250734==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D38B.09B918E7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D38B.09B918E7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

all,

one comment inline...

Brian Trammell wrote:
> On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:
>=20
>
>> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>>
>> IPFIX: Proposal for new work
>>       Based on discussion at IETF 69, Chicago
>>
>> For IPFIX mailing list, we suggest that items 1-6
>> (above the --- line) be adopted as new WG work items.
>> Please comment by 6 Aug 07 <<<<
>> Also, we need reviewers; please fill in and email back the
>> questionnaire form below!!
>>

...

>>
>> 2. SCTP Per-Stream Draft (Benoit Claise)
>>   Agreed: Needs to be explored, as a possible protocol option.
>>   Procedure: Make this a WG item, as Experimental RFC.
>>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It's unclear to me that, after the stream restriction change in point 0=
.=20
> above, this should be Experimental as opposed to Informational... Per=20
> 2026, Experimental RFCs are intended as an archival record of a researc=
h=20
> work. Unless the primary intention is to change this draft to be a=20
> description and evaluation of the performance benefits of this (and=20
> potentially other) stream selection methods, it appears very much to be=
=20
> the description of an export method (which will be in line with the=20
> protocol after the stream restriction change in point 0. above) that ha=
s=20
> potential performance and other benefits within a defined set of use=20
> cases, very much like the recently-approved (Informational) Reducing=20
> Redundancy draft.
>=20

I agree on this point. The per-stream draft is the description of an opti=
onal method for SCTP export, offering enhanced functionality for a limite=
d set of applications. Informational seems the most appropriate choice, p=
retty much for the same reasons that brought the Working Group to decide =
the status of Reducing Redundancy (i.e. informational).=20


Regards,
Elisa





*************************************************************************=
*************************=20
E-mail Confidentiality Notice and Disclaimer.=20

This email and any files transmitted with it are confidential and are int=
ended solely for the use=20
of the individual or entity to which they are addressed. Access to this e=
-mail by anyone else is=20
unauthorised. If you are not the intended recipient, any disclosure, copy=
ing, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-m=
ail messages are not=20
necessarily secure. Hitachi does not accept responsibility for any change=
s made to this message=20
after it was sent.=20

Please note that Hitachi checks outgoing e-mail messages for the presence=
=20of computer viruses.=20
*************************************************************************=
*************************

------_=_NextPart_001_01C7D38B.09B918E7
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7235.2=
">
<TITLE>Re: [IPFIX] *Proposed* new work items, work item # 2</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>all,<BR>
<BR>
one comment inline...<BR>
<BR>
Brian Trammell wrote:<BR>
&gt; On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:<BR>
&gt;<BR>
&gt;<BR>
&gt;&gt; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . =
. . .<BR>
&gt;&gt;<BR>
&gt;&gt; IPFIX: Proposal for new work<BR>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Based on discussion at IETF =
69, Chicago<BR>
&gt;&gt;<BR>
&gt;&gt; For IPFIX mailing list, we suggest that items 1-6<BR>
&gt;&gt; (above the --- line) be adopted as new WG work items.<BR>
&gt;&gt; Please comment by 6 Aug 07 &lt;&lt;&lt;&lt;<BR>
&gt;&gt; Also, we need reviewers; please fill in and email back the<BR>
&gt;&gt; questionnaire form below!!<BR>
&gt;&gt;<BR>
<BR>
...<BR>
<BR>
&gt;&gt;<BR>
&gt;&gt; 2. SCTP Per-Stream Draft (Benoit Claise)<BR>
&gt;&gt;&nbsp;&nbsp; Agreed: Needs to be explored, as a possible protocol=
=20option.<BR>
&gt;&gt;&nbsp;&nbsp; Procedure: Make this a WG item, as Experimental RFC.=
<BR>
&gt;&gt;&nbsp;&nbsp; Milestones:&nbsp; WG LC after IETF 70, to IESG befor=
e IETF&nbsp; 71.<BR>
&gt;<BR>
&gt; It's unclear to me that, after the stream restriction change in poin=
t 0.<BR>
&gt; above, this should be Experimental as opposed to Informational... Pe=
r<BR>
&gt; 2026, Experimental RFCs are intended as an archival record of a rese=
arch<BR>
&gt; work. Unless the primary intention is to change this draft to be a<B=
R>
&gt; description and evaluation of the performance benefits of this (and<=
BR>
&gt; potentially other) stream selection methods, it appears very much to=
=20be<BR>
&gt; the description of an export method (which will be in line with the<=
BR>
&gt; protocol after the stream restriction change in point 0. above) that=
=20has<BR>
&gt; potential performance and other benefits within a defined set of use=
<BR>
&gt; cases, very much like the recently-approved (Informational) Reducing=
<BR>
&gt; Redundancy draft.<BR>
&gt;<BR>
<BR>
I agree on this point. The per-stream draft is the description of an opti=
onal method for SCTP export, offering enhanced functionality for a limite=
d set of applications. Informational seems the most appropriate choice, p=
retty much for the same reasons that brought the Working Group to decide =
the status of Reducing Redundancy (i.e. informational).<BR>
<BR>
<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>


<P><FONT face=3D"Courier New"=20
size=3D2>****************************************************************=
**********************************<BR></FONT><FONT=20
face=3D"Courier New" size=3D2>E-mail Confidentiality Notice and Disclaime=
r.=20
</FONT></P>
<P><FONT face=3D"Courier New" size=3D2>This email and any files transmitt=
ed with it=20
are confidential and are intended solely for the use of the individual or=
=20entity=20
to which they are addressed. Access to this e-mail by anyone else is=20
unauthorised. If you are not the intended recipient,any disclosure, copyi=
ng,=20
distribution or any action taken or omitted to be taken in reliance on it=
, is=20
prohibited. <BR>E-mail messages are not necessarily secure.Hitachi does n=
ot=20
accept responsibility for any changes made to this message after it was=20
sent.<BR><BR>Please note that Hitachi checks outgoing e-mail&nbsp;message=
s for=20
the presence of computer viruses.=20
<BR>*********************************************************************=
*****************************</FONT></P>
</BODY>
</HTML>

------_=_NextPart_001_01C7D38B.09B918E7--


--===============0314250734==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0314250734==--




From ipfix-bounces@ietf.org Tue Jul 31 11:54:27 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFu37-0001oD-6M; Tue, 31 Jul 2007 11:54:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFu36-0001o7-7Y
	for ipfix@ietf.org; Tue, 31 Jul 2007 11:54:16 -0400
Received: from gatekeeper.hitachi-eu.com ([194.36.128.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFu35-0006r3-5q
	for ipfix@ietf.org; Tue, 31 Jul 2007 11:54:16 -0400
X-ASG-Debug-ID: 1185897253-01cf004c0000-urGyNO
X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi
X-Barracuda-Connect: primary.hitachi-eu.net[193.39.225.234]
X-Barracuda-Start-Time: 1185897253
X-ASG-Whitelist: Client
Received: from mhd-mta-int.hitachi-eu.com (primary.hitachi-eu.net
	[193.39.225.234])
	by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 90E6880838
	for <ipfix@ietf.org>; Tue, 31 Jul 2007 16:54:13 +0100 (BST)
Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by
	mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 1, 8, 2172)
	id <B46af5b250000>; Tue, 31 Jul 2007 15:54:13 +0000
Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by
	MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jul 2007 16:54:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: Re: [IPFIX] *Proposed* new work items, work item # 2
Subject: Re: [IPFIX] *Proposed* new work items, work item # 2
Date: Tue, 31 Jul 2007 16:54:12 +0100
Message-ID: <AEC82A8A9DA33047ABC0902A36E889130922AD@mhdexcb.adhel.hitachi-eu.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [IPFIX] *Proposed* new work items, work item # 2
Thread-Index: AcfTiZ15Tn9B9Hi3QBOclj1Ny7O4UA==
From: "Boschi, Elisa" <Elisa.Boschi@Hitachi-eu.com>
To: <bht@cert.org>
X-OriginalArrivalTime: 31 Jul 2007 15:54:12.0251 (UTC)
	FILETIME=[09D976B0:01C7D38B]
X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0314250734=="
Errors-To: ipfix-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0314250734==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D38B.09B918E7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D38B.09B918E7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

all,

one comment inline...

Brian Trammell wrote:
> On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:
>=20
>
>> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>>
>> IPFIX: Proposal for new work
>>       Based on discussion at IETF 69, Chicago
>>
>> For IPFIX mailing list, we suggest that items 1-6
>> (above the --- line) be adopted as new WG work items.
>> Please comment by 6 Aug 07 <<<<
>> Also, we need reviewers; please fill in and email back the
>> questionnaire form below!!
>>

...

>>
>> 2. SCTP Per-Stream Draft (Benoit Claise)
>>   Agreed: Needs to be explored, as a possible protocol option.
>>   Procedure: Make this a WG item, as Experimental RFC.
>>   Milestones:  WG LC after IETF 70, to IESG before IETF  71.
>=20
> It's unclear to me that, after the stream restriction change in point 0=
.=20
> above, this should be Experimental as opposed to Informational... Per=20
> 2026, Experimental RFCs are intended as an archival record of a researc=
h=20
> work. Unless the primary intention is to change this draft to be a=20
> description and evaluation of the performance benefits of this (and=20
> potentially other) stream selection methods, it appears very much to be=
=20
> the description of an export method (which will be in line with the=20
> protocol after the stream restriction change in point 0. above) that ha=
s=20
> potential performance and other benefits within a defined set of use=20
> cases, very much like the recently-approved (Informational) Reducing=20
> Redundancy draft.
>=20

I agree on this point. The per-stream draft is the description of an opti=
onal method for SCTP export, offering enhanced functionality for a limite=
d set of applications. Informational seems the most appropriate choice, p=
retty much for the same reasons that brought the Working Group to decide =
the status of Reducing Redundancy (i.e. informational).=20


Regards,
Elisa





*************************************************************************=
*************************=20
E-mail Confidentiality Notice and Disclaimer.=20

This email and any files transmitted with it are confidential and are int=
ended solely for the use=20
of the individual or entity to which they are addressed. Access to this e=
-mail by anyone else is=20
unauthorised. If you are not the intended recipient, any disclosure, copy=
ing, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-m=
ail messages are not=20
necessarily secure. Hitachi does not accept responsibility for any change=
s made to this message=20
after it was sent.=20

Please note that Hitachi checks outgoing e-mail messages for the presence=
=20of computer viruses.=20
*************************************************************************=
*************************

------_=_NextPart_001_01C7D38B.09B918E7
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7235.2=
">
<TITLE>Re: [IPFIX] *Proposed* new work items, work item # 2</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>all,<BR>
<BR>
one comment inline...<BR>
<BR>
Brian Trammell wrote:<BR>
&gt; On Jul 25, 2007, at 5:08 PM, Nevil Brownlee wrote:<BR>
&gt;<BR>
&gt;<BR>
&gt;&gt; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . =
. . .<BR>
&gt;&gt;<BR>
&gt;&gt; IPFIX: Proposal for new work<BR>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Based on discussion at IETF =
69, Chicago<BR>
&gt;&gt;<BR>
&gt;&gt; For IPFIX mailing list, we suggest that items 1-6<BR>
&gt;&gt; (above the --- line) be adopted as new WG work items.<BR>
&gt;&gt; Please comment by 6 Aug 07 &lt;&lt;&lt;&lt;<BR>
&gt;&gt; Also, we need reviewers; please fill in and email back the<BR>
&gt;&gt; questionnaire form below!!<BR>
&gt;&gt;<BR>
<BR>
...<BR>
<BR>
&gt;&gt;<BR>
&gt;&gt; 2. SCTP Per-Stream Draft (Benoit Claise)<BR>
&gt;&gt;&nbsp;&nbsp; Agreed: Needs to be explored, as a possible protocol=
=20option.<BR>
&gt;&gt;&nbsp;&nbsp; Procedure: Make this a WG item, as Experimental RFC.=
<BR>
&gt;&gt;&nbsp;&nbsp; Milestones:&nbsp; WG LC after IETF 70, to IESG befor=
e IETF&nbsp; 71.<BR>
&gt;<BR>
&gt; It's unclear to me that, after the stream restriction change in poin=
t 0.<BR>
&gt; above, this should be Experimental as opposed to Informational... Pe=
r<BR>
&gt; 2026, Experimental RFCs are intended as an archival record of a rese=
arch<BR>
&gt; work. Unless the primary intention is to change this draft to be a<B=
R>
&gt; description and evaluation of the performance benefits of this (and<=
BR>
&gt; potentially other) stream selection methods, it appears very much to=
=20be<BR>
&gt; the description of an export method (which will be in line with the<=
BR>
&gt; protocol after the stream restriction change in point 0. above) that=
=20has<BR>
&gt; potential performance and other benefits within a defined set of use=
<BR>
&gt; cases, very much like the recently-approved (Informational) Reducing=
<BR>
&gt; Redundancy draft.<BR>
&gt;<BR>
<BR>
I agree on this point. The per-stream draft is the description of an opti=
onal method for SCTP export, offering enhanced functionality for a limite=
d set of applications. Informational seems the most appropriate choice, p=
retty much for the same reasons that brought the Working Group to decide =
the status of Reducing Redundancy (i.e. informational).<BR>
<BR>
<BR>
Regards,<BR>
Elisa<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>


<P><FONT face=3D"Courier New"=20
size=3D2>****************************************************************=
**********************************<BR></FONT><FONT=20
face=3D"Courier New" size=3D2>E-mail Confidentiality Notice and Disclaime=
r.=20
</FONT></P>
<P><FONT face=3D"Courier New" size=3D2>This email and any files transmitt=
ed with it=20
are confidential and are intended solely for the use of the individual or=
=20entity=20
to which they are addressed. Access to this e-mail by anyone else is=20
unauthorised. If you are not the intended recipient,any disclosure, copyi=
ng,=20
distribution or any action taken or omitted to be taken in reliance on it=
, is=20
prohibited. <BR>E-mail messages are not necessarily secure.Hitachi does n=
ot=20
accept responsibility for any changes made to this message after it was=20
sent.<BR><BR>Please note that Hitachi checks outgoing e-mail&nbsp;message=
s for=20
the presence of computer viruses.=20
<BR>*********************************************************************=
*****************************</FONT></P>
</BODY>
</HTML>

------_=_NextPart_001_01C7D38B.09B918E7--


--===============0314250734==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix

--===============0314250734==--




From ipfix-bounces@ietf.org Tue Jul 31 13:09:14 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFvDa-0005ME-KO; Tue, 31 Jul 2007 13:09:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvDY-0005Jj-F4
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:09:08 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFvDV-0007mV-FX
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:09:08 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6VH8wuQ034125;
	Wed, 1 Aug 2007 02:08:58 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 01 Aug 2007 02:08:58 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
In-Reply-To: <46AC6D38.4010806@cisco.com>
References: <20070729030242.485A.AKOBA@nttv6.net> <46AC6D38.4010806@cisco.com>
Message-Id: <20070801002750.C845.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 01 Aug 2007 02:08:59 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f4e722e9456ead69ba4cdd21dd3d3600
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Please see in-line.

On Sun, 29 Jul 2007 11:34:32 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Here with a few replies to some of your points. I was happy with your 
> replies to all the other points, so I snipped out all that text for brevity.
> 
> 
> >>>    handling the Flow Records of each function.  In addition, this
> >>>    describes the model of the solution scenario using IPFIX Mediator.
> >>
> >> It's unclear what this last line means.
> > 
> > "this" indicates this draft.
> > This document describes the model of the solution scenario using IPFIX Mediator
> > which refer to chapter 5. 
> 
> "Solution" to what? First there would have to be a problem to solve.
> 

I see. I will add problem statements.

> 
> >> Also, what are "renewed Flow Records"?
> > 
> > This part is described about Flow Mediation.
> > 
> > I means that the "renewed Flow Records" is modified Flow Records or
> > aggregated Flow Records.
> > 
> > Modification of Flow Records means that some fields are added and deleted,
> > and whose value are modified.
> 
> That's two different kinds of modification:
> 
> 1. changing the value of the fields
> 2. changing the template and record structure (adding / removing fields)
> 

Yes.

> It would be good to make this clear - and indicate when each would be done.
> 
> 

I don't indicate that all functions are needed in Mediator. At first, I
would like to define the function of changing the Flow Records.

In next version, I will think more about description.


> >>>    generated and distributed to an appropriate Collector or traffic
> >>>    analyzer in accordance with flow content.
> >>
> >> Must the mediator understand the content? eg, what about Enterprise 
> >> Specific elements?
> > 
> > Mediator doesn't need to understand all content, as semantic. After decoding
> > by the collecting process, Flow Records are distributed in accordance
> > with specified elements contents, such as input IF indexes or Peering AS.

It might be improper description. I meant that "content" is value of
some information elements. Did I misunderstand "content"?

If the Mediator distributes Flow Records in accordance with Peering AS,
the Mediator must understand the value of Peering AS fields. But, the
Mediator does not need to see the value of other fields.

> 
> If the mediator doesn't understand the content, then it cannot do this. 
> Or at least, not do it very well.
> 
> eg, if it sees that a field is one octet, it may choose to distribute to 
> four collectors as follows:
> 
> 0x00 - 0x3F -> Collector 1
> 0x40 - 0x7F -> Collector 2
> 0x80 - 0xBF -> Collector 3
> 0xC0 - 0xFF -> Collector 4
> 
> However, the octet may only contain 6 bits of information (ie, 0x00 - 
> 0x3F) so all the traffic will go to Collector 1.
> 
> Or the field may be a counter - so traffic will be divided across the 
> collectors, depending how much was counted. That doesn't seem to make a 
> lot of sense (except perhaps, a special collector to analyse extra-small 
> or extra-large flows).
> 
> 
> > In this case, Mediator doesn't need to understand other field contents.
> > In the distribution of Flow Records, Some fields which should be understood
> > are restricted.
> 
> You mean, distribution can only be made according to some well 
> understood fields?
> 
> 
Yes. At least, mediator does not need to see the value of all fields. 
Even if the mediator can not recognize the value of some enterprise
information element, what is necessary is just to forward the Flow Records
with its fields.


> >>>       Firewall and an IPFIX concentrator are one node of IPFIX
> >>>       Mediators.
> >>
> >> This last line is unclear.
> > 
> > In next version, I will add the description about what is IPFIX Mediator.
> > I means that IPFIX Mediator is generic name of the several nodes, such as
> > the IPFIX proxy, IPFIX firewall and IPFIX concentrator.
> 
> In another mail, I had suggested that since this draft is already quite 
> complex, it might be better to divide into seperate drafts covering 
> different functions. eg, from the titles above, you could have three 
> drafts describing proxy, firewall and concentrator. You would still be 
> able to made a mediator product which complies with all three of these 
> drafts together.
> 

I would like to know other members comments.

> >> How does information get *out* of the Storing Process?
> > 
> > This part is out of scope of this document.
> > As solution, several solution can be considered.
> > 
> > In case of our system, other node, such as analyzer, submitted the query
> > that contains the specified time slot as XML, IPFIX Mediator replies this
> > query by replaying the NetFlow packets. 
> 
> OK. I think it would be good to add a small note indicating that data 
> may be retrieved from the Storing Process in different ways which are 
> outside the scope of the current work.
> 
> 
Thank you. I will add a small note.

> 
> >>>    Observation Domain ID
> >>>
> >>>       An IPFIX Mediator doesn't host the Observation Point and
> >>>       Observation Domain.  Though, the Observation Domain ID in IPFIX
> >>>       header sent by IPFIX Mediator also indicates the largest set of
> >>>       Observation Points in the Original Exporter, but this value does
> >>>       not indicate the physical entity of the Original Exporter.  If
> >>>       inputted Flow Records are aggregated in the Metering Process, the
> >>>       Observation Domain ID value in IPFIX header SHOULD be 0.
> >> I think only if the mediator is spoofing the original source exorter. 
> >> Arguably a whole new set of Observation Domain values applies on the 
> >> mediation device.
> > 
> > This part need a discussion with IPFIX members.
> > If IPFIX Proxy handles one exporting session and one collecting session,
> > simply IPFIX Proxy doesn't need to change the observation domain values.
> 
> I agree, because it's a transparent device, ie it's invisible to the 
> collector.
> 

invisible?

At least, the source ip address of IPFIX session is changed to IPFIX
proxy address. The collector presumes this address indicates the original
exporter and the observation domain is attached to this exporter.

> 
> > I think, If IPFIX Proxy handles multiple session on the both sides,
> > IPFIX Proxy needs to assign the new Observation Domain values.
> 
> I think it would be possible for a device to receive information from 
> other devices, process the information and re-report the information as 
> if it had been observed locally.
> 
> Viewed another way, we could have three IPFIX devices (A, B, C) 
> reporting to a fourth device (D) as so:
> 
> 	+----------+    +----------+    +----------+
> 	| device A |    | device B |    | device C |
> 	+----------+    +----------+    +----------+
> 	      |               |               |
> 	      +---------------+---------------+
> 	                      |
> 	                +----------+
> 	                | device D |
> 	                +----------+
> 
> 
> I believe device D could report a new observation domain as so:
> 
> 
> 	+----------------------------------------------+
> 	|                                              |
> 	| +----------+    +----------+    +----------+ |
> 	| | device A |    | device B |    | device C | |
> 	| +----------+    +----------+    +----------+ |
> 	|                                              |
> 	|                                     device D |
> 	+----------------------------------------------+
> 
> 
> In this case, device D would use its own Observation Domain IDs and not 
> have to report OD ID 0.
> 

I can consider as you mentioned. I think that setting ODID 0 is exactly
not wrong according to IPFIX protocol draft, as follows.

           The Observation Domain ID 
           SHOULD be 0 when no specific Observation Domain ID is 
           relevant for the entire IPFIX Message.  For example, when 
           exporting the Exporting Process Statistics, or in case of 
           hierarchy of Collector when aggregated data records are 
           exported.  

It might depend on the policy of device D.

> 
> >> I think any of the metering sub-processes should be able to send data to 
> >> the storing process. Also, the Exporting process may send data there too 
> >> (consider Brian's file draft). Finally, there should be a route *out* of 
> >> the storing process - either to the outside, and/or to the Metering 
> >> Process, and/or to the Exporting Process.
> >>
> > 
> > Good idea. Roughly, I can image following figure.
> > 
> >       +--------------------------------------------------------------+
> >       |                        IPFIX Mediator                        |
> >       | .----------.                                     .---------. |
> >       | |          |  .-------------------------------.  |         | |
> >       | |Collecting|  |        Metering Process       |  |Exporting| |
> >       | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
> >       | |          |--->sub    |-->sub    |->|sub    |-->|         | |
> >     IPFIX          |  ||process|  |process|  |process||  |         IPFIX
> >     --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
> >       | |          || |'-------'  '-------'  '-------'|  |         | |
> >       | |          || '----|----------|----------|----'  |         | |
> >       | |          ||      |          |          |       |         | |
> >       | |          ||   .--\/---------\/---------\/--.   |         | |
> >       | |          |'---|       Storing Process      |<--|         | |
> >       | |          |--->|                            |-->|         | |
> >       | |          |    '----------------------------'   |         | |
> >       | |          |------------------------------------>|         | |
> >       | '----------'                                     '---------' |
> >       +--------------------------------------------------------------+
> 
> Yes, this is exactly what I had in mind.
>
I will add above figure.

> 
> >>> 3.2.2.  Aggregation Process
> >>
> >> As a general question, is it valid to aggregate fields which were not 
> >> originally key fields?
> > 
> > I think that the aggregate key field does not depend on the original key
> > fields.
> 
> For sure it's possible - even if statistically it might not make any sense.
> 
> 

Please let me know in what kind of case it does not make any sense.

> >>> 4.6.  Reporting of Exporter Information
> >>>
> >>>    Reporting of Exporter Information, such as Exporter IP address, is
> >> Surely that's a loss of privacy?
> > 
> > It is depends on the role of IPFIX Mediator.
> > If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
> > becomes to grow the vulnerability.
> > On the other hand, if it is other nodes, such as concentrator, Exporter
> > IP address is important information for traffic analysis, such as traffic
> > engineering.
> > 
> > In case of making traffic matrix, Exporter IP address can indicate the
> > ingress router of network domain.
> 
> Very true. So it's worth indicating this in the draft.
> 

Yes.
> 
> 
> >>> 5.4.  Distribution of Flow Records
> >>>
> >>>    An IPFIX Mediator distributes Flow Records based on Flow Record
> >>>    content.  This function enables load balancing of Collector and
> >>>    sorting Flow Records without extra Collector functions.  If the Flow
> >>>    Records are used as accounting information, this solution is useful.
> >>
> >> It's unclear to me what this means.
> > 
> > Surely, it is too short explanation. For example, if an IPFIX Mediator
> > distributes Flow Records on the basis of input IF indexes which
> > indicates customer, measuring total traffic volume by each Collector can
> > indicate each customer's accounting information.
> 
> I see how this could work if the mediator knows which interface connects 
> to which customer or it's able to tell the collector by some means.
> 

Yes.

> > On careful thought, it is better that this sentence is omitted.
> 
> Oh?
> 
This sentence is not consistent with the meaning of the paragraph.
I will improve the paragraph.


> 
> >>>    When we disclose traffic information to each customer, security or
> >>
> >> "we"? -> The mediator, perhaps?
> >
> > I was confused how to use "we". I mean it is network service provider. 
> > The Mediator is preferable.
> 
> Sometimes people write "I" or "we" instead of the device, eg "I will 
> export" -> no, you personally won't export anything. Your device will 
> export...
> 
Yes. Thank you.

> 
> >>>    Session#b Data Record:
> >>>       Field Count = 7
> >>>       Scope Count = 1
> >>>       templateId = XXX
> >>>       exporterIPv4Address = 1.1.1.1
> >>>       collectorIPv4Address = 2.2.2.2
> >>>       collectorTransportProtocol = 16
> >>>       exporterTransportPort = 10
> >>>       collectorTransportPort = 20
> >>>       observationDomainId = 10
> >>
> >> Could you use real-world values in the examples here and below?
> >
> > Is it preferable using private address?
> 
> You could use 10. or 192. addresses.
> 
> > Surely, the destination port number should be 4739.
> 
> Exactly. And also real looking exporterTransportPort, 
> observationDomainId and so on.
> 

OK.

> Thanks.
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 31 13:09:14 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFvDa-0005ME-KO; Tue, 31 Jul 2007 13:09:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvDY-0005Jj-F4
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:09:08 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFvDV-0007mV-FX
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:09:08 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6VH8wuQ034125;
	Wed, 1 Aug 2007 02:08:58 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 01 Aug 2007 02:08:58 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Paul Aitken <paitken@cisco.com>
In-Reply-To: <46AC6D38.4010806@cisco.com>
References: <20070729030242.485A.AKOBA@nttv6.net> <46AC6D38.4010806@cisco.com>
Message-Id: <20070801002750.C845.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 01 Aug 2007 02:08:59 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f4e722e9456ead69ba4cdd21dd3d3600
Cc: ipfix@ietf.org
Subject: [IPFIX] Re: Review: draft-kobayashi-ipfix-mediator-model-00
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Paul,

Please see in-line.

On Sun, 29 Jul 2007 11:34:32 +0100
Paul Aitken <paitken@cisco.com> wrote:

> Kobayashi-san,
> 
> Here with a few replies to some of your points. I was happy with your 
> replies to all the other points, so I snipped out all that text for brevity.
> 
> 
> >>>    handling the Flow Records of each function.  In addition, this
> >>>    describes the model of the solution scenario using IPFIX Mediator.
> >>
> >> It's unclear what this last line means.
> > 
> > "this" indicates this draft.
> > This document describes the model of the solution scenario using IPFIX Mediator
> > which refer to chapter 5. 
> 
> "Solution" to what? First there would have to be a problem to solve.
> 

I see. I will add problem statements.

> 
> >> Also, what are "renewed Flow Records"?
> > 
> > This part is described about Flow Mediation.
> > 
> > I means that the "renewed Flow Records" is modified Flow Records or
> > aggregated Flow Records.
> > 
> > Modification of Flow Records means that some fields are added and deleted,
> > and whose value are modified.
> 
> That's two different kinds of modification:
> 
> 1. changing the value of the fields
> 2. changing the template and record structure (adding / removing fields)
> 

Yes.

> It would be good to make this clear - and indicate when each would be done.
> 
> 

I don't indicate that all functions are needed in Mediator. At first, I
would like to define the function of changing the Flow Records.

In next version, I will think more about description.


> >>>    generated and distributed to an appropriate Collector or traffic
> >>>    analyzer in accordance with flow content.
> >>
> >> Must the mediator understand the content? eg, what about Enterprise 
> >> Specific elements?
> > 
> > Mediator doesn't need to understand all content, as semantic. After decoding
> > by the collecting process, Flow Records are distributed in accordance
> > with specified elements contents, such as input IF indexes or Peering AS.

It might be improper description. I meant that "content" is value of
some information elements. Did I misunderstand "content"?

If the Mediator distributes Flow Records in accordance with Peering AS,
the Mediator must understand the value of Peering AS fields. But, the
Mediator does not need to see the value of other fields.

> 
> If the mediator doesn't understand the content, then it cannot do this. 
> Or at least, not do it very well.
> 
> eg, if it sees that a field is one octet, it may choose to distribute to 
> four collectors as follows:
> 
> 0x00 - 0x3F -> Collector 1
> 0x40 - 0x7F -> Collector 2
> 0x80 - 0xBF -> Collector 3
> 0xC0 - 0xFF -> Collector 4
> 
> However, the octet may only contain 6 bits of information (ie, 0x00 - 
> 0x3F) so all the traffic will go to Collector 1.
> 
> Or the field may be a counter - so traffic will be divided across the 
> collectors, depending how much was counted. That doesn't seem to make a 
> lot of sense (except perhaps, a special collector to analyse extra-small 
> or extra-large flows).
> 
> 
> > In this case, Mediator doesn't need to understand other field contents.
> > In the distribution of Flow Records, Some fields which should be understood
> > are restricted.
> 
> You mean, distribution can only be made according to some well 
> understood fields?
> 
> 
Yes. At least, mediator does not need to see the value of all fields. 
Even if the mediator can not recognize the value of some enterprise
information element, what is necessary is just to forward the Flow Records
with its fields.


> >>>       Firewall and an IPFIX concentrator are one node of IPFIX
> >>>       Mediators.
> >>
> >> This last line is unclear.
> > 
> > In next version, I will add the description about what is IPFIX Mediator.
> > I means that IPFIX Mediator is generic name of the several nodes, such as
> > the IPFIX proxy, IPFIX firewall and IPFIX concentrator.
> 
> In another mail, I had suggested that since this draft is already quite 
> complex, it might be better to divide into seperate drafts covering 
> different functions. eg, from the titles above, you could have three 
> drafts describing proxy, firewall and concentrator. You would still be 
> able to made a mediator product which complies with all three of these 
> drafts together.
> 

I would like to know other members comments.

> >> How does information get *out* of the Storing Process?
> > 
> > This part is out of scope of this document.
> > As solution, several solution can be considered.
> > 
> > In case of our system, other node, such as analyzer, submitted the query
> > that contains the specified time slot as XML, IPFIX Mediator replies this
> > query by replaying the NetFlow packets. 
> 
> OK. I think it would be good to add a small note indicating that data 
> may be retrieved from the Storing Process in different ways which are 
> outside the scope of the current work.
> 
> 
Thank you. I will add a small note.

> 
> >>>    Observation Domain ID
> >>>
> >>>       An IPFIX Mediator doesn't host the Observation Point and
> >>>       Observation Domain.  Though, the Observation Domain ID in IPFIX
> >>>       header sent by IPFIX Mediator also indicates the largest set of
> >>>       Observation Points in the Original Exporter, but this value does
> >>>       not indicate the physical entity of the Original Exporter.  If
> >>>       inputted Flow Records are aggregated in the Metering Process, the
> >>>       Observation Domain ID value in IPFIX header SHOULD be 0.
> >> I think only if the mediator is spoofing the original source exorter. 
> >> Arguably a whole new set of Observation Domain values applies on the 
> >> mediation device.
> > 
> > This part need a discussion with IPFIX members.
> > If IPFIX Proxy handles one exporting session and one collecting session,
> > simply IPFIX Proxy doesn't need to change the observation domain values.
> 
> I agree, because it's a transparent device, ie it's invisible to the 
> collector.
> 

invisible?

At least, the source ip address of IPFIX session is changed to IPFIX
proxy address. The collector presumes this address indicates the original
exporter and the observation domain is attached to this exporter.

> 
> > I think, If IPFIX Proxy handles multiple session on the both sides,
> > IPFIX Proxy needs to assign the new Observation Domain values.
> 
> I think it would be possible for a device to receive information from 
> other devices, process the information and re-report the information as 
> if it had been observed locally.
> 
> Viewed another way, we could have three IPFIX devices (A, B, C) 
> reporting to a fourth device (D) as so:
> 
> 	+----------+    +----------+    +----------+
> 	| device A |    | device B |    | device C |
> 	+----------+    +----------+    +----------+
> 	      |               |               |
> 	      +---------------+---------------+
> 	                      |
> 	                +----------+
> 	                | device D |
> 	                +----------+
> 
> 
> I believe device D could report a new observation domain as so:
> 
> 
> 	+----------------------------------------------+
> 	|                                              |
> 	| +----------+    +----------+    +----------+ |
> 	| | device A |    | device B |    | device C | |
> 	| +----------+    +----------+    +----------+ |
> 	|                                              |
> 	|                                     device D |
> 	+----------------------------------------------+
> 
> 
> In this case, device D would use its own Observation Domain IDs and not 
> have to report OD ID 0.
> 

I can consider as you mentioned. I think that setting ODID 0 is exactly
not wrong according to IPFIX protocol draft, as follows.

           The Observation Domain ID 
           SHOULD be 0 when no specific Observation Domain ID is 
           relevant for the entire IPFIX Message.  For example, when 
           exporting the Exporting Process Statistics, or in case of 
           hierarchy of Collector when aggregated data records are 
           exported.  

It might depend on the policy of device D.

> 
> >> I think any of the metering sub-processes should be able to send data to 
> >> the storing process. Also, the Exporting process may send data there too 
> >> (consider Brian's file draft). Finally, there should be a route *out* of 
> >> the storing process - either to the outside, and/or to the Metering 
> >> Process, and/or to the Exporting Process.
> >>
> > 
> > Good idea. Roughly, I can image following figure.
> > 
> >       +--------------------------------------------------------------+
> >       |                        IPFIX Mediator                        |
> >       | .----------.                                     .---------. |
> >       | |          |  .-------------------------------.  |         | |
> >       | |Collecting|  |        Metering Process       |  |Exporting| |
> >       | |Process   |  |.-------.  .-------.  .-------.|  |Process  | |
> >       | |          |--->sub    |-->sub    |->|sub    |-->|         | |
> >     IPFIX          |  ||process|  |process|  |process||  |         IPFIX
> >     --> |          |.->|#1     |  |#2     |  |#3     ||  |         |-->
> >       | |          || |'-------'  '-------'  '-------'|  |         | |
> >       | |          || '----|----------|----------|----'  |         | |
> >       | |          ||      |          |          |       |         | |
> >       | |          ||   .--\/---------\/---------\/--.   |         | |
> >       | |          |'---|       Storing Process      |<--|         | |
> >       | |          |--->|                            |-->|         | |
> >       | |          |    '----------------------------'   |         | |
> >       | |          |------------------------------------>|         | |
> >       | '----------'                                     '---------' |
> >       +--------------------------------------------------------------+
> 
> Yes, this is exactly what I had in mind.
>
I will add above figure.

> 
> >>> 3.2.2.  Aggregation Process
> >>
> >> As a general question, is it valid to aggregate fields which were not 
> >> originally key fields?
> > 
> > I think that the aggregate key field does not depend on the original key
> > fields.
> 
> For sure it's possible - even if statistically it might not make any sense.
> 
> 

Please let me know in what kind of case it does not make any sense.

> >>> 4.6.  Reporting of Exporter Information
> >>>
> >>>    Reporting of Exporter Information, such as Exporter IP address, is
> >> Surely that's a loss of privacy?
> > 
> > It is depends on the role of IPFIX Mediator.
> > If it is IPFIX Firewall or IPFIX Proxy, exporting Exporter IP address
> > becomes to grow the vulnerability.
> > On the other hand, if it is other nodes, such as concentrator, Exporter
> > IP address is important information for traffic analysis, such as traffic
> > engineering.
> > 
> > In case of making traffic matrix, Exporter IP address can indicate the
> > ingress router of network domain.
> 
> Very true. So it's worth indicating this in the draft.
> 

Yes.
> 
> 
> >>> 5.4.  Distribution of Flow Records
> >>>
> >>>    An IPFIX Mediator distributes Flow Records based on Flow Record
> >>>    content.  This function enables load balancing of Collector and
> >>>    sorting Flow Records without extra Collector functions.  If the Flow
> >>>    Records are used as accounting information, this solution is useful.
> >>
> >> It's unclear to me what this means.
> > 
> > Surely, it is too short explanation. For example, if an IPFIX Mediator
> > distributes Flow Records on the basis of input IF indexes which
> > indicates customer, measuring total traffic volume by each Collector can
> > indicate each customer's accounting information.
> 
> I see how this could work if the mediator knows which interface connects 
> to which customer or it's able to tell the collector by some means.
> 

Yes.

> > On careful thought, it is better that this sentence is omitted.
> 
> Oh?
> 
This sentence is not consistent with the meaning of the paragraph.
I will improve the paragraph.


> 
> >>>    When we disclose traffic information to each customer, security or
> >>
> >> "we"? -> The mediator, perhaps?
> >
> > I was confused how to use "we". I mean it is network service provider. 
> > The Mediator is preferable.
> 
> Sometimes people write "I" or "we" instead of the device, eg "I will 
> export" -> no, you personally won't export anything. Your device will 
> export...
> 
Yes. Thank you.

> 
> >>>    Session#b Data Record:
> >>>       Field Count = 7
> >>>       Scope Count = 1
> >>>       templateId = XXX
> >>>       exporterIPv4Address = 1.1.1.1
> >>>       collectorIPv4Address = 2.2.2.2
> >>>       collectorTransportProtocol = 16
> >>>       exporterTransportPort = 10
> >>>       collectorTransportPort = 20
> >>>       observationDomainId = 10
> >>
> >> Could you use real-world values in the examples here and below?
> >
> > Is it preferable using private address?
> 
> You could use 10. or 192. addresses.
> 
> > Surely, the destination port number should be 4739.
> 
> Exactly. And also real looking exporterTransportPort, 
> observationDomainId and so on.
> 

OK.

> Thanks.
> -- 
> Paul Aitken
> Cisco Systems Ltd, Edinburgh, Scotland.
> 

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 31 13:25:00 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFvSr-0006x3-5n; Tue, 31 Jul 2007 13:24:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvSq-0006ww-8z
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:24:56 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFvSo-0008DQ-Jx
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:24:56 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6VHOrhq034230;
	Wed, 1 Aug 2007 02:24:54 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 01 Aug 2007 02:24:54 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46AEFC3B.1090505@informatik.uni-tuebingen.de>
References: <46AE4984.3050109@cisco.com>
	<46AEFC3B.1090505@informatik.uni-tuebingen.de>
Message-Id: <20070801021823.C848.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 01 Aug 2007 02:24:54 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Gerhard,

I understood what you thought. 
The description of each functions, aggregation, anonymization and filtering
might be better to move to other drafts. I would like to know other
IPFIX members comments about this approach.

To prevent from being misunderstood, I do not intend to restrict these
functions in mediator. Even if the IPFIX mediator draft describes the
several functions, I think that it is hard to say that they are
restricted in only mediator functions.

First of all, the concept of flow includes the aggregated Flow and fine
grained Flow. It implies the metering process of the original exporter
covers the aggregation function.
And also, the filtering function of Flow Records seems to be covered by
the process of the original Exporter according to IPFIX architecture
draft figure 6. 

Regards,
Atsushi KOBAYASHI


On Tue, 31 Jul 2007 11:09:15 +0200
Gerhard Muenz <muenz@informatik.uni-tuebingen.de> wrote:

> 
> Kobayashi, Paul, all,
> 
> Paul Aitken wrote:
> > Kobayashi-san,
> > 
> > 
> >>>> The aggregation draft is very specific, while your mediator draft is
> >>>> very broad.
> >>>
> >>> This is a good point. I wonder whether it would be better to divide
> >>> the mediator into several separate and more general drafts which
> >>> vendors could implement in a single product?
> >>
> >> Do you mean my draft should be separated into each device, as follows?
> >>
> >> - IPFIX concentrator
> >> - IPFIX proxy
> >> - IPFIX firewall
> >> - IPFIX distributor It distributes Flow Records to several collectors.
> >> My draft has not
> >> described enough, yet.
> >> ...
> >>
> >> I can't name the flow mediation device that modifies the Flow Records.
> >>
> >> Surely, making up the drafts of each device is one of approaches.
> > 
> > Exactly, instead of covering such a broad scope in one draft. However,
> > it's only one possible approach.
> 
> IPFIX concentrator, IPFIX proxy, IPFIX firewall, IPFIX distributor etc.,
> do we really need to distinguish between this whole bunch of new devices?
> 
> I think these expressions reflect more the role or function of a
> mediator within a given network.
> 
> The question is also, if operators really need all of these new
> functionalities, or if we talk about potentially useful things that will
> never be used in practice.
> 
> >> But, IPFIX protocol considerations and internal component might become
> >> similar description. Other things could be common parts.
> >> I think that making up the document of similar devices might be unhappy.
> >> Even if becoming the separated drafts, the overview draft of IPFIX
> >> Mediators might be necessary for common parts.
> > 
> > True.
> > 
> > 
> >> Roughly, it could be separated into the IPFIX protocol Mediation draft
> >> and the Flow Mediation draft.
> >>
> >> And also, the Flow Mediation could be separated into changing the
> >> granularity of Flow, such as filtering and aggregation, and changing the
> >> content of Flow Records, such as modification.
> >>
> >> But yet, should my draft be separated into some devices?
> > 
> > I had hoped some other IPFIX-ers would comment.
> 
> I see the following two aspects:
> 
> 1) *Relaying and multiplexing of IPFIX transport sessions* without
> changing or filtering the data. This is currently called "protocol
> mediation". If this function is really requested by operators, there are
> some issues to be solved, like:
> - how to translate knowledge about the original observation domain into
> option data?
> - how to convert relative timestamps?
> - how to do the template management, especially in case of multiplexing?
> 
> 2) *Filtering, anonymization and aggregation* of measurement data.
> This is currently called "flow mediation", yet I think that it should
> not be restricted to flow data, and also not be restricted to mediators.
> The issues here are mostly related to the reporting of what is going on
> in the Metering Process, i.e. what kind of filtering, what kind of
> anonymization, what kind of aggregation etc. takes place.
> I think that all these functions are not specific to the Mediator, i.e.
> they can also be implemented in a usual exporter. So I would not cover
> them in a mediator draft, but in a more generic draft (or several
> problem-specific ones) describing advanced functions within the Metering
> Process and how to report them.
> 
> Regards,
> Gerhard
> 
> 
> -- 
> Dipl.-Ing. Gerhard M$B".(Bz
> Computer Networks and Internet
> Wilhelm Schickard Institute for Computer Science
> University of Tuebingen
> Sand 13 (Room B309), D-72076 Tuebingen, Germany
> Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
> E-mail: muenz@informatik.uni-tuebingen.de
> WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From ipfix-bounces@ietf.org Tue Jul 31 13:25:01 2007
Return-path: <ipfix-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFvSr-0006x3-5n; Tue, 31 Jul 2007 13:24:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvSq-0006ww-8z
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:24:56 -0400
Received: from mail.nttv6.net ([2001:fa8::25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFvSo-0008DQ-Jx
	for ipfix@ietf.org; Tue, 31 Jul 2007 13:24:56 -0400
Received: from [127.0.0.1] (mail.nttv6.net [192.68.245.115])
	by mail.nttv6.net (8.14.1/8.14.1) with ESMTP id l6VHOrhq034230;
	Wed, 1 Aug 2007 02:24:54 +0900 (JST) (envelope-from akoba@nttv6.net)
Date: Wed, 01 Aug 2007 02:24:54 +0900
From: kobayashi atsushi <akoba@nttv6.net>
To: Gerhard Muenz <muenz@informatik.uni-tuebingen.de>
Subject: Re: [IPFIX] *Proposed* new work items, take two
In-Reply-To: <46AEFC3B.1090505@informatik.uni-tuebingen.de>
References: <46AE4984.3050109@cisco.com>
	<46AEFC3B.1090505@informatik.uni-tuebingen.de>
Message-Id: <20070801021823.C848.AKOBA@nttv6.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.02 [ja]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(mail.nttv6.net [192.68.245.115]);
	Wed, 01 Aug 2007 02:24:54 +0900 (JST)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: ipfix@ietf.org
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipfix>,
	<mailto:ipfix-request@ietf.org?subject=subscribe>
Errors-To: ipfix-bounces@ietf.org


Hi Gerhard,

I understood what you thought. 
The description of each functions, aggregation, anonymization and filtering
might be better to move to other drafts. I would like to know other
IPFIX members comments about this approach.

To prevent from being misunderstood, I do not intend to restrict these
functions in mediator. Even if the IPFIX mediator draft describes the
several functions, I think that it is hard to say that they are
restricted in only mediator functions.

First of all, the concept of flow includes the aggregated Flow and fine
grained Flow. It implies the metering process of the original exporter
covers the aggregation function.
And also, the filtering function of Flow Records seems to be covered by
the process of the original Exporter according to IPFIX architecture
draft figure 6. 

Regards,
Atsushi KOBAYASHI


On Tue, 31 Jul 2007 11:09:15 +0200
Gerhard Muenz <muenz@informatik.uni-tuebingen.de> wrote:

> 
> Kobayashi, Paul, all,
> 
> Paul Aitken wrote:
> > Kobayashi-san,
> > 
> > 
> >>>> The aggregation draft is very specific, while your mediator draft is
> >>>> very broad.
> >>>
> >>> This is a good point. I wonder whether it would be better to divide
> >>> the mediator into several separate and more general drafts which
> >>> vendors could implement in a single product?
> >>
> >> Do you mean my draft should be separated into each device, as follows?
> >>
> >> - IPFIX concentrator
> >> - IPFIX proxy
> >> - IPFIX firewall
> >> - IPFIX distributor It distributes Flow Records to several collectors.
> >> My draft has not
> >> described enough, yet.
> >> ...
> >>
> >> I can't name the flow mediation device that modifies the Flow Records.
> >>
> >> Surely, making up the drafts of each device is one of approaches.
> > 
> > Exactly, instead of covering such a broad scope in one draft. However,
> > it's only one possible approach.
> 
> IPFIX concentrator, IPFIX proxy, IPFIX firewall, IPFIX distributor etc.,
> do we really need to distinguish between this whole bunch of new devices?
> 
> I think these expressions reflect more the role or function of a
> mediator within a given network.
> 
> The question is also, if operators really need all of these new
> functionalities, or if we talk about potentially useful things that will
> never be used in practice.
> 
> >> But, IPFIX protocol considerations and internal component might become
> >> similar description. Other things could be common parts.
> >> I think that making up the document of similar devices might be unhappy.
> >> Even if becoming the separated drafts, the overview draft of IPFIX
> >> Mediators might be necessary for common parts.
> > 
> > True.
> > 
> > 
> >> Roughly, it could be separated into the IPFIX protocol Mediation draft
> >> and the Flow Mediation draft.
> >>
> >> And also, the Flow Mediation could be separated into changing the
> >> granularity of Flow, such as filtering and aggregation, and changing the
> >> content of Flow Records, such as modification.
> >>
> >> But yet, should my draft be separated into some devices?
> > 
> > I had hoped some other IPFIX-ers would comment.
> 
> I see the following two aspects:
> 
> 1) *Relaying and multiplexing of IPFIX transport sessions* without
> changing or filtering the data. This is currently called "protocol
> mediation". If this function is really requested by operators, there are
> some issues to be solved, like:
> - how to translate knowledge about the original observation domain into
> option data?
> - how to convert relative timestamps?
> - how to do the template management, especially in case of multiplexing?
> 
> 2) *Filtering, anonymization and aggregation* of measurement data.
> This is currently called "flow mediation", yet I think that it should
> not be restricted to flow data, and also not be restricted to mediators.
> The issues here are mostly related to the reporting of what is going on
> in the Metering Process, i.e. what kind of filtering, what kind of
> anonymization, what kind of aggregation etc. takes place.
> I think that all these functions are not specific to the Mediator, i.e.
> they can also be implemented in a usual exporter. So I would not cover
> them in a mediator draft, but in a more generic draft (or several
> problem-specific ones) describing advanced functions within the Metering
> Process and how to report them.
> 
> Regards,
> Gerhard
> 
> 
> -- 
> Dipl.-Ing. Gerhard M$B".(Bz
> Computer Networks and Internet
> Wilhelm Schickard Institute for Computer Science
> University of Tuebingen
> Sand 13 (Room B309), D-72076 Tuebingen, Germany
> Phone:  +49 7071 29-70534       Fax: +49 7071 29-5220
> E-mail: muenz@informatik.uni-tuebingen.de
> WWW:    http://net.informatik.uni-tuebingen.de/~muenz

--- 
Atsushi KOBAYASHI  <akoba@nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637


_______________________________________________
IPFIX mailing list
IPFIX@ietf.org
https://www1.ietf.org/mailman/listinfo/ipfix



From sygbcbarrickboh@bcbarrick.com Tue Jul 31 16:00:24 2007
Return-path: <sygbcbarrickboh@bcbarrick.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IFxtI-0002hi-Mt; Tue, 31 Jul 2007 16:00:24 -0400
Received: from abrb31.neoplus.adsl.tpnet.pl ([83.8.95.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IFxtG-00044F-In; Tue, 31 Jul 2007 16:00:24 -0400
Received: from [83.8.95.31] by bcbarrick.com; Tue, 31 Jul 2007 20:00:23 -0100
Date:	Tue, 31 Jul 2007 20:00:23 -0100
From:	"Brittney Grimes" <sygbcbarrickboh@bcbarrick.com>
X-Mailer: The Bat! (v2.00.8) Business
Reply-To: sygbcbarrickboh@bcbarrick.com
X-Priority: 3 (Normal)
Message-ID: <412156188.90424665021995@bcbarrick.com>
To: idmr-archive@lists.ietf.org
Subject: Olny this 5 days special price on pharma for you dear customer
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="----------0146E3C09888F46E"
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

------------0146E3C09888F46E
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Best Greetings!!! 
Incomparable offer for you Our Dear Customer!!!
Only these 5 days for our byers incredible offer!!! 
On all medicinal remedies you want!!!   
Fill in your life with colours of bliss!!!  
http://boughtdecimal.cn/ 

Truly Yours, 
Online association of druggists
------------0146E3C09888F46E
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<strong><font color="#1CA82E"><em>Best Greetings!!! </em></font><br>
Incomparable offer for you <font color="#FF0000"><em>Our Dear Customer!!!</em></font><br>
Only these <font color="#FF0000"><em>5 days</em></font> for our byers incredible offer!!! <br>
On all medicinal remedies you want!!! </strong> <strong><br><br> 
<a href="http://boughtdecimal.cn/" target="_blank"><em>Fill in your life with colours of bliss!!! </em></a></strong> 
<font color="#D9EDFF">http://boughtdecimal.cn/</font><br><br> 

<strong>Truly Yours,<br> 
<em>Online association of druggists</em></strong></p>

</BODY></HTML>
------------0146E3C09888F46E--





