Video Games r' Me

______ [|Orchard Bank|] _______

_An Orchard Bank Mastercard offer for you!_

_Get a Fast Decision on a new MasterCard_ "-

_You're invited to apply for an Orchard Bank MasterCard_ "-

___________________________________
__optoutlink__

[| HSBC Card Services, Inc |1441 Schilling Place|Salinas, CA .3912 |]

____________________________________________
__Unsubscribe for mailling__ Names and descriptions of the possible FROM and TO fields: N: aol ; America Online; America Online, Inc.; commercial; N: alternex ; AlterNex; IBASE; non-profit; N: applelink ; AppleLink; Apple Computer, Inc.; commercial; N: arcom ; ArCom; Swiss PTT; commercial; X.400 only N: att ; AT&T Mail; AT&T; commercial; N: bitnet ; BITNET; none; academic; N: bix ; Byte Information eXchange; Byte magazine; commercial; N: bmug ; BMUG ; Berkeley Macintosh Users Group; in-house; N: bulmail ; BULMAIL; Sprint; commercial; N: calvacom ; Calvacom; - Reseau & Communication Informatique (RCI-Calvacom); commercial; N: chasque ; Chasque; Instituto del Tercer Mundo; non-profit; N: comlink ; ComLink; ? ; non-profit; N: compuserve ; CompuServe; CompuServe Inc.; commercial; N: connect ; Connect Professional Information Network; ?; commercial; N: easylink ; Easylink; AT&T; commercial; N: easynet ; Easynet; DEC; in-house; N: econet ; EcoNet; Institute for Global Communications; non-profit; N: envoy ; Envoy-100; Telecom Canada; commercial; X.400 N: fax ; Facsimile document transmission; none; none; N: fidonet ; FidoNet; none; bbs; N: fmedia ; Francomedia; Francomedia; non-profit; N: fr/atlas ; FR/ATLAS ; X400 ADMD France Telecom Transpac ; commercial; N: genie ; GEnie; GE Information Services; commercial; N: geonet ; GeoNet Mailbox Systems; - Geonet Mailbox Services GmbH/Systems Inc.; commercial; N: glasnet ; GlasNet; ? ; non-profit; N: gold-400 ; GNS Gold 400; British Telecom; commercial; X.400 N: goldgate ; GoldGate Telcom Gold; Net-Tel Computer Systems; ?; N: greennet ; GreenNet; Soft Solutions Ltd; commercial; N: gsfcmail ; GSFCmail; NASA/Goddard Space Flight Center; in-house; N: ibm ; VNET; IBM; in-house; N: ibmmail ; IBM Mail Exchange; IBM; commercial; N: internet ; Internet; none; academic; N: keylink ; KeyLink; Telecom Australia; commercial; X.400 N: mausnet ; Mausnet; Mausnet; non-profit; N: mci ; MCIMail; MCI; commercial; N: nicarao ; Nicarao; CRIES; non-profit; N: niftyserve ; Nifty Serve; Nissho Iwai and Fujitsu; commercial; N: nordnet ; NordNet; ? ; non-profit; N: nsi ; NASA Science Internet; NASA; government; - Dual-protocol: instructions given here pertain only to NSI-DECnet addresses - (NSI-TCP/IP addresses should be treated as shown for 'internet') N: omnet ; OMNET; OMNET; commercial; N: peacenet ; PeaceNet/EcoNet; Institute for Global Communications; - non-profit; N: pegasus ; Pegasus; Pegasus Networks; non-profit; N: prodigy ; PRODIGY; commercial; ?; N: pronet ; Pro-Net Australia; National Info. Resource Gateway; ?; N: satlink ; Argentina SatLink Internet Services; - SatLink Internet Services; commercial; N: se/atlas ; SE/ATLAS ; X400 ADMD France Telecom - SWEDEN ; commercial; N: sinet ; Schlumberger Information NETwork; ?; ?; N: sprintmail ; SprintMail; Sprint; commercial; From: yanoff@alumni.cs.uwm.edu (Scott A. Yanoff) Newsgroups: comp.mail.misc, alt.bbs.lists, alt.internet.services, comp.misc Subject: Updated Inter-Network Mail Guide Date: 22 Apr 1997 21:42:36 GMT Message-ID: <5jjbcc$phk@uwm.edu> Summary: No changes recently. Archive-name: mail/inter-network-guide VERSION: $Date: 2/28/97 $ * INTER-NETWORK MAIL GUIDE: Last Update: 2/28/97 * Further mods (C) Copyright 1997 Scott Yanoff (yanoff@alumni.cs.uwm.edu) (Inter-Network Mail Guide - Original Copyright (C) 1992 by John J. Chew) This guide is available via anonymous ftp to: ftp.csd.uwm.edu Also via WWW/Mosaic, URL is: http://alpha.acast.nova.edu/cgi-bin/inmgq.pl INTRODUCTION This file documents methods of sending mail from one network to another. It represents the aggregate knowledge of the readers of comp.mail.misc and many contributors elsewhere. If you know of any corrections or additions to this file, please follow the instructions in the section entitled 'HOW TO FORMAT INFORMATION FOR SUBMISSION' and then mail the information to me: Scott A. Yanoff <yanoff@alpha2.csd.uwm.edu>. HOW TO USE THIS GUIDE If you just want to browse the guide manually for information, this is what you need to know. The guide is organized as a list of entries. Each entry tells you how to get from one network to another. Here is what a typical entry might look like: FROM: mynet TO: yournet RECIPIENT: youraddress CONTACT: contactaddress INSTR: send to 'youraddress@thegateway' This means that to send mail FROM a network called 'mynet' TO a RECIPIENT address 'youraddress' on a network called 'yournet', you should follow the INSTRUCTIONS shown and address your mail to 'youraddress@thegateway'. N: telecom ; Telecom Australia; National Videotex Network; ?; N: telkom400 ; Telkom 400; South African X400 Commercial Network; ?; N: thenet ; Texas Higher Education Network; University of Texas; - academic ; N: unisys ; Unisys' Mapper Mail; Unisys; in-house; N: web ; The Web; Nirv Community Resource Centre; non-profit; N: wwivnet ; WWIVnet; WWIVnet; non-profit; The 'RECIPIENT' record gives an example of an address on the destination network, to make it clear in subsequent lines what text requires subsitution. The 'CONTACT' record gives an address for inquiries concerning the gateway, expressed as an address reachable from the source (#FROM:) network. Presumably, if you can't get the gateway to work at all, then knowing an unreachable address on another network will not be of great help. The 'INSTR' records, of which there may be several, give verbal instructions to a user of the source network to let them send mail to a user on the destination network. Text that needs to be typed will appear in double quotes, with C-style escapes if necessary. If the instructions consist simply of mailing to a certain address, this will be indicated by the words 'send to' followed by a quoted address. If there are alternative addresses, they will be marked 'or to' instead. HOW TO FORMAT INFORMATION FOR SUBMISSION Here is what I really want in the way of information. If you are adding a new network to the list, tell me what its official name is (pay attention to capitalization), what the name of its responsible organization is, and what kind of a network it is (academic, commercial, government, in-house or non-profit). If this isn't clear, look at the examples above. For each connection, give me an entry that looks something like: FROM: foonet TO: barnet RECIPIENT: baraddress CONTACT: contactaddress INSTR: send to 'baraddress@thegateway' Note that 'contactaddress' must be an address expressed in foonet's native format, and not that of barnet, since if a user is having trouble accessing barnet, giving him/her an address on that net to contact for help is not productive. If there is no contact/postmaster address, please tell me. If there are more complicated instructions, use additional #INSTR: lines. Once you've got all the information together, send it to me in an e-mail message with the words 'INMG update' in the Subject: line. You can in general expect an answer back from me within a week. FROM: aol TO: applelink RECIPIENT: user CONTACT: Internet INSTR: send to 'user@applelink' FROM: aol TO: compuserve RECIPIENT: 71234,567 CONTACT: Internet INSTR: send to '71234.567@cis' FROM: aol TO: genie RECIPIENT: user CONTACT: Internet INSTR: send to 'user@genie' FROM: aol TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: Internet INSTR: send to 'user@creditcardwisdom.net' FROM: applelink TO: bitnet RECIPIENT: user@site INSTR: send to 'user@site.bitnet@internet#' FROM: applelink TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'user@creditcardwisdom.net@internet#' (address must be < 35 characters) FROM: arcom TO: internet RECIPIENT: G=test; S=user; O=organization; A=arcom; C=ch; CONTACT: postmaster@switch.ch INSTR: send to - '/G=test/S=user/O=organization/P=switch/A=arcom/C=ch/@chx400.switch.ch' INSTR: this should work for all servers connected to switch, INSTR: i.e. all universities, federal agencies etc. FROM: att TO: bitnet RECIPIENT: user@site INSTR: send to 'internet!site.bitnet!user' FROM: att TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'internet!creditcardwisdom.net!user' FROM: bitnet TO: ibm RECIPIENT: USER at VMNODE or (VMNODE)USER <- this is the internal syntax CONTACT: nic@vnet INSTR: send to 'useralias@vnet' INSTR: Both sender and receiver have to be registred for bitnet gateway use. INSTR: To look up if the recipient is registred on the bitnet gateway and to INSTR: get his useralias, mail to nic@vnet or nic@vnet.ibm.com with INSTR: the line 'WHOIS LASTNAME, FIRSTNAME' in the message body. FROM: bitnet TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: Methods for sending mail from Bitnet to the Internet vary depending on - what mail software is running at the Bitnet site in question. In the - best case, users should simply be able to send mail to 'user@creditcardwisdom.net'. - If this doesn't work, try 'user%creditcardwisdom.net@gateway' where 'gateway' is a - Bitnet-Internet gateway site nearby. Finally, if neither of these - works, you may have to try hand-coding an SMTP envelope for your mail. FROM: bulmail TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'C=US, A=TELEMAIL, P=INTERNET, DDA:ID = user(a)creditcardwisdom.net' INSTR: for special characters, use @=(a), %=(p), !=(b), _=(u) INSTR: Use only Body Parts: Note or TextFile. INSTR: For help send E-mail to C=BG, A=BULMAIL, S=HELPDESK INSTR: Help is also available by phoning +359 2 707435. FROM: calvacom TO: fax RECIPIENT: (1) 41 08 11 99 INSTR: send to 'TLC/41081199' INSTR: use standard phone numbers as calling from Paris, France. FROM: calvacom TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: postmaster@calvacom.fr INSTR: send to 'EM/user@creditcardwisdom.net' FROM: calvacom TO: easylink RECIPIENT: number CONTACT: 19000600 INSTR: send to 'ML/number' INSTR: Calvacom professionnal account needed. FROM: compuserve TO: fax RECIPIENT: +1 415 555 1212 INSTR: send to '>FAX:14155551212' INSTR: not transitive - message must originate from a CompuServe user INSTR: for calls outside the NANP, use the appropriate country/city codes FROM: compuserve TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'internet:user@creditcardwisdom.net' (only from CompuServe users) FROM: compuserve TO: mci RECIPIENT: ABC@XYZ CONTACT: (unknown) INSTR: send to '>MHS:ABC@XYZ' FROM: compuserve TO: niftyserve RECIPIENT: user CONTACT: postmaster@niftyserve.or.jp or call 03-5471-5800 or fax 03-5471-5890 INSTR: send to 'NIFTY:user' - Incoming messages limited to 30,000 lines for text; 1MB for binary files FROM: connect TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'DASN' - and set the first line of message: '"user@creditcardwisdom.net"@DASN' FROM: easylink TO: calvacom RECIPIENT: JS10 (John Smith) INSTR: send to '19000600 /ATTN JS10 SMITH+' FROM: easynet TO: bitnet RECIPIENT: user@site CONTACT: DECWRL::ADMIN INSTR: send to 'nm%DECWRL::"user@site.bitnet"' (from VMS using NMAIL) INSTR: send to 'user@site.bitnet' (from Ultrix) INSTR: or to 'user%site.bitnet@decwrl.dec.com' (from Ultrix via IP) INSTR: or to 'DECWRL::"user@site.bitnet"' (from Ultrix via DECN) FROM: easylink TO: internet RECIPIENT: John Doe <user@creditcardwisdom.net> CONTACT: send message to SVC+ INSTR: change @ to !, enter as a UUCP address INSTR: Line 1: IPM+ INSTR: Line 2: NAME John Doe INSTR: Line 3: ADMD ATTMAIL INSTR: Line 4: PRMD ATTMAIL INSTR: Line 5: DDA.ID=!I!N!T!E!R!N!E!T!creditcardwisdom.net!!user INSTR: Line 6: blank INSTR: Line 7: Enter text, end with NNNN as the first 4 characters - on the line. That line will not be sent. FROM: envoy TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: postmaster INSTR: send to '[RFC-822="user(a)creditcardwisdom.net"]INTERNET' INSTR: for special characters, use @=(a), !=(b), _=(u), INSTR: any=(three octal digits) FROM: fax TO: calvacom RECIPIENT: JS10 (John Smith) INSTR: send to '+33 1 41 08 11 99' INSTR: and write on every pages 'ATTN JS10 SMITH' INSTR: fax are manually processed. FROM: fidonet TO: internet RECIPIENT: user@machine.site.creditcardwisdom.net INSTR: convert to 'user@machine.site.creditcardwisdom.net ON 1:1/31 FROM: fidonet TO: wwivnet RECIPIENT: number@node CONTACT: Kevin C. ON 1:100/215 INSTR: convert to '#number @node ON 1:100/215' INSTR: WWIVgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, - they absorb cost of long distance connects to pick-up and deliver. - Keep messages under 10K, use infrequently, do NOT use mail-lists or - file/list-server commands. FROM: fmedia TO: internet RECIPIENT: user@machine.site.creditcardwisdom.net INSTR: convert to 'user@machine.site.creditcardwisdom.net ON 101:161/1 FROM: fr/atlas TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: /c=fr/admd=atlas/s=helpdesk/ (Phone: +33 99 28 33 80) INSTR: send to '/c=fr/admd=atlas/prmd=internet/dda.RFC-822=user(a)creditcardwisdom.net' FROM: genie TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: postmaster@genie.geis.com INSTR: send to user@creditcardwisdom.net@INET# FROM: geonet TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'DASN' INSTR: set subject line to 'user@creditcardwisdom.net!subject' FROM: gold-400 TO: internet RECIPIENT: user@host INSTR: send to '/DD.RFC-822=user(a)host/O=uknet/PRMD=uk.ac/ADMD=gold 400/C=GB/' INSTR: for special characters, use @=(a), %=(p), !=(b), "=(q) FROM: gsfcmail TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: cust.svc INSTR: send to '(SITE:SMTPMAIL,ID:<user(a)creditcardwisdom.net>)' INSTR: or to '(C:USA,A:TELEMAIL,P:SMTPMAIL,ID:<user(a)creditcardwisdom.net>)' INSTR: or send to 'POSTMAN' - and set the first line of message to 'To: user@creditcardwisdom.net' INSTR: Help is also available by phoning +1 800 858 9947. FROM: gsfcmail TO: nsi RECIPIENT: host::user CONTACT: cust.svc INSTR: send to '(SITE:SMTPMAIL,ID:<user(a)host.DN.NASA.GOV>)' INSTR: or to '(C:USA,A:TELEMAIL,P:SMTPMAIL,ID:<user(a)host.DN.NASA.GOV>)' INSTR: or send to 'POSTMAN' - and set the first line of message to 'To: user@host.DN.NASA.GOV' FROM: ibmmail TO: internet RECIPIENT: "userid@creditcardwisdom.net" INSTR: imbed the following lines in messages sent from IBMMAIL and address - the message to IBMMAIL(INTERNET) - /INTERNET - /TO userid1@creditcardwisdom.net - /CC userid2@creditcardwisdom.net - /REPORT - /END FROM: internet TO: alternex RECIPIENT: user CONTACT: suporte@ax.apc.org or +55 (21) 286-0348 INSTR: send to 'user@ax.apc.org' FROM: internet TO: aol RECIPIENT: user CONTACT: postmaster@aol.com INSTR: send to user@aol.com (all lower-case, remove spaces) FROM: internet TO: applelink RECIPIENT: user INSTR: send to 'user@applelink.apple.com' FROM: internet TO: arcom RECIPIENT: G=test; S=user; O=organization; A=arcom; C=ch; CONTACT: postmaster@switch.ch INSTR: send to - '/G=test/S=user/O=organization/P=switch/A=arcom/C=ch/@chx400.switch.ch' INSTR: this should work for all servers connected to switch, INSTR: i.e. all universities, federal agencies etc. FROM: internet TO: att RECIPIENT: user INSTR: send to 'user@attmail.com' FROM: internet TO: bitnet RECIPIENT: user@site INSTR: send to 'user%site.bitnet@gateway' where 'gateway' is a gateway host - that is on both the internet and bitnet. Some examples of gateways - are: cunyvm.cuny.edu mitvma.mit.edu. Check first to see what local - policies are concerning inter-network forwarding. FROM: internet TO: bix RECIPIENT: user INSTR: send to 'user@bix.com' FROM: internet TO: bmug RECIPIENT: John Smith or John J. Smith CONTACT: Email the director: Steve_Costa@bmug.org or phone (510)849-BMUG INSTR: send to 'John.Smith@bmug.org' or 'John_J_Smith@bmug.org' FROM: internet TO: bulmail RECIPIENT: (G=John, S=Smith, O=organization, A=BULMAIL, C=BG) INSTR: send to 'John.Smith/O=organization/@BULMAIL.Sprint.com' INSTR: For help send E-mail to helpdesk@bulmail.sprint.com INSTR: Help is also available by phoning +359 2 707435. FROM: internet TO: calvacom RECIPIENT: JS10 (John Smith) INSTR: send to 'js10@calvacom.fr' INSTR: msgs are limited to 100 000 chars each. FROM: internet TO: chasque RECIPIENT: user CONTACT: apoyo@chasque.apc.org or +598 (2) 496192 INSTR: send to 'user@chasque.apc.org' FROM: internet TO: comlink RECIPIENT: user CONTACT: support@oln.comlink.apc.org or +49 (511) 350-3081 INSTR: send to 'user@oln.comlink.apc.org' FROM: internet TO: compuserve RECIPIENT: 71234,567 INSTR: send to '71234.567@CompuServe.com' INSTR: Ordinary Compuserve account IDs are pairs of octal numbers FROM: internet TO: compuserve RECIPIENT: organization:department:user INSTR: send to 'user@department.organization.compuserve.com' INSTR: This syntax is for use with members of organizations which have a - private CompuServe mail area. 'department' may not always be present. FROM: internet TO: connect RECIPIENT: NAME INSTR: send to 'NAME@connectinc.com' FROM: internet TO: easylink RECIPIENT: user mail number: 62###### INSTR: send to: 62######@eln.attmail.com FROM: internet TO: easynet RECIPIENT: HOST::USER CONTACT: admin@decwrl.dec.com INSTR: send to 'user@host.enet.dec.com' INSTR: or to 'user%host.enet@decwrl.dec.com' FROM: internet TO: easynet RECIPIENT: John Smith @ABC CONTACT: admin@decwrl.dec.com INSTR: send to 'John.Smith@ABC.MTS.DEC.COM' INSTR: this syntax is for sending mail to ALL-IN-1 users FROM: internet TO: econet RECIPIENT: user CONTACT: support@igc.apc.org or +1 (415) 442-0220 INSTR: send to 'user@igc.apc.org FROM: internet TO: envoy RECIPIENT: John Smith (ID=userid) INSTR: send to 'userid@resonet.com' FROM: internet TO: envoy RECIPIENT: John Smith at Company X (G=John; S=Smith; P=Xco) INSTR: send to '/G=John/S=Smith/P=X/@tc.resonet.com' FROM: internet TO: fax RECIPIENT: 1-223-4567890 INSTR: send to 'remote-printer.comment@0.9.8.7.6.5.4.3.2.2.1.tpc.int' INSTR: 'comment' is a comment to print in fax' cover-sheet, replace spaces with - an underscore. INSTR: the zone must be covered, to have a list of covered zones mail to - tpc-coverage@town.hall.org FROM: internet TO: fmedia RECIPIENT: Jean Dupont at 101:2/3.4 (or 101:2/3.4@fmedia.ftn) INSTR: send to 'Jean.Dupont%101-2-3-4@absint.login.qc.ca' INSTR: if no point number (the 4th one) is provided you *must* add zero. - Thus, 101:12/34 is 101:12/34.0 FROM: internet TO: fr/atlas RECIPIENT: /c=fr/a=atlas/o=organization/ou=org-unit/s=name/g=givenname/ CONTACT: helpdesk@atlas.fr (Phone: +33 99 28 33 80) INSTR: send to 'givenname.name@org-unit.organization.atlas.fr' INSTR: for PRMD users, there are special mappings between X400 address INSTR: and Internet address, contact HELPDESK for more information. FROM: internet TO: genie RECIPIENT: user CONTACT: postmaster@genie.geis.com INSTR: send to user@genie.geis.com FROM: internet TO: geonet RECIPIENT: user at host INSTR: send to user@host.geonet.de INSTR: geo1 (Europe), geo2 (UK), geo4 (USA) FROM: internet TO: glasnet RECIPIENT: user CONTACT: support@glas.apc.org or +7 (095) 208-0889 INSTR: send to 'user@glas.apc.org' FROM: internet TO: gold-400 RECIPIENT: (G:John, I:Q, S:Smith, OU: org_unit, O:organization, PRMD:prmd) INSTR: send to 'john.q.smith@org_unit.org.prmd.gold-400.gb' INSTR: or to - '"/G=John/I=Q/S=Smith/OU=org_unit/O=org/PRMD=prmd/ADMD=gold 400/C=GB/" - @mhs-relay.ac.uk' FROM: internet TO: goldgate RECIPIENT: 10087:CQQ061 INSTR: send to '10087.CQQ061@goldgate.ac.uk' INSTR: or to '/G=10087/S=CQQ061/P=uk.ac/O=GoldGate/C=GB/' FROM: internet TO: greennet RECIPIENT: user CONTACT: support@gn.apc.org or +44 (71) 608-3040 INSTR: user@gn.apc.org FROM: internet TO: gsfcmail RECIPIENT: user CONTACT: naic@nasa.gov INSTR: send to 'user@gsfcmail.nasa.gov' INSTR: or to '/PN=user/ADMD=TELEMAIL/PRMD=GSFC/O=GSFCMAIL/C=US/ - @x400.msfc.nasa.gov' FROM: internet TO: ibm RECIPIENT: user@[vmnode].tertiary_creditcardwisdom.net.ibm.com CONTACT: postmaster@tertiary_creditcardwisdom.net.ibm.com INSTR: send to 'user@[vmnode].tertiary_creditcardwisdom.net.ibm.com' FROM: internet TO: ibm RECIPIENT: USER at VMNODE or (VMNODE)USER <- this is the internal syntax CONTACT: nic@vnet.ibm.com INSTR: send to 'user@vmnode.vnet.ibm.com' INSTR: The recipient has to be registered for internet email, to look up INSTR: whether he is or not, mail to nic@vnet.ibm.com with INSTR: the line 'WHOIS LASTNAME, FIRSTNAME' in the message body. FROM: internet TO: ibmmail RECIPIENT: ccsssuuu@IBMMAIL.COM CONTACT: postmaster@ibmmail.com INSTR: send to ccsssuuu@ibmmail.com - cc=country code, sss=company site, uuu=unique number (alphanumeric base 35 - <36?> number) together this form the "userid" for ibmmail. FROM: internet TO: keylink RECIPIENT: (G:John, I:Q, S:Smith, O:MyOrg, A:Telememo, C:au) CONTACT: aarnet@aarnet.edu.au INSTR: send to John.Q.Smith@MyOrg.telememo.au INSTR: for keylink Private Mail creditcardwisdom.nets such as INSTR: (G:John, S:Smith, O:MyDept, P:AusGov, A:Telememo, C:au) INSTR: send to John.Smith@MyDept.AusGov.telememo.au FROM: internet TO: mausnet RECIPIENT: hans schmidt @ box CONTACT: postmaster@hb.maus.de INSTR: send to 'hans_schmidt@box.maus.de' FROM: internet TO: mci RECIPIENT: Sam Smith <Smith%Node1%ABCMail@MCIMail.com> CONTACT: MCI_Help@MCIMail.com or (800) 444-6245 or +1 202-833-8484 INSTR: Addressing to an MCI Mail REMS mailbox from the Internet: INSTR: INSTR: The Internet user can also send a INSTR: message to an MCI Mail REMS mailbox. INSTR: The recipient's name and REMS information INSTR: is entered on one line, followed by INSTR: @MCIMail.com INSTR: INSTR: The general rule for addressing is: INSTR: INSTR: To: Full Name <mbx1%mbx2%EMS_Name@MCIMail.com> INSTR: INSTR: The percent character (%) is used to INSTR: separate the MBX lines and the EMS INSTR: name in the address. INSTR: INSTR: For example: INSTR: INSTR: To: Sam Smith <Smith%Node1%ABCMail@MCIMail.com> INSTR: is the equivalent to the following MCI Mail INSTR: REMS address: INSTR: INSTR: To: Sam Smith INSTR: EMS: ABCMail INSTR: MBX: Smith INSTR: MBX: Node1 INSTR: INSTR: There are characters that require INSTR: special treatment when included INSTR: in an envelope from the Internet. INSTR: These include ()<>@;:\"[]%_/+ INSTR: and comma and space. If any of INSTR: these characters are included in INSTR: a REMS MBX line, contact MCI Mail INSTR: Customer Support at 800 444-6245 INSTR: for information on how to treat INSTR: these characters when sending from INSTR: the Internet. FROM: internet TO: MHS/Netware host gated to MCI (1) RECIPIENT: jsmith@group (John Smith) CONTACT: 267-1163 (MCI Help) INSTR: at the `To:' prompt type INSTR: jsmith+rORGGROUPNAME@mcimail.com INSTR: Note that the first part of the address is a dummy address INSTR: for the MHS server, all relevant information is enclosed in INSTR: braces. FROM: internet TO: nicarao RECIPIENT: user CONTACT: support@nicarao.apc.org or +505 (2) 26228 INSTR: send to 'user@nicarao.apc.org' FROM: internet TO: niftyserve RECIPIENT: user CONTACT: postmaster@niftyserve.or.jp or call 03-5471-5800 or fax 03-5471-5890 INSTR: send to 'user@niftyserve.or.jp' - Mail received via the internet is limited to 3000 lines. FROM: internet TO: nordnet RECIPIENT: user CONTACT: support@pns.apc.org or +46 (8) 600-0331 INSTR: send to 'user@pns.apc.org' FROM: internet TO: nsi RECIPIENT: host::user CONTACT: naic@nasa.gov INSTR: send to 'user@host.dnet.nasa.gov' INSTR: or to 'user%host.dnet@ames.arc.nasa.gov' INSTR: or to 'user%host.dnet@east.gsfc.nasa.gov' INSTR: Help is also available by phoning +1 800 858 9947. FROM: internet TO: omnet RECIPIENT: user CONTACT: /dd.un=omnet.service/c=us/admd=telemail/o=omnet/@sprint.com INSTR: send to '/dd.un=user/o=omnet/admd=telemail/c=us/@sprint.com' INSTR: otherwise, try: user@gateway.omnet.com INSTR: Help is available by phoning +1 617 244 4333 FROM: internet TO: peacenet RECIPIENT: user CONTACT: support@igc.org INSTR: send to 'user@igc.apc.org' FROM: internet TO: pegasus RECIPIENT: user CONTACT: support@peg.apc.org or +61 (7) 2571111 INSTR: send to 'user@peg.apc.org' FROM: internet TO: prodigy RECIPIENT: user CONTACT: postmaster@prodigy.com INSTR: send to 'userid@prodigy.com' For example: abcd01a@prodigy.com FROM: internet TO: pronet RECIPIENT: user CONTACT: support@pronet.com or +61 3 349-1719 (Brian Evans) INSTR: send to 'user@tanus.oz.au' FROM: internet TO: satlink RECIPIENT: user@node CONTACT: info@satlink.net (+54-1-474-4512) INSTR: send to 'user@[node].satlink.net' FROM: internet TO: se/atlas RECIPIENT: /c=se/a=atlas/o=organization/ou=org-unit/s=name/g=givenname/ CONTACT: helpdesk@se.atlas.net (Phone: +33 99 28 33 80) INSTR: send to 'givenname.name@org-unit.organization.se.atlas.net' INSTR: for PRMD users, there are special mappings between X400 address INSTR: and Internet address, contact HELPDESK for more information. FROM: internet TO: sinet RECIPIENT: node::user or node1::node::user INSTR: send to 'user@node.SINet.SLB.COM' INSTR: or to 'user%node@node1.SINet.SLB.COM' FROM: internet TO: sprintmail RECIPIENT: John Smith at SomeOrganization INSTR: send to - '/G=John/S=Smith/O=SomeOrganization/ADMD=TELEMAIL/C=US/@Sprint.COM' Help is available by phoning +1 800 877 5045 FROM: internet TO: telecom RECIPIENT: user CONTACT: support@pronet.com or +61 3 349-1719 (Brian Evans) INSTR: send to 'user@viatel.pronet.com' INSTR: User mailboxes consist of a 9 digit number. INSTR: Eg: the postmaster at viatel could be reached INSTR: at 010000003@viatel.pronet.com. User mailbox INSTR: queries can be directed to: postmaster@viatel.pronet.com FROM: Internet TO: telkom400 RECIPIENT: Donald Duck CONTACT: Helpdesk at TEL 0800228400 or +27-21-454321 ext 210 or 256 or 252 CONTACT: Helpdesk@X400.telkom400.inca.za CONTACT: Autoanswer@X400.telkom400.inca.za INSTR: For a Registered User send to - Donald.Duck@X400.telkom400.inca.za - For an Unregistered used send to - oas@emx.telkom400.inca.za - First Line in Body of Message use Standard X400 adding format of - emg: - To: C=za a=telkom400 S=Donald G=Duck - emg: - Body of message follows - You Should be able to use all the valid X400 addressing commands FROM: internet TO: thenet RECIPIENT: user@host INSTR: send to 'user%host.decnet@utadnx.cc.utexas.edu' FROM: internet TO: unisys RECIPIENT: 0123/EMMK CONTACT: INSTR: send to EMMK.0123@ofis.unisys.com FROM: internet TO: web RECIPIENT: user CONTACT: spider@web.apc.org or +1 (416) 596-0212 INSTR: send to 'user@web.apc.org FROM: internet TO: wwivnet RECIPIENT: number@node CONTACT: faq-request@tfsquad.mn.org or bryen@tfsquad.mn.org INSTR: convert to 'number-node@wwiv.tfsquad.mn.org' INSTR: WWCPgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, - they absorb cost of long distance connects to pick-up and deliver. - Keep messages under 10K, use infrequently, do NOT use mail-lists or - file/list-server commands. FROM: keylink TO: internet RECIPIENT: John Smith <user@creditcardwisdom.net> CONTACT: (G:CUSTOMER, S:SERVICE, O:CUST.SERVICE, P:telememo, C:au) INSTR: send to '(C:au, A:telememo, P:oz.au, "RFC-822":"John Smith - <user(a)creditcardwisdom.net>")' INSTR: special characters must be mapped: @->(a), %->(p), !->(b), "->(q) FROM: mausnet TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: sysop@k2 INSTR: send to 'user@creditcardwisdom.net' FROM: mci TO: compuserve RECIPIENT: John Smith (71234,567) CONTACT: 267-1163 (MCI Help) INSTR: at the 'To:' prompt type 'John Smith (EMS)' INSTR: at the 'EMS:' prompt type 'compuserve' INSTR: at the first 'Mbx:' prompt type 'P=CSMail' INSTR: at the second 'Mbx:' prompt type 'D=ID=71234,567' FROM: mci TO: internet RECIPIENT: John Smith <user@creditcardwisdom.net> CONTACT: 267-1163 (MCI Help) INSTR: at the 'To:' prompt type 'John Smith (EMS)' INSTR: at the 'EMS:' prompt type 'INTERNET' INSTR: at the 'Mbx:' prompt type 'user@creditcardwisdom.net' FROM: MHS/Netware host gated to MCI TO: internet RECIPIENT: John Smith <jsmith@host.creditcardwisdom.net> CONTACT: 267-1163 (MCI Help) INSTR: at the `To:' prompt type INSTR: jsmith@host {to: John Smith | ems: internet| mbx: jsmith@host.creditcardwisdom.net} INSTR: Note that the first part of the address is a dummy address INSTR: for the MHS server, all relevant information is enclosed in INSTR: braces. FROM: niftyseve TO: compuserve RECIPIENT: user (71234,567) CONTACT: postmaster@niftyserve.or.jp or call 03-5471-5800 or fax 03-5471-5890 INSTR: at ':' prompt type 'CIS>71234.567' - Outgoing messages limited to 300 lines. FROM: niftyserve TO: internet RECIPIENT: user CONTACT: postmaster@niftyserve.or.jp or call 03-5471-5800 or fax 03-5471-5890 INSTR: send to 'INET:user@creditcardwisdom.net' - Outgoing messages are limited to 300 lines. FROM: nsi TO: gsfcmail RECIPIENT: user CONTACT: naic@nasa.gov INSTR: send to 'east::"user@gsfcmail.nasa.gov"' INSTR: or to 'east::"/PN=user/ADMD=TELEMAIL/PRMD=GSFC/O=GSFCMAIL/C=US/ - @x400.msfc.nasa.gov' INSTR: Help is also available by phoning +1 800 858 9947. FROM: nsi TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: east::"naic@nasa.gov" INSTR: send to 'east::"user@creditcardwisdom.net"' INSTR: or to 'dftnic::"user@creditcardwisdom.net"' INSTR: or to 'nssdca::in%"user@creditcardwisdom.net"' INSTR: or to 'jpllsi::"user@creditcardwisdom.net"' INSTR: Help is also available by phoning +1 800 858 9947. FROM: nsi TO: omnet RECIPIENT: user CONTACT: omnet.service INSTR: send to 'east::"user@omnet.com"' INSTR: Help also available by phoning +1 617 244 4333 (OMN customers only) FROM: nsi TO: sprintmail RECIPIENT: John Smith at SomeOrganization CONTACT: east::"naic@nasa.gov" INSTR: send to - '/G=John/S=Smith/O=SomeOrganization/ADMD=TELEMAIL/C=US/@Sprint.COM' INSTR: Help is available by phoning +1 800 827 4685 FROM: omnet TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: omnet.service INSTR: send to '(site:internet, id:<user(a)creditcardwisdom.net>)' INSTR: Or, enter 'compose manual' at the command prompt. Choose the Internet - address option from the menu that appears. (Option 3.) INSTR: Help also available by phoning +1 617 244 4333 FROM: prodigy TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: Send to 'user@creditcardwisdom.net' after composing mail offline using Mail Manager. INSTR: From Mail Manager, hit alt-f, put dot ahead of Internet email, OK button. INSTR: Enter normal Internet creditcardwisdom.net address, subject, DONE button. Edit screen INSTR: allows message entry. SEND NOW button logs into Prodigy & sends message. INSTR: INSTR: Special note: Mail Manager software is required to send Internet mail. INSTR: It is available to subscribers for download from Prodigy. FROM: satlink TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: info@satlink.net (+54-1-474-4512) INSTR: send to 'user@creditcardwisdom.net' FROM: se/atlas TO: internet RECIPIENT: user@creditcardwisdom.net CONTACT: /c=se/admd=atlas/s=helpdesk/ INSTR: send to '/c=se/admd=atlas/prmd=internet/dda.RFC-822=user(a)creditcardwisdom.net' FROM: sinet TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'M_MAILNOW::M_INTERNET::"user@creditcardwisdom.net"' INSTR: or to 'M_MAILNOW::M_INTERNET::creditcardwisdom.net::user' FROM: sprintmail TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to '(C:USA,A:TELEMAIL,P:INTERNET,"RFC-822":<user(a)creditcardwisdom.net>) DEL' INSTR: Help is available by phoning +1 800 827 4685 INSTR: Replace each underscore in 'user' or 'creditcardwisdom.net' with '(u)'. FROM: sprintmail TO: nsi RECIPIENT: host::user INSTR: send to - '(C:USA,A:TELEMAIL,P:INTERNET,"RFC-822":<user(a)host.DNET.NASA.GOV>) DEL' INSTR: Help is available by phoning +1 800 827 4685 FROM: telkom400 TO: internet RECIPIENT: Donald.Duck@somewhere.co.za CONTACT: Helpdesk at TEL 0800228400 or +27-21-454321 ext 210 or 256 or 252 INSTR: Send To C=za admd=telkom400 prmd=telkom ddaType=rfc-822 - ddaValue=Donald.Duck(a)somewhere.co.za - For Special characters use @=(a), %=(p), !=(!), "=(q) FROM: thenet TO: internet RECIPIENT: user@creditcardwisdom.net INSTR: send to 'UTADNX::WINS%" user@creditcardwisdom.net "' FROM: unisys TO: internet RECIPIENT: john@smith.co.uk CONTACT: INSTR: Ensure first line of e-mail contains the entry: #john@smith.co.uk - Create remainder of email as normal, except in TO field type: postmaster FROM: wwivnet TO: internet RECIPIENT: user@machine.site.creditcardwisdom.net CONTACT: faq-request@9702 or 1@9702 INSTR: convert to 'user#machine.site.creditcardwisdom.net@506' - If 'user' begins with digits, begin address with a quote. INSTR: WWCPgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, - they absorb cost of long distance connects to pick-up and deliver. - Keep messages under 10K, use infrequently, do NOT use mail-lists or - file/list-server commands. -- _/\ _ !\ _ @ Milwaukee, WI - A Great Place On a Great Lake ! _! !! ! !_ ~~ @ ~ ~~ ! ! ! !! ! ! !~~__=||_~ ~~~ ! ! ! _! ! ~~~ ~\____/ ~~~ yanoff@alumni.cs.uwm.edu Message-ID: <math/algebra-help/welcome_996743981@rtfm.mit.edu> X-Last-Updated: 2001/01/06 From: brahms@mindspring.com (Stan Brown) Newsgroups: alt.algebra.help Subject: [alt.algebra.help] FAQ pointer and welcome Summary: This posting tells where to find the Frequently Asked Questions list for the newsgroup alt.algebra.help, including posting guidelines. Please read it, or at least skim the questions, before posting to alt.algebra.help. Date: 02 Aug 2001 09:20:52 GMT Archive-name: math/algebra-help/welcome Alt-algebra-help-archive-name: FAQ-pointer Posting-Frequency: every 4 days Last-modified: 2000-01-04 URL: http://oakroadsystems.com/aah/ Welcome to alt.algebra.help! To help you fit in to our community, and to help us help you most effectively, please have a look at our Frequently Asked Questions (FAQ) list at http://oakroadsystems.com/aah/ You'll find answers to some common math questions there, as well as some hints on working with the other newsgroup members. You probably want to start with these items: How do I post math expressions? <http://oakroadsystems.com/aah/xexpr.htm> I need help with my homework! <http://oakroadsystems.com/aah/xhwork1.htm> Please try to skim these for anything relevant before you post, and of course please look at <http://oakroadsystems.com/aah/> to make sure your specific question isn't answered there. Anyone can point out errors in the FAQ or suggest improvements. Once again, welcome! We look forward to your participation. (This announcement is posted about every four days. You should not see multiple copies, because it is posted with "Expires" and "Supersedes" headers. Otherwise, you may want to adjust your kill file appropriately.) <title> acedb-faq - ACEDB Genome Database Software FAQ acorn/archives - Acorn ftp and mail-server archives (fortnightly posting) acorn/faq/csafaq - Comp.Sys.Acorn.FAQ acorn/faq/part1 - Comp.Sys.Acorn.FAQ part 1 of 3 acorn/faq/part2 - Comp.Sys.Acorn.FAQ part 2 of 3 acorn/faq/part3 - Comp.Sys.Acorn.FAQ part 3 of 3 acorn/faq/part4 - Comp.Sys.Acorn.FAQ part 4 of 4 acorn/faq/part5 - Comp.Sys.Acorn.FAQ part 5 of 5 acorn/games - The comp.sys.acorn.games FAQ acorn/mailing-lists - Listing of Acorn-related Mailing-Lists acorn/networking/faq - comp.sys.acorn.networking Frequently Asked Questions acorn/programmer - The comp.sys.acorn.programmer FAQ active-newsgroups/part1 - List of Active Newsgroups (Part 1) active-newsgroups/part2 - List of Active Newsgroups (Part 2) active-newsgroups/part3 - List of Active Newsgroups (Part 3) active-noise-control-faq - Active Noise Control FAQ v1996-03-14 afs-faq - AFS distributed filesystem FAQ ai-faq/alife - comp.ai.alife Frequently Asked Questions (FAQ) ai-faq/expert/part1 - FAQ: Expert System Shells 1/1 [Monthly posting] ai-faq/general/part1 - REPOST: Artificial Intelligence FAQ: General Questions & Answers 1/6 [Monthly posting] ai-faq/general/part2 - Artificial Intelligence FAQ: Newsgroups and Mailing Lists 2/6 [Monthly posting] ai-faq/general/part3 - Artificial Intelligence FAQ: Associations and Journals 3/6 [Monthly posting] ai-faq/general/part4 - Artificial Intelligence FAQ: Bibliography 4/6 [Monthly posting] ai-faq/general/part5 - REPOST: Artificial Intelligence FAQ: AI Web Directories & Online Papers 5/6 [Monthly posting] ai-faq/general/part6 - Artificial Intelligence FAQ: Open Source AI Software 6/6 [Monthly posting] ai-faq/general/part7 - Artificial Intelligence FAQ: FTP Resources 7/7 [Monthly posting] ai-faq/genetic/part1 - FAQ: comp.ai.genetic part 1/6 (A Guide to Frequently Asked Questions) ai-faq/genetic/part2 - FAQ: comp.ai.genetic part 2/6 (A Guide to Frequently Asked Questions) ai-faq/genetic/part3 - FAQ: comp.ai.genetic part 3/6 (A Guide to Frequently Asked Questions) ai-faq/genetic/part4 - FAQ: comp.ai.genetic part 4/6 (A Guide to Frequently Asked Questions) ai-faq/genetic/part5 - FAQ: comp.ai.genetic part 5/6 (A Guide to Frequently Asked Questions) ai-faq/genetic/part6 - FAQ: comp.ai.genetic part 6/6 (A Guide to Frequently Asked Questions) ai-faq/neural-nets/part1 - comp.ai.neural-nets FAQ, Part 1 of 7: Introduction ai-faq/neural-nets/part2 - comp.ai.neural-nets FAQ, Part 2 of 7: Learning ai-faq/neural-nets/part3 - comp.ai.neural-nets FAQ, Part 3 of 7: Generalization ai-faq/neural-nets/part4 - comp.ai.neural-nets FAQ, Part 4 of 7: Books, data, etc. ai-faq/neural-nets/part5 - comp.ai.neural-nets FAQ, Part 5 of 7: Free software ai-faq/neural-nets/part6 - comp.ai.neural-nets FAQ, Part 6 of 7: Commercial software ai-faq/neural-nets/part7 - comp.ai.neural-nets FAQ, Part 7 of 7: Hardware air-industry/posting-guide - misc.transport.air-industry posting guidelines FAQ aix-faq/part1 - comp.unix.aix Frequently Asked Questions (Part 1 of 5) aix-faq/part2 - comp.unix.aix Frequently Asked Questions (Part 2 of 5) aix-faq/part3 - comp.unix.aix Frequently Asked Questions (Part 3 of 5) aix-faq/part4 - comp.unix.aix Frequently Asked Questions (Part 4 of 5) aix-faq/part5 - comp.unix.aix Frequently Asked Questions (Part 5 of 5) alt-2600/faq/part1 - alt.2600 FAQ Revision .014 (1/4) alt-2600/faq/part2 - alt.2600 FAQ Revision .014 (2/4) alt-2600/faq/part3 - alt.2600 FAQ Revision .014 (3/4) alt-2600/faq/part4 - alt.2600 FAQ Revision .014 (4/4) alt-2600/survival-guide - The alt.2600 Survival Guide alt-beer-faq - Alt.beer faq 20020123 revision alt-cellular-gsm/gsm-security-faq - GSM Security FAQ Revision 2004/06/23 - Part 1/1 alt-creation-guide - So You Want to Create an Alt Newsgroup alt-gothic-faq - alt.gothic FAQ v3.2 alt-hierarchies/alt-advice - How (not) to create Alt groups FAQ alt-hierarchies/emily-alt-advice - Emily Postnews answers your questions on how to create a new alt group alt-hierarchies/part1 - Alternative Newsgroup Hierarchies (Part 1) alt-hierarchies/part2 - Alternative Newsgroup Hierarchies (Part 2) alt-hierarchies/part3 - Alternative Newsgroup Hierarchies (Part 3) alt-hierarchies/part4 - Alternative Newsgroup Hierarchies (Part 4) alt-hierarchies/part5 - Alternative Newsgroup Hierarchies (Part 5) alt-internet-search-engines/faq - alt.internet.search-engines FAQ Revision 2004/06/23 - Part 1/1 alt-life-itself/faq - [alt.life.itself] Here are the answers alt-newsgroups/part1 - Another listing of newsgroups in the "alt" hierarchy, Part 1 of 10 alt-newsgroups/part10 - Another listing of newsgroups in the "alt" hierarchy, Part 10 of 10 alt-newsgroups/part2 - Another listing of newsgroups in the "alt" hierarchy, Part 2 of 10 alt-newsgroups/part3 - Another listing of newsgroups in the "alt" hierarchy, Part 3 of 10 alt-newsgroups/part4 - Another listing of newsgroups in the "alt" hierarchy, Part 4 of 10 alt-newsgroups/part5 - Another listing of newsgroups in the "alt" hierarchy, Part 5 of 10 alt-newsgroups/part6 - Another listing of newsgroups in the "alt" hierarchy, Part 6 of 10 alt-newsgroups/part7 - Another listing of newsgroups in the "alt" hierarchy, Part 7 of 10 alt-newsgroups/part8 - Another listing of newsgroups in the "alt" hierarchy, Part 8 of 10 alt-newsgroups/part9 - Another listing of newsgroups in the "alt" hierarchy, Part 9 of 10 alt-recovery-na-welcome - [alt.recovery.na] Welcome - read this first! alt-recovery/alcoholics-anonymous-faq - Alt.Recovery.AA Frequently Asked Questions (FAQ) 386bsd-faq/part1 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 1 of 10) 386bsd-faq/part10 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 10 of 10) 386bsd-faq/part2 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 2 of 10) 386bsd-faq/part3 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 3 of 10) 386bsd-faq/part4 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 4 of 10) 386bsd-faq/part5 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 5 of 10) 386bsd-faq/part6 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 6 of 10) 386bsd-faq/part7 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 7 of 10) 386bsd-faq/part8 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 8 of 10) 386bsd-faq/part9 - [comp.unix.bsd] NetBSD, FreeBSD, and OpenBSD FAQ (Part 9 of 10) 3b1-faq/part1 - comp.sys.3b1 FAQ part1 3b1-faq/part2 - comp.sys.3b1 FAQ part2 3d-programmer-info - FAQ: 3-D Information for the Programmer A alt-recovery/clutter - alt.recovery.clutter FAQ alt-recovery/welcome - Welcome to Alt.Recovery (FAQ) alt-sex/alt-sex-wanted-faq - alt.sex.wanted FAQ alt-sex/celibacy - Celibate FAQ, v1.7 alt-sex/fetish-fashion/part1 - alt.sex.fetish.fashion FAQ (1/9): General Information alt-sex/fetish-fashion/part2 - alt.sex.fetish.fashion FAQ (2/9): Questions & Answers alt-sex/fetish-fashion/part3 - alt.sex.fetish.fashion FAQ (3/9): Vocabulary alt-sex/fetish-fashion/part4 - alt.sex.fetish.fashion FAQ (4/9): Behind the fashions alt-sex/fetish-fashion/part5 - alt.sex.fetish.fashion FAQ (5/9): Fetish fashion in books, movies, tv etc. alt-sex/fetish-fashion/part6 - alt.sex.fetish.fashion FAQ (6/9): The Guides alt-sex/fetish-fashion/part7 - alt.sex.fetish.fashion FAQ (7/9): Supplier list - England (UK) alt-sex/fetish-fashion/part8 - alt.sex.fetish.fashion FAQ (8/9): Supplier list - Europe & Far East alt-sex/fetish-fashion/part9 - alt.sex.fetish.fashion FAQ (9/9): Supplier list - North America alt-sex/movies/part1 - asm FAQ v5.70 1/12: Welcome to alt.sex.movies alt-sex/movies/part10 - asm FAQ v5.70 10/12: What Should I Rent? alt-sex/movies/part11 - asm FAQ v5.70 11/12: Legal Issues alt-sex/movies/part12 - asm FAQ v5.70 12/12: Housekeeping alt-sex/movies/part2 - asm FAQ v5.70 2/12: Netiquette for Newbies alt-sex/movies/part3 - asm FAQ v5.70 3/12: How To Break Into Porn alt-sex/movies/part4 - asm FAQ v5.70 4/12: The Issues of Porn Production alt-sex/movies/part5 - asm FAQ v5.70 5/12: What Goes On Backstage? alt-sex/movies/part6 - asm FAQ v5.70 6/12: Celebrity Skin alt-sex/movies/part7 - asm FAQ v5.70 7/12: Porn Stars and Their Stories alt-sex/movies/part8 - asm FAQ v5.70 8/12:Bios, Magazines, Ratings and Freaks alt-sex/movies/part9 - asm FAQ v5.70 9/12: Where, What and How To Get... alt-sex/movies/welcome - ***Welcome to alt.sex.movies! *** alt-sex/pointers - Pointer to Sex Info on the Net, Ver. 5.4 alt-sex/prostitution/bibliography - [ASP] alt.sex.prostitution FAQ (4/4) alt-sex/prostitution/faq - [ASP] alt.sex.prostitution FAQ (1/4) alt-sex/prostitution/issues - [ASP] alt.sex.prostitution FAQ (2/4) alt-sex/prostitution/organizations - [ASP] alt.sex.prostitution FAQ (3/4) alt-sex/seduction/fast/official-faq - Alt.Seduction.Fast Official FAQ alt-sex/seduction/fast/welcome - alt.seduction.fast FAQ and answers v1.3 (modified 12/13/1999) alt-sex/spanking-faq - alt.sex.spanking Frequently Asked Questions (FAQ) alt-sex/stories/moderated-faq - {alt.sex.stories.moderated} Frequently Asked Questions alt-sources-intro - Welcome to alt.sources! (biweekly posting) alt-spleen/faq/part1 - 2alt.spleen FAQ - Contents (v5.7, part 1 of 5) alt-spleen/faq/part2 - alt.spleen FAQ - Basic Spleen Facts (v5.8, part 2 of 5) alt-spleen/faq/part3 - alt.spleen FAQ - General Spleen Tips (v5.7, part 3 of 5) alt-spleen/faq/part4 - alt.spleen FAQ - Spleen Trivia (v5.8, part 4 of 5) alt-spleen/faq/part5 - alt.spleen FAQ - Appendix (v5.7, part 5 of 5) alt-spleen/fobobaq - alt.spleen FOBOBAQ (version 10-5-98) alt-support-childfree/faq - FAQ Part 1 for alt.support.childfree alt-support-depression/An-ASD-Sampler/part1 - An alt.support.depression Sampler - part 1 of 3 alt-support-depression/An-ASD-Sampler/part2 - An alt.support.depression Sampler - part 2 of 3 alt-support-depression/An-ASD-Sampler/part3 - An alt.support.depression Sampler - part 3 of 3 alt-support-depression/books - Mood Disorders Bibliography - Biographical alt-support-depression/faq/part1 - alt.support.depression FAQ Part 1[5] alt-support-depression/faq/part2 - REPOST: alt.support.depression FAQ Part 2[5] alt-support-depression/faq/part3 - alt.support.depression FAQ Part 3[5] alt-support-depression/faq/part4 - alt.support.depression FAQ Part 4[5] alt-support-depression/faq/part5 - alt.support.depression FAQ Part 5[5] alt-support-depression/My-Book-List/part1 - My Book List (alt.support.depression) - part 1 of 3 alt-support-depression/My-Book-List/part2 - My Book List (alt.support.depression) - part 2 of 3 alt-support-depression/My-Book-List/part3 - My Book List (alt.support.depression) - part 3 of 3 alt-teens/faq - ALT.TEENS FAQ v 1.3 alt-usage-english-faq - alt.usage.english FAQ alt.cellular.gsm.security/faq - alt.cellular.gsm.security FAQ Revision 2004/02/10 - Part 1/1 alt.cellular.gsm/gsm-security-faq - GSM Security FAQ Revision 2004/02/11 - Part 1/1 alt.illuminati_FAQ - alt.illuminati FAQ index v. 2.0 (index) alt.sex/femdom/bibliography - The Dominatrix in Print and Other Media, Ver. 5.0 alt.tv.hercules/hfaq_1 - alt.tv.hercules FAQ (1/3) About The Usenet and alt.tv.hercules alt.tv.hercules/hfaq_2 - alt.tv.hercules FAQ (2/3) About HERCULES: THE LEGENDARY JOURNEYS & About Kevin Sorbo's Movies alt.tv.hercules/hfaq_3 - alt.tv.hercules FAQ (3/3) Personal Information About the Stars & Miscellaneous alt/magick/questions - Study Questions (alt.magicK kreEePing oOze Ref4) amiga/AmigaUUCP-FAQ/part1 - alt.sys.amiga.uucp Frequently Asked Questions (FAQ 1/2) - AmigaUUCP general information amiga/AmigaUUCP-FAQ/part2 - alt.sys.amiga.uucp Frequently Asked Questions (FAQ 2/2) - AmigaUUCP technical information amiga/AmiTCP-faq - AmiTCP/IP Frequently Asked Questions (FAQ) amiga/AMosaic-faq - Amiga Mosaic & WWW Frequently Asked Questions (FAQ) amiga/books - Amiga Related Books FAQ amiga/CD32-FAQ/part1 - Amiga CD32 Frequently Asked Questions (FAQ) - Part 1 of 2 amiga/CD32-FAQ/part2 - Amiga CD32 Frequently Asked Questions (FAQ) - Part 2 of 2 amiga/games-FAQ - comp.sys.amiga.games Frequently Asked Questions (FAQ) amiga/introduction/part1 - Amiga FAQ (Frequently asked questions) (Part 1 of 4) amiga/introduction/part2 - Amiga FAQ (Frequently asked questions) (Part 2 of 4) amiga/introduction/part3 - Amiga FAQ (Frequently asked questions) (Part 3 of 4) amiga/introduction/part4 - Amiga FAQ (Frequently asked questions) (Part 4 of 4) amiga/networking-faq/part1 - Amiga Networking Frequently Asked Questions (FAQ) Part 1/2 amiga/networking-faq/part2 - Amiga Networking Frequently Asked Questions (FAQ) Part 2/2 amstrad8bit-faq - comp.sys.amstrad.8bit FAQ v1.27 1 / 16 1/1 anarchy/theory/faq - Anarchist Theory FAQ Version 5.2 angst-faq - alt.angst FAQ -- Monthly Posting animals/dolphin-faq/index - Dolphin FAQ (Index) animals/dolphin-faq/part1 - Dolphin FAQ (1/3) animals/dolphin-faq/part2 - Dolphin FAQ (2/3) animals/dolphin-faq/part3 - Dolphin FAQ (3/3) animals/llama-alpaca - FAQ about Llamas and Alpacas animation-faq - [rec.arts.animation] Frequently Asked Questions v. 29 anime/conventions - [INFO] Anime/Manga Convention Guide anime/faq - [FAQ] rec.arts.anime.misc: Frequently Asked Questions anime/faq-lists - rec.arts.anime FAQ and Information Catalog 08-01-08 anime/misc-faq - rec.arts.anime.misc faq list (May 2002) anime/music/part1 - Anime Music FAQ for REC.ARTS.ANIME.* 1/3 anime/music/part2 - Anime Music FAQ for REC.ARTS.ANIME.* 2/3 anime/music/part3 - Anime Music FAQ for REC.ARTS.ANIME.* 3/3 anime/music/welcome - Welcome to rec.arts.anime.music [FAQ] anime/newsgroups - [INFO] Anime Newsgroup Master List 05-01-08 anime/primer - [FAQ] rec.arts.anime.misc: Anime Primer anime/resources - [FAQ] rec.arts.anime.misc: Anime Resources List anime/welcome - Welcome to rec.arts.anime.misc 05-01-08 antiques/radio+phono/faq/part1 - Rec.antiques.radio+phono General Questions(FAQ: 1/9) antiques/radio+phono/faq/part2 - Rec.antiques.radio+phono Phono Spares and Services(FAQ: 2/9) antiques/radio+phono/faq/part3 - Rec.antiques.radio+phono Phono General Questions(FAQ: 3/9) antiques/radio+phono/faq/part4 - Rec.antiques.radio+phono Radio General Questions(FAQ: 4/9) antiques/radio+phono/faq/part5 - Rec.antiques.radio+phono Radio Spares and Services(FAQ: 5/9) antiques/radio+phono/faq/part6 - Rec.antiques.radio+phono Cosmetic and Cabinet Questions(FAQ: 6/9) antiques/radio+phono/faq/part7 - Rec.antiques.radio+phono Radio Technical Questions(FAQ: 7/9) antiques/radio+phono/faq/part8 - Rec.antiques.radio+phono Tools and Test Equipment(FAQ: 8/9) antiques/radio+phono/faq/part9 - Rec.antiques.radio+phono Miscellaneous Questions(FAQ: 9/9) anu-faq - FAQ: news.software.anu-news apl-faq - APL language FAQ apple2/emulators-faq/part1 - Apple ][ Emulator Resources Guide 1.3.5 (1/1) apple2/faq/part1 - Apple II Csa2 FAQs: 1Main-Start, Part 1/25 apple2/faq/part10 - Apple II Csa2 FAQs: File Utilities, Part 10/25 apple2/faq/part11 - Apple II Csa2 FAQs: Games, Part 11/25 apple2/faq/part12 - Apple II Csa2 FAQs: Hard Disks & SCSI, Part 12/25 apple2/faq/part13 - Apple II Csa2 FAQs: Hardware Hacking, Part 13/25 apple2/faq/part14 - Apple II Csa2 FAQs: History, Part 14/25 apple2/faq/part15 - Apple II Csa2 FAQs: Input Devices, Part 15/25 apple2/faq/part16 - Apple II Csa2 FAQs: Monitors, Part 16/25 apple2/faq/part17 - Apple II Csa2 FAQs: Power & Cooling, Part 17/25 apple2/faq/part18 - Apple II Csa2 FAQs: Printers, Part 18/25 apple2/faq/part19 - Apple II Csa2 FAQs: Sound & Music, Part 19/25 apple2/faq/part2 - Apple II Csa2 FAQs: 2Main-Contents, Part 2/25 apple2/faq/part20 - Apple II Csa2 FAQs: Telecom Hardware & Transfers, Part 20/25 apple2/faq/part21 - Apple II Csa2 FAQs: Uploading & Downloading, Part 21/25 apple2/faq/part22 - Apple II Csa2 FAQs: Users' Groups, Part 22/25 apple2/faq/part23 - Apple II Csa2 FAQs: Zip Drives & Tape, Part 23/25 apple2/faq/part24 - Apple II Csa2 FAQs: 3Main-A2Websites, Part 24/25 apple2/faq/part25 - Apple II Csa2 FAQs: 4Main-GetIt, Part 25/25 apple2/faq/part3 - Apple II Csa2 FAQs: Accelerators, Part 3/25 apple2/faq/part4 - Apple II Csa2 FAQs: Applications, Part 4/25 apple2/faq/part5 - Apple II Csa2 FAQs: CD-ROM, Part 5/25 apple2/faq/part6 - Apple II Csa2 FAQs: DOS & ProDOS, Part 6/25 apple2/faq/part7 - Apple II Csa2 FAQs: Diskettes, Part 7/25 apple2/faq/part8 - Apple II Csa2 FAQs: Error List, Part 8/25 apple2/faq/part9 - Apple II Csa2 FAQs: Floppy Disk Drives, Part 9/25 apple2/GNO-faq - comp.sys.apple2.gno FAQ (v1.18) apple2/mainhall/part1 - Apple II comp.sys.apple2 FAQs, Part 1/2 apple2/mainhall/part2 - Apple II comp.sys.apple2 FAQs, Part 2/2 apple2/programmerfaq/part1 - Apple II comp.sys.apple2.programmer FAQs, Part 1/1 aquaria/general-faq/beginner - [FAQ] Aquaria: Beginning Fishkeeping aquaria/general-faq/disease - [FAQ] Aquaria: Disease, Algae and Snails aquaria/general-faq/filter - [FAQ] Aquaria: Filters aquaria/general-faq/firstfish - [FAQ] Aquaria: Good (and Bad) First Fish; Breeding aquaria/general-faq/food - [FAQ] Aquaria: Food aquaria/general-faq/intro - [FAQ] Aquaria: Newsgroup Topics and Conversion Tables aquaria/general-faq/plants - [FAQ] Aquaria: Plants aquaria/general-faq/README - [FAQ] Aquaria: Read Me First -- Contents aquaria/general-faq/resource - [FAQ] Aquaria: Societies, Books and Mailorder aquaria/general-faq/sw-begin - [FAQ] Aquaria: Beginning Saltwater aquaria/reefkeeper-faq/part1 - REEFKEEPERS FAQ: Water, Filtration, Lights, Cost (1/3) aquaria/reefkeeper-faq/part2 - REEFKEEPERS FAQ: Organisms (2/3) aquaria/reefkeeper-faq/part3 - REEFKEEPERS FAQ: Catalogs, Q&A, Books, Tables, Credits (3/3) arch-storage/part1 - comp.arch.storage FAQ 1/2 arch-storage/part2 - comp.arch.storage FAQ 2/2 argentina-faq/part1 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 1 of 8) argentina-faq/part2 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 2 of 8) argentina-faq/part3 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 3 of 8) argentina-faq/part4 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 4 of 8) argentina-faq/part5 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 5 of 8) argentina-faq/part6 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 6 of 8) argentina-faq/part7 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 7 of 8) argentina-faq/part8 - Soc.culture.Argentina & Argentine Mailing List FAQ (Part 8 of 8) arts/ascii - [FAQ] ASCII Art - answers to frequently asked questions arts/henson+muppets/faq - rec.arts.henson+muppets FAQ assembly-language/x86/a86 - x86 Assembly Language FAQ - A86 and D86 assembly-language/x86/borland - x86 Assembly Language FAQ - TASM assembly-language/x86/general/part1 - x86 Assembly Language FAQ - General Part I assembly-language/x86/general/part2 - x86 Assembly Language FAQ - General Part II assembly-language/x86/general/part3 - x86 Assembly Language FAQ - General Part III assembly-language/x86/microsoft - x86 Assembly Language FAQ - MASM astrology-faq - [alt.astrology] FAQ Part 1/1: Contents of this FAQ astrology/astrology/part1 - [alt.astrology] FAQ Part 1/11: Contents of this FAQ astrology/astrology/part10 - [alt.astrology] FAQ Part 10/11: Astrological forums outside USENET <div style='clear: both;'></div> </div> <div class='post-footer'> <div class='post-footer-line post-footer-line-1'> <span class='post-author vcard'> Posted by <span class='fn' itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://www.blogger.com/profile/05881156058110198345' itemprop='url'/> <a class='g-profile' href='https://www.blogger.com/profile/05881156058110198345' rel='author' title='author profile'> <span itemprop='name'>Fife1100</span> </a> </span> </span> <span class='post-timestamp'> at <meta content='http://vgrme.blogspot.com/2011/07/kife1100-our-records-indicate-you-may.html' itemprop='url'/> <a class='timestamp-link' href='https://vgrme.blogspot.com/2011/07/kife1100-our-records-indicate-you-may.html' rel='bookmark' title='permanent link'><abbr class='published' itemprop='datePublished' title='2011-07-15T05:21:00-07:00'>5:21 AM</abbr></a> </span> <span class='post-comment-link'> <a class='comment-link' href='https://vgrme.blogspot.com/2011/07/kife1100-our-records-indicate-you-may.html#comment-form' onclick=''> No comments: </a> </span> <span class='post-icons'> <span class='item-action'> <a href='https://www.blogger.com/email-post/7488702759706651678/6035167939372060807' title='Email Post'> <img alt='' class='icon-action' height='13' src='https://resources.blogblog.com/img/icon18_email.gif' width='18'/> </a> </span> <span class='item-control blog-admin pid-323726523'> <a href='https://www.blogger.com/post-edit.g?blogID=7488702759706651678&postID=6035167939372060807&from=pencil' title='Edit Post'> <img alt='' class='icon-action' height='18' src='https://resources.blogblog.com/img/icon18_edit_allbkg.gif' width='18'/> </a> </span> </span> <div class='post-share-buttons goog-inline-block'> </div> </div> <div class='post-footer-line post-footer-line-2'> <span class='post-labels'> </span> </div> <div class='post-footer-line post-footer-line-3'> <span class='post-location'> </span> </div> </div> </div> </div> </div></div> <div class="date-outer"> <h2 class='date-header'><span>Monday, July 11, 2011</span></h2> <div class="date-posts"> <div class='post-outer'> <div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'> <meta content='http://s.ytimg.com/yt/img/email_logo_no_tagline.png' itemprop='image_url'/> <meta content='7488702759706651678' itemprop='blogId'/> <meta content='6021623425379676631' itemprop='postId'/> <a name='6021623425379676631'></a> <h3 class='post-title entry-title' itemprop='name'> <a href='https://vgrme.blogspot.com/2011/07/your-youtube-password.html'>Your YouTube Password</a> </h3> <div class='post-header'> <div class='post-header-line-1'></div> </div> <div class='post-body entry-content' id='post-body-6021623425379676631' itemprop='description articleBody'> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tr valign="center"> <td align="left" width="180"> <a href="http://www.youtube.com/"> <img alt="YouTube" border="0" height="33" src="http://s.ytimg.com/yt/img/email_logo_no_tagline.png" width="175"> </a> </td> <td align="right"> <a href="http://www.google.com/support/youtube/bin/static.py?page=start.cs">help center</a> | <a href="http://www.youtube.com/account#notifications/events">e-mail options</a> | <a href="http://www.youtube.com/email_spam?v=1a&c=IJnyAJNKNpaxIg8DPILAPBQvNxtylnaPD43cyy8NP9cRCnGSdTPiSccajAvOIv0MKJ2PPzwi-zePcRjJ1etrBT6OBmwIDHEQM6p92yetVFScfUm3wJiljRAONs9e1QRb_l32OaIC3SDf8wKabQJa3FmtiuGGYQq6">report spam</a> </td> </tr> <tr> <td colspan="2" style="padding: 10px 0px 0px 0px;"> <h2>Hi Kife1100,</h2> <p class="largeText">Since you sign in to YouTube through Google, you need to <a href="https://www.google.com/accounts/recovery?email=Kife1100%40gmail.com">change your password</a> there.</p> <p>- The YouTube Team </p> </td> </tr> <tr> <td colspan="2" align="center" style="padding-top: 50px; color: #ccc;"> © 2011 YouTube, LLC<br> 901 Cherry Ave, San Bruno, CA 94066 </td> </tr> </table> <div style='clear: both;'></div> </div> <div class='post-footer'> <div class='post-footer-line post-footer-line-1'> <span class='post-author vcard'> Posted by <span class='fn' itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://www.blogger.com/profile/05881156058110198345' itemprop='url'/> <a class='g-profile' href='https://www.blogger.com/profile/05881156058110198345' rel='author' title='author profile'> <span itemprop='name'>Fife1100</span> </a> </span> </span> <span class='post-timestamp'> at <meta content='http://vgrme.blogspot.com/2011/07/your-youtube-password.html' itemprop='url'/> <a class='timestamp-link' href='https://vgrme.blogspot.com/2011/07/your-youtube-password.html' rel='bookmark' title='permanent link'><abbr class='published' itemprop='datePublished' title='2011-07-11T13:22:00-07:00'>1:22 PM</abbr></a> </span> <span class='post-comment-link'> <a class='comment-link' href='https://vgrme.blogspot.com/2011/07/your-youtube-password.html#comment-form' onclick=''> No comments: </a> </span> <span class='post-icons'> <span class='item-action'> <a href='https://www.blogger.com/email-post/7488702759706651678/6021623425379676631' title='Email Post'> <img alt='' class='icon-action' height='13' src='https://resources.blogblog.com/img/icon18_email.gif' width='18'/> </a> </span> <span class='item-control blog-admin pid-323726523'> <a href='https://www.blogger.com/post-edit.g?blogID=7488702759706651678&postID=6021623425379676631&from=pencil' title='Edit Post'> <img alt='' class='icon-action' height='18' src='https://resources.blogblog.com/img/icon18_edit_allbkg.gif' width='18'/> </a> </span> </span> <div class='post-share-buttons goog-inline-block'> </div> </div> <div class='post-footer-line post-footer-line-2'> <span class='post-labels'> </span> </div> <div class='post-footer-line post-footer-line-3'> <span class='post-location'> </span> </div> </div> </div> </div> </div></div> <div class="date-outer"> <h2 class='date-header'><span>Saturday, July 9, 2011</span></h2> <div class="date-posts"> <div class='post-outer'> <div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'> <meta content='http://s.ytimg.com/yt/img/logo_tagline_small.gif' itemprop='image_url'/> <meta content='7488702759706651678' itemprop='blogId'/> <meta content='6504179505439613047' itemprop='postId'/> <a name='6504179505439613047'></a> <h3 class='post-title entry-title' itemprop='name'> <a href='https://vgrme.blogspot.com/2011/07/subscription-update-jul-9-2011.html'>Subscription Update - Jul 9, 2011</a> </h3> <div class='post-header'> <div class='post-header-line-1'></div> </div> <div class='post-body entry-content' id='post-body-6504179505439613047' itemprop='description articleBody'> <table width="100%" cellspacing="0" cellpadding="0" border="0"> <tr valign="center"> <td align="left" width="180"> <a href="http://www.youtube.com/"> <img alt="YouTube" border="0" height="33" src="http://s.ytimg.com/yt/img/logo_tagline_small.gif" width="175"> </a> </td> <td align="right"> <a href="http://www.google.com/support/youtube/">Help Center</a> | <a href="http://www.youtube.com/account_notifications?feature=digest">Email Options</a> </td> </tr> <tr> <td colspan="2" style="padding: 10px 0 0 0;"> <h2>Your Latest Subscription Videos <span style="color:#666;font-weight:normal">- July 9, 2011</h2> <p>Here are the newest videos from each of your subscriptions. To change the subscriptions for which you receive updates, or to turn off updates, go to <a href="http://www.youtube.com/account_notifications?feature=digest">your email options</a>.</p> <hr style="border:1px solid #ccc;"> <br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/Trumpf?feature=digest" target="_blank"><img height="42" src="http://i3.ytimg.com/i/ZsiZ9RIRtzpoToh4noauAw/1.jpg?v=aa9182" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">Trumpf<span style="font-weight:normal;font-size:15px;color:#666;"> posted 4 new videos <a href="http://www.youtube.com/watch_videos?video_ids=ycbNmrKufBs%2CsdFXP_iVzzU%2CNogefvuSJIw%2C1plBETMURYM&force_ap=1&title=Trumpf&feature=digest" style="margin-left:10px;border:1px solid #999;padding:3px 5px;text-decoration:none;color:#222;background-color:#eee;font-size:12px;font-weight:bold;border-radius:3px;">Play all »</a></span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=ycbNmrKufBs&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i1.ytimg.com/vi/ycbNmrKufBs/default.jpg" title="This Is Just a Warmup [Game 1/5]" /></a> <div><a href="http://www.youtube.com/watch?v=ycbNmrKufBs&feature=digest" target="_blank">This Is Just a Warmup [Game 1/5]</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 26, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=sdFXP_iVzzU&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i2.ytimg.com/vi/sdFXP_iVzzU/default.jpg" title="This Was a Rough Game... [Game 2/5]" /></a> <div><a href="http://www.youtube.com/watch?v=sdFXP_iVzzU&feature=digest" target="_blank">This Was a Rough Game... [Game 2/5]</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 27, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=NogefvuSJIw&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i3.ytimg.com/vi/NogefvuSJIw/default.jpg" title="M14, It's AMAZING [Game 3/5]" /></a> <div><a href="http://www.youtube.com/watch?v=NogefvuSJIw&feature=digest" target="_blank">M14, It's AMAZING [Game 3/5]</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 28, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/Dmanlamius76?feature=digest" target="_blank"><img height="42" src="http://i3.ytimg.com/vi/Z83pyY-svFU/default.jpg" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">Dmanlamius76<span style="font-weight:normal;font-size:15px;color:#666;"> posted 1 new video </span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td><a href="http://www.youtube.com/watch?v=HQ9hfK9iCzo&feature=digest" target="_blank"><img align="top" alt="Thumbnail" src="http://i1.ytimg.com/vi/HQ9hfK9iCzo/default.jpg" title="20 thousand thankyous..." /></a></td> <td width="300" style="padding-left:10px;"><a href="http://www.youtube.com/watch?v=HQ9hfK9iCzo&feature=digest" target="_blank">20 thousand thankyous...</a> <div style="font-size:11px;color:#666;padding-top:5px">Jun 29, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/FLuffeeTalks?feature=digest" target="_blank"><img height="42" src="http://i3.ytimg.com/vi/nx_6pbOiXHw/default.jpg" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">FLuffeeTalks<span style="font-weight:normal;font-size:15px;color:#666;"> posted 5 new videos <a href="http://www.youtube.com/watch_videos?video_ids=2S3bq-5XpnM%2C7kh4ysmG4Ls%2CWM4UlumUdNA%2CM07uCQBVhKY%2CD0Gck1P3H6E&force_ap=1&title=FLuffeeTalks&feature=digest" style="margin-left:10px;border:1px solid #999;padding:3px 5px;text-decoration:none;color:#222;background-color:#eee;font-size:12px;font-weight:bold;border-radius:3px;">Play all »</a></span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=2S3bq-5XpnM&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i1.ytimg.com/vi/2S3bq-5XpnM/default.jpg" title="11 year-old STEALS CAR!" /></a> <div><a href="http://www.youtube.com/watch?v=2S3bq-5XpnM&feature=digest" target="_blank">11 year-old STEALS CAR!</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 26, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=7kh4ysmG4Ls&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i2.ytimg.com/vi/7kh4ysmG4Ls/default.jpg" title="CRACKHEAD FIGHT!" /></a> <div><a href="http://www.youtube.com/watch?v=7kh4ysmG4Ls&feature=digest" target="_blank">CRACKHEAD FIGHT!</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 27, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=WM4UlumUdNA&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i3.ytimg.com/vi/WM4UlumUdNA/default.jpg" title="WEED thrown at COP!" /></a> <div><a href="http://www.youtube.com/watch?v=WM4UlumUdNA&feature=digest" target="_blank">WEED thrown at COP!</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 28, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/RoosterTeeth?feature=digest" target="_blank"><img height="42" src="http://i3.ytimg.com/i/zH3iADRIq1IJlIXjfNgTpA/1.jpg?v=6794df" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">RoosterTeeth<span style="font-weight:normal;font-size:15px;color:#666;"> posted 14 new videos <a href="http://www.youtube.com/watch_videos?video_ids=xFYcELzCgc4%2CHq6n2v2sN1A%2CI1lPT1UFjNc%2CectBxUMJHnA%2CqXKv0oJdtjg%2CxwLCl7Pqz2E%2CC6-Rs3xQkyw%2CVPYM2nLhiK4%2CYG5915bDk_Q%2CRBm06K5eGGA%2CDJlT0RSbdTY%2CP4PENiLCAJ0%2CUw8B-nv3o8w%2CFv5_lXtlXNg&force_ap=1&title=RoosterTeeth&feature=digest" style="margin-left:10px;border:1px solid #999;padding:3px 5px;text-decoration:none;color:#222;background-color:#eee;font-size:12px;font-weight:bold;border-radius:3px;">Play all »</a></span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=xFYcELzCgc4&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i1.ytimg.com/vi/xFYcELzCgc4/default.jpg" title="Shadows of the Damned: Boner-riffic" /></a> <div><a href="http://www.youtube.com/watch?v=xFYcELzCgc4&feature=digest" target="_blank">Shadows of the Damned: Boner-riffic</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=Hq6n2v2sN1A&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i2.ytimg.com/vi/Hq6n2v2sN1A/default.jpg" title="Halo: Reach - Fails of the Weak Volume 40 (Funny Halo Screw Ups and Bloopers!)" /></a> <div><a href="http://www.youtube.com/watch?v=Hq6n2v2sN1A&feature=digest" target="_blank">Halo: Reach - Fails of the Weak Volume 40 (Funny Halo Screw Ups and Bloopers!)</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=I1lPT1UFjNc&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i3.ytimg.com/vi/I1lPT1UFjNc/default.jpg" title="Shadows of the Damned - Portal Easter Egg!" /></a> <div><a href="http://www.youtube.com/watch?v=I1lPT1UFjNc&feature=digest" target="_blank">Shadows of the Damned - Portal Easter Egg!</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/chuggaaconroy?feature=digest" target="_blank"><img height="42" src="http://i2.ytimg.com/i/IJ6_pI8ZBc_xVMPYzwQz9g/1.jpg?v=bce49f" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">chuggaaconroy<span style="font-weight:normal;font-size:15px;color:#666;"> posted 6 new videos <a href="http://www.youtube.com/watch_videos?video_ids=IhtUHXGNhqc%2CkxSfE6hsAZo%2CZJioJJEDa-Y%2CHxO64eDjxfU%2CShWBvyyWKpM%2Ch8MAuZlFjAk&force_ap=1&title=chuggaaconroy&feature=digest" style="margin-left:10px;border:1px solid #999;padding:3px 5px;text-decoration:none;color:#222;background-color:#eee;font-size:12px;font-weight:bold;border-radius:3px;">Play all »</a></span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=IhtUHXGNhqc&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i1.ytimg.com/vi/IhtUHXGNhqc/default.jpg" title="Pikmin 2 - Episode 13" /></a> <div><a href="http://www.youtube.com/watch?v=IhtUHXGNhqc&feature=digest" target="_blank">Pikmin 2 - Episode 13</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=kxSfE6hsAZo&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i2.ytimg.com/vi/kxSfE6hsAZo/default.jpg" title="Pikmin 2 - Episode 14" /></a> <div><a href="http://www.youtube.com/watch?v=kxSfE6hsAZo&feature=digest" target="_blank">Pikmin 2 - Episode 14</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 25, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=ZJioJJEDa-Y&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i3.ytimg.com/vi/ZJioJJEDa-Y/default.jpg" title="Luigi's Mansion - Episode 6" /></a> <div><a href="http://www.youtube.com/watch?v=ZJioJJEDa-Y&feature=digest" target="_blank">Luigi's Mansion - Episode 6</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 26, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/machinima?feature=digest" target="_blank"><img height="42" src="http://i4.ytimg.com/i/cMTZY1rFXO3Rj44D5VMyiw/1.jpg?v=6729ba" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">machinima<span style="font-weight:normal;font-size:15px;color:#666;"> posted 157 new videos <a href="http://www.youtube.com/watch_videos?video_ids=kP2N5OVYnFs%2CQw4bn9RP0C0%2CrrV-0lXq2d0%2C2fU2VTZI2as%2CQw4bn9RP0C0%2Cp1L2rXf9UEY%2CdmEyrinPyYg%2CEnkdKTQSxUg%2Cp1L2rXf9UEY%2CbGHkIMXqOKg%2CbGHkIMXqOKg%2C-afmBFkhWUU%2CeFfp6edjGp4%2CtjKknarkX0c%2CtjKknarkX0c%2CPSNfC8baNug%2CPSNfC8baNug%2Cu1G9GMBc76Q%2C9O-TchG14dw%2C9O-TchG14dw%2Cd58NxU4sfJM%2Cd58NxU4sfJM%2CPbpgMS8UNHA%2CPbpgMS8UNHA%2CRHshNo9k7tA%2CRHshNo9k7tA%2CmM-bfn8vZ_w%2CwT24FWoE1g0%2CwT24FWoE1g0%2CLjGahTjJLpc%2CNJyA7R9Vpo0%2ClgFE24K7VZo%2ClgFE24K7VZo%2CQSNe4Troi_E%2CQSNe4Troi_E%2CVhEzJKer4GI%2CN0ZEuNkYhg8%2CY4alRU-b5P4%2CY4alRU-b5P4%2C4x44nDFPvYY%2C4x44nDFPvYY%2CjBth9D7Oib0%2CjBth9D7Oib0%2CdSaytpmIDsk%2CGbG41v_FeuY%2CdSaytpmIDsk%2C-9wwCq5_z0g%2CGbG41v_FeuY%2CZdP0gEZRsoM%2CZdP0gEZRsoM%2CNni9QjpGSNE%2CNni9QjpGSNE%2CsrdR55V7D-s%2CsrdR55V7D-s%2CZxMj6FFm2sw%2CZxMj6FFm2sw%2CHi6RRRuc64k%2CJCGgtcpJI8g%2C8nbJfM7De6c%2CMBZ3zl56vMQ%2C8nbJfM7De6c%2Cm-qNkW3yIGg%2C2lTcUNWhj-Y%2C2lTcUNWhj-Y%2CgOvNJbjshoo%2CV-tgSGYU9fw%2CgOvNJbjshoo%2Ceoa5Npb7h4A%2C7SAIWcfHC5c%2CV-tgSGYU9fw%2Ceoa5Npb7h4A%2C0-MsST27eTg%2CshHPPYPanCE%2C0-MsST27eTg%2CshHPPYPanCE%2C1gGkrq5kj0k%2CaP7Ml9Wg6XY%2CjjFVmRnEFZc%2CaP7Ml9Wg6XY%2CjjFVmRnEFZc%2COlriLIgWCTA%2C3uF4RK7u2PM%2COlriLIgWCTA%2CjzTuzj7doTA%2CFI3gtacaN00%2C2WetkbEdC5s%2CbMhPAYXw1QA%2CbMhPAYXw1QA%2CeHNwcNwleCU%2C_jeBeP-kRjg%2CeHNwcNwleCU%2CThzvdnh0Lpg%2CwOFOiHjwmN8%2C51HEsuEznrc%2C51HEsuEznrc%2CrIOBtKzJC5M%2CxyIWyhtx0rw%2COAa4qdYNyqM%2Cf1qxptGWd3U%2COAa4qdYNyqM%2CvdcxpvSj0P8%2CvdcxpvSj0P8%2CBebSU8R1Vh4%2CgY97XgvQmDw%2CBebSU8R1Vh4%2CFpdAcwCaCNQ%2CtMAVkyBNMBg%2CFpdAcwCaCNQ%2CygEKekSQkpU%2CwXb9A6OUyMI%2CtMAVkyBNMBg%2CygEKekSQkpU%2CErChxQihYGw%2CErChxQihYGw%2C3RJdwFiDL04%2CNODOjgUZ2tk%2CNODOjgUZ2tk%2CKiR7vm1Fo3A%2CUQx7KnFyYOM%2Ck_2lMNtOZoU%2CUQx7KnFyYOM%2Ck_2lMNtOZoU%2CAKbh0GAMB4g%2CAKbh0GAMB4g%2CGwtr210jINs%2CGwtr210jINs%2CbRY-9C-2M5E%2CBeCjkwrqZYc%2CbRY-9C-2M5E%2Cge2w1dEvNJo%2Cge2w1dEvNJo%2CA7pG5NIRDec%2CA7pG5NIRDec%2Cf1RNt6iDTvs%2CBcVuynz16Tk%2CBcVuynz16Tk%2CTov8ncs-ia8%2CTov8ncs-ia8%2CyvRPBPuRS68%2CyvRPBPuRS68%2C3BOXG3ogwPk%2CL5OY9j_23Gs%2C3BOXG3ogwPk%2C7eCj6FUWknk%2CYIqhx9B8HYA%2C7eCj6FUWknk%2CpZguMCQMpmM%2CpZguMCQMpmM%2CL5eJw12hld0%2CsQ9oSurjDzc%2CsQ9oSurjDzc%2CXVIo_Tm-OeI%2Cj4XLHisOlSE%2CYwFmCrN295Y%2CYwFmCrN295Y%2C5KMc0OnLRPw%2CyL1p0HRsBiM&force_ap=1&title=machinima&feature=digest" style="margin-left:10px;border:1px solid #999;padding:3px 5px;text-decoration:none;color:#222;background-color:#eee;font-size:12px;font-weight:bold;border-radius:3px;">Play all »</a></span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=kP2N5OVYnFs&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i1.ytimg.com/vi/kP2N5OVYnFs/default.jpg" title="Call of Duty 4: Modern Warfare: Pubmasters 1 (CoD4 Montage)" /></a> <div><a href="http://www.youtube.com/watch?v=kP2N5OVYnFs&feature=digest" target="_blank">Call of Duty 4: Modern Warfare: Pubmasters 1 (CoD4 Montage)</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=Qw4bn9RP0C0&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i2.ytimg.com/vi/Qw4bn9RP0C0/default.jpg" title="Niko Vs The Flying Traffic of Doom (GTA IV Machinima)" /></a> <div><a href="http://www.youtube.com/watch?v=Qw4bn9RP0C0&feature=digest" target="_blank">Niko Vs The Flying Traffic of Doom (GTA IV Machinima)</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> <td style="padding-right:20px;" width="140"><a href="http://www.youtube.com/watch?v=rrV-0lXq2d0&feature=digest" target="_blank"><img alt="Thumbnail" src="http://i3.ytimg.com/vi/rrV-0lXq2d0/default.jpg" title="The Inconvenience (Minecraft Machinima)" /></a> <div><a href="http://www.youtube.com/watch?v=rrV-0lXq2d0&feature=digest" target="_blank">The Inconvenience (Minecraft Machinima)</a></div> <div style="font-size:11px;color:#666;padding-top:5px">Jun 24, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td style="padding:0 10px 0 0;"><a href="http://www.youtube.com/user/shaun0728?feature=digest" target="_blank"><img height="42" src="http://i3.ytimg.com/i/zRrheyUCB_qUrrfQ_sEG-Q/1.jpg?v=b7a187" width="42" /></a></td> <td><h3 style="margin:0;padding: 10px 0 25px">shaun0728<span style="font-weight:normal;font-size:15px;color:#666;"> posted 1 new video </span></h3> <table cellpadding="0" cellspacing="0" border="0"> <tr valign="top"> <td><a href="http://www.youtube.com/watch?v=C9hc_vUg4TA&feature=digest" target="_blank"><img align="top" alt="Thumbnail" src="http://i1.ytimg.com/vi/C9hc_vUg4TA/default.jpg" title="Sniping on Annihilation Map Pack" /></a></td> <td width="300" style="padding-left:10px;"><a href="http://www.youtube.com/watch?v=C9hc_vUg4TA&feature=digest" target="_blank">Sniping on Annihilation Map Pack</a> <div style="font-size:11px;color:#666;padding-top:5px">Jun 30, 2011</div></td> </tr> </table> </td> </tr> </table> <br><br> </td> </tr> <tr> <td colspan="2" align="center" style="padding-top: 50px; color: #CCC;"> © 2011 YouTube, LLC<br> 901 Cherry Ave, San Bruno, CA 94066 </td> </tr> </table> <div style='clear: both;'></div> </div> <div class='post-footer'> <div class='post-footer-line post-footer-line-1'> <span class='post-author vcard'> Posted by <span class='fn' itemprop='author' itemscope='itemscope' itemtype='http://schema.org/Person'> <meta content='https://www.blogger.com/profile/05881156058110198345' itemprop='url'/> <a class='g-profile' href='https://www.blogger.com/profile/05881156058110198345' rel='author' title='author profile'> <span itemprop='name'>Fife1100</span> </a> </span> </span> <span class='post-timestamp'> at <meta content='http://vgrme.blogspot.com/2011/07/subscription-update-jul-9-2011.html' itemprop='url'/> <a class='timestamp-link' href='https://vgrme.blogspot.com/2011/07/subscription-update-jul-9-2011.html' rel='bookmark' title='permanent link'><abbr class='published' itemprop='datePublished' title='2011-07-09T12:43:00-07:00'>12:43 PM</abbr></a> </span> <span class='post-comment-link'> <a class='comment-link' href='https://vgrme.blogspot.com/2011/07/subscription-update-jul-9-2011.html#comment-form' onclick=''> No comments: </a> </span> <span class='post-icons'> <span class='item-action'> <a href='https://www.blogger.com/email-post/7488702759706651678/6504179505439613047' title='Email Post'> <img alt='' class='icon-action' height='13' src='https://resources.blogblog.com/img/icon18_email.gif' width='18'/> </a> </span> <span class='item-control blog-admin pid-323726523'> <a href='https://www.blogger.com/post-edit.g?blogID=7488702759706651678&postID=6504179505439613047&from=pencil' title='Edit Post'> <img alt='' class='icon-action' height='18' src='https://resources.blogblog.com/img/icon18_edit_allbkg.gif' width='18'/> </a> </span> </span> <div class='post-share-buttons goog-inline-block'> </div> </div> <div class='post-footer-line post-footer-line-2'> <span class='post-labels'> </span> </div> <div class='post-footer-line post-footer-line-3'> <span class='post-location'> </span> </div> </div> </div> </div> </div></div> <div class="date-outer"> <h2 class='date-header'><span>Thursday, July 7, 2011</span></h2> <div class="date-posts"> <div class='post-outer'> <div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'> <meta content='7488702759706651678' itemprop='blogId'/> <meta content='3196945117987532544' itemprop='postId'/> <a name='3196945117987532544'></a> <h3 class='post-title entry-title' itemprop='name'> <a href='https://vgrme.blogspot.com/2011/07/account-alert-your-transunion.html'>- Account Alert!, Your TransUnion CreditScore Has Changed!</a> </h3> <div class='post-header'> <div class='post-header-line-1'></div> </div> <div class='post-body entry-content' id='post-body-3196945117987532544' itemprop='description articleBody'> <title> Softwire Mesh Framework Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Wu, et al. Standards Track [Page 1] RFC 5565 Softwire Mesh Framework June 2009 Abstract The Internet needs to be able to handle both IPv4 and IPv6 packets. However, it is expected that some constituent networks of the Internet will be "single-protocol" networks. One kind of single- protocol network can parse only IPv4 packets and can process only IPv4 routing information; another kind can parse only IPv6 packets and can process only IPv6 routing information. It is nevertheless required that either kind of single-protocol network be able to provide transit service for the "other" protocol. This is done by passing the "other kind" of routing information from one edge of the single-protocol network to the other, and by tunneling the "other kind" of data packet from one edge to the other. The tunnels are known as "softwires". This framework document explains how the routing information and the data packets of one protocol are passed through a single-protocol network of the other protocol. The document is careful to specify when this can be done with existing technology and when it requires the development of new or modified technology. Table of Contents 1. Introduction ....................................................3 2. Specification of Requirements ...................................6 3. Scenarios of Interest ...........................................7 3.1. IPv6-over-IPv4 Scenario ....................................7 3.2. IPv4-over-IPv6 Scenario ....................................9 4. General Principles of the Solution .............................10 4.1. E-IP and I-IP .............................................10 4.2. Routing ...................................................10 4.3. Tunneled Forwarding .......................................11 5. Distribution of Inter-AFBR Routing Information .................11 6. Softwire Signaling .............................................13 7. Choosing to Forward through a Softwire .........................15 8. Selecting a Tunneling Technology ...............................15 9. Selecting the Softwire for a Given Packet ......................16 10. Softwire OAM and MIBs .........................................17 10.1. Operations and Maintenance (OAM) .........................17 10.2. MIBs .....................................................18 11. Softwire Multicast ............................................18 11.1. One-to-One Mappings ......................................18 11.1.1. Using PIM in the Core .............................19 11.1.2. Using mLDP and Multicast MPLS in the Core .........20 11.2. MVPN-Like Schemes ........................................21 12. Inter-AS Considerations .......................................22 13. Security Considerations .......................................23 13.1. Problem Analysis .........................................23 13.2. Non-Cryptographic Techniques .............................24 Wu, et al. Standards Track [Page 2] RFC 5565 Softwire Mesh Framework June 2009 13.3. Cryptographic Techniques .................................26 14. References ....................................................27 14.1. Normative References .....................................27 14.2. Informative References ...................................28 15. Contributors ..................................................30 16. Acknowledgments ...............................................30 1. Introduction The routing information in any IP backbone network can be thought of as being in one of two categories: "internal routing information" or "external routing information". The internal routing information consists of routes to the nodes that belong to the backbone, and to the interfaces of those nodes. External routing information consists of routes to destinations beyond the backbone, especially destinations to which the backbone is not directly attached. In general, BGP [RFC4271] is used to distribute external routing information, and an Interior Gateway Protocol (IGP) such as OSPF [RFC2328] or IS-IS [RFC1195] is used to distribute internal routing information. Often an IP backbone will provide transit routing services for packets that originate outside the backbone and whose destinations are outside the backbone. These packets enter the backbone at one of its "edge routers". They are routed through the backbone to another edge router, after which they leave the backbone and continue on their way. The edge nodes of the backbone are often known as "Provider Edge" (PE) routers. The term "ingress" (or "ingress PE") refers to the router at which a packet enters the backbone, and the term "egress" (or "egress PE") refers to the router at which it leaves the backbone. Interior nodes are often known as "P routers". Routers that are outside the backbone but directly attached to it are known as "Customer Edge" (CE) routers. (This terminology is taken from [RFC4364].) When a packet's destination is outside the backbone, the routing information that is needed within the backbone in order to route the packet to the proper egress is, by definition, external routing information. Traditionally, the external routing information has been distributed by BGP to all the routers in the backbone, not just to the edge routers (i.e., not just to the ingress and egress points). Each of the interior nodes has been expected to look up the packet's destination address and route it towards the egress point. This is known as "native forwarding": the interior nodes look into each packet's header in order to match the information in the header with the external routing information. Wu, et al. Standards Track [Page 3] RFC 5565 Softwire Mesh Framework June 2009 It is, however, possible to provide transit services without requiring that all the backbone routers have the external routing information. The routing information that BGP distributes to each ingress router specifies the egress router for each route. The ingress router can therefore "tunnel" the packet directly to the egress router. "Tunneling the packet" means putting on some sort of encapsulation header that will force the interior routers to forward the packet to the egress router. The original packet is known as the "encapsulation payload". The P routers do not look at the packet header of the payload but only at the encapsulation header. Since the path to the egress router is part of the internal routing information of the backbone, the interior routers then do not need to know the external routing information. This is known as "tunneled forwarding". Of course, before the packet can leave the egress, it has to be decapsulated. The scenario where the P routers do not have external routes is sometimes known as a "BGP-free core". That is something of a misnomer, though, since the crucial aspect of this scenario is not that the interior nodes don't run BGP, but that they don't maintain the external routing information. In recent years, we have seen this scenario deployed to support VPN services, as specified in [RFC4364]. An edge router maintains multiple independent routing/addressing spaces, one for each VPN to which it interfaces. However, the routing information for the VPNs is not maintained by the interior routers. In most of these scenarios, MPLS is used as the encapsulation mechanism for getting the packets from ingress to egress. There are some deployments in which an IP-based encapsulation, such as L2TPv3 (Layer 2 Transport Protocol) [RFC3931] or GRE (Generic Routing Encapsulation) [RFC2784] is used. This same technique can also be useful when the external routing information consists not of VPN routes, but of "ordinary" Internet routes. It can be used any time it is desired to keep external routing information out of a backbone's interior nodes, or in fact any time it is desired for any reason to avoid the native forwarding of certain kinds of packets. This framework focuses on two such scenarios. 1. In this scenario, the backbone's interior nodes support only IPv6. They do not maintain IPv4 routes at all, and are not expected to parse IPv4 packet headers. Yet, it is desired to use such a backbone to provide transit services for IPv4 packets. Therefore, tunneled forwarding of IPv4 packets is Wu, et al. Standards Track [Page 4] RFC 5565 Softwire Mesh Framework June 2009 required. Of course, the edge nodes must have the IPv4 routes, but the ingress must perform an encapsulation in order to get an IPv4 packet forwarded to the egress. 2. This scenario is the reverse of scenario 1, i.e., the backbone's interior nodes support only IPv4, but it is desired to use the backbone for IPv6 transit. In these scenarios, a backbone whose interior nodes support only one of the two address families is required to provide transit services for the other. The backbone's edge routers must, of course, support both address families. We use the term "Address Family Border Router" (AFBR) to refer to these PE routers. The tunnels that are used for forwarding are referred to as "softwires". These two scenarios are known as the "Softwire Mesh Problem" [SW-PROB], and the framework specified in this document is therefore known as the "Softwire Mesh Framework". In this framework, only the AFBRs need to support both address families. The CE routers support only a single address family, and the P routers support only the other address family. It is possible to address these scenarios via a large variety of tunneling technologies. This framework does not mandate the use of any particular tunneling technology. In any given deployment, the choice of tunneling technology is a matter of policy. The framework accommodates at least the use of MPLS ([RFC3031], [RFC3032]) -- both LDP-based (Label Distribution Protocol, [RFC5036]) and RSVP-TE-based (Resource Reservation Protocol - Traffic Engineering, [RFC3209]) -- L2TPv3 [RFC3931], GRE [RFC2784], and IP-in-IP [RFC2003]. The framework will also accommodate the use of IPsec tunneling, when that is necessary in order to meet security requirements. It is expected that, in many deployments, the choice of tunneling technology will be made by a simple expression of policy, such as "always use IP-IP tunnels", or "always use LDP-based MPLS", or "always use L2TPv3". However, other deployments may have a mixture of routers, some of which support, say, both GRE and L2TPv3, but others of which support only one of those techniques. It is desirable therefore to allow the network administration to create a small set of classes, and to configure each AFBR to be a member of one or more of these classes. Then the routers can advertise their class memberships to each other, and the encapsulation policies can be expressed as, e.g., "use L2TPv3 to tunnel to routers in class X; use GRE to tunnel to routers in 3.1. IPv6-over-IPv4 Scenario In this scenario, the client networks run IPv6 but the backbone network runs IPv4. This is illustrated in Figure 1. +--------+ +--------+ | IPv6 | | IPv6 | | Client | | Client | | Network| | Network| +--------+ +--------+ | \ / | | \ / | | \ / | | X | | / \ | | / \ | | / \ | +--------+ +--------+ | AFBR | | AFBR | +--| IPv4/6 |---| IPv4/6 |--+ | +--------+ +--------+ | +--------+ | | +--------+ | IPv4 | | | | IPv4 | | Client | | | | Client | | Network|------| IPv4 |-------| Network| +--------+ | only | +--------+ | | | +--------+ +--------+ | +--| AFBR |---| AFBR |--+ | IPv4/6 | | IPv4/6 | +--------+ +--------+ | \ / | | \ / | | \ / | | X | | / \ | | / \ | | / \ | +--------+ +--------+ | IPv6 | | IPv6 | | Client | | Client | | Network| | Network| +--------+ +--------+ Figure 1: IPv6-over-IPv4 Scenario Wu, et al. Standards Track [Page 7] RFC 5565 Softwire Mesh Framework June 2009 The IPv4 transit core may or may not run MPLS. If it does, MPLS may be used as part of the solution. While Figure 1 does not show any "backdoor" connections among the client networks, this framework assumes that there will be such connections. That is, there is no assumption that the only path between two client networks is via the pictured transit-core network. Hence, the routing solution must be robust in any kind of topology. Many mechanisms for providing IPv6 connectivity across IPv4 networks have been devised over the past ten years. A number of different tunneling mechanisms have been used, some provisioned manually, and others based on special addressing. More recently, L3VPN (Layer 3 Virtual Private Network) techniques from [RFC4364] have been extended to provide IPv6 connectivity, using MPLS in the AFBRs and, optionally, in the backbone [V6NLRI-V4NH]. The solution described in this framework can be thought of as a superset of [V6NLRI-V4NH], with a more generalized scheme for choosing the tunneling (softwire) technology. In this framework, MPLS is allowed -- but not required -- even at the AFBRs. As in [V6NLRI-V4NH], there is no manual provisioning of tunnels, and no special addressing is required. Wu, et al. Standards Track [Page 8] RFC 5565 Softwire Mesh Framework June 2009 3.2. IPv4-over-IPv6 Scenario In this scenario, the client networks run IPv4 but the backbone network runs IPv6. This is illustrated in Figure 2. +--------+ +--------+ | IPv4 | | IPv4 | | Client | | Client | | Network| | Network| +--------+ +--------+ | \ / | | \ / | | \ / | | X | | / \ | | / \ | | / \ | +--------+ +--------+ | AFBR | | AFBR | +--| IPv4/6 |---| IPv4/6 |--+ | +--------+ +--------+ | +--------+ | | +--------+ | IPv6 | | | | IPv6 | | Client | | | | Client | | Network|------| IPv6 |-------| Network| +--------+ | only | +--------+ | | | +--------+ +--------+ | +--| AFBR |---| AFBR |--+ | IPv4/6 | | IPv4/6 | +--------+ +--------+ | \ / | | \ / | | \ / | | X | | / \ | | / \ | | / \ | +--------+ +--------+ | IPv4 | | IPv4 | | Client | | Client | | Network| | Network| +--------+ +--------+ The choice of tunneling technology is a matter of policy configured at the ingress AFBR. It is envisioned that, in most cases, the policy will be a very simple one, and will be the same at all the AFBRs of a given transit core -- e.g., "always use LDP-based MPLS" or "always use L2TPv3". However, other deployments may have a mixture of routers, some of which support, say, both GRE and L2TPv3, but others of which support only one of those techniques. It is desirable therefore to allow the network administration to create a small set of classes and to configure each AFBR to be a member of one or more of these classes. Then the routers can advertise their class memberships to each other, and the encapsulation policies can be expressed as, e.g., "use L2TPv3 to talk to routers in class X; use GRE to talk to routers in class Wu, et al. Standards Track [Page 15] RFC 5565 Softwire Mesh Framework June 2009 Y". To support such policies, it is necessary for the AFBRs to be able to advertise their class memberships. [RFC5512] specifies a way in which an AFBR may advertise, to other AFBRS, various characteristics that may be relevant to the policy (e.g., "I belong to class Y"). In many cases, these characteristics can be represented by arbitrarily selected communities or extended communities, and the policies at the ingress can be expressed in terms of these classes (i.e., communities). Policy may also require a certain class of traffic to receive a certain quality of service, and this may impact the choice of tunnel and/or tunneling technology used for packets in that class. This framework allows a variety of tunneling technologies to be used for instantiating softwires. The choice of tunneling technology is a matter of policy, as discussed in Section 1. While in many cases the policy will be unconditional, e.g., "always use L2TPv3 for softwires", in other cases the policy may specify that the choice is conditional upon information about the softwire remote endpoint, e.g., "use L2TPv3 to talk to routers in class X; use GRE to talk to routers in class Y". It is desirable therefore to allow the network administration to create a small set of classes, and to configure each AFBR to be a member of one or more of these classes. If each such class is represented as a community or extended community, then [RFC5512] specifies a method that AFBRs can use to advertise their class memberships to each other. This framework also allows for policies of arbitrary complexity, which may depend on characteristics or attributes of individual address prefixes as well as on QoS or security considerations. However, the specification of such policies is not within the scope of this document. 9. Selecting the Softwire for a Given Packet Suppose it has been decided to send a given packet through a softwire. Routing provides the address, in the address family of the transport network, of the BGP next hop. The packet MUST be sent through a softwire whose remote endpoint address is the same as the BGP next hop address. Sending a packet through a softwire is a matter of first encapsulating the packet with an encapsulation header that can be processed by the transit network and then transmitting towards the softwire's remote endpoint address. Wu, et al. Standards Track [Page 16] RFC 5565 Softwire Mesh Framework June 2009 In many cases, once one knows the remote endpoint address, one has all the information one needs in order to form the encapsulation header. This will be the case if the tunnel technology instantiating the softwire is, e.g., LDP-based MPLS, IP-in-IP, or GRE without optional header fields. If the tunnel technology being used is L2TPv3 or GRE with optional header fields, additional information from the remote endpoint is needed in order to form the encapsulation header. The procedures for sending and receiving this information are described in [RFC5512]. will be impacted. There are several techniques available to monitor the status of the tunnel endpoints (AFBRs) as well as the tunnels themselves. These techniques allow operations such as softwire path tracing, remote softwire endpoint pinging, and remote softwire endpoint liveness failure detection. Examples of techniques applicable to softwire OAM include: o BGP/TCP timeouts between AFBRs o ICMP or LSP echo request and reply addressed to a particular AFBR o BFD (Bidirectional Forwarding Detection) [BFD] packet exchange between AFBR routers Another possibility for softwire OAM is to build something similar to [RFC4378] or, in other words, to create and generate softwire echo request/reply packets. The echo request sent to a well-known UDP port would contain the egress AFBR IP address and the softwire identifier as the payload (similar to the MPLS Forwarding Equivalence Wu, et al. Standards Track [Page 17] RFC 5565 Softwire Mesh Framework June 2009 Class contained in the LSP echo request). The softwire echo packet would be encapsulated with the encapsulation header and forwarded across the same path (inband) as that of the softwire itself. This mechanism can also be automated to periodically verify remote softwire endpoint reachability, with the loss of reachability being signaled to the softwire application on the local AFBR, thus enabling suitable actions to be taken. Consideration must be given to the trade-offs between the scalability of such mechanisms versus the time required for detection of loss of endpoint reachability for such automated mechanisms. In general, a framework for softwire OAM can, for a large part, be based on the [RFC4176] framework. 10.2. MIBs Specific MIBs do exist to manage elements of the Softwire Mesh Framework. However, there will be a need to either extend these MIBs or create new ones that reflect the functional elements that can be SNMP-managed within the softwire network. 11. Softwire Multicast A set of client networks, running E-IP, that are connected to a provider's I-IP transit core may wish to run IP multicast applications. Extending IP multicast connectivity across the transit core can be done in a number of ways, each with a different set of characteristics. Most (though not all) of the possibilities are either slight variations of the procedures defined for L3VPNs in [L3VPN-MCAST]. We will focus on supporting those multicast features and protocols that are typically used across inter-provider boundaries. Support is provided for PIM-SM (Protocol Independent Multicast - Sparse Mode) and PIM-SSM (PIM Source-Specific Mode). Support for BIDIR-PIM (Bidirectional PIM), BSR (Bootstrap Router Mechanism for PIM), and AutoRP (Automatic Rendezvous Point Determination) is not provided as these features are not typically used across inter-provider boundaries. 11.1. One-to-One Mappings In the "one-to-one mapping" scheme, each client multicast tree is extended through the transit core so that for each client tree there is exactly one tree through the core. Wu, et al. Standards Track [Page 18] RFC 5565 Softwire Mesh Framework June 2009 The one-to-one scheme is not used in [L3VPN-MCAST] because it requires an amount of state in the core routers that is proportional to the number of client multicast trees passing through the core. In the VPN context, this is considered undesirable because the amount of state is unbounded and out of the control of the service provider. However, the one-to-one scheme models the typical "Internet multicast" scenario where the client network and the transit core are both IPv4 or both IPv6. If it scales satisfactorily for that case, it should also scale satisfactorily for the case where the client network and the transit core support different versions of IP. 11.1.1. Using PIM in the Core When an AFBR receives an E-IP PIM control message from one of its CEs, it translates it from E-IP to I-IP, and forwards it towards the source of the tree. Since the routers in the transit core will not generally have a route to the source of the tree, the AFBR must include an "RPF (Reverse Path Forwarding) Vector" [RFC5496] in the PIM message. Suppose an AFBR A receives an E-IP PIM Join/Prune message from a CE for either an (S,G) tree or a (*,G) tree. The AFBR would have to "translate" the PIM message into an I-IP PIM message. It would then send it to the neighbor that is the next hop along the route to the root of the (S,G) or (*,G) tree. In the case of an (S,G) tree, the root of the tree is S; in the case of a (*,G) tree, the root of the tree is the Rendezvous Point (RP) for the group G. Note that the address of the root of the tree will be an E-IP address. Since the routers within the transit core (other than the AFBRs) do not have routes to E-IP addresses, A must put an RPF Vector [RFC5496] in the PIM Join/Prune message that it sends to its upstream neighbor. The RPF Vector will identify, as an I-IP address, the AFBR B that is the egress point in the transit network along the route to the root of the multicast tree. AFBR B is AFBR A's BGP next hop for the route to the root of the tree. The RPF Vector allows the core routers to forward PIM Join/Prune messages upstream towards the root of the tree, even though they do not maintain E-IP routes. In order to translate an E-IP PIM message into an I-IP PIM message, the AFBR A must translate the address of S (in the case of an (S,G) group) or the address of G's RP from the E-IP address family to the I-IP address family, and the AFBR B must translate them back. In the case where E-IP is IPv4 and I-IP is IPv6, it may be possible to do this translation algorithmically. A can translate the IPv4 S into the corresponding IPv4-mapped IPv6 address [RFC4291], and then B can translate it back. At the time of this writing, there is no such Wu, et al. Standards Track [Page 19] RFC 5565 Softwire Mesh Framework June 2009 thing as an IPv4-mapped IPv6 multicast address, but if such a thing were to be standardized, then A could also translate the IPv4 G into IPv6, and B could translate it back. The precise circumstances under which these translations are to be done would be a matter of policy. Obviously, this translation procedure does not generalize to the case where the client multicast is IPv6 but the core is IPv4. To handle that case, one needs additional signaling between the two AFBRs. Each downstream AFBR needs to signal the upstream AFBR that it needs a multicast tunnel for (S,G). The upstream AFBR must then assign a multicast address G' to the tunnel and inform the downstream of the P-G value to use. The downstream AFBR then uses PIM/IPv4 to join the (S',G') tree, where S' is the IPv4 address of the upstream ASBR (Autonomous System Border Router). The (S',G') trees should be SSM trees. This procedure can be used to support client multicasts of either IPv4 or IPv6 over a transit core of the opposite protocol. However, it only works when the client multicasts are SSM, since it provides no method for mapping a client "prune a source off the (*,G) tree" operation into an operation on the (S',G') tree. This method also requires additional signaling. The BGP-based signaling of [L3VPN-MCAST-BGP] is one signaling method that could be used. Other signaling methods could be defined as well. 11.1.2. Using mLDP and Multicast MPLS in the Core LDP extensions for point-to-multipoint and multipoint-to-multipoint LSPs are specified in [MLDP]; we will use the term "mLDP" to refer to those LDP extensions. If the transit core implements mLDP and supports multicast MPLS, then client Source-Specific Multicast (SSM) trees can be mapped one-to-one onto P2MP (Point-to-Multipoint) LSPs. When an AFBR A receives an E-IP PIM Join/Prune message for (S,G) from one of its CEs, where G is an SSM group, it would use mLDP to join a P2MP LSP. The root of the P2MP LSP would be the AFBR B that is A's BGP next hop on the route to S. In mLDP, a P2MP LSP is uniquely identified by a combination of its root and an "FEC (Forwarding Equivalence Class) identifier". The original (S,G) can be algorithmically encoded into the FEC identifier so that all AFBRs that need to join the P2MP LSP for (S,G) will generate the same FEC identifier. When the root of the P2MP LSP (AFBR B) receives such an mLDP message, it extracts the original (S,G) from the FEC identifier, creates an "ordinary" E-IP PIM Join/Prune message, and sends it to the CE that is its next hop on the route to S. Wu, et al. Standards Track [Page 20] RFC 5565 Softwire Mesh Framework June 2009 The method of encoding the (S,G) into the FEC identifier needs to be standardized. The encoding must be self-identifying so that a node that is the root of a P2MP LSP can determine whether a FEC identifier is the result of having encoded a PIM (S,G). The appropriate state machinery must be standardized so that PIM events at the AFBRs result in the proper mLDP events. For example, if at some point an AFBR determines (via PIM procedures) that it no longer has any downstream receivers for (S,G), the AFBR should invoke the proper mLDP procedures to prune itself off the corresponding P2MP LSP. Note that this method cannot be used when the G is a Sparse Mode group. The reason this method cannot be used is that mLDP does not have any function corresponding to the PIM "prune this source off the shared tree" function. So if a P2MP LSP were mapped one-to-one with a P2MP LSP, duplicate traffic could end up traversing the transit core (i.e., traffic from S might travel down both the shared tree and S's source tree). Alternatively, one could devise an AFBR-to-AFBR protocol to prune sources off the P2MP LSP at the root of the LSP. It is recommended, though, that client SM multicast groups be supported by other methods, such as those discussed below. Client-side bidirectional multicast groups set up by PIM-bidir could be mapped using the above technique to MP2MP (Multipoint-to- Multipoint) LSPs set up by mLDP [MLDP]. We do not consider this further, as inter-provider bidirectional groups are not in use anywhere. 11.2. MVPN-Like Schemes The "MVPN (Multicast VPN)-like schemes" are those described in [L3VPN-MCAST] and its companion documents (such as [L3VPN-MCAST-BGP]). To apply those schemes to the softwire environment, it is necessary only to treat all the AFBRs of a given transit core as if they were all, for multicast purposes, PE routers attached to the same VPN. The MVPN-like schemes do not require a one-to-one mapping between client multicast trees and transit-core multicast trees. In the MVPN environment, it is a requirement that the number of trees in the core scales less than linearly with the number of client trees. This requirement may not hold in the softwire scenarios. The MVPN-like schemes can support SM, SSM, and Bidir groups. They provide a number of options for the control plane: Wu, et al. Standards Track [Page 21] RFC 5565 Softwire Mesh Framework June 2009 - LAN-like Use a set of multicast trees in the core to emulate a LAN (Local Area Network) and run the client-side PIM protocol over that "LAN". The "LAN" can consist of a single Bidir tree containing all the AFBRs or a set of SSM trees, one rooted at each AFBR and containing all the other AFBRs as receivers. - NBMA (Non-Broadcast Multiple Access), using BGP The client-side PIM signaling can be translated into BGP-based signaling, with a BGP Route Reflector mediating the signaling. These two basic options admit of many variations; a comprehensive discussion is in [L3VPN-MCAST]. For the data plane, there are also a number of options: - All multicast data sent over the emulated LAN. This particular option is not very attractive, though, for the softwire scenarios, as every AFBR would have to receive every client multicast packet. - Every multicast group mapped to a tree that is considered appropriate for that group, in the sense of causing the traffic of that group to go to "too many" AFBRs that don't need to receive it. Again, a comprehensive discussion of the issues can be found in [L3VPN-MCAST]. 12. Inter-AS Considerations We have so far only considered the case where a "transit core" consists of a single Autonomous System (AS). If the transit core consists of multiple ASes, then it may be necessary to use softwires whose endpoints are AFBRs attached to different Autonomous Systems. In this case, the AFBR at the remote endpoint of a softwire is not the BGP next hop for packets that need to be sent on the softwire. Since the procedures described above require the address of a remote softwire endpoint to be the same as the address of the BGP next hop, those procedures do not work as specified when the transit core consists of multiple ASes. There are several ways to deal with this situation. 1. Don't do it; require that there be AFBRs at the edge of each AS so that a transit core does not extend more than one AS. Wu, et al. Standards Track [Page 22] RFC 5565 Softwire Mesh Framework June 2009 2. Use multi-hop EBGP to allow AFBRs to send BGP routes to each other, even if the ABFRs are not in the same or in neighboring ASes. 3. Ensure that an ASBR that is not an AFBR does not change the next hop field of the routes for which encapsulation is needed. In the latter two cases, BGP recursive next hop resolution needs to be done, and encapsulations may need to be "stacked" (i.e., multiple layers of encapsulation may need to be used). For instance, consider packet P with destination IP address D. Suppose it arrives at ingress AFBR A1 and that the route that is the best match for D has BGP next hop B1. So A1 will encapsulate the packet for delivery to B1. If B1 is not within A1's AS, A1 will need to look up the route to B1 and then find the BGP next hop, call it B2, of that route. If the interior routers of A1's AS do not have routes to B1, then A1 needs to encapsulate the packet a second time, this time for delivery to B2. 13. Security Considerations 13.1. Problem Analysis In the Softwire Mesh Framework, the data packets that are encapsulated are E-IP data packets that are traveling through the Internet. These data packets (the softwire "payload") may or may not need such security features as authentication, integrity, confidentiality, or replay protection. However, the security needs of the payload packets are independent of whether or not those packets are traversing softwires. The fact that a particular payload packet is traveling through a softwire does not in any way affect its security needs. Thus, the only security issues we need to consider are those that affect the I-IP encapsulation headers, rather than those that affect the E-IP payload. Since the encapsulation headers determine the routing of packets traveling through softwires, they must appear "in the clear". In the Softwire Mesh Framework, for each receiving endpoint of a tunnel, there are one or more "valid" transmitting endpoints, where the valid transmitting endpoints are those that are authorized to tunnel packets to the receiving endpoint. If the encapsulation header has no guarantee of authentication or integrity, then it is possible to have spoofing attacks, in which unauthorized nodes send Wu, et al. Standards Track [Page 23] RFC 5565 Softwire Mesh Framework June 2009 encapsulated packets to the receiving endpoint, giving the receiving endpoint the invalid impression the encapsulated packets have really traveled through the softwire. Replay attacks are also possible. The effect of such attacks is somewhat limited, though. The receiving endpoint of a softwire decapsulates the payload and does further routing based on the IP destination address of the payload. Since the payload packets are traveling through the Internet, they have addresses from the globally unique address space (rather than, e.g., from a private address space of some sort). Therefore, these attacks cannot cause payload packets to be delivered to an address other than the one appearing in the destination IP address field of the payload packet. However, attacks of this sort can result in policy violations. The authorized transmitting endpoint(s) of a softwire may be following a policy according to which only certain payload packets get sent through the softwire. If unauthorized nodes are able to encapsulate the payload packets so that they arrive at the receiving endpoint looking as if they arrived from authorized nodes, then the properly authorized policies have been side-stepped. Attacks of the sort we are considering can also be used in denial- of-service attacks on the receiving tunnel endpoints. However, such attacks cannot be prevented by use of cryptographic authentication/integrity techniques, as the need to do cryptography on spoofed packets only makes the denial-of-service problem worse. (The assumption is that the cryptography mechanisms are likely to be more costly than the decapsulation/forwarding mechanisms. So if one tries to eliminate a flooding attack on the decapsulation/forwarding mechanisms by discarding packets that do not pass a cryptographic integrity test, one ends up just trading one kind of attack for another.) This section is largely based on the security considerations section of RFC 4023, which also deals with encapsulations and tunnels. 13.2. Non-Cryptographic Techniques If a tunnel lies entirely within a single administrative domain, then, to a certain extent, there are certain non-cryptographic techniques one can use to prevent spoofed packets from reaching a tunnel's receiving endpoint. For example, when the tunnel encapsulation is IP-based: Wu, et al. Standards Track [Page 24] RFC 5565 Softwire Mesh Framework June 2009 - The receiving endpoints of the tunnels can be given a distinct set of addresses, and those addresses can be made known to the border routers. The border routers can then filter out packets, destined to those addresses, that arrive from outside the domain. - The transmitting endpoints of the tunnels can be given a distinct set of addresses, and those addresses can be made known to the border routers and to the receiving endpoints of the tunnels. The border routers can filter out all packets arriving from outside the domain with source addresses that are in this set, and the receiving endpoints can discard all packets that appear to be part of a softwire, but whose source addresses are not in this set. If an MPLS-based encapsulation is used, the border routers can refuse to accept MPLS packets from outside the domain, or they can refuse to accept such MPLS packets whenever the top label corresponds to the address of a tunnel receiving endpoint. These techniques assume that, within a domain, the network is secure enough to prevent the introduction of spoofed packets from within the domain itself. That may not always be the case. Also, these techniques can be difficult or impossible to use effectively for tunnels that are not in the same administrative domain. A different technique is to have the encapsulation header contain a cleartext password. The 64-bit "cookie" of L2TPv3 [RFC3931] is sometimes used in this way. This can be useful within an administrative domain if it is regarded as infeasible for an attacker to spy on packets that originate in the domain and that do not leave the domain. An attacker would then not be able to discover the password. An attacker could, of course, try to guess the password, but if the password is an arbitrary 64-bit binary sequence, brute force attacks that run through all the possible passwords would be infeasible. This technique may be easier to manage than ingress filtering is, and may be just as effective if the assumptions hold. Like ingress filtering, though, it may not be applicable for tunnels that cross domain boundaries. Therefore, it is necessary to also consider the use of cryptographic techniques for setting up the tunnels and for passing data through them. Wu, et al. Standards Track [Page 25] RFC 5565 Softwire Mesh Framework June 2009 13.3. Cryptographic Techniques If the path between the two endpoints of a tunnel is not adequately secure, then: - If a control protocol is used to set up the tunnels (e.g., to inform one tunnel endpoint of the IP address of the other), the control protocol MUST have an authentication mechanism, and this MUST be used when the tunnel is set up. If the tunnel is set up automatically as the result of, for example, information distributed by BGP, then the use of BGP's MD5-based authentication mechanism [RFC2385] is satisfactory. - Data transmission through the tunnel should be secured with IPsec. In the remainder of this section, we specify the way IPsec may be used, and the implementation requirements we mention are meant to be applicable whenever IPsec is being used. We consider only the case where IPsec is used together with an IP- based tunneling mechanism. Use of IPsec with an MPLS-based tunneling mechanism is for further study. If it is deemed necessary to use tunnels that are protected by IPsec, the tunnel type SHOULD be negotiated by the tunnel endpoints using the procedures specified in [RFC5566]. That document allows the use of IPsec tunnel mode but also allows one to treat the tunnel head and the tunnel tail as the endpoints of a Security Association, and to use IPsec transport mode. In order to use IPsec transport mode, encapsulated packets should be viewed as originating at the tunnel head and as being destined for the tunnel tail. A single IP address of the tunnel head will be used as the source IP address, and a single IP address of the tunnel tail will be used as the destination IP address. This technique can be used to carry MPLS packets through an IPsec Security Association, by first encapsulating the MPLS packets in MPLS-in-IP or MPLS-in-GRE [RFC4023] and then applying IPsec transport mode. When IPsec is used to secure softwires, IPsec MUST provide authentication and integrity. Thus, the implementation MUST support either ESP (IP Encapsulating Security Payload) with null encryption [RFC4303] or else AH (IP Authentication Header) [RFC4302]. ESP with encryption MAY be supported. If ESP is used, the tunnel tail MUST check that the source IP address of any packet received on a given SA (IPsec Security Association) is the one expected, as specified in Section 5.2, step 4, of [RFC4301]. Wu, et al. Standards Track [Page 26] RFC 5565 Softwire Mesh Framework June 2009 Since the softwires are set up dynamically as a byproduct of passing routing information, key distribution MUST be done automatically by means of IKEv2 [RFC4306]. If a PKI (Public Key Infrastructure) is not available, the IPsec Tunnel Authenticator sub-TLV described in [RFC5566] MUST be used and validated before setting up an SA. The selectors associated with the SA are the source and destination addresses of the encapsulation header, along with the IP protocol number representing the encapsulation protocol being used. 14. References 14.1. Normative References [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, October 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, March 2000. [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. [RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed., "Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)", RFC 4023, March 2005. [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute", RFC 5512, April 2009. Wu, et al. Standards Track [Page 27] RFC 5565 Softwire Mesh Framework June 2009 [RFC5566] Berger, L., White, R. and E. Rosen, "BGP IPsec Tunnel Encapsulation Attribute", RFC 5566, June 2009. [V4NLRI-V6NH] Le Faucheur, F. and E. Rosen, "Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop", RFC 5549, May 2009. [V6NLRI-V4NH] De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur, "Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)", RFC 4798, February 2007. 14.2. Informative References [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding Detection", Work in Progress, February 2009. [L3VPN-MCAST] Rosen, E., Ed., and R. Aggarwal, Ed., "Multicast in MPLS/BGP IP VPNs", Work in Progress, March 2009. [L3VPN-MCAST-BGP] Aggarwal, R., Rosen, E., Morin, T. and Y. Rekhter, "BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs", Work in Progress, April 2009. [MLDP] Minei, I., Ed., Kompella, K., Wijnands, IJ., Ed., and B. Thomas, "Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths", Work in Progress, April 2009. [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 Signature Option", RFC 2385, August 1998. [RFC4176] El Mghazli, Y., Ed., Nadeau, T., Boucadair, M., Chan, K., and A. Gonguet, "Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management", RFC 4176, October 2005. [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006. Wu, et al. Standards Track [Page 28] RFC 5565 Softwire Mesh Framework June 2009 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC4301] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005. [RFC4302] Kent, S., "IP Authentication Header", RFC 4302, December 2005. [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005. [RFC4306] Kaufman, C., Ed., "Internet Key Exchange (IKEv2) Protocol", RFC 4306, December 2005. [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private Networks (VPNs)", RFC 4364, February 2006. [RFC4378] Allan, D., Ed., and T. Nadeau, Ed., "A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)", RFC 4378, February 2006. [RFC4459] Savola, P., "MTU and Fragmentation Issues with In- the-Network Tunneling", RFC 4459, April 2006. [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., "LDP Specification", RFC 5036, October 2007. [RFC5496] Wijnands, IJ., Boers, A., and E. Rosen, "The Reverse Path Forwarding (RPF) Vector TLV", RFC 5496, March 2009. [SW-PROB] Li, X., Ed., Dawkins, S., Ed., Ward, D., Ed., and A. Durand, Ed., "Softwire Problem Statement", RFC 4925, July 2007. Wu, et al. Standards Track [Page 29] RFC 5565 Softwire Mesh Framework June 2009 15. Contributors Xing Li Tsinghua University Department of Electronic Engineering, Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5983 EMail: xing@cernet.edu.cn Simon Barber Cisco Systems, Inc. 250 Longwater Avenue Reading, ENGLAND, RG2 6GB United Kingdom EMail: sbarber@cisco.com Pradosh Mohapatra Cisco Systems, Inc. 3700 Cisco Way San Jose, CA 95134 USA EMail: pmohapat@cisco.com John Scudder Juniper Networks 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA EMail: jgs@juniper.net 16. Acknowledgments David Ward, Chris Cassar, Gargi Nalawade, Ruchi Kapoor, Pranav Mehta, Mingwei Xu, and Ke Xu provided useful input into this document. Wu, et al. Standards Track [Page 30] RFC 5565 Softwire Mesh Framework June 2009 Authors' Addresses Jianping Wu Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5983 EMail: jianping@cernet.edu.cn Yong Cui Tsinghua University Department of Computer Science, Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 EMail: yong@csnet1.cs.tsinghua.edu.cn Chris Metz Cisco Systems, Inc. 3700 Cisco Way San Jose, CA 95134 USA EMail: chmetz@cisco.com Eric C. Rosen Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719 USA EMail: erosen@cisco.com

URGENT!! -Your CreditScore Updated: View..ASAP

Your July 7th Credit score Status Notification! View..ASAP

Curious?
-Check Your Free Credit Reports and Scores Today!

__________________
-Optout-link-
..Go-Here..

=freescore360=
[4447_North_Central_Expressway]
[Suite-110-PMB-406,dallas]
[texas_75205]
__________________

-UnsubScribe-link-
..Go-Here..

Video Games r' Me

Swidget 1.0

Friday, July 15, 2011

kife1100.. Our records indicate you . may hold a line of credit!

Tuesday, July 5, 2011

Stars and Starlets

Followers

Blog Archive

About Me