[GTER] Fwd: Gomide
Adriano Cansian
adriano at acmesecurity.org
Thu Oct 18 10:54:24 -03 2018
Prezado Demi e demais,
É com grande pesar que li esta notícia há pouco. Conheci o Gomide na FAPESP
em 1992 quando eu tinha 26 anos, e devo a ele, assim como a você e ao
Vilson Sarto, grande parte do meu conhecimento e de minha iniciação ao
mundo da Internet.
Ele realmente era uma pessoa excepcional, grande mentor e muito dedicada ao
que fazia. Lembro-me que, nesta época, quando a Internet caia, nós
ligávamos diretamente para ele, que prontamente corrigia alguma rota ou
rebootava o velho e bom Cisco IGS+. É fato que, às vezes, a gente achava
que o Gomide não existia, mas sim que era um bot mal humorado que respondia
mensagens automaticamente :-)
O Fred já postou a justa homenagem que foi feita a ela no GTER-22. O link é
uma excelente forma de entender quem ele foi.
Também em homenagem a ele, reproduzo abaixo o infame
"internet-number-template" que ele pedia pra gente preencher quando
precisava de IPs. É longo, mas você verá facilmente o toque Gomidiano :-)
"Classe B, nem pensar!" - Alberto Courrege Gomide
Rest in peace, Gomide!
-Adriano Cansian
[URL
ftp://ftp.ansp.br/pub1/fapesp/formularios/internet-number-template.txt][09/94
]
Este formulario consiste do formulario original, levemente alterado
para as condicoes locais, e acrescido de informacoes necessarias aqui.
Serve para todos: entidades academicas, organizacoes sem fins
lucrativos, entidades governamentais, e entidades com fins lucrativos.
Pode ser obtido por ftp anonimo, maquina mixit.ansp.br (143.108.1.18)
no diretorio ~pub1/fapesp/formularios, ou pelo listserv at fapq.fapesp.br
com o comando "get <fapesp.formularios>internet-number-template.txt
O formulario deve ser devolvido __COM__ os textos ilustrativos;
espera-se que o solicitante tenha lido esses textos e concorde com o
seu conteudo. Claro esta' que este documento nao tem valor legal...
No entanto, espera-se que voce saiba que:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Os enderecos IP nao sao mais o recurso critico; o recurso critico agora
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
e' o espaco gasto nas tabelas de roteamento. Devido a isto, os enderecos
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
IP nao sao mais _propriedade_ do usuario. Em havendo mudancas de rotea-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
mento, o usuario tera' que trocar os seus enderecos IP. Portanto, e'
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
importante saber-se qual sera' o seu provedor de acesso, para alocar
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
o endereco IP dentro do bloco CIDR conveniente para o roteamento.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This form must be completed as part of the application process for
obtaining an Internet Protocol (IP) Network Number. To obtain an
Internet number, please provide the following information on-line, in
electronic format, to registro at fapesp.br.
Depois do formulario em si, segue-se um apendice que tem que ser
preenchido pelo solicitante. Trata-se do dito formato SWIP, exigido
pelo Internic.Net, para registro no servidor whois padrao. Esse
formato e' *necessario*, *mesmo*, e nao serao aceitos formularios com
formato SWIP invalido.
Por favor espere uma resposta dentro de 8 dias uteis. Nao, nao e'
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
muito, nao... :-) Principalmente, NAO FIQUE COBRANDO O NUMERO
^^^^^^^^^^^^^^^^^^^
POR TELEFONE !!!
Se voce nao possui correio eletronico, por favor envie um disquete com
o formulario preenchido para:
Fundacao de Amparo `a Pesquisa - (11)831-3357
a/c Centro de Processamento de Dados - CPD
Rua Pio XI, 1500 - Alto da Lapa
05468-901 - Sao Paulo - SP
Voce pode conseguir o texto deste formulario em disquete, enviando um
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
disquete com retorno pago para o endereco acima.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
O formulario nunca deve ser enviado diretamente `a Fapesp, mas sim ser
encaminhado atraves do seu "sponsor" - veja o item (1).
Once Registration Services receives your completed application we will
send you an acknowledgement, via electronic or postal mail.
NOTE: This application is solely for obtaining a legitimate IP network
number assignment. If you're interested in officially registering a
domain please complete the domain application found in
domain-template.txt.
***********************************************************************
*** NON-CONNECTED NETWORKS ***
If the networks you are requesting address space for will
NEVER TO BE CONNECTED TO THE INTERNET, YOU ARE REQUIRED TO REFER TO
AND ADHERE TO THE GUIDELINES SET FORTH IN RFC 1597, UNDER SECTION 3
"PRIVATE ADDRESS SPACE". This RFC contains important information
regarding the Policies/Procedures that are to be implemented when
IP address space is requested for networks that will NEVER be connected
to the Internet. A large portion of address space (one (1) class A,
sixteen (16) class Bs and two-hundred fifty-six (256) class Cs) has
been reserved for address allocation for non-connected networks. Please
obtain the IP address space you require by utilizing the IP
address range(s) that have been reserved by the IANA for use by all
non-connected networks specified in this RFC. RFC 1597 may be obtained
via anonymous FTP from DS.INTERNIC.NET (198.49.45.10).
************************************************************************
YOUR APPLICATION MUST BE TYPED.
Na verdade, preferimos nao receber pedidos em papel...
Deixe sempre presente o record de versao:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
0. Version : 95092800
1) If the network will be connected to the Internet, you must provide
the name of the governmental sponsoring organization or commercial
service provider, and the name, title, mailing address, phone number,
net mailbox, and NIC Handle (if any) of the contact person (POC) at
that organization who has authorized the network connection. This
person will serve as the POC for administrative and policy questions
about authorization to be a part of the Internet. Examples of such
sponsoring organizations are: DISA DNS, The National Science
Foundation (NSF), or similar government, educational or commercial
network service providers.
NOTE: IF THE NETWORK WILL NEVER BE CONNECTED TO THE INTERNET, PLEASE
UTILIZE THE ADDRESS SPACE RESERVED FOR NON-CONNECTED NETWORKS THAT IS
SPECIFIED IN RFC 1597. IF YOU INTEND TO CONNECT THIS NETWORK TO THE
INTERNET BUT HAVE NOT YET CHOSEN A SERVICE PROVIDER, LEAVE THIS
SECTION BLANK, BUT INDICATE THE APPROXIMATE DATE OF YOUR INTERNET
CONNECTION IN SECTION 9 OF THIS TEMPLATE. IF YOU INTEND TO CONNECT TO
THE INTERNET AND HAVE ALREADY CHOSEN A PROVIDER, YOU ARE REQUIRED TO
SUBMIT THIS REQUEST TO YOUR SERVICE PROVIDER FOR PROCESSING. SERVICE
PROVIDERS ARE ALLOCATED BLOCKS OF ADDRESSES TO SUPPORT THE NETWORKING
NEEDS OF THEIR CUSTOMERS. THIS PROCEDURE WILL ENSURE THAT THE NUMBER
OF ENTRIES ADDED TO THE INTERNET ROUTING TABLES IS KEPT TO A MINIMUM,
AND CIDR IS USED AS EFFICIENTLY AS POSSIBLE. THE ABOVE PROCEDURES
PERTAIN EXCLUSIVELY TO REQUESTS FOR CLASS C ADDRESS(ES).
Notem que o sponsor nao e' a instituicao solicitante, mas sim quem vai
lhe prover acesso `a Internet. Exemplos: RNP, ANSP, outras redes
academicas regionais, Embratel, etc.
Se voce nao pretende conectar-se aa Internet, nao precisa de um
endereco IP... Se voce pretende conectar-se aa Internet em algum tempo
futuro, por favor espere esse futuro chegar, antes de pedir um
endereco IP.
Mesmo sendo conhecido o nichandle, e' necessario preencher
todos os dados da pessoa.
1a. Sponsoring Organization :
1b. Contact name (Lastname, Firstname) :
1c. Contact title : (cargo)
1d. Mail Address : (endereco postal)
1e. Phone :
1f. Net mailbox : (endereco eletronico)
1g. NIC handle (if known) :
2) Provide the name, title, mailing address, phone number, and
organization of the technical Point-of-Contact (POC). The on-line mailbox
and NIC Handle (if any) of the technical POC should also be included. This
is the POC for resolving technical problems associated with the network and
for updating information about the network. The technical POC may also be
responsible for hosts attached to this network.
Mesmo sendo conhecido o nichandle, e' necessario preencher
todos os dados da pessoa.
2a. NIC handle (if known) :
2b. Technical POC name (Lastname, Firstname) :
2c. Technical POC title : (cargo)
2d. Mail address : (endereco postal)
2e. Phone :
2f. Net Mailbox : (endereco eletronico)
3) Supply the SHORT mnemonic name for the network (up to 12 characters).
This is the name that will be used as an identifier in internet name and
address tables. The only special character that may be used in a network
name is a dash (-). PLEASE DO NOT USE PERIODS OR UNDERSCORES. The syntax
XXXX.com and XXXX.net are not valid network naming conventions and should
only be used when applying for a domain.
Na verdade o nome nao podera' ser especificado por voce, pois e'
necessario que nao existam dois networks de entidades diferentes com o
mesmo nome. O Registro atribuira' o nome correto; voce deve preencher
este campo com sua sugestao para o nome, que sera' seguida sempre que
possivel.
3. Network name :
4) Identify the geographic location of the network and the organization
responsible for establishing the network.
Isto significa a organizacao que esta' recebendo o network.
4a. Postal address for main/headquarters network site :
4b. Name of Organization :
6) Estimate the size of the network to include the number of hosts and
subnets/segments that will be supported by the network. A "host" is
defined as any device (PC, printer etc.) that will be assigned an
address from the host portion of the network number. A host may also be
characterized as a node or device.
Host Information
----------------
6a. Initially :
6b. Within one year :
6c. Within two years :
6d. Within five years :
Subnet/Segment Information
--------------------------
6e. Initially :
6f. Within one year :
6g. Within two years :
6h. Within five years :
7) Unless a strong and convincing reason is presented, the network (if
it qualifies at all) will be assigned a single class C network number. If
a class C network number is not acceptable for your purposes, you are
required to submit substantial, detailed justification in support of your
requirements.
********************************************************************
*
THE NIC WOULD STRONGLY SUGGEST YOU CONSIDER SUBNETTING *
CLASS C ADDRESSES WHEN MULTIPLE SEGMENTS WILL BE USED TO SUPPORT *
A MINIMAL AMOUNT OF HOST ADDRESSES. MULTIPLE CLASS C NUMBERS *
SHOULD BE UTILIZED WHEN IT IS NECESSARY TO SUPPORT MORE THAN 256 *
HOSTS ON A SINGLE NETWORK. YOU MAY WISH TO CONFER WITH A NETWORK *
CONSULTANT AND ROUTER VENDOR FOR ADDITIONAL INFORMATION. *
*
********************************************************************
(Note: If there are plans for more than a few local networks, and more
than 100 hosts, you are strongly urged to consider subnetting. [Reference
RFC 950 and RFC 1466])
Nota: ClassB, nem pensar.
Isto significa que voce devera' considerar coisas tais como
"qual o subnetting (mascara) que eu devo utilizar?"
"quantos ethernets diferentes eu tenho que ligar por SLIP ?"
"como eu posso me espremer dentro de um unico ClassC ?"
Neste item devera' ser especificado explicitamente o numero de ClassC
que estao sendo pedidos.
7. Reason :
8) Networks are characterized as being either Research, Educational,
Government - Non Defense, or Commercial, and the network address space
is shared between these four areas. Which type is this network?
Existe tambem o tipo "org", organizacoes nao governamentais sem fins
lucrativos.
8. Type of network :
9) What is the purpose of the network?
9. Purpose :
10) E' necessario saber-se com exatidao quais sao os planos de conexao
`a Internet, para que se possa manter o roteamento optimizado. Qual o
endereco IP e nome da maquina/roteador - DO SEU SPONSOR - que vai
receber sua conexao, e em qual endereco postal, com cidade, cep, etc.
10a. nome da maquina/roteador :
10b. endereco IP da maquina/roteador :
10c. organizacao :
10d. endereco postal :
Se houver mais que um ponto de conexao, especifica-los todos. Se nao
houver ainda um host definitivo, informar o host principal da
organizacao que vai lhe fornecer acesso aa rede Internet, nesse mesmo
local/cidade.
11. Descreva brevemente sua Organizacao/Instituicao e
quais seus objetivos.
Para maiores informacoes contacte:
via e-mail: povo_do_registro at fapesp.br
via telefone: 011-837-0311 ext.247
via correio postal: Rua Pio XI 1500 - Alto da Lapa
a/c Centro de Processamento de Dados
05468-901 - Sao Paulo - SP
RECOMMENDED READING (available via anonymous FTP from
DS.INTERNIC.NET (198.49.45.10)
Gerich, E. Guidelines for Management of IP Address Space, Ann Arbor, MI:
Merit Network, Inc.; May 1993; RFC 1466. 10 p.
(DS.INTERNIC.NET RFC1466.TXT).
Rekhter, Y., Moskowitz. B., Karrenberg, D., de Groot, G.
Address Allocation for Private Internets, IBM Corp., Chrysler Corp.,
RIPE NCC; March 1994; RFC 1597. 8 p. (DS.INTERNIC.NET RFC1597.TXT).
Braden, R.T.; Postel, J.B. Requirements for Internet Gateways. Marina
del Rey, CA: University of Southern California, Information Sciences
Inst.; 1987 June; RFC 1009. 55 p. (DS.INTERNET.NET POLICY RFC1009.TXT).
Internet Engineering Task Force, Braden, R.T. Requirements for Internet
Hosts -- Communication Layers. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; October 1989;
RFC 1122. 116 p. (DS.INTERNIC.NET RFC1122.TXT).
Internet Engineering Task Force, Braden, R.T. Requirements for Internet
Hosts -- Application and Support. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; October 1989;
RFC 1123. 98 p. (DS.INTERNIC.NET RFC1123.TXT).
Internet Activities Board. Internet Official Protocol Standards.
1994 March; RFC 1600. 34p. (DS.INTERNIC.NET POLICY RFC1600.TXT).
[Note: the current version is always available as "STD 1".]
Mogul, J.; Postel, J.B. Internet Standard Subnetting Procedure.
Stanford, CA: Stanford University; 1985 August; RFC 950. 18 p.
(DS.INTERNIC.NET POLICY RFC950.TXT).
Postel, J.B. Internet Control Message Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.; 1981
September; RFC 792. 21 p. (DS.INTERNIC.NET POLICY RFC792.TXT).
Postel, J.B. Transmission Control Protocol. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.; 1981
September; RFC 793. 85 p. (DS.INTERNIC.NET POLICY RFC793.TXT).
Postel, J.B. Address Mappings. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; 1981 September; RFC
796. 7 p. (DS.INTERNIC.NET POLICY RFC796.TXT).
Obsoletes: IEN 115 (NACC 0968-79)
Postel, J.B. User Datagram Protocol. Marina del Rey, CA: University
of Southern California, Information Sciences Inst.; 1980 August 28;
RFC 768. 3 p. (DS.INTERNIC.NET POLICY RFC768.TXT).
Postel, J.B. Internet Protocol. Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; 1981 September; RFC
791. 45 p. (DS.INTERNIC.NET POLICY RFC791.TXT).
Reynolds, J.K.; Postel, J.B. Assigned Numbers. Marina del Rey, CA:
University of Southern California, Information Sciences Inst.;
1992 JUly; RFC 1340. 139p. (DS.INTERNIC.NET POLICY RFC1340.TXT).
[Note: the current version is always available as "STD 2".]
===============================================================================
APENDICE 1
Formato SWIP dos dados
Por favor, leia tambem o arquivo README.swip-template-1.4 que esta'
disponivel tambem em:
URL ftp://ftp.ansp.br/pub1/fapesp/formularios/README.swip-template-1.4
-------- Blank SWIP Template ---------
---------------------< CUT HERE >-------------------------
WDB_version: 1.4
---
(N)new (M)modify (D)delete: conforme o caso
(A)allocate (S)assign: usa-se sempre "S"
---
ntsnum: O numero do network, dado pelo Registro no formato xxx.xxx.xxx.0
ntenum:
Se um unico network, preenche-se apenas o campo "ntsnum". No caso
de um bloco de networks, preenche-se o campo "ntenum" com o ultimo
network do bloco.
ntname: O nome do network, sugerido pelo usuario e fornecido pelo Registro
org: nome da Organizacao que pede o network (nao o provedor!)
street:
city:
state:
zipcode: o CEP da Organizacao que pede o network
cntry: BR
maint: BRAZ
---
hname: nome do host que vai prover in-addr.arpa name service
ipaddr: endereco IP do host
---
hname: nome do host que vai prover in-addr.arpa name service
ipaddr: endereco IP do host
NOTA: Se nao houver ao menos DOIS servidores de in-addr.arpa,
o registro nao sera' aceito
---
Para a Pessoa de Contacto do network, pertencente aa Organizacao
que pede o network, preencher ou somente o "nichandl" ou todos os
outros campos.
nichandl:
lname:
fname:
mname:
org:
street:
city:
state:
zipcode:
cntry:
mbox:
phne:
END OF FILE
---------------------< CUT HERE >-------------------------
===============================================================================
APENDICE 2
Exemplo de um template preenchido
WDB_version: 1.4
---
(N)new (M)modify (D)delete: N
(A)allocate (S)assign: S
---
ntsnum: 200.17.48.0
ntenum:
ntname: RNP-EVENTOS
org: RNP - Rede Nacional de Pesquisa
street: Rua Marques de Paranagua' 111
city: Sao Paulo
state: SP
zipcode: 01303-050
cntry: BR
maint: BRAZ
---
hname: sp.cr-sp.rnp.br.
ipaddr: 200.9.132.43
---
hname: orquidea.cr-sp.rnp.br.
ipaddr: 200.9.132.34
---
nichandl:
lname: da Silva
fname: Cassio
mname: Roque
org: RNP - Rede Nacional de Pesquisa
street: Rua Marques de Paranagua' 111
city: Sao Paulo
state: SP
zipcode: 01303-050
cntry: BR
mbox: cassio at cr-sp.rnp.br
phne: +55-11-256-1622
END OF FILE
===============================================================================
On Thu, Oct 18, 2018 at 10:08 AM Demi Getschko <demi at nic.br> wrote:
> Repasso, realmente muito triste...
>
> demi
>
>
> -------- Forwarded Message --------
> Subject: [CG-CORE] Gomide
> Date: Thu, 18 Oct 2018 08:37:17 -0300
> From: Demi Getschko <demi at cgi.br>
> Reply-To: cg-core at cgi.br
> To: Comite Gestor - Todas e Todos <cg-core at cgi.br>
>
>
>
> Prezad*s
>
> Acabo de receber a notícia de que ontem faleceu Alberto Gomide. Além de
> ter sido FUNDAMENTAL para a Internet brasileira, Gomide foi um dos seres
> humanos mais dignos, corretos e íntegros que conheci... Todos perdemos
> mais um valor, daqueles cada vez mais raros nos dias de hoje...
>
> abraços desalentados.
>
> demi
>
> PS. ... e morreu no dia seguinte ao da morte de Postel, que ocorreu há
> vinte anos atras.
>
> --
> gter list https://eng.registro.br/mailman/listinfo/gter
>
--
Adriano Mauro Cansian, Prof. Dr.
br.linkedin.com/in/adrianocansian/
ACME! CyberSecurity Research Labs
UNESP - São José do Rio Preto, SP - Brazil
+ 55 (17) 3221-2235 / 3221-2475
More information about the gter
mailing list